BackendBench
Coffee

Home › Convert › Azure Functions to Quartz

Azure Functions → Quartz

Convert Azure Functions cron to Quartz

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

Result

    What changes from Azure Functions to Quartz

    Worked examples

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

    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.

    Quartz

    second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (1-7, 1 = Sunday), year (1970-2199, optional).

    Quartz uses the JVM default time zone unless you set one: CronScheduleBuilder.cronSchedule(expr).inTimeZone(TimeZone.getTimeZone("UTC")).

    Go the other way

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

    Frequently asked questions

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

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

    Is every Azure Functions expression convertible to Quartz?

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

    Does Quartz 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