The retirement announcement for all Dotnet8

Question

The retirement announcement for all Dotnet8

Muthusamy, Reegan 45

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

0 comments

5 answers

Your answer

Answer 1

Nancy Vo (WICLOUD CORPORATION) 8,155 Microsoft External Staff Moderator

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.

Muthusamy, Reegan 45 Reputation points

2026-06-15T16:58:36.8633333+00:00

Yes, i accept you answers. will you able to help with the KQL query that will fetch entire apps(webapp,functionapp) running across subscriptions ?
Bruce (SqlWork.com) 85,281 Reputation points

2026-06-16T00:31:06.8833333+00:00

Normally you would just query your source repo. That’s how I find the projects requiring update.
Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator

2026-06-16T06:58:33.4833333+00:00
Hi @Muthusamy, Reegan ,

To help make things clearer, please refer to the following steps:

Azure Resource Graph is the tool for this - it acts like a search engine for all your Azure resources across multiple subscriptions in one shot

You'd write a KQL query targeting the resource type for web apps, which covers both WebApps and FunctionApps

The query would return details like app name, subscription, resource group, region - basically a full inventory

From there you can filter further based on what you need

However, since this goes deeper into Azure Resource Graph and cross-subscription querying, I'd suggest posting a new thread on Microsoft Q&A with the "Azure" tag - the Azure specialists there will be able to give you a much more thorough answer and help if you run into any issues along the way.

If any part of the explanation helped address your question so far, I would greatly appreciate it if you could follow the instructions here. This can help other community members facing similar scenarios.

Thank you.
Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator

2026-06-18T02:18:27.36+00:00

Hi @Muthusamy, Reegan ,

Just checking in to see if you had a chance to review my previous response. Please feel free to reach out if you have any questions - I’m here to help.
Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator

2026-06-22T06:34:39.14+00:00

Hi @Muthusamy, Reegan ,

Since I haven’t received any recent updates, I’ll go ahead and close this thread for now. If you still need assistance, please feel free to reach out at any time. I’ll be happy to help.

Thank you.
Krzysztof Nowicki 81 Reputation points

2026-08-17T09:44:50.4133333+00:00

Hi @Nancy Vo (WICLOUD CORPORATION)

Do Logic App Standard workflows require any changes for .NET 8 in‑process retirement?

We are using Logic App Standard with workflows only (no custom Azure Functions). Our App Service configuration includes:

FUNCTIONS_WORKER_RUNTIME = dotnet

FUNCTIONS_INPROC_NET8_ENABLED = 1

FUNCTIONS_EXTENSION_VERSION = ~4

Many thanks
Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator

2026-08-18T10:47:55.5+00:00

Hello @Krzysztof Nowicki ,

You may not need to change your Logic App workflows for the .NET 8 update if you are not using your own C# code. The update rules are mostly meant for custom code, not for standard workflows. The settings you shared look like the normal setup, and Microsoft usually handles the background updates for these apps.

Answer 2

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.

Answer 3

Bruce (SqlWork.com) 85,281

.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.

0 comments

Answer 4

Muthusamy, Reegan 45

what about DotNet8 isolated version ?

Bruce (SqlWork.com) 85,281 Reputation points

2026-06-15T14:59:08.05+00:00

It’s the same. It will still run, just no security patches or support if any issues. Note: dotnet isolated is a hosting option, not a separate runtime. Also there is no separate .net 8 and .net 8 LTS. .net was a LTS release (3 years support). .net 10 is the current LTS, and still has a little over 2 years support.

Answer 5

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: