BestPaid guides · .NET · Azure Functions

Azure Functions in-process support ended on November 10, 2026. Here is how to move to the isolated worker on .NET 10.

On November 10, 2026 two things ended on the same day: support for .NET 8 and support for the Azure Functions .NET in-process model. The in-process model stops at .NET 8, so there is no in-process path to .NET 10. Every C# function app on it has to move to the isolated worker model to keep getting security fixes.

Sources: Microsoft's migration guide (updated November 9, 2026), runtime versions and the .NET support policy. This page is our own summary; follow Microsoft's guide for every detail.

1. Find the apps that still run in-process

In-process apps report the runtime dotnet; isolated apps report dotnet-isolated. With Azure PowerShell signed in to the right subscription:

Get-AzFunctionApp | Where-Object { $_.Runtime -eq 'dotnet' } | Select-Object Name, ResourceGroupName

2. Change the project file

For .NET 10 the project now uses the Azure.Functions.Sdk project SDK and drops Microsoft.NET.Sdk.Functions:

<Project Sdk="Azure.Functions.Sdk/1.0.0">
  <PropertyGroup>
    <TargetFramework>net10.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>
  <ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="*latest stable*" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore" Version="*latest stable*" />
    <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="*latest stable*" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.ApplicationInsights" Version="*latest stable*" />
  </ItemGroup>
</Project>

Pin real version numbers from NuGet instead of the placeholders. If a dependency only works on .NET Framework, the isolated worker also runs on net48, but then you stay on .NET Framework.

3. Swap every WebJobs extension for its Worker twin

An isolated app must not reference any Microsoft.Azure.WebJobs.* package or Microsoft.Azure.Functions.Extensions. The common swaps:

In-process packageIsolated worker package
Microsoft.Azure.WebJobs.Extensions.Storage...Worker.Extensions.Storage.Blobs, .Storage.Queues, .Tables
...WebJobs.Extensions.ServiceBusMicrosoft.Azure.Functions.Worker.Extensions.ServiceBus
...WebJobs.Extensions.EventHubsMicrosoft.Azure.Functions.Worker.Extensions.EventHubs
...WebJobs.Extensions.CosmosDBMicrosoft.Azure.Functions.Worker.Extensions.CosmosDB
...WebJobs.Extensions.DurableTaskMicrosoft.Azure.Functions.Worker.Extensions.DurableTask
Timer trigger (built in before)add Microsoft.Azure.Functions.Worker.Extensions.Timer
Microsoft.Azure.Functions.Extensions (DI)remove: DI is built in

New extension versions can change host.json settings too: Service Bus 5.x, for example, uses a different structure from 4.x.

4. Add Program.cs and retire Startup.cs

using Microsoft.Azure.Functions.Worker;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;

var host = new HostBuilder()
    .ConfigureFunctionsWebApplication()
    .ConfigureServices(services =>
    {
        services.AddApplicationInsightsTelemetryWorkerService();
        services.ConfigureFunctionsApplicationInsights();
        // everything your FunctionsStartup registered goes here
    })
    .Build();

host.Run();

Move the registrations from your FunctionsStartup class here, then delete it. Log filtering for your own code now lives in Program.cs too: host.json only controls the host's logs.

5. Fix the function signatures

public class GetGreeting(ILogger<GetGreeting> logger)
{
    [Function("GetGreeting")]
    public IActionResult Run([HttpTrigger(AuthorizationLevel.Function, "get")] HttpRequest req)
    {
        logger.LogInformation("Greeting requested");
        return new OkObjectResult($"Hello, {req.Query["name"]}!");
    }
}

6. The traps that break apps quietly

7. Deploy through a staging slot

Two changes have to land together: the app setting FUNCTIONS_WORKER_RUNTIME becomes dotnet-isolated, and the migrated code is published. In between, the app throws runtime/payload mismatch errors (AZFD0013). So:

  1. create a staging slot;
  2. set FUNCTIONS_WORKER_RUNTIME=dotnet-isolated there (not as a slot setting) and switch the stack to .NET 10;
  3. publish the migrated project to the slot and test it;
  4. swap into production and check again;
  5. update your CI/CD so it keeps the new runtime and framework.
No time to do this across every function app? We migrate .NET apps and Azure Functions to .NET 10 LTS at a fixed price, one pull request per step. It starts with a $490 audit of every project and package and a fixed quote within 3 business days.
See the .NET 10 upgrade offer