Home โบ Azure Functions โบ Hourly during business hours on weekdays
Azure Functions cron expression: hourly during business hours on weekdays
To run a Azure Functions job hourly during business hours on weekdays, use:
0 0 9-17 * * 1-5At minute 0, during hours 09, 10, 11, 12, 13, 14, 15, 16, 17, on Mon, Tue, Wed, Thu and Fri.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Hourly, but only from 9 to 17 on weekdays, so nothing runs overnight or at weekends.
- Hourly stock or price snapshots
- Support SLA checks
- Syncing with a partner that only works in office hours
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 09:00:00 |
| 2 | Fri, 01 Jan 2027, 10:00:00 |
| 3 | Fri, 01 Jan 2027, 11:00:00 |
| 4 | Fri, 01 Jan 2027, 12:00:00 |
| 5 | Fri, 01 Jan 2027, 13:00:00 |
| 6 | Fri, 01 Jan 2027, 14:00:00 |
Hourly during business hours on weekdays in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | 0 0 9-17 * * 1-5 |
| Quartz | 0 0 9-17 ? * 2-6 |
| Spring | 0 0 9-17 * * 1-5 |
| Crontab | 0 9-17 * * 1-5 |
| Kubernetes | 0 9-17 * * 1-5 |
| AWS EventBridge | 0 9-17 ? * 2-6 * |
| Jenkins | H 9-17 * * 1-5 |
| GitHub Actions | 0 9-17 * * 1-5 |
| node-cron | 0 9-17 * * 1-5 |
| Apache Airflow | 0 9-17 * * 1-5 |
| Google Cloud Scheduler | 0 9-17 * * 1-5 |
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 9-17 * * 1-5")] 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
9-17 includes hour 17, so the last run is at 17:00, not 16:00. The range is inclusive.
Frequently asked questions
How do I run a Azure Functions job hourly during business hours on weekdays?
Use 0 0 9-17 * * 1-5. At minute 0, during hours 09, 10, 11, 12, 13, 14, 15, 16, 17, on Mon, Tue, Wed, Thu and Fri.
What is the hourly during business hours on weekdays cron expression in other systems?
Quartz: 0 0 9-17 ? * 2-6; Spring: 0 0 9-17 * * 1-5; Crontab: 0 9-17 * * 1-5. 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.