Home › Convert › Azure Functions to GitHub Actions
Convert Azure Functions cron to GitHub Actions
Azure Functions expressions look similar to GitHub Actions, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Azure Functions to GitHub Actions
- GitHub Actions 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; GitHub Actions fires when either does. Schedules that restrict both are flagged.
Worked examples
| Schedule | Azure Functions | GitHub Actions |
|---|---|---|
| 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 * * * * *→* * * * *. GitHub Actions has no seconds field; the seconds value "*/10" was dropped. - every 30 seconds:
*/30 * * * * *→* * * * *. GitHub Actions 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-6, 0 = Sunday).
GitHub Actions schedules are always UTC. Convert your local time to UTC before writing the expression.
Go the other way
Convert GitHub Actions to Azure Functions, or open the Azure Functions builder or the GitHub Actions builder.
Frequently asked questions
How do I convert a Azure Functions cron expression to GitHub Actions?
Paste it into the converter above with Azure Functions as the source and GitHub Actions as the target. For example, 0 * * * * * becomes * * * * *.
Is every Azure Functions expression convertible to GitHub Actions?
Yes for the common schedules we tested (29 of 29), though unusual expressions with special characters might need manual review.
Does GitHub Actions 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.