Home โบ Azure Functions โบ Every 15 minutes during business hours on weekdays
Azure Functions cron expression: every 15 minutes during business hours on weekdays
To run a Azure Functions job every 15 minutes during business hours on weekdays, use:
0 */15 9-17 * * 1-5Every 15 minutes, 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
Frequent checks during working hours only, which cuts the number of runs by about two thirds compared with all day, every day.
- Order-desk polling
- Intraday risk or trade reports
- Helpdesk escalation checks
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, 09:15:00 |
| 3 | Fri, 01 Jan 2027, 09:30:00 |
| 4 | Fri, 01 Jan 2027, 09:45:00 |
| 5 | Fri, 01 Jan 2027, 10:00:00 |
| 6 | Fri, 01 Jan 2027, 10:15:00 |
Every 15 minutes during business hours on weekdays in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | 0 */15 9-17 * * 1-5 |
| Quartz | 0 */15 9-17 ? * 2-6 |
| Spring | 0 */15 9-17 * * 1-5 |
| Crontab | */15 9-17 * * 1-5 |
| Kubernetes | */15 9-17 * * 1-5 |
| AWS EventBridge | */15 9-17 ? * 2-6 * |
| Jenkins | H/15 9-17 * * 1-5 |
| GitHub Actions | */15 9-17 * * 1-5 |
| node-cron | */15 9-17 * * 1-5 |
| Apache Airflow | */15 9-17 * * 1-5 |
| Google Cloud Scheduler | */15 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 */15 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
- NCRONTAB has a leading seconds field: 0 */5 * * * * runs every five minutes at second 0, while */5 * * * * * runs every five seconds.
- Weekdays are numbered 0-6 with Sunday as 0, and English names such as Mon or Monday are accepted, case-insensitively.
- 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
The last run is 17:45, not 17:00, because the hour range is 9-17 and the minute step still fires inside hour 17.
Frequently asked questions
How do I run a Azure Functions job every 15 minutes during business hours on weekdays?
Use 0 */15 9-17 * * 1-5. Every 15 minutes, during hours 09, 10, 11, 12, 13, 14, 15, 16, 17, on Mon, Tue, Wed, Thu and Fri.
What is the every 15 minutes during business hours on weekdays cron expression in other systems?
Quartz: 0 */15 9-17 ? * 2-6; Spring: 0 */15 9-17 * * 1-5; Crontab: */15 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.