Home › Convert › Azure Functions to Apache Airflow
Convert Azure Functions cron to Apache Airflow
Azure Functions expressions look similar to Apache Airflow, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Azure Functions to Apache Airflow
- Apache Airflow has no seconds field, so a schedule that fires on specific seconds cannot be converted exactly. The seconds value is dropped and flagged.
- Azure Functions requires both day fields to match; Apache Airflow fires when either does. Schedules that restrict both are flagged.
Worked examples
| Schedule | Azure Functions | Apache Airflow |
|---|---|---|
| every minute | 0 * * * * * | * * * * * |
| every 5 minutes | 0 */5 * * * * | */5 * * * * |
| every 10 minutes | 0 */10 * * * * | */10 * * * * |
| every 15 minutes | 0 */15 * * * * | */15 * * * * |
| every 30 minutes | 0 */30 * * * * | */30 * * * * |
| every hour | 0 0 * * * * | 0 * * * * |
| every 2 hours | 0 0 */2 * * * | 0 */2 * * * |
| every 3 hours | 0 0 */3 * * * | 0 */3 * * * |
Conversions that come with a warning
- every 10 seconds:
*/10 * * * * *→* * * * *. Apache Airflow (croniter) has no seconds field; the seconds value "*/10" was dropped. - every 30 seconds:
*/30 * * * * *→* * * * *. Apache Airflow (croniter) has no seconds field; the seconds value "*/30" was dropped.
Field layout and time zones
second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).
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.
minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.
Go the other way
Convert Apache Airflow to Azure Functions, or open the Azure Functions builder or the Apache Airflow builder.
Frequently asked questions
How do I convert a Azure Functions cron expression to Apache Airflow?
Paste it into the converter above with Azure Functions as the source and Apache Airflow as the target. For example, 0 * * * * * becomes * * * * *.
Is every Azure Functions expression convertible to Apache Airflow?
Yes for the common schedules we tested (29 of 29), though unusual expressions with special characters might need manual review.
Does Apache Airflow run in the same time zone as Azure Functions?
Not necessarily. Conversion changes the syntax, not the time zone. Check where each system evaluates the schedule before you rely on the same clock times.