timetobail
My stack

Azure Functions · Forced move · Tracked since October 17, 2026 · Sources checked Oct 17

Time to bail on Azure Functions apps on Node.js 22?

Time to Bail · Boarding pass

FromAzure Functions apps on Node.js 22
ToYour pick

Act. You can stay.

Node.js 22 on Azure Functions loses support April 30, 2027. Move to Node.js 24.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
End of support
Time left
194days
Status
Act

Azure Functions Node.js 22 support ends April 30, 2027

Azure Functions support for Node.js 22 ends on April 30, 2027. Apps keep running, but get no security patches. Node.js 24 is supported until April 30, 2028.

Email me 7 days before Apr 30

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

How it is winding down

  1. Apr 30, 2027End of supportNext
  2. Sep 30Linux Consumption retires

What to do before April 30

Tick steps as you go. Your progress stays in this browser.

  1. Find apps on Node.js 22

    Check WEBSITE_NODE_DEFAULT_VERSION on Windows and linuxFxVersion on Linux.

  2. Test on Node.js 24

    Run your functions locally or in a staging slot on Node.js 24.

  3. Switch the version

    Set Node.js 24. On Linux Consumption, move to Flex Consumption first.

Email me 7 days before Apr 30

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
End of supportApril 30, 2027[1]
VersionNode.js 22 on Azure Functions[1]
After that dateApps still run and can be deployed, but get no security patches, new features or performance fixes[2]
Possible limitMicrosoft may limit these apps, including scaling to 1 instance[2]
Move toNode.js 24, supported until April 30, 2028[1]
Linux Consumption planNode.js 22 is the last version there; newer versions need Flex Consumption[1]
Linux Consumption retiresSeptember 30, 2028[1]
Windows appsThe version is the WEBSITE_NODE_DEFAULT_VERSION app setting, for example ~24[3]
Apps on Node.js 22Get no security patches after April 30, 2027[1]

Sources

Check it yourself. Every fact above links here.

  1. Supported languages in Azure Functions Microsoft · primary · checked Oct 17
  2. Azure Functions language stack support policy Microsoft · primary · checked Oct 17
  3. Update language stack versions in Azure Functions Microsoft · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on Azure Functions apps on Node.js 22? Act. You can stay. Node.js 22 on Azure Functions loses support April 30, 2027. Move to Node.js 24.

On our scale this is Act: change a setting or plan before the date. You can stay.

Azure Functions support for Node.js 22 ends on April 30, 2027. Apps keep running, but get no security patches. Node.js 24 is supported until April 30, 2028.

Here are the facts we checked:

  • End of support: April 30, 2027 (Microsoft)
  • Version: Node.js 22 on Azure Functions (Microsoft)
  • After that date: Apps still run and can be deployed, but get no security patches, new features or performance fixes (Microsoft)
  • Possible limit: Microsoft may limit these apps, including scaling to 1 instance (Microsoft)
  • Move to: Node.js 24, supported until April 30, 2028 (Microsoft)
  • Linux Consumption plan: Node.js 22 is the last version there; newer versions need Flex Consumption (Microsoft)
  • Linux Consumption retires: September 30, 2028 (Microsoft)
  • Windows apps: The version is the WEBSITE_NODE_DEFAULT_VERSION app setting, for example ~24 (Microsoft)
  • Apps on Node.js 22: Get no security patches after April 30, 2027 (Microsoft)

You can stay on Azure Functions. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Microsoft is the main source for this page. Azure Functions has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Apps on Node.js 22: Get no security patches after April 30, 2027.

The date to remember is April 30, 2027. Make the change before then.

What to do before April 30

  1. Find apps on Node.js 22. Check WEBSITE_NODE_DEFAULT_VERSION on Windows and linuxFxVersion on Linux.
  2. Test on Node.js 24. Run your functions locally or in a staging slot on Node.js 24.
  3. Switch the version. Set Node.js 24. On Linux Consumption, move to Flex Consumption first.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Azure Functions apps on Node.js 22 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product