A cloud coding workflow highlights version 26, with Linux and server deployments marked compatible.
Azure Functions now lists Node.js 26 as a public preview runtime. It is a Linux-only option for testing, not for production. The change looks minor, but the hosting-plan and OS limits decide whether it applies to your app at all.

A cloud coding workflow highlights version 26, with Linux and server deployments marked compatible. What the preview covers​

Microsoft Learn's Node.js reference says new production apps should use Node.js 24. It adds that Node.js 26 is available in preview only on Linux and isn't supported on Windows.

The runtime-version table matches this. Node.js 26 is "Preview (Linux only)" with no end-of-support date listed. Node.js 24 is GA until April 30, 2028, and Node.js 22 is GA until April 30, 2027.

"Preview" has a specific meaning in Azure Functions. GA is fully supported and approved for production use. Preview is not yet supported, but is expected to reach GA in the future. Treat this release as a compatibility check, not a migration target.

The Azure Updates page itself was not readable during research. Everything here comes from Microsoft's documentation and related project pages.

Who can use it​

Your setupNode.js 26 preview?What to do
Linux, Flex ConsumptionYesTest in a non-production app
Linux, Premium or DedicatedYesTest in a non-production app
Linux ConsumptionNoNode.js 22 is the last version on this plan. Migrate to Flex Consumption first.
Windows (any plan)NoUse Node.js 24 or 22.

Linux Consumption is a plan with a limited future. Microsoft's docs say newer Node.js versions aren't being added to it. The same docs say Linux Consumption hosting is scheduled to retire on September 30, 2028. That date is context, not part of this announcement.

How to test it safely​

This is my synthesis of Microsoft's documented steps. Microsoft has not published it as a formal checklist.

  1. Run your functions locally on Node.js 26 first. Microsoft's portal steps say to verify locally before changing the version.
  2. Check that the app runs the latest Functions runtime. Microsoft says to do this before upgrading your Node.js version.
  3. Use a non-production Linux app. The portal path is Settings > Configuration. Open the Function runtime settings tab to check the runtime. Then open General settings and, for Linux apps only, select Node.js 26 to test the preview.
  4. Expect a restart. Saving the change restarts the app. Plan for that before you touch anything live.
  5. Confirm what actually loaded. Log process.version from any function. The Learn page's summary says this shows the version the runtime is using.

I found no verified Node.js 26-specific CLI command for Functions. The documented linuxFxVersion example is for Node.js 24, so don't swap in a 26 value without checking official guidance. For the same reason, don't use WEBSITE_NODE_DEFAULT_VERSION. That is the Windows mechanism, and Windows doesn't support Node.js 26.

Model and tooling notes​

  • Node.js programming model v3 and v4 both list Node.js 26 as preview on Linux.
  • You can't mix v3 and v4 functions in one app.
  • If @azure/functions is absent from package.json, the default is v3.
  • Microsoft recommends v4 for new projects.
  • TypeScript works by transpiling to JavaScript. No separate TypeScript preview is described.

Nothing I found says Node.js 26 requires moving from v3 to v4. The preview is only about the runtime choice.

What to expect next​

The Node.js 26 LTS release has apparently already happened. A maintainer on the Azure Functions Node.js library issue tracker said the plan was LTS on October 28, then a Functions LTS release about a month later for Flex Consumption and Dedicated/Premium Linux. A GitHub issue about the base image adds that Windows would follow. Those are maintainer statements, not a committed schedule.

Azure App Service for Linux already shows how this can go. App Service says Node.js 26 has moved into Long Term Support, making it a production upgrade target on App Service for Linux. That is a different product from Azure Functions. Functions docs still call Node.js 26 preview, and no GA date or end-of-support date has been published.

Practical takeaways​

  • Test Node.js 26 in staging if you run Linux on Flex Consumption, Premium or Dedicated.
  • Stay on Node.js 24 for new production apps. Node.js 22 remains supported until April 2027.
  • Windows apps have nothing to do yet.
  • Linux Consumption apps can't try Node.js 26 until they move to Flex Consumption. That move is also a reasonable step ahead of the 2028 retirement.

For a minor runtime update, the main action is to check your hosting plan and OS before you plan any work.

 

References

  1. (In preview) Public Preview: Azure Functions support for Node.js 26 Azure Updates 2026-11-17T20:00:32Z
  2. Support Node.js 26 · Issue #443 · Azure/azure-functions-nodejs-library · GitHub github.com
  3. Publish and document the GA Azure Functions Node.js 26 base image · Issue #1261 · Azure/azure-functions-docker · GitHub github.com