Serverless runtime support dates

1. Each table comes from the vendor's own page. We copy the dates as the vendor prints them.
2. Some dates are only a month or a part of a year. We show that text as it is. We never turn it into a day, and we do not count days to it.
3. Ending soon means the next key date is in the next 90 days. We count days from today.
4. What to do opens our page about that change, when we have one.
5. If a vendor moves a date, we fix the table after we check the vendor page.

Cloud Run functions runtime support schedule

What the dates mean, in short, from Google Cloud's pages: Google states that the deprecation date starts the deprecation period, during which you can generally still create and update workloads on the runtime but should migrate, and that the decommission date starts the decommission period, after which you can no longer create or update workloads on the runtime and existing workloads may be disabled; a blank date means that phase is not yet scheduled, Go dates may be postponed under Go's release policy, and the Cloud Run source-deploy runtime page (s2) prints identical dates for every runtime listed here.

• Runtime support | Cloud Run functions · Google Cloud · read October 22, 2026
• Cloud Run runtime lifecycle · Google Cloud · read October 22, 2026

App Engine standard runtime support schedule

What the dates mean, in short, from Google Cloud's pages: Google states that at end of support it stops applying security updates and patches to the runtime and you can no longer create or update apps on it, although existing apps keep running and serving traffic (deployments can sometimes be re-enabled by organization policy); at deprecation the ability to re-enable deployments is removed; and after decommissioning apps still on the runtime may be disabled without further notice. The schedule page prints no GA dates, blank cells are not explained on the page, and key dates may be delayed (Go dates depend on newer Go releases).

• Runtime support schedule | App Engine standard environment · Google Cloud · read October 22, 2026
• Runtime lifecycle | App Engine standard environment · Google Cloud · read October 22, 2026

Azure Functions language support schedule

What the dates mean, in short, from Microsoft's pages: Each date is the expected end-of-support date (the Java table says "Supported until") for that language stack version on Functions runtime v4.x, the only runtime version the page lists; Microsoft states that support ends on the earlier of the language community's end-of-support date or the base operating system's, and that after it apps on the retired version can still be created, deployed and run but get no new features, security patches or performance optimizations and may be limited to fewer instances. The in-process .NET model itself loses support on November 10, 2026, .NET 9's date was extended from May 12, 2026, and each Go major release is supported until two newer major releases are available.

• Supported languages in Azure Functions · Microsoft Learn · read October 22, 2026
• Azure Functions language stack support policy · Microsoft Learn · read October 22, 2026