On November 10, 2026, Microsoft ended support for .NET 8 and .NET 9. No more security fixes, no more servicing updates, no more technical support. The applications keep running. They just stop getting patched.
In September we wrote about what this date means for Sitecore, Sitefinity and Optimizely sites. For most of those content management systems, the answer was not much. This post is about the other half: the software organizations built for themselves. Member and constituent portals, integration services, internal tools, scheduled jobs and the APIs behind mobile apps. In our experience, that is where .NET 8 is most often running, and where nobody is watching the date.
Where this comes from. Microsoft's .NET blog announcement of June 29, 2026, Microsoft's .NET support policy page, and Microsoft's .NET Framework lifecycle documentation, all read directly.
What Ended
Microsoft's words: it "will no longer provide servicing updates, security fixes, or technical support for these versions." Applications built on .NET 8 or .NET 9 will continue to run. November 10 was a Patch Tuesday, and Microsoft said each version might get one final update that day if there was a known critical issue. After that, nothing.
The supported destination is .NET 10, a long-term support release. Microsoft's support policy lists its end of support as November 14, 2028.
The first Patch Tuesday with fixes that .NET 8 and 9 will not get is December 8. From then on, each monthly release can carry fixes your application will not get.
Where .NET 8 Hides
Organizations rarely think of themselves as running .NET. They think of themselves as running the member portal, or the permit lookup, or the integration that moves orders from the website to the accounting system. Those are the places to look:
- Portals. Member, constituent, student, customer and vendor portals built as custom applications.
- Integrations. Services that move data between an AMS, CRM, ERP or student information system and the website.
- Scheduled jobs. Nightly imports, report generators and email jobs that run on a server nobody logs into.
- APIs. The back end of a mobile app, a public data feed, or a partner integration.
- Internal tools. Staff tools, intranets and dashboards built in-house or by a past vendor.
- Website front ends. Optimizely CMS 12 sites and the rendering hosts in front of headless platforms, which our September post covered.
How to Check in Ten Minutes
- Look at the project file. Each .NET project file names its target framework. A value of net8.0 or net9.0 means it is on the clock.
- Ask the server. On the server, the command dotnet –list-runtimes lists every runtime installed.
- Check the hosting settings. In Azure App Service, the runtime stack is in the app's configuration settings.
- Check container images. A container image tagged 8.0 or 9.0 is running an unsupported runtime.
One distinction matters. .NET Framework 4.8 and 4.8.1 are a different product. Microsoft defines .NET Framework as a component of Windows, so its support follows the Windows version it runs on. An application on .NET Framework 4.8 is not affected by November 10. Its deadline is the Windows Server it sits on.
What Moving to .NET 10 Involves
For a well-kept application, the move is usually a contained project: change the target framework, update the third-party packages to versions that support .NET 10, work through the breaking changes Microsoft documents for each release, test, update the runtime on the server, and deploy.
In our experience, the risk is rarely in your own code. It is in a package that was never updated, a library whose maintainer stopped, or an application that nobody has opened since the developer who built it left. Those are the ones that turn a two-week upgrade into something longer, and they are the ones worth finding first.
Why Not Wait
Nothing breaks on November 11. That is exactly why this slides. The cost shows up later: in a security questionnaire from a funder or a customer, a cyber insurance renewal, an auditor's finding, or a vulnerability that gets a fix for .NET 10 and none for the version you are on. Government agencies and school districts are likely to see it first in a security review. Businesses are likely to see it in a customer's vendor assessment.
Need Your Applications Moved to .NET 10?
We find out which runtime each of your applications, portals and integration services runs on, upgrade them to .NET 10, test them and deploy them. If nobody on your staff owns that code anymore, our partnership plans can put a developer on it every month.