Home โบ Azure Functions โบ Every weekday at 8:30 AM
Azure Functions cron expression: every weekday at 8:30 AM
To run a Azure Functions job every weekday at 8:30 AM, use:
0 30 8 * * 1-5At 08:30 UTC, 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
A half-hour offset before the working day starts, so output is waiting by 9.
- Pre-market data loads
- Pre-opening health checks
- Morning briefing emails
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 08:30:00 |
| 2 | Mon, 04 Jan 2027, 08:30:00 |
| 3 | Tue, 05 Jan 2027, 08:30:00 |
| 4 | Wed, 06 Jan 2027, 08:30:00 |
| 5 | Thu, 07 Jan 2027, 08:30:00 |
| 6 | Fri, 08 Jan 2027, 08:30:00 |
Every weekday at 8:30 AM in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | 0 30 8 * * 1-5 |
| Quartz | 0 30 8 ? * 2-6 |
| Spring | 0 30 8 * * 1-5 |
| Crontab | 30 8 * * 1-5 |
| Kubernetes | 30 8 * * 1-5 |
| AWS EventBridge | 30 8 ? * 2-6 * |
| Jenkins | 30 8 * * 1-5 |
| GitHub Actions | 30 8 * * 1-5 |
| node-cron | 30 8 * * 1-5 |
| Apache Airflow | 30 8 * * 1-5 |
| Google Cloud Scheduler | 30 8 * * 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 30 8 * * 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
The minute comes first, then the hour. 30 8 means 08:30, while 8 30 would be an invalid hour.
Frequently asked questions
How do I run a Azure Functions job every weekday at 8:30 AM?
Use 0 30 8 * * 1-5. At 08:30 UTC, on Mon, Tue, Wed, Thu and Fri.
What is the every weekday at 8:30 AM cron expression in other systems?
Quartz: 0 30 8 ? * 2-6; Spring: 0 30 8 * * 1-5; Crontab: 30 8 * * 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.