AzureEnd of support
Azure Functions: .NET in-process model end of support
End of support date for the in-process model for .NET apps in Azure Functions: 10 Nov 2026. Apps on this model can still be used after that date but stop receiving security and feature updates.
Support ended , 10 Nov 2026
What breaks
From the end of support date, the in-process model for .NET apps in Azure Functions is no longer supported. .NET apps that use the in-process model can still be used after that date, but they no longer receive security and feature updates from Microsoft. Microsoft states that apps on this model need to transition to the isolated worker model by that date to continue being supported.
Who is affected
Matching resource types
azurerm_linux_function_app
Fields the check reads
site_config.application_stack.dotnet_versionsite_config.application_stack.use_dotnet_isolated_runtime
What to do
Move .NET apps from the in-process model to the isolated worker model by 10 Nov 2026: migrate to the isolated worker model.
Replacement
Isolated worker model
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourceaka.msOfficial
Last checked against the first source in this list on .
Related
- , 14 Sep 2026Azure Functions: runtime version 1.x end of supportSource
- , 30 Sep 2026Azure Functions: runtime v3 on Linux Consumption retirementSource
- , 1 Oct 2026Azure Functions: Python 3.10 end of supportSource
- , 10 Nov 2026Azure Functions: .NET 8 and .NET 9 end of supportSource
- , 10 Nov 2026Azure Functions: PowerShell 7.4 end of supportSource
- , 30 Apr 2027Azure Functions: Node.js 22 end of supportSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item