.NET 8 and .NET 9 are out of support. A 90-day plan to .NET 10

.NET 8, .NET 9 and the Azure Functions in-process model no longer get security patches. A practical 90-day plan to reach .NET 10 without a rewrite.

On November 10, 2026, Microsoft stopped shipping security updates for both .NET 8 and .NET 9. It's an unusual "double cliff": .NET 9's support was extended to 24 months, which put it on the same day as .NET 8. The Azure Functions in-process model for .NET reached end of support on the same date. (Microsoft's announcement, Functions migration guide)

Nothing stops working overnight. But every vulnerability found from now on stays open, and auditors, insurers and enterprise customers increasingly ask which runtime you're on. The target is .NET 10, the current long-term support release, supported until November 2028.

Days 1–15: find out what you're running

Most teams underestimate how many services they have on .NET 8. Build a simple inventory:

  • Every repository's TargetFramework, including test projects and tools.
  • Container base images (mcr.microsoft.com/dotnet/aspnet:8.0 and similar).
  • Azure Functions apps, and whether they use the in-process or isolated worker model.
  • Shared NuGet packages your teams publish, because everything that consumes them moves with them.

Rank the list by exposure: internet-facing APIs and anything handling payments or personal data go first.

Days 15–60: upgrade in small, boring steps

For most ASP.NET Core and worker services, moving from .NET 8 to .NET 10 is a small change, not a migration project:

  1. Change the target framework and update Microsoft packages to their 10.x versions.
  2. Fix the build warnings. Treat new analyzer warnings as a free code review.
  3. Check the documented breaking changes for the libraries you actually use.
  4. Run the test suite and a load test against staging. Compare memory and latency with the old version.
  5. Release behind your normal pipeline, one service at a time.

Azure Functions on the in-process model need more: move to the isolated worker model first, then to .NET 10. Bindings, middleware and dependency injection change shape, and Durable Functions packages need replacing. Budget days per app, not hours.

Days 60–90: close the gaps

  • Remove the old runtimes and base images so nothing quietly slides back.
  • Add a pipeline check that fails builds targeting an unsupported framework.
  • Put the next date in the calendar now. .NET 10 support ends in November 2028, and planning a year ahead costs far less than another scramble.

What if you can't move everything in time?

Prioritize by risk, isolate what's left behind a gateway, and document the exception with an owner and a date. A short, honest list of known exceptions is far better than an unknown estate.

If you'd like a second pair of eyes, our .NET modernization work covers exactly this, and the Health Check gives you a ranked inventory in two weeks.

Dealing with this in your own system? We do this work for a living. The first call is free.

Book a call