BackendBench
Coffee

Home › Convert › Azure Functions to Crontab

Azure Functions → Crontab

Convert Azure Functions cron to Crontab

Azure Functions expressions look similar to Crontab, but the differences matter. Paste yours below; the result is checked against the original run times.

Result

    What changes from Azure Functions to Crontab

    Worked examples

    ScheduleAzure FunctionsCrontab
    every minute0 * * * * ** * * * *
    every 5 minutes0 */5 * * * **/5 * * * *
    every 10 minutes0 */10 * * * **/10 * * * *
    every 15 minutes0 */15 * * * **/15 * * * *
    every 30 minutes0 */30 * * * **/30 * * * *
    every hour0 0 * * * *0 * * * *
    every 2 hours0 0 */2 * * *0 */2 * * *
    every 3 hours0 0 */3 * * *0 */3 * * *

    Conversions that come with a warning

    Field layout and time zones

    Azure Functions

    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.

    Crontab

    minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

    Cron runs in the server's local time zone. Check it with the date command, or put CRON_TZ=Asia/Kolkata above the line on cronie-based systems.

    Go the other way

    Convert Crontab to Azure Functions, or open the Azure Functions builder or the Crontab builder.

    Frequently asked questions

    How do I convert a Azure Functions cron expression to Crontab?

    Paste it into the converter above with Azure Functions as the source and Crontab as the target. For example, 0 * * * * * becomes * * * * *.

    Is every Azure Functions expression convertible to Crontab?

    Yes for the common schedules we tested (29 of 29), though unusual expressions with special characters might need manual review.

    Does Crontab 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.

    More tools you might need