Microsoft announced on November 17, 2026 that native Go support for Azure Functions on the Flex Consumption plan is generally available. The same Ignite 2026 update batch put Python 3.15 and Node.js 26 support into public preview.
Go developers no longer need the custom handler workaround to run serverless code on Azure. A separate preview also lets Flex Consumption apps ship their own Linux worker image with system packages, which removes a long-standing limit of the plan.
Native Go Worker Reaches GA
Until now, Go functions on Azure ran through a custom handler: your code had to run its own HTTP server, and you wrote function.json files by hand. The new Go worker plugs straight into the Functions host, which manages triggers and scaling.
The programming model is code-first. A Go project builds a function app in its main function, registers each function with a fluent builder that uses functional options, and starts the worker. HTTP functions use standard net/http handlers, while event triggers receive typed payloads.
Features listed in the GA release include:
- Azure Functions triggers such as HTTP, timer, Cosmos DB, Queue Storage, Service Bus and Azure SQL.
- Typed batch processing and injection of Blob Storage SDK clients.
- HTTP streaming responses.
- Durable Functions orchestrations and activities.
- Structured logging, plus configurable OpenTelemetry export next to Application Insights host telemetry.
The developer reference lists Go 1.24 or later, Azure Functions Core Tools 4.12 or later and Azure CLI 2.87.0 or later for deployment. Core Tools handles local runs, packaging and publishing, and the worker code, releases and samples live in the Azure/azure-functions-golang-worker repository on GitHub.
Python 3.15 Preview With a Rust-Based Transport
Python 3.15 support works with both the v1 and v2 Python programming models. The bigger change sits under the hood: a new transport written in Rust now handles messaging with the Functions host and embeds CPython.
Microsoft says the old worker relied on the grpcio and protobuf packages, which could clash with the versions an app needed. The new transport drops that dependency, cutting conflicts and improving performance. Apps can still use grpcio and protobuf themselves, and developers keep writing plain Python.
The planned scope is Linux x64 on the Flex Consumption, Elastic Premium and Dedicated plans, where each plan is offered.
Node.js 26 Preview
JavaScript and TypeScript function apps can now be tested on Node.js 26 with the usual Azure Functions programming model. The preview covers Linux on the Flex Consumption, Elastic Premium and Dedicated plans.
Linux Consumption is not supported, and Windows hosting plans will get Node.js 26 later. Teams on the older Linux Consumption plan will need to move to Flex Consumption to use the new runtime.
Custom Worker Images for Flex Consumption
Flex Consumption apps used to run only in a worker environment managed by Microsoft that could not be extended. Apps that needed native binaries, system libraries, fonts or drivers had to be redesigned or moved to another hosting option.
The new preview lets you build a Linux worker image that holds your code, a supported language worker and any OS-level software. Microsoft gives examples such as Puppeteer with Chromium, PDF generation with Puppeteer Sharp and encryption with GnuPG. Azure still runs and patches the Functions host separately, and the preview supports .NET isolated, Python, Go and Node.js.
What It Means for Developers
Go teams that avoided Azure Functions, or kept a custom handler running, should test the native worker. Removing the extra HTTP server and hand-written binding files means less code to maintain, and Durable Functions support opens up long-running workflows in Go.
For Python, the Rust transport may quietly fix dependency errors that came from grpcio or protobuf version clashes. Run your full test suite on 3.15 in a staging slot before any switch, since native extensions are often the last to support a new Python release.
The worker image preview is worth a look for anyone who skipped Flex Consumption because of a missing system package. Pin images by digest so that each tested environment moves to production unchanged. For more on the new Python release, see our report on PyCharm 2026.3 and Python 3.15 support.
Conclusion
Azure Functions now treats Go as a first-class language on Flex Consumption, while Python 3.15 and Node.js 26 enter preview on Linux plans. Custom worker images close a key gap in Flex Consumption, though they and the new runtimes are previews and should stay in test environments for now.
Sources
- Azure Updates: Generally Available: Golang support on Azure Functions Flex Consumption
- Microsoft Learn: Azure Functions Go developer reference
- Azure Updates: Public Preview: Azure Functions support for Python 3.15
- Azure Updates: Public Preview: Azure Functions support for Node.js 26
- Azure Updates: Public Preview: OS-level dependency support via containers for Azure Functions Flex Consumption
See my articles more often when you search Google.
