Home › Convert › Azure Functions to node-cron
Convert Azure Functions cron to node-cron
Azure Functions expressions look similar to node-cron, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Azure Functions to node-cron
- Azure Functions and node-cron use the same five-field layout and weekday numbering, so most expressions convert unchanged.
Worked examples
| Schedule | Azure Functions | node-cron |
|---|---|---|
| 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 * * * |
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.
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.
Go the other way
Convert node-cron to Azure Functions, or open the Azure Functions builder or the node-cron builder.
Frequently asked questions
How do I convert a Azure Functions cron expression to node-cron?
Paste it into the converter above with Azure Functions as the source and node-cron as the target. For example, 0 * * * * * becomes * * * * *.
Is every Azure Functions expression convertible to node-cron?
Yes for the common schedules we tested (29 of 29), though unusual expressions with special characters might need manual review.
Does node-cron 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.