Share via

The retirement announcement for all Dotnet8

Muthusamy, Reegan 40 Reputation points
2026-06-11T12:14:42.27+00:00

The retirement announcement for all Dotnet versions, ASP.Net Core, DotNet8 isolated and Dotnet8 LTS

Developer technologies | .NET | .NET Runtime
0 comments No comments

5 answers

Sort by: Most helpful
  1. Bruce (SqlWork.com) 84,086 Reputation points
    2026-06-11T14:13:46.0833333+00:00

    .net 8 support ends nov 10, 2026.

    https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

    Your .net azure functions won’t stop running on this date, there just will be no security updates or support if you have an issue.

    note: some companies face legal liabilities if running on unsupported software.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. Nancy Vo (WICLOUD CORPORATION) 5,700 Reputation points Microsoft External Staff Moderator
    2026-06-12T02:51:34.12+00:00

    Hello @Muthusamy, Reegan ,

    Thanks for your question.

    Due to .NET and .NET Core support policy, on November 10, 2026, support for .NET 8 will end. Your apps will continue to run, but security updates will no longer be available and Microsoft will no longer provide customer service for .NET 8.

    ASP.NET Core follows the same lifecycle as .NET - they share the same release and retirement dates.

    Note: The isolated worker model itself does not have its own separate support lifecycle. Its support is tied to the underlying .NET runtime version it runs on.

    I hope this addresses your question. If this response was helpful, please consider following the guidance to provide feedback.

    Was this answer helpful?

    0 comments No comments

  3. Richard Wright 0 Reputation points
    2026-06-11T19:00:18.01+00:00

    To clarify the lifecycle, .NET 8 is a Long-Term Support (LTS) release with a fixed 3-year support window that officially reaches its End of Support (EOS) on November 10, 2026. This retirement date applies uniformly across the entire ecosystem, including the .NET 8 Runtime, ASP.NET Core, and both the In-Process and Isolated Worker models for Azure Functions. After this date, Microsoft will stop issuing monthly security patches and technical support, meaning any production workloads still running on version 8.0 should be updated to .NET 10 (the latest LTS release) to maintain compliance and security.

    Was this answer helpful?

    0 comments No comments

  4. Muthusamy, Reegan 40 Reputation points
    2026-06-11T12:19:34.4633333+00:00

    what about DotNet8 isolated version ?

    Was this answer helpful?

    0 comments No comments

  5. AI answer

    2026-06-11T12:15:00.3466667+00:00

    For .NET 8 and related components, the available lifecycle information in the context is:

    • .NET 8 is a Long-Term Support (LTS) release and will be supported for three years. This applies to the .NET 8 runtime and SDK, including ASP.NET Core 8 and .NET MAUI for .NET 8, as they are part of the .NET 8 wave.
    • The detailed and most up-to-date support timelines (including end-of-support/retirement dates) for .NET 8, ASP.NET Core 8, and other .NET 8 components are maintained in the official .NET Core and .NET 8 Support Policy page.

    The context does not list a specific calendar end date for .NET 8 LTS, ASP.NET Core 8, or “.NET 8 isolated,” but it explicitly states that .NET 8 is LTS with three years of support and points to the central support policy page for exact lifecycle details.

    For planning purposes:

    • Treat .NET 8 (runtime and SDK) as supported for three years from its LTS release date.
    • Use the .NET Core and .NET 8 Support Policy page to confirm exact retirement/end-of-support dates for .NET 8, ASP.NET Core 8, and related workloads.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.