Home โบ Azure Functions โบ Every minute
Azure Functions cron expression: every minute
To run a Azure Functions job every minute, use:
0 * * * * *Every minute.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
The fastest schedule most cron systems allow. It suits near-real-time polling where waiting five minutes is too slow.
- Polling a queue or an inbox for new work
- Heartbeat pings to an uptime monitor
- Flushing a small in-memory buffer to disk
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 00:00:00 |
| 2 | Fri, 01 Jan 2027, 00:01:00 |
| 3 | Fri, 01 Jan 2027, 00:02:00 |
| 4 | Fri, 01 Jan 2027, 00:03:00 |
| 5 | Fri, 01 Jan 2027, 00:04:00 |
| 6 | Fri, 01 Jan 2027, 00:05:00 |
Every minute in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | 0 * * * * * |
| Quartz | 0 * * * * ? |
| Spring | 0 * * * * * |
| Crontab | * * * * * |
| Kubernetes | * * * * * |
| AWS EventBridge | * * * * ? * |
| Jenkins | * * * * * |
| node-cron | * * * * * |
| Apache Airflow | * * * * * |
| Google Cloud Scheduler | * * * * * |
Need to translate a different expression? Use the cron converter.
Ready-to-use Azure Functions config
Drop this into your project. The expression is the one above.
[Function("MyTimer")]
public void Run([TimerTrigger("0 * * * * *")] TimerInfo timer)
{
// ...
}WEBSITE_TIME_ZONE=Eastern Standard Time # Windows name; Linux uses America/New_York
# Without it, NCRONTAB runs in UTC.The Azure Functions fields, in order: second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).
Things to watch out for in Azure Functions
- NCRONTAB has a leading seconds field: 0 */5 * * * * runs every five minutes at second 0, while */5 * * * * * runs every five seconds.
- Azure Functions evaluates NCRONTAB in UTC unless the WEBSITE_TIME_ZONE app setting is set; with it, the schedule adjusts for daylight saving. The setting is not supported on Linux Consumption or Flex Consumption plans.
The common mistake with this schedule
A job that takes longer than one minute will overlap with the next run. Guard against it with a lock, Quartz @DisallowConcurrentExecution, or concurrencyPolicy: Forbid in Kubernetes.
Frequently asked questions
How do I run a Azure Functions job every minute?
Use 0 * * * * *. Every minute.
What is the every minute cron expression in other systems?
Quartz: 0 * * * * ?; Spring: 0 * * * * *; Crontab: * * * * *. The table on this page lists every dialect.
Which time zone does Azure Functions use for this schedule?
Azure Functions evaluates NCRONTAB in UTC unless the WEBSITE_TIME_ZONE app setting is set; with it, the schedule adjusts for daylight saving. The setting is not supported on Linux Consumption or Flex Consumption plans.