Azure Functions .NET in-process reached end of support on November 10, 2026. Existing functions may continue to run, but Microsoft no longer provides security or product fixes for that execution model. Moving to isolated worker requires code, package, and configuration changes; it is not a runtime toggle.
What ended and what remains supported
The in-process model runs function code inside the Functions host and was limited to .NET 8. The isolated worker model runs the application in a separate process, supports modern .NET and compatible .NET Framework versions, provides process control, and uses standard .NET dependency injection.
Identify affected applications
Inspect FUNCTIONS_WORKER_RUNTIME. A value of dotnet means in-process; dotnet-isolated means the application already uses isolated worker.
az functionapp config appsettings list \
--name <function-app> \
--resource-group <resource-group> \
--query "[?name=='FUNCTIONS_WORKER_RUNTIME'].value" \
-o tsvKey technical changes
- Target a supported .NET version and use
Azure.Functions.SdkwithMicrosoft.Azure.Functions.Worker. - Remove references in the
Microsoft.Azure.WebJobs.*andMicrosoft.Azure.Functions.Extensionsnamespaces. - Replace trigger and binding extensions with
Microsoft.Azure.Functions.Worker.Extensions.*packages. - Add
Program.csas the entry point and move service and middleware registration. - Replace
[FunctionName]with[Function]and review binding input and output types. - Obtain
ILogger<T>through dependency injection. - Revalidate
host.json, Application Insights, serialization, authentication, and Durable Functions.
Migration risks to test
The change can affect HTTP contracts, JSON serialization, middleware behavior, retries, Service Bus or Storage bindings, and telemetry. Durable Functions need their own migration path. Run regression tests with realistic workloads and compare error rates, latency, dependencies, and traces before production promotion.
A safe migration plan
- Inventory Function Apps, runtime values, hosting plans, regions, triggers, extensions, and criticality.
- Migrate a low-risk function first and create a reusable isolated-worker template.
- Deploy to a slot or parallel Function App with equivalent identities, configuration, and secrets.
- Run functional, load, and observability tests; verify queues, timers, and duplicate-event handling.
- Perform a controlled cutover with a defined rollback window.
- Update IaC, pipelines, runbooks, and policies so new in-process projects cannot be introduced.
Architecture considerations
For Linux applications targeting .NET 10 or later, Microsoft recommends Flex Consumption rather than the legacy Linux Consumption plan. When possible, separate the execution-model migration from a hosting-plan migration to reduce concurrent risk.
Related reading
For additional Azure architecture and operations context, see Microsoft Azure: The Latest Updates and Features.