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.
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
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.
An isolated app must not reference any Microsoft.Azure.WebJobs.* package or Microsoft.Azure.Functions.Extensions. The common swaps:
| In-process package | Isolated worker package |
|---|---|
Microsoft.Azure.WebJobs.Extensions.Storage | ...Worker.Extensions.Storage.Blobs, .Storage.Queues, .Tables |
...WebJobs.Extensions.ServiceBus | Microsoft.Azure.Functions.Worker.Extensions.ServiceBus |
...WebJobs.Extensions.EventHubs | Microsoft.Azure.Functions.Worker.Extensions.EventHubs |
...WebJobs.Extensions.CosmosDB | Microsoft.Azure.Functions.Worker.Extensions.CosmosDB |
...WebJobs.Extensions.DurableTask | Microsoft.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.
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.
[FunctionName("X")] becomes [Function("X")]: a plain find-and-replace.ILogger log parameter goes away. Take ILogger<T> in the class constructor instead.using Microsoft.Azure.WebJobs; with using Microsoft.Azure.Functions.Worker;.Input suffix (CosmosDBInput), output bindings an Output suffix (QueueOutput, BlobOutput); triggers keep their names.IAsyncCollector<T> becomes a T[] return; IBinder is replaced by an injected SDK client.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"]}!");
}
}
[JsonProperty] and [JsonIgnore] without any error, so a renamed field simply arrives empty. Switch to [JsonPropertyName] or configure Newtonsoft explicitly.ReadToEnd or Write on the request or response throws InvalidOperationException: Synchronous operations are disallowed. Use the async methods and return Task<IActionResult>.TaskOrchestrationContext, DurableTaskClient). Plan for in-flight orchestrations before you switch.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:
FUNCTIONS_WORKER_RUNTIME=dotnet-isolated there (not as a slot setting) and switch the stack to .NET 10;