SaaS
Microsoft Azure
Microsoft is ending support for the Node.js 22 LTS runtime on Azure App Service on 30 April 2027; apps keep running but stop receiving security updates and customer support, and Microsoft directs developers to upgrade to Node 24 LTS
departs 30 Apr 2027
Quick answers
- Is it true that Azure App Service ends support for Node 22 LTS on 30 April 2027?
- Yes. Microsoft Azure has officially announced it, effective 30 Apr 2027. This is the Azure App Service runtime end-of-support, not the end of Node.js 22 itself.
- When does it take effect?
- 30 Apr 2027. Verified against the vendor's own announcement.
- What should I use instead?
- Microsoft's required action is to upgrade affected App Service apps to Node 24 LTS before 30 April 2027 (its upgrade steps are at aka.ms/nodeversion, and the runtime support policy at learn.microsoft.com/azure/app-service/language-support-policy).
What this means for you
This is the Azure App Service runtime end-of-support, not the end of Node.js 22 itself. If you host a Node app on Azure App Service pinned to the Node 22 LTS runtime stack, Microsoft says that on 30 April 2027 support for Node 22 LTS ends: your apps "will continue to run, but security updates will no longer be available, and we'll no longer provide customer service for Node 22 LTS." In practice that means a running app is not switched off, but the platform stops patching the Node 22 runtime underneath it, so you accumulate unpatched runtime CVEs and lose Microsoft support for any Node-22-specific issue. This tracks the upstream Node.js release calendar — Node 22 is the current "Jod" LTS line and its own community end-of-life is scheduled for April 2027 — so App Service is retiring the stack in step with upstream rather than early.
Where to go
Microsoft's required action is to upgrade affected App Service apps to Node 24 LTS before 30 April 2027 (its upgrade steps are at aka.ms/nodeversion, and the runtime support policy at learn.microsoft.com/azure/app-service/language-support-policy). Practically: find every App Service app whose runtime stack is set to Node 22 (in the Azure Portal under Configuration → General settings → Stack settings, or the linuxFxVersion / WEBSITE_NODE_DEFAULT_VERSION setting in your infrastructure-as-code), test your app against Node 24 in a staging slot, update the app's engines/CI to Node 24, and roll it out via a deployment slot swap so you can fall back if something breaks. Node 24 became the active LTS line in October 2025, so libraries and build tooling largely support it already; watch for native-addon rebuilds and any dependency that has not yet published Node 24-compatible binaries. There is a long runway here — the point of logging it now is so the upgrade lands as routine maintenance rather than a scramble in April 2027.
- Node 24 LTS on Azure App Service — Microsoft's named upgrade target (aka.ms/nodeversion)
- Containerize the app and deploy your own pinned Node image to App Service or Azure Container Apps if you need a specific runtime version
Microsoft is retiring the Node.js 22 LTS runtime on Azure App Service on 30 April 2027. In an official Azure Updates notice, Microsoft writes that after that date “support for Node 22 LTS will end. Your apps that are hosted on App Service will continue to run, but security updates will no longer be available, and we’ll no longer provide customer service for Node 22 LTS.”
The distinction that matters: this is the App Service runtime stack reaching end of support, not your app being shut off. An app pinned to the Node 22 stack keeps serving traffic after 30 April 2027, but the platform stops patching the Node runtime beneath it — so you inherit any Node 22 security vulnerability disclosed after that date, and Microsoft support will no longer help with Node-22-specific problems. For a public-facing service, running indefinitely on an unpatched runtime is the risk, not an immediate outage.
App Service is retiring the stack in step with upstream Node.js, not ahead of it. Node 22 (“Jod”) is the current active LTS line, and its own community end-of-life is scheduled for April 2027; Microsoft is aligning the platform to that calendar.
The migration is a runtime version bump. Microsoft’s required action is to move affected apps to Node 24 LTS before the cutoff. Find every App Service app whose stack is set to Node 22 (Portal → Configuration → General settings → Stack settings, or the linuxFxVersion / WEBSITE_NODE_DEFAULT_VERSION value in your infrastructure-as-code), test against Node 24 in a staging slot, bump your engines and CI, and roll out with a deployment slot swap so you can fall back if anything regresses. Node 24 has been the active LTS line since October 2025, so most libraries and build tooling already support it — the usual snags are native addons that need rebuilding and any dependency without Node 24-compatible binaries yet.
There is a long runway. The value of logging it now is that the upgrade lands as scheduled maintenance rather than an April-2027 scramble.
Entry changelog
- — last reviewed.
- — Entry created from the official Microsoft Azure Updates retirement notice (id 567334), verified against the Microsoft release-communications API (microsoft.com/releasecommunications/api/v2/azure/567334), which returns product "App Service", tag "Retirements", and the text "On April 30 2027, support for Node 22 LTS will end." The Azure Updates page itself is JS-rendered so the API is the machine-readable primary source. Date 30 April 2027 quoted, not inferred; migration target (Node 24 LTS) taken directly from the notice's required-action link. Surfaced via the azure-updates Layer-1 source. No detect: fingerprint — the retirement is specific to the App Service runtime stack, and a package.json Node 22 engine would false-positive on every Node 22 repo regardless of where it is hosted.
Put this countdown in your README
Building on Microsoft Azure? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/azure-app-service-node-22-lts-eol)Spot an error or a changed date? Tell us and it’s corrected the same night.