Home โบ Azure Functions โบ Every Sunday at midnight
Azure Functions cron expression: every Sunday at midnight
To run a Azure Functions job every Sunday at midnight, use:
0 0 0 * * 0At 00:00 UTC, on Sun.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
The traditional weekly maintenance slot, at the very start of Sunday. It sits in the quietest part of the week for most business systems, so heavy clean-up jobs rarely disturb anyone.
- Weekly log rotation
- Weekly vacuum or optimise
- Weekly data exports
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Sun, 03 Jan 2027, 00:00:00 |
| 2 | Sun, 10 Jan 2027, 00:00:00 |
| 3 | Sun, 17 Jan 2027, 00:00:00 |
| 4 | Sun, 24 Jan 2027, 00:00:00 |
| 5 | Sun, 31 Jan 2027, 00:00:00 |
| 6 | Sun, 07 Feb 2027, 00:00:00 |
Every Sunday at midnight in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | 0 0 0 * * 0 |
| Quartz | 0 0 0 ? * 1 |
| Spring | 0 0 0 * * 0 |
| Crontab | 0 0 * * 0 |
| Kubernetes | 0 0 * * 0 |
| AWS EventBridge | 0 0 ? * 1 * |
| Jenkins | H 0 * * 0 |
| GitHub Actions | 0 0 * * 0 |
| node-cron | 0 0 * * 0 |
| Apache Airflow | 0 0 * * 0 |
| Google Cloud Scheduler | 0 0 * * 0 |
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 0 0 * * 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
- Weekdays are numbered 0-6 with Sunday as 0, and English names such as Mon or Monday are accepted, case-insensitively.
- The format is {second} {minute} {hour} {day} {month} {day-of-week}; five fields are accepted too. The default time zone is UTC.
- 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
Sunday as 0 works in Unix cron but not in Quartz, where the range is 1-7. Use 1 or SUN there.
Frequently asked questions
How do I run a Azure Functions job every Sunday at midnight?
Use 0 0 0 * * 0. At 00:00 UTC, on Sun.
What is the every Sunday at midnight cron expression in other systems?
Quartz: 0 0 0 ? * 1; Spring: 0 0 0 * * 0; Crontab: 0 0 * * 0. 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.