.NET 11 End of Life (EOL): 14 November 2028, and Whether to Take It
.NET 11 is a Standard Term Support release, supported until 14 November 2028, the same day as .NET 10. What it adds, what breaks, where it runs yet, and when .NET 12 is due.
Written Shahzeb Umer
SubscribeStatus
Supported
Support ends .
- Time left
- 726 days
- Latest release
- 11.0.0
- Support type
- Standard
2 years of support
- Supported10 Nov 2026 – 14 Nov 2028
Supported for 2 years, from 10 Nov 2026 to 14 Nov 2028.
Who still patches it
Six places Microsoft .NET 11 runs, five deadlines.
- Microsoft (runtime, ASP.NET Core, SDK): Patched to 14 Nov 2028
- Azure App Service (Linux, GA 11 Nov 2026): Follows Microsoft, 14 Nov 2028
- Azure Functions (isolated worker model): Follows Microsoft, 14 Nov 2028
- Ubuntu 22.04 to 26.04 (dotnet/backports PPA): Best effort to 14 Nov 2028
- Container images (mcr.microsoft.com/dotnet, 11.0): Rebuilt to 14 Nov 2028
- GitHub-hosted runners (SDK 11.0.100 on Ubuntu): Preinstalled, no end announced
Where to move
Be on Microsoft .NET 11.
The short version
- .NET 11 came out on 10 November 2026 as a Standard Term Support (STS) release and is supported until 14 November 2028: two years, ending the same day as .NET 10 (LTS), because Microsoft now gives STS releases 24 months. The only release so far is 11.0.0.
- As of 15 November 2026 it runs on Azure App Service for Linux, Azure Functions' isolated worker model, Microsoft's container images, where
latestnow means 11, and GitHub's Ubuntu runners. AWS Lambda has nodotnet11runtime, Red Hat has shipped only release candidates, and Ubuntu offers it only through a backports PPA. - Take 11 where your platform already runs it and you want C# 15's union types, EF Core 11 or runtime async: it costs no support time. Stay on 10 for AWS Lambda, RHEL or Ubuntu's archive. Either way, plan for .NET 12, the next LTS release, expected in November 2027.
On this page
.NET 11 is supported until 14 November 2028. Microsoft released it on 10 November 2026 as a Standard Term Support (STS) release, and it ends on the same day as .NET 10, the long-term support (LTS) release that came out a year earlier.
That makes 11 an unusual choice: newer than 10, but no longer-lived. This page covers why the dates line up, what 11 adds, what changes from 10, and where it runs yet, as of 15 November 2026. If you are moving off .NET 8 or 9, which lost support on 10 November 2026, start with the .NET 10 page.
Why .NET 11 ends on the same day as .NET 10
Microsoft ships a major .NET every November. Even-numbered releases are LTS, with three years of support; odd-numbered ones are STS, which Microsoft's policy defines as "supported for one year after a subsequent release". Until 2025 that meant 18 months. In September 2025 Microsoft moved STS to 24 months, starting with .NET 9, which is why .NET 9 ended alongside .NET 8.
The arithmetic for 11 and 10:
- .NET 10 came out on 11 November 2025. Three years takes it to November 2028.
- .NET 11 came out on 10 November 2026. Its successor, .NET 12, is expected in November 2027, and a year after that is November 2028.
- Both end on that month's Patch Tuesday, 14 November 2028.
Microsoft's reason for the change was dependencies: out-of-band releases such as Aspire can pull STS versions of packages into an app built on an LTS release, and under the old policy those packages lost support first. The effect is that an STS release now never ends before the LTS release beside it.
STS is not lower quality. Microsoft says "the quality of all releases is the same" and only the length of support differs. 11 gets the same monthly servicing as 10, and 11.0.0 already carried the security fixes released on 10 November. As with 10, only the newest patch is supported, and the last six months are security fixes only.
The dates agree everywhere they're published: the support policy, the release metadata and the dotnet/core repository all give 14 November 2028. Microsoft's Lifecycle site still listed no end date for .NET 11 after its 11 November update.
Should you take .NET 11?
Take it if you deploy to containers, Azure App Service on Linux or Azure Functions, you want C# 15's union types, EF Core 11 or runtime async, and you can move to Visual Studio 2026 version 18.12. It costs no support time, and from 11 the move to .NET 12 is one release instead of two.
Stay on 10 if you deploy to AWS Lambda's managed runtime, install .NET from RHEL, Amazon Linux or Ubuntu's archive, build .NET MAUI apps that need time to absorb the switch from Mono to CoreCLR, or run on x86 hardware from before about 2013.
Coming from 8 or 9, either works, since both end on 14 November 2028. 10 is the safer landing because more platforms carry it today.
What .NET 11 adds
C# 15 is the default for net11.0 projects. Its headline is union types, a value that is exactly one of a fixed set of types, with switch expressions the compiler checks for exhaustiveness:
public record class Cat(string Name);
public record class Dog(string Name);
public union Pet(Cat, Dog);
string Describe(Pet pet) => pet switch
{
Cat c => $"cat {c.Name}",
Dog d => $"dog {d.Name}",
};
It also brings closed hierarchies (a closed class can only be derived from within its own assembly), arguments in collection expressions such as [with(StringComparer.OrdinalIgnoreCase), ..names], extension indexers, and labeled break and continue. A new memory-safety model is in preview.
The runtime adds Runtime Async, which moves async suspension and resumption from compiler-generated state machines into the runtime, for cleaner stack traces and less overhead. .NET 11's own libraries are compiled with it; your projects opt in with <Features>runtime-async=on</Features>, and Microsoft still calls it a preview. The JIT removes more bounds checks and devirtualizes more calls, Half arithmetic uses hardware FP16 instructions, and Native AOT shrinks interface dispatch.
The libraries gain Zstandard compression, run-and-capture Process helpers, LINQ FullJoin, IEEE decimal types (Decimal32, Decimal64, Decimal128), X25519 key exchange, a DnsResolver for typed DNS lookups, and System.Text.Json support for C# and F# unions and JSON Lines.
The SDK starts faster, with a Native AOT CLI front end and the MSBuild server on by default. It adds dotnet run -e for environment variables, run-level --timeout and --maximum-failed-tests options for dotnet test, a minimum package age for NuGet sources, a dotnet new mcpserver template, and dotnetup, a toolchain manager in public preview.
ASP.NET Core 11 serializes C# unions in JSON bodies (described as anyOf in OpenAPI), adds asynchronous validation for minimal APIs and Blazor forms, makes OpenAPI 3.2 the default document version, refreshes SignalR authentication without reconnecting, and adds a CacheView component for static server rendering.
EF Core 11 requires .NET 11. It prunes needless joins for reference navigations, translates FullJoin, supports complex types and JSON columns on TPT and TPC inheritance, adds experimental SQL Server vector indexes, and can create and apply a migration in one step with dotnet ef database update --add.
.NET MAUI now runs on CoreCLR by default, replacing Mono.
What breaks from .NET 10 to 11
From Microsoft's breaking-change lists for .NET 11, ASP.NET Core 11 and EF Core 11. Microsoft calls the .NET list a work in progress.
1. The CPU floor rose. High on old x86 hardware. .NET 11 needs x86-64-v2 on x64 (SSE4.2, POPCNT and the rest), which Microsoft says covers every chip Intel and AMD still support; the last ones without it went out of support around 2013. On older CPUs the process stops with "The current CPU is missing one or more of the baseline instruction sets." ReadyToRun code now targets x86-64-v3 on Linux and Windows, so CPUs without AVX2 may start apps more slowly. Arm64 minimums are unchanged.
2. A failed background service now fails the process. Medium. When a BackgroundService throws and stops the host, RunAsync and StopAsync now throw too, so the app exits with a non-zero code instead of zero, and process supervisors see the failure.
3. Kestrel enforces more of the HTTP specs. Medium behind proxies. HTTP/2 and HTTP/3 requests are now also rejected for Keep-Alive, Proxy-Connection, Transfer-Encoding or Upgrade headers, not just Connection and TE, and an HTTP/1.1 request with both Content-Length and Transfer-Encoding closes the connection after the response.
4. OpenAPI moved on. Medium. Microsoft.OpenApi is now 3.x, which can break code that uses its types, such as document transformers, and generated documents default to OpenAPI 3.2. Set OpenApiVersion if your client tooling expects an older version.
5. EF Core 11 and SqlClient 7. Medium; high on Cosmos DB.
- Microsoft.Data.SqlClient 7 moved Entra ID authentication out, so apps using
ActiveDirectoryDefaultor managed identity need theMicrosoft.Data.SqlClient.Extensions.Azurepackage. UseSqlServerdefaults to compatibility level 160, SQL Server 2022. On SQL Server 2019 or older, setUseCompatibilityLevel(150).Migrate()throws when the assembly has no migrations at all.- The Cosmos DB provider no longer preserves JSON properties your model doesn't map, so saving an entity drops them.
6. ASP.NET Core removals. Low to medium. The ConcurrencyLimiter middleware, MVC compatibility options and obsolete Blazor APIs are gone, and hosting now emits OpenTelemetry semantic-convention tags on HTTP activities, which can change what tracing dashboards show.
7. Stricter libraries. Low. TAR readers verify header checksums and ZIP readers verify CRC32, so corrupt archives that used to extract now throw. Math.Round returns correctly rounded results, dependency injection aggregates exceptions thrown while disposing a scope, and an empty string in a later configuration provider now overrides earlier ones.
8. SDK behavior. Low, mostly CI. Container publishing tries wslc on Windows and container on macOS before Docker and Podman, the NuGet locks directory moved on Linux, and the CLI's own telemetry switched to OpenTelemetry.
9. Platform support narrowed. Windows Server 2012 and 2012 R2, still on .NET 10's supported list, are not on 11's, and Microsoft's Windows container images for 11 are Server 2025 only. For .NET MAUI, CoreCLR replaces Mono, Android needs API level 24 or later, and Android x86 is unsupported.
Tools you need
Visual Studio 2026 version 18.12 or later. Microsoft supports targeting net11.0 only from 18.12, the version that ships SDK 11.0.100. Visual Studio Code with C# Dev Kit, or the dotnet CLI on its own, work on Windows, Linux and macOS.
In GitHub Actions, GitHub's Ubuntu images from 11 November 2026 include SDK 11.0.100. The windows-latest image's most recent listed build, from 3 November, has neither SDK 11 nor Visual Studio 18.12, so install the SDK and build with the CLI:
- uses: actions/setup-dotnet@v6
with:
dotnet-version: '11.0.x'
- run: dotnet build -c Release
Where .NET 11 runs, as of 15 November 2026
| Where it runs | Status | What happens after | Source |
|---|---|---|---|
| Microsoft: runtime, ASP.NET Core, SDK | 11.0.0 and SDK 11.0.100 since 10 November 2026; supported until 14 November 2028 | No more patches | Support policy |
| Azure App Service for Linux | Generally available since 11 November 2026, on Ubuntu 26.04 images; Linux is now the portal's default for new .NET 11 apps | Follows Microsoft's date | App Service |
| Azure App Service for Windows | Not announced as generally available; Microsoft says Windows "remains available for applications that need it" | Check az webapp list-runtimes --os windows in your region |
App Service |
| Azure Functions, isolated worker model | Generally available since 10 November 2026; C# only, F# "temporarily unavailable"; not on Linux Consumption | Follows Microsoft's date | Functions |
| Azure Functions, in-process model | Not supported; the model's own support ended 10 November 2026 | Isolated worker model only | Functions |
| AWS Lambda | No dotnet11 runtime or base image |
Custom runtime on provided.al2023, or your own container image |
Lambda runtimes |
| Ubuntu 22.04, 24.04 and 26.04 | dotnet11 11.0.0 in Canonical's ppa:dotnet/backports since 10 November 2026; not in the 24.04 or 26.04 archive |
Best-effort support, not beyond Microsoft's date | Launchpad |
| RHEL 10 | Release candidate 2 RPMs, in an 11 November 2026 advisory; no 11.0.0 build yet, and no advisory found for RHEL 8 or 9 | Red Hat follows Microsoft's lifecycle | RHSA-2026:98571 |
| Amazon Linux 2023 | No .NET 11 packages in its 21 October 2026 package list | Use Microsoft's binaries or a container | AL2023 packages |
mcr.microsoft.com/dotnet images, 11.0 |
11.0 and latest are Ubuntu 26.04; also chiseled Ubuntu, Alpine 3.24, Azure Linux 3.0 and 4.0, and Windows Server 2025 |
Rebuilt until 14 November 2028 | dotnet-docker |
| GitHub-hosted runners | SDK 11.0.100 on the Ubuntu 24.04 and 26.04 images | No end announced | runner-images |
latest already moved. Microsoft's latest tags point to .NET 11 on Ubuntu 26.04, so a FROM mcr.microsoft.com/dotnet/aspnet:latest built since 10 November gets a new .NET and a new OS at once. Pin 10.0 or 11.0 on purpose.
Ubuntu's archive has only 10. 24.04 and 26.04 carry dotnet10 in Main; of the released versions, only 26.10, an interim release, has 11 in its archive, in Universe. Canonical gives the backports PPA "best-effort" support, which doesn't extend beyond Microsoft's lifetime. The Ubuntu hub has the release dates.
Functions projects need the new SDK. .NET 11 function apps require Azure.Functions.Sdk 1.0.1 or later as the project SDK, plus an explicit Microsoft.Azure.Functions.Worker reference, 2.50.0 or later.
How to check what you run
On a machine or in a container:
dotnet --list-runtimes # Microsoft.NETCore.App 11.0.0 means .NET 11
dotnet --list-sdks # 11.0.100 is the first .NET 11 SDK
/lib64/ld-linux-x86-64.so.2 --help | grep x86-64-v2 # "supported" means the CPU meets .NET 11's floor
In your repositories, where unpinned tags have already moved:
grep -rnE --include='Dockerfile*' 'mcr\.microsoft\.com/dotnet/[a-z-]+(:latest)?( |$)' .
grep -rhoE --include='*.csproj' --include='Directory.Build.props' '<TargetFrameworks?>[^<]+' . | sort | uniq -c
cat global.json 2>/dev/null
On Azure:
# Lists the .NET stacks App Service for Linux offers in your region
az webapp list-runtimes --os linux | grep DOTNET
# Azure Functions on Linux: DOTNET-ISOLATED|11.0 for a .NET 11 app
az functionapp config show --name APP --resource-group RG --query linuxFxVersion -o tsv
What comes next: .NET 12
Microsoft releases a new .NET every November, and even-numbered releases are LTS, so .NET 12, expected in November 2027, will be the next LTS release. As of 15 November 2026 Microsoft hasn't named its release day or published a preview; .NET 11's first preview came in February 2026, nine months before release.
When 12 ships, both 10 and 11 have one year left, to 14 November 2028. Teams on 11 make that move from the release right before it; teams on 10 skip one. Under the LTS policy, 12 gets three years from its release. Every .NET version has its dates on the hub.
Sources
- Microsoft: .NET support policy, releases index, 11.0 release metadata and supported OS list, .NET 11 release notes, dotnet/core releases and Microsoft Lifecycle
- Announcements: Announcing .NET 11 and STS releases supported for 24 months
- What's new: .NET 11, the .NET 11 runtime, C# 15 and EF Core 11
- Breaking changes: .NET 11, minimum hardware requirements, BackgroundService failures, ASP.NET Core 11, Kestrel protocol compliance and EF Core 11
- Tools: SDK, MSBuild and Visual Studio versioning, setup-dotnet, runner images for Ubuntu 24.04 and windows-latest
- Azure: App Service .NET 11 preview and general availability, Azure Functions .NET 11 announcement, supported languages and isolated worker guide
- AWS: Lambda runtimes, Lambda .NET base images and the Amazon Linux 2023 package list
- Linux: .NET on Ubuntu, Canonical's .NET availability, the dotnet/backports PPA, the Ubuntu archive, Red Hat .NET life cycle and RHSA-2026:98571
- Containers: dotnet-docker image tags and supported tags policy
- endoflife.date: .NET: the dates in the status box, MIT licensed
Common questions
When is .NET 11 end of life?
When was .NET 11 released?
Is .NET 11 an LTS release?
Should I upgrade from .NET 10 to .NET 11?
When will .NET 12 be released?
When does .NET 12 support end?
Which Visual Studio version supports .NET 11?
net11.0 only from 18.12, so earlier Visual Studio 2026 releases and Visual Studio 2022 aren't supported for it. Visual Studio Code with C# Dev Kit, or the dotnet CLI alone, also work.Does AWS Lambda support .NET 11?
dotnet10 and no dotnet11, and AWS publishes no .NET 11 base image. You can still run .NET 11 on Lambda as a custom runtime on provided.al2023 or from your own container image.Also on the calendar
End-of-life dates for the rest of your stack.
- Kubernetes end of life3 supportedNext to end: 1.35, 28 Feb 2027
- Microsoft .NET end of life2 supportedNext to end: 11, 14 Nov 2028
- Node.js end of life3 supportedNext to end: 22, 30 Apr 2027
- OpenSSL end of life3 supportedNext to end: 4.0, 14 May 2027
- PHP end of life5 supportedNext to end: 8.2, 31 Dec 2026
- PostgreSQL end of life5 supportedNext to end: 15, 11 Nov 2027
- Python end of life5 supportedNext to end: 3.11, Oct 2027
- Ubuntu end of life4 supportedNext to end: 22.04, 1 Jun 2027
Dates checked against endoflife.date (MIT). How we check datesReport a wrong dateEvery Microsoft .NET version