Home › Cron › Azure Functions
Azure Functions Timer (NCRONTAB) Generator
Azure Functions timer triggers use NCRONTAB: {second} {minute} {hour} {day} {month} {day-of-week}. It looks like cron with an extra field at the front, and it runs in UTC unless you configure a time zone.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
What to know about Azure Functions cron
- The format is
{second} {minute} {hour} {day} {month} {day-of-week}. Five-field expressions are accepted too. - Weekdays are numbered 0-6 with Sunday as 0, and English names (Mon, Monday, Jan) are accepted, case-insensitively. There is no
?and noL. - The default time zone is UTC. Set the
WEBSITE_TIME_ZONEapp setting to use another zone; the schedule then adjusts for daylight saving. It is not supported on Linux Consumption or Flex Consumption plans. - Schedules that fire more than once a minute are not monitored by default (
UseMonitordefaults tofalse), so a missed run is not caught up. - Do not set
RunOnStartupto true in production: the function then runs whenever the app starts or scales out.
Common Azure Functions schedules
Ready-made expressions for the schedules people search for most. Each page explains the expression and shows the first run times.
Frequently asked questions
What is NCRONTAB?
The cron format of the NCrontab library that Azure Functions uses. It is like Unix cron with an extra seconds field at the beginning.
How do I run a function every 5 minutes?
Use 0 */5 * * * *. The leading 0 is the seconds field.
How do I schedule in my local time zone?
Set WEBSITE_TIME_ZONE, for example Eastern Standard Time on Windows or America/New_York on Linux, then write the expression in local time.
Moving a schedule between systems? Use the cron format converter, or read the cron error fixes.