Week ahead, November 9 to 15: .NET 8 leaves support on all three clouds

The week of November 9, 2026 has one date that matters more than the rest. On Tuesday, November 10, .NET 8 and .NET 9 reach end of support, and Azure, AWS and Google Cloud each change the status of their .NET 8 serverless runtimes on that same day. Meanwhile KubeCon + CloudNativeCon North America runs in Salt Lake City from November 9 to 12. Here is what ships, retires and opens this week, and what to do about it.

This week at a glance

Date	What happens	Where
Mon, Nov 9	KubeCon NA co-located events, including Agentics Day: MCP + Agents, Cloud Native AI + Inference Day, Platform Engineering Day and Observability Day	CNCF, Salt Lake City
Tue, Nov 10	.NET 8 (LTS) and .NET 9 (STS) end of support	Microsoft .NET
Tue, Nov 10	Support for the Azure Functions in-process model ends	Azure
Tue, Nov 10	Lambda dotnet8 runtime and container-only dotnet9 runtime deprecated	AWS
Tue, Nov 10	Cloud Run functions dotnet8 runtime deprecated	Google Cloud
Tue, Nov 10	End of servicing for Azure IoT Edge 1.5 (LTS) and PowerShell 7.4 (LTS)	Microsoft lifecycle
Nov 10 to 12	KubeCon keynotes and breakouts; no virtual component, recordings follow on the CNCF YouTube channel	CNCF
Around Nov 11	GKE Stable channel auto-upgrade target for 1.36 (an approximate date on the release schedule)	Google Cloud

What is it?

End of support means the vendor stops shipping fixes for a version. Think of a car model that no longer gets recall repairs: it still drives, but the next defect found is yours to live with. For .NET, Microsoft’s support policy lists November 10, 2026 as the end of support for both .NET 8 and .NET 9, with .NET 10 (LTS) supported until November 14, 2028. Each cloud then decides what its managed runtimes do with that date, and the three providers have made different choices.

What changed?

One end-of-support date, three different follow-on schedules.

Azure: the Azure Functions migration guide states that support for the in-process model ends on November 10, 2026 and points apps to the isolated worker model, recommending .NET 10. For App Service, the language support policy says apps on an out-of-support runtime continue to run unchanged, but get no security patches or related support for that runtime.
AWS: the Lambda runtimes page lists dotnet8 with a deprecation date of November 10, 2026, then block function create on July 29, 2027 and block function update on August 31, 2027. The container-only dotnet9 runtime is deprecated the same day, with no block dates scheduled.
Google Cloud: the Cloud Run functions runtime support page lists dotnet8 as deprecated on November 10, 2026 and decommissioned on May 10, 2027. During deprecation you can generally still create and update workloads; after decommission you cannot, and workloads may be disabled.

On the Kubernetes side, KubeCon NA opens with a Monday of co-located events, with keynotes on Tuesday, Wednesday and Thursday. CNCF says there is no virtual component this year; breakout and keynote recordings will be published on its YouTube channel, and the schedule says within two weeks. We previewed the event, and the two that follow it, in Three conferences in four weeks.

Coming up after this week

Microsoft Ignite: November 17 to 20, 2026, San Francisco.
AKS: Kubernetes 1.34 reaches community end of life in November 2026, and 1.31 LTS ends the same month, per the AKS release calendar.
AWS re:Invent: November 30 to December 4, 2026, Las Vegas, with a free livestream registration for keynotes.
Amazon EKS: Kubernetes 1.34 leaves standard support on December 2, 2026.

Where is it heading? (analysis)

This is our reading, not a vendor statement. The three providers now publish runtime lifecycles in a similar shape: a deprecation date tied to the language’s own end of support, followed months later by a hard stop on creating or updating functions. The gap between those dates is your real migration window, and it differs by provider: about six months on Cloud Run functions before decommission, and nine to ten months on Lambda before creates and updates are blocked. Expect the same pattern when Node.js and Python versions age out, and expect platform teams to track runtime dates in one place across clouds rather than per service.

What should I do?

Platform teams: inventory every function and web app still on .NET 8, .NET 9 or the Azure Functions in-process model, across all three clouds, and set .NET 10 as the default in templates.
Operations teams: put the hard dates on the calendar now: May 10, 2027 for Cloud Run functions, July 29 and August 31, 2027 for Lambda. Plan releases so no emergency fix lands after updates are blocked.
Security and governance teams: treat .NET 8 workloads as unpatched from November 10 and record any exception with an owner and an end date.
Everyone following KubeCon remotely: bookmark the CNCF YouTube channel and pick the AI inference and agent sessions to watch once recordings post.

New to the site? Start with Welcome to azCloudOps.

Discuss: how are you tracking runtime end-of-support dates across Azure, AWS and Google Cloud, and which .NET 8 workload will be hardest to move? Share your approach in the comments.

Sources

Last verified: November 9, 2026