You supply the worker; Azure still runs the host
The distinction is what goes into the image. A Flex Consumption worker image contains the application, one supported Functions language worker, its runtime and dependencies, and whatever Linux packages the code needs. Azure still operates the Functions host outside the image, handling triggers, routing requests and events, and scaling the app. This isn’t general-purpose container hosting, and Microsoft’s documentation says full-host Functions images built for other hosting options aren’t compatible with the Flex worker-only model.
Microsoft provides worker packages or artifacts and sample Dockerfiles, but not a Flex Consumption base image. The team deploying the app chooses a compatible base and owns the patching cycle for everything it ships, from the language worker to the browser and native libraries. The appeal is that a missing OS package no longer has to dictate the hosting plan. The trade-off is that a browser security fix, for example, now needs to make it through your build, test, and deployment pipeline.
What changes in the deployment pipeline
The Function App is still a Microsoft.Web/sites resource. In an infrastructure template, the key change is properties.functionAppConfig.deployment.storage.type: a code-package deployment uses BlobContainer, while a worker-image deployment uses Registry. Put the fully qualified image reference in deployment.storage.value and configure pull credentials or identity through deployment.storage.authentication. Omit functionAppConfig.runtime for the registry-backed app because the image supplies the runtime and worker. Keep the app’s scaling and concurrency settings in the template.
Build and scan a linux/amd64 image, push it to the registry, and pin the release to an immutable digest. The digest identifies the exact build you tested and gives you a specific version to point back to if an update fails. Local tests still have a place, but Microsoft doesn’t offer a supported way to run the complete Flex worker container locally during the preview. Make a live invocation in Azure part of the release check rather than treating a successful local build or registry push as proof the app works.
Microsoft’s.NET 10 sample makes the difference concrete: PuppeteerSharp launches OS-installed Chromium to turn an HTTP request containing HTML into a PDF. Azure Container Registry Tasks builds the Linux image, so the sample’s Azure Developer CLI deployment doesn’t require Docker on the developer’s PC. The endpoint runs Chromium without root privileges, blocks JavaScript and external resources, and caps rendering time and output. Those are sample-level safeguards, not Flex Consumption defaults. The sample also uses anonymous HTTP triggers for simplicity, so it shouldn’t be copied as-is for a service that accepts untrusted documents.
Where the preview fits—and where it doesn’t
Check region and subscription eligibility before provisioning; Microsoft’s sample requires a subscription enabled for registry-backed Flex deployments. The worker image must target Linux AMD64 and use a documented language version. The preview doesn’t support Durable Functions, the Azure Service Bus extension’s triggers or output bindings, or availability zones. These are limits of the worker-image preview, not a description of the whole Flex Consumption plan: Microsoft Learn documents Durable Functions support for the broader plan with supported storage providers.
A good first test is a nonproduction function that already fits Flex Consumption except for a native dependency—an internal PDF renderer that needs Chromium and a specific font, for example. If the app already works as a code package, the registry, image scanning, and patching add work without solving a problem. And if Service Bus or Durable Functions is central to the workload, the preview’s compatibility limits settle the question before you write a Dockerfile.
References
- (In preview) Public Preview: OS-level dependency support via containers for Azure Functions Flex Consumption Azure Updates · 2026-11-17T20:00:32Z
- Public preview: OS-level dependency support via containers for Azure Functions Flex Consumption | Microsoft Community Hub techcommunity.microsoft.com
- GitHub - Azure-Samples/flex-container-html2pdf-dotnet: Azure Functions Flex Consumption container sample for .NET 10 HTML-to-PDF rendering with PuppeteerSharp and Chromium, deployed securely with azd and Bicep. · GitHub github.com