Home › Convert › node-cron to Azure Functions
Convert node-cron cron to Azure Functions
node-cron expressions look similar to Azure Functions, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from node-cron to Azure Functions
- Azure Functions has no
L,Wor#symbols. Schedules like "last day of the month" cannot be converted and are refused rather than silently changed.
Worked examples
| Schedule | node-cron | Azure Functions |
|---|---|---|
| every minute | * * * * * | 0 * * * * * |
| every 5 minutes | */5 * * * * | 0 */5 * * * * |
| every 10 minutes | */10 * * * * | 0 */10 * * * * |
| every 15 minutes | */15 * * * * | 0 */15 * * * * |
| every 30 minutes | */30 * * * * | 0 */30 * * * * |
| every hour | 0 * * * * | 0 0 * * * * |
| every 2 hours | 0 */2 * * * | 0 0 */2 * * * |
| every 3 hours | 0 */3 * * * | 0 0 */3 * * * |
What cannot be converted
These common node-cron schedules have no equivalent in Azure Functions. The converter refuses them instead of guessing.
- on the last day of every month:
0 0 L * *. This schedule cannot be expressed in Azure Functions NCRONTAB: "L" is not a valid dom value. - on the last Friday of every month at noon:
0 12 * * 5L. This schedule cannot be expressed in Azure Functions NCRONTAB: "5L" is not a valid dow value.
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-7, 0 and 7 = Sunday).
node-cron uses the server time zone unless you pass { timezone: "Asia/Kolkata" }. Its documentation advises timezone: "UTC" for jobs that must not skip or repeat when clocks change.
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.
Go the other way
Convert Azure Functions to node-cron, or open the node-cron builder or the Azure Functions builder.
Frequently asked questions
How do I convert a node-cron cron expression to Azure Functions?
Paste it into the converter above with node-cron as the source and Azure Functions as the target. For example, * * * * * becomes 0 * * * * *.
Is every node-cron expression convertible to Azure Functions?
No. Out of 32 common schedules, 2 cannot be expressed in Azure Functions: on the last day of every month; on the last Friday of every month at noon.
Does Azure Functions run in the same time zone as node-cron?
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.