What changed
Microsoft first introduced Go as a first-class Azure Functions language in public preview on the Flex Consumption plan. That preview arrived at Build 2026. The November announcement moves the same capability to general availability. Microsoft's documentation defines GA as "Fully supported and approved for production use."
That matters because preview features usually come without production support commitments. Many enterprise change-control boards won't let a workload run on one.
What is supported
Microsoft's Ignite post says Go support is generally available on Flex Consumption with Go 1.24 or later. It lists these capabilities, all built on the open-source Azure Functions Go worker:
- Direct gRPC link to the host. Go functions talk to the Functions host over gRPC.
- Standard
net/httphandlers. This includeshttp.Flusherresponse streaming. - Typed triggers. They cover Azure event sources.
- Azure SDK input bindings.
- Durable Functions orchestrations. These work through
middleware/durabletask. - Structured logging. It uses
log/slog. - OpenTelemetry.
The Ignite post also says the Durable Task SDK for Go is itself in public preview and requires Go 1.25 or later. That is a separate component from the GA worker. Teams that want Go orchestrations should treat that part as preview.
The Build-era preview described a code-first, idiomatic model. The go build command produces a single static binary that the Functions host invokes directly. That preview listed HTTP, Timer, Service Bus, Event Hubs, Event Grid, Cosmos DB, and Blob Storage triggers. The GA announcement refers to typed triggers across Azure event sources but doesn't list every one. Check the Go developer reference before you assume a specific trigger or binding is available.
The limits
- Flex Consumption only. Microsoft's documentation says Go support is available only for function apps hosted in the Flex Consumption plan. Premium, Dedicated and Windows Consumption are not options for Go.
- Linux only. Flex Consumption is a Linux-based Azure Functions hosting plan. The plan is not a route to Go on Windows hosting.
- Runtime 4.x. Go support is generally available for Flex Consumption apps and requires Azure Functions runtime 4.x.
- Version lifecycle. Go 1.24 or later is listed as GA, and each major Go release is supported until two newer major releases are available. Microsoft's table points to the Go release policy rather than giving a fixed end-of-support date. Plan to upgrade Go regularly.
- Regions. Flex Consumption is available in many Azure regions, but it doesn't currently support all of them. Verify the plan and the Go runtime in your target region before you commit.
Checking your region
Microsoft's migration guidance describes a command that lists the stack versions Flex Consumption supports in a region. The Flex Consumption documentation gives this form for Go:
az functionapp list-flexconsumption-runtimes --location <REGION> --runtime go --query '[].{version:version}' -o tsv
If the command returns Go versions, the region supports the runtime. If it returns nothing, pick a different region.
Flex Consumption cost and scaling
Go GA comes with Flex Consumption's billing model, so cost planning matters. In the plan's on-demand mode, the plan builds on the Consumption pay-for-what-you-use billing model. Microsoft's documentation describes two modes:
- On demand. You pay for memory provisioned while instances execute functions, plus executions. No minimum instance count is required.
- Always ready. You pay a baseline for memory across the always-ready instances, and there are no free grants.
Always-ready instances are the usual way to cut cold starts. They also stop the app from scaling to zero cost. Microsoft's documentation says to check the Azure Functions pricing page for current rates and free grants.
Two quota and design points also apply. The default regional quota is 250 cores for all Flex Consumption instances in a subscription and region. Always-ready instances count against that quota. Microsoft also says you can only have one app per Flex Consumption plan.
Why the custom-handler route matters
Go has long worked on Azure Functions through custom handlers, where you run your own HTTP server. A Microsoft Q&A answer says custom handlers have been GA since about 2021, and that Flex Consumption support for them has since rolled out. That route relied on an HTTP server you supplied. The native worker replaces that arrangement with gRPC and typed triggers, according to Microsoft's Ignite post. Existing custom-handler apps aren't automatically moved by this announcement. Treat any migration as a deliberate project and test it.
Documentation caution
Microsoft has been updating its docs, and older pages and cached search results may still show Go as preview. The current language-support page lists Go 1.24 or later as GA. If you see a conflicting listing, trust the dated GA announcement and the current docs.
Practical takeaways
- Confirm your target region supports Flex Consumption and Go.
- Use Go 1.24 or later, and plan upgrades as new Go releases arrive.
- Decide between on-demand and always-ready based on latency needs and budget.
- Check each trigger and binding you need against the Go developer reference.
- Treat the Durable Task SDK for Go as preview until Microsoft says otherwise.
Go GA is a support-status milestone, not a promise of feature parity with every other Functions language. For teams building event-driven Go services, though, the Flex Consumption path is now a supported production option.
References
- (Launched) Generally Available: Golang support on Azure Functions Flex Consumption Azure Updates · 2026-11-17T20:00:32Z
- flex-consumption-plan.md github.com
- Azure Functions Flex Consumption plan hosting | Microsoft Learn learn.microsoft.com