Home โบ Azure Functions โบ On the last day of every month
Azure Functions cron expression: on the last day of every month
To run a Azure Functions job on the last day of every month, use:
0 0 0 28-31 * *At 00:00 UTC, on the 28th, 29th, 30th and 31st of the month.
0 0 0 28-31 * * [ "$(date -d tomorrow +\%d)" = "01" ] && /path/to/jobYour week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Month-end closing jobs. Months have different lengths, so you cannot write a single fixed day.
- Month-end financial close
- Final monthly invoice run
- Monthly data snapshots
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Thu, 28 Jan 2027, 00:00:00 |
| 2 | Fri, 29 Jan 2027, 00:00:00 |
| 3 | Sat, 30 Jan 2027, 00:00:00 |
| 4 | Sun, 31 Jan 2027, 00:00:00 |
| 5 | Sun, 28 Feb 2027, 00:00:00 |
| 6 | Sun, 28 Mar 2027, 00:00:00 |
On the last day of every month in every dialect
| System | Expression |
|---|---|
| Azure Functions (this page) | 0 0 0 28-31 * * |
| Quartz | 0 0 0 L * ? |
| Spring | 0 0 0 L * * |
| Crontab | 0 0 28-31 * * |
| Kubernetes | 0 0 28-31 * * |
| AWS EventBridge | 0 0 L * ? * |
| Jenkins | H 0 28-31 * * |
| GitHub Actions | 0 0 28-31 * * |
| node-cron | 0 0 L * * |
| Apache Airflow | 0 0 L * * |
| Google Cloud Scheduler | 0 0 28-31 * * |
Need to translate a different expression? Use the cron converter.
Ready-to-use Azure Functions config
Drop this into your project. The expression is the one above.
[Function("MyTimer")]
public void Run([TimerTrigger("0 0 0 28-31 * *")] TimerInfo timer)
{
// ...
}WEBSITE_TIME_ZONE=Eastern Standard Time # Windows name; Linux uses America/New_York
# Without it, NCRONTAB runs in UTC.The Azure Functions fields, in order: second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).
Things to watch out for in Azure Functions
- NCRONTAB has no ? and no L. Test how your version combines day-of-month with day-of-week before relying on both.
- NCRONTAB has no L, W or # symbols. Run on a broader schedule and check the date inside the function.
- 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.
The common mistake with this schedule
Unix cron has no "last day" symbol. The common 28-31 workaround fires up to four times a month, so the job must check that tomorrow is the 1st.
Frequently asked questions
How do I run a Azure Functions job on the last day of every month?
Use 0 0 0 28-31 * *. At 00:00 UTC, on the 28th, 29th, 30th and 31st of the month. This dialect has no native rule for it, so the job must also check the date (see the guard command above).
What is the on the last day of every month cron expression in other systems?
Quartz: 0 0 0 L * ?; Spring: 0 0 0 L * *; Crontab: 0 0 28-31 * *. The table on this page lists every dialect.
Which time zone does Azure Functions use for this schedule?
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.