Many business applications are designed to run quietly in the background. Customer portals, internal workflow systems, reporting tools, and integrations may operate for years without drawing much attention. That stability is valuable, but it can also create a false sense that no action is needed.
Microsoft has confirmed that .NET 8 and .NET 9 will both reach end of support on November 10, 2026. After that date, Microsoft will no longer provide security fixes, servicing updates, or technical support for applications running on those versions. The applications will not suddenly stop working, but the risk surrounding them will begin to grow.
With the deadline approaching, organizations should identify affected systems now and build an upgrade plan that allows enough time for testing, deployment, and unexpected complications.
What End of Support Actually Means
Microsoft releases new versions of .NET on a predictable schedule. Each version has a defined support period during which it receives security updates, reliability fixes, and technical assistance. Once that period ends, the software becomes unsupported.
An unsupported application may continue performing exactly as it did the day before. The difference is what happens when a new vulnerability, compatibility issue, or production problem appears. Microsoft will no longer issue a patch for the unsupported version, and support options may be limited when an organization needs help most.
This is why end of support is a business risk, not just a technical milestone. It can affect cybersecurity, compliance, insurance requirements, vendor relationships, and the ability to respond quickly to an incident.
Why Two Versions Are Affected at Once
.NET 8 is a Long-Term Support release, while .NET 9 is a Standard Term Support release. Those labels describe the length of the support window, not the software's quality or security. Due to Microsoft’s current lifecycle schedule, both versions reach the end of their support periods on the same date.
Microsoft recommends moving affected applications to .NET 10, which is a Long Term Support release supported through November 2028. For businesses, this creates a clear destination and a longer runway before the next major support deadline.
The Upgrade Is More Than Changing a Version Number
Some well-maintained applications can move to .NET 10 with relatively modest effort. Others may require additional work because the application depends on older software libraries, hosting configurations, build processes, or integrations.
The visible application is only part of the picture. An upgrade review should also include background services, scheduled jobs, APIs, mobile application services, reporting utilities, deployment pipelines, and administrative tools. Smaller components are easy to miss because users may not interact with them directly.
Third-party dependencies also matter. A library may need updating or replacement before it supports the newer platform. Hosting environments and developer workstations need the correct runtime and tools. Automated tests may expose behavior that changed between versions. These are manageable issues when discovered early, but they can become expensive when found days before a deadline.
A Practical Readiness Plan
Organizations can reduce risk by treating the upgrade as a structured maintenance project:
- Inventory applications and services. Identify every system running on .NET 8 or .NET 9, including internal tools and background processes that may not appear in a normal application list.
- Confirm business ownership. Determine who relies on each application, how critical it is, and which business processes would be affected by an outage or failed deployment.
- Review dependencies. Evaluate third-party packages, integrations, hosting services, databases, identity providers, and deployment tools for compatibility with .NET 10.
- Prioritize by risk. Start with internet-facing, customer-facing, regulated, or revenue-producing systems. Give complex applications additional time for remediation and testing.
- Test realistic workflows. Validate critical business functions, security controls, integrations, performance, scheduled work, and error handling in a nonproduction environment.
- Plan deployment and rollback. Choose an appropriate release window, communicate with stakeholders, monitor the upgraded application, and document how to recover if unexpected behavior appears.
Do Not Confuse Supported With Fully Maintained
Moving to .NET 10 addresses the major platform deadline, but it should not be the only maintenance activity. Microsoft’s support policy requires systems to remain current with monthly servicing updates. Applications also depend on third-party packages that follow their own release and security schedules.
A sustainable maintenance plan includes regular patching, dependency reviews, vulnerability monitoring, testing, and documentation. This creates smaller, predictable changes instead of large emergency upgrades every few years. It also helps development and support teams stay familiar with the application, improving response time when the business needs a change.
Use the Deadline to Improve the Application
A platform upgrade is an opportunity to look beyond basic compatibility. Teams can review slow processes, outdated integrations, unreliable deployments, missing monitoring, and security practices that have accumulated over time. Not every issue needs to be addressed during the same project, but identifying them creates a more useful modernization roadmap.
The goal is not to adopt technology simply because it is newer. The goal is to keep important systems supportable, secure, and ready for future business needs.
November Will Arrive Quickly
November 10 may appear to leave plenty of time, but assessment, scheduling, testing, and approval can consume that time quickly. Organizations with multiple applications should not assume they can upgrade everything during one maintenance window.
IowaComputerGurus has more than 20 years of experience helping organizations maintain, modernize, and support Microsoft-based applications. If you are unsure which .NET versions your systems use or what an upgrade will require, now is the time to assess the environment and establish a practical path forward.