Azure Function app in process , it will still run till Q1 Jan 27

vasu soni 0 Reputation points
2026-10-21T06:33:22.1433333+00:00

As the title, will the current runtime of .net 8 inprocess

Still run till Q1 Jan 2027 ?

We have a lot analysis left

Azure Functions
Azure Functions

An Azure service that provides an event-driven serverless compute platform.

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

10 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-21T06:34:00.62+00:00

    No—do not plan on a .NET 8 in-process Azure Function remaining supported until Q1 2027; support ends on November 10, 2026, and continued operation after that date is not guaranteed.

    Both relevant support timelines converge on that date:

    • Azure Functions ends support for the in-process execution model on November 10, 2026.
    • .NET 8 in-process on Functions runtime 4.x also has an expected end-of-support date of November 10, 2026.
    • The in-process model supports only .NET 8 currently and cannot move to a later .NET version. Moving to a later supported .NET version requires migration to the isolated worker model. ^1^

    What happens after November 10, 2026

    An existing app may continue running, because the date represents support retirement rather than a documented automatic shutdown. However, Microsoft does not guarantee compatibility, issue resolution, deployment reliability, or continued behavior for the unsupported model. Therefore, there is no supported or guaranteed operating window through January–March 2027. ^2^

    Treat November 10, 2026—not Q1 2027—as the production deadline.

    1. Inventory all in-process apps now.
      In-process apps use FUNCTIONS_WORKER_RUNTIME=dotnet. Microsoft provides this PowerShell inventory pattern: ^3^ 
         $FunctionApps = Get-AzFunctionApp
   $AppInfo = @{}

   foreach ($App in $FunctionApps) {
       if ($App.Runtime -eq 'dotnet') {
           $AppInfo.Add($App.Name, $App.Runtime)
       }
   }

   $AppInfo
    2. Complete dependency and compatibility analysis, especially:
      • Microsoft.Azure.WebJobs.* package replacements
      • Trigger and binding extensions
      • Dependency injection and middleware
      • HTTP request/response types
      • Application Insights configuration
      • Build and deployment pipeline dependencies
    3. Migrate each project to the isolated worker model.
      Follow Microsoft’s migration guide, which covers project-file conversion, package replacements, code changes, local testing, and Azure configuration. ^3^
    4. Test locally using Functions runtime 4.x, then validate in a non-production Function App or deployment slot.
    5. Finish production migration before November 10, 2026, leaving time for load testing, rollback, and operational monitoring.

    If the analysis cannot be completed immediately, keeping the existing .NET 8 in-process workload unchanged can provide short-term stability, but it does not extend its supported lifetime into 2027.

    References

    1. Supported languages in Azure Functions (programming-language-csharp)
    2. .NET 6 and In-process model retirement - Microsoft Q&A
    3. Migrate C# apps from the in-process model to the isolated worker model
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Fabian Zankl 345 Reputation points
    2026-10-21T07:19:43.7+00:00

    Hi @vasu soni ,

    You are asking whether function apps on .NET 8 with the in-process model will keep running until Q1 2027, because the migration analysis will not be finished by the retirement date.

    Short answer: they are documented to keep running after the retirement date, but from November 10, 2026 they run without support, and the platform reserves the right to restrict them.

    The dates

    Support for the in-process model ends on November 10, 2026. The .NET support policy lists the same day as the end of support for .NET 8 itself, so after that date neither the hosting model nor the .NET runtime underneath your apps receives patches.

    What happens after November 10, 2026

    The Azure Functions language stack support policy describes the retirement phase. Apps on retired versions can still be created and deployed and continue to run on the platform, but they get no new features, security patches, or performance optimizations. The same page states that, where required, Microsoft may limit the number of instances allocated to such apps, including limiting scaling to one instance, and that you must upgrade before receiving support for the app. The page currently lists no exceptions to this policy.

    No documented date exists after which in-process apps stop running.

    What this means for your timeline

    Based on the currently documented retirement behavior, continued operation into Q1 2027 is a reasonable planning assumption, but the documentation does not guarantee it. For the period between November 10 and the end of your migration, plan around these consequences from the policy:

    1. No security fixes for the retired in-process model or the unsupported .NET 8 runtime.
    2. A possible instance limit. The policy reserves this measure for cases where it is required; no such limit has been announced. It would matter most for apps that depend on scale-out (high-volume queue, Event Hubs, or Service Bus triggers).
    3. Support for the app requires upgrading it to a supported version first.

    If the analysis cannot be finished for all apps before November 10, my recommendation (a risk assessment of my own, not Microsoft guidance) is to order the migration by exposure: internet-facing HTTP functions and apps that need more than one instance first. The migration guide includes a PowerShell script that lists all in-process apps in a subscription, and it recommends a staging slot so that the switch of FUNCTIONS_WORKER_RUNTIME to dotnet-isolated and the new deployment reach production together in one swap.

    Target .NET 10 for the isolated worker model, which is what the migration guide recommends. Moving to .NET 8 isolated would leave you on a runtime that also leaves support on November 10, 2026. I wrote up the path from .NET 8 in-process to .NET 10 isolated, including the build errors that appear during the switch, in Skip .NET 11: your Azure estate belongs on .NET 10.

    References

    Drafted with help from Claude, disclosed per the Q&A AI usage policy. All technical claims checked against the Azure Functions documentation on Microsoft Learn and the .NET support policy.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more