.NET 9 End of Life November 10, 2026 – Your Options

The Countdown: Nine Months to .NET 9 End of Life

Microsoft .NET 9 reaches end of life on November 10, 2026. That is a fixed date – no extensions, no grace period for this release. Because .NET 9 is not a Long-Term Support (LTS) release, it has a standard 18-month support lifecycle, and the clock is already ticking. The latest public build is 9.0.18, but no further updates, security patches, or bug fixes will arrive after November 10, 2026.

With about nine months remaining, you have time to act – but not unlimited time. The right path depends on your workload, budget, and risk tolerance. This article compares the three realistic options: migrate to a newer .NET version, buy vendor extended support (if available), or transition to a third-party maintenance provider.

---

Option 1: Migrate / Upgrade to a Supported .NET Version

Upgrading removes the end-of-life risk entirely. You move your applications to a newer .NET release – either the next standard-term release (e.g., .NET 10, if timing aligns) or an LTS release (e.g., .NET 8 LTS or .NET 10 LTS).

Cost profile: Upfront investment in developer time, testing, and possible refactoring. Ongoing costs are the same as your current licensing model (no additional vendor fees).

Risk: Low to moderate. Breaking changes between .NET versions are documented, but any code relying on deprecated APIs or framework-specific behavior may require rework. The risk is higher if your application is complex, tightly coupled to .NET 9 features, or uses third-party libraries that are themselves not yet compatible with the target version.

Timeline: Nine months is tight but feasible for a well-planned migration. You need to allocate time for assessment, development, QA, and roll-out. If you have a large portfolio of applications, prioritize those that are under active development or have the shortest upgrade path.

Best for: Applications that are actively being developed, where staying current with the .NET ecosystem is a strategic advantage. Also suitable for organizations that have already invested in CI/CD pipelines and can move quickly.

---

Option 2: Vendor Extended Support (If Offered)

Microsoft sometimes offers paid extended support for certain .NET versions after the standard end-of-life date. However, because .NET 9 is a non-LTS release, custom extended support agreements are rare and often expensive. The vendor page for Microsoft provides details on current support options, but you should check directly with your account team. As of now, there is no publicly announced extended support program for .NET 9.

Cost profile: High. Extended support, if available, typically costs 2–4x the original licensing cost per year. It also requires a separate contract and may include minimum commitment terms.

Risk: Low – you continue to receive security patches from Microsoft, so compliance and vulnerability management remain covered. However, you are still on an older version with no new features, and the extended support period is finite (usually one to three years).

Timeline: You should initiate the conversation within the next two months, as negotiations and contract execution can take several weeks. If extended support is not available by mid-2026, you will have to fall back to another option.

Best for: Organizations with a very small number of critical .NET 9 applications that cannot be easily upgraded in the required timeframe, and where the cost of extended support is acceptable compared to the cost of migration or third-party support.

---

Option 3: Third-Party Support for .NET 9

Third-party maintenance providers, including 3rd Party Support, can keep .NET 9 running safely well past Microsoft’s official end-of-life date. This is not a temporary extension – it is a long-term, ongoing support model that covers security patches, bug fixes, and compatibility issues without requiring you to upgrade the runtime.

Cost profile: Low to moderate, typically 50–60% less than Microsoft’s extended support (if Microsoft offers it). You pay a fixed annual fee and avoid the large upfront cost of a migration project.

Risk: Low. Reputable third-party providers have deep expertise in the .NET runtime and can deliver patches that address CVEs and functional defects. The risk is mainly reputational – some organizations prefer vendor-backed support for compliance reasons. However, third-party support is widely used in mature IT environments where stability trumps freshness.

Timeline: You can sign up at any point before or after the end-of-life date. There is no rush to make a decision this month, but starting the conversation three to four months before EOL is recommended to ensure a smooth transition.

Best for: Stable, mature applications that are not under active development – for example, line-of-business apps that are “keep the lights on” workloads. Also ideal for organizations that want to defer the cost and disruption of a full migration while still maintaining compliance and security.

---

Decision Checklist

Use this quick checklist to evaluate which path fits your situation.

Question	Migrate / Upgrade	Vendor Extended Support	Third-Party Support
Is the application under active development?	Yes	No	No (or minimal)
Do you have a budget for a one-time migration project?	Yes	No (but high recurring cost)	Possibly (low recurring cost)
Is the application critical and cannot tolerate downtime?	Yes (plan carefully)	Yes (if available)	Yes
Do you need to stay on .NET 9 for the next 2+ years?	Not recommended	Possibly (finite term)	Yes
Is your team comfortable with a new runtime version?	Yes	No (stay on .NET 9)	No (stay on .NET 9)
Can you accept a non-vendor patch source?	N/A	N/A	Yes

If you answered “No” to most questions except the last one, third-party support is likely your best bet.

---

Next Steps

November 10, 2026, is not a deadline you can ignore. Running .NET 9 after that date without support exposes your organization to unpatched vulnerabilities and compliance gaps. The good news is that nine months is enough time to execute any of the three paths – but only if you start now.

If you want to keep your .NET 9 applications running securely without the cost and disruption of a migration, contact us to discuss a third-party support plan tailored to your environment. We help IT teams bridge the gap between vendor deadlines and business reality.