timetobail
My stack

Microsoft Azure · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Azure Functions apps on the in-process model?

Time to Bail · Boarding pass

FromAzure Functions apps on the in-process model
ToYour pick

Act. You can stay.

In-process support ends November 10, 2026. Move to the isolated worker model on .NET 10.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
In-process support ends
Time left
25days
Status
Act

Azure Functions in-process model support ends November 10, 2026

Support for the in-process model of C# Azure Functions ends on November 10, 2026, the same day as .NET 8. Microsoft says to move apps to the isolated worker model and .NET 10.

What to do before November 10

Tick steps as you go. Your progress stays in this browser.

  1. Find in-process apps

    Look for function apps with FUNCTIONS_WORKER_RUNTIME set to dotnet. Microsoft gives a PowerShell script for this.

  2. Move the project to the isolated model

    Follow Microsoft's migration guide, target .NET 10 and test locally with Core Tools 4.x.

  3. Switch the app in Azure

    Set FUNCTIONS_WORKER_RUNTIME to dotnet-isolated and publish the new project together. Use a staging slot.

Facts we checked

Facts and their sources
In-process support endsNovember 10, 2026[1]
Only version in-process runs.NET 8, which also ends November 10, 2026[2]
Isolated worker on .NET 10Supported until November 14, 2028[2]
.NET 10 in-process?No. .NET 10 is not supported by the in-process model[2]
What to move toThe isolated worker model; target .NET 10, or .NET Framework 4.8 if you must[1]
Test locally withAzure Functions Core Tools version 4.x[1]
The app setting to changeFUNCTIONS_WORKER_RUNTIME from dotnet to dotnet-isolated[1]
In-process function appsLose support on November 10, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. Migrate C# apps from the in-process model to the isolated worker model Microsoft · primary · checked Oct 13
  2. Azure Functions runtime versions overview Microsoft · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Azure Functions apps on the in-process model? Act. You can stay. In-process support ends November 10, 2026. Move to the isolated worker model on .NET 10.

On our scale this is Act: change a setting or plan before the date. You can stay.

Support for the in-process model of C# Azure Functions ends on November 10, 2026, the same day as .NET 8. Microsoft says to move apps to the isolated worker model and .NET 10.

Here are the facts we checked:

  • In-process support ends: November 10, 2026 (Microsoft)
  • Only version in-process runs: .NET 8, which also ends November 10, 2026 (Microsoft)
  • Isolated worker on .NET 10: Supported until November 14, 2028 (Microsoft)
  • .NET 10 in-process?: No. .NET 10 is not supported by the in-process model (Microsoft)
  • What to move to: The isolated worker model; target .NET 10, or .NET Framework 4.8 if you must (Microsoft)
  • Test locally with: Azure Functions Core Tools version 4.x (Microsoft)
  • The app setting to change: FUNCTIONS_WORKER_RUNTIME from dotnet to dotnet-isolated (Microsoft)
  • In-process function apps: Lose support on November 10, 2026 (Microsoft)

You can stay on Microsoft Azure. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Microsoft is the main source for this page. Microsoft Azure has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

In-process function apps: Lose support on November 10, 2026.

The date to remember is November 10, 2026. Make the change before then.

What to do before November 10

  1. Find in-process apps. Look for function apps with FUNCTIONS_WORKER_RUNTIME set to dotnet. Microsoft gives a PowerShell script for this.
  2. Move the project to the isolated model. Follow Microsoft's migration guide, target .NET 10 and test locally with Core Tools 4.x.
  3. Switch the app in Azure. Set FUNCTIONS_WORKER_RUNTIME to dotnet-isolated and publish the new project together. Use a staging slot.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Azure Functions apps on the in-process model can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product