Azure Retired 20+ Services and APIs in September 2026 — Seven Separate Deadlines, One Table
Nobody announced this as a wave, which is exactly why it is worth a page. Microsoft's own Ending Support in 2026 lifecycle page lists more than twenty Azure services, APIs and SDKs that retired in September 2026, across seven separate dates: September 13, 14, 15, 17, 19, 21 and 30. There was no single headline deadline to circle on a calendar — there were seven, and the September 30 batch alone killed ten distinct things, including an entire desktop-virtualization offering and three generations of Service Bus control-plane APIs.
The September table
Every row is from Microsoft's lifecycle page, checked August 23, 2026; migration targets are the ones Microsoft names in each retirement notice linked from that page.
| Date | What retired | Microsoft's documented path |
|---|---|---|
| Sep 13, 2026 | Computer Vision API v1.0, v2.0, v2.1, v3.0 and v3.1 | Move to a current Computer Vision API version |
| Sep 14, 2026 | Azure Functions 1.x runtime | Upgrade to a supported Functions runtime |
| Sep 14, 2026 | Azure Monitor Data Collector API | Migrate to the Logs Ingestion API (custom logs migration) |
| Sep 14, 2026 | Monitoring support for AKS-Engine | Monitoring for AKS-Engine ended; see the retirement notice |
| Sep 15, 2026 | Activity logs legacy connector & storage integration API | Replaced by diagnostic settings |
| Sep 15, 2026 | Azure Maps Gen1 price tier | Move to a current Azure Maps pricing tier |
| Sep 17, 2026 | Azure Maps Render V1 | Migrate to a current Render API |
| Sep 19, 2026 | Azure Maps Web SDK Map Controls v1.xx | Upgrade the Web SDK map control |
| Sep 21, 2026 | SMART on FHIR proxy in Azure Health Data Services | Transition to SMART on FHIR (Azure Health Data Services) |
| Sep 30, 2026 | Azure API for FHIR (Gen 1 offering) | Migrate to Azure Health Data Services FHIR service |
| Sep 30, 2026 | Azure Virtual Desktop (Classic) | Migrate to current (ARM-based) Azure Virtual Desktop |
| Sep 30, 2026 | Azure FXT Edge Filer | Hardware offering retired; plan replacement storage caching |
| Sep 30, 2026 | Azure Container Registry 2017-03-01 (GA) API | Move to a current ACR API version |
| Sep 30, 2026 | Azure Maps Web SDK v2.0–v2.0.32 + Service Module | Upgrade to a current Web SDK version |
| Sep 30, 2026 | Container Log V1 | Transition to the ContainerLogV2 table |
| Sep 30, 2026 | Get AlertSummary API (Azure Monitor) | Get Alert Smart Groups API retired; see the retirement notice |
| Sep 30, 2026 | Service Bus control-plane APIs v2014-09, v2015-08, v2016-07 | Update Service Bus SDK libraries |
| Sep 30, 2026 | Single URL Ping Test in Application Insights | Transition to standard tests for availability testing |
| Sep 30, 2026 | Track 0 and Track 1 Service Bus SDKs + SBMP protocol | Update to current-track Service Bus SDKs |
| Sep 30, 2026 | Azure Functions v3 runtime on Linux Consumption plans — apps stopped running | Migrate to the Functions v4 runtime |
The three most likely to have caught people
Azure Virtual Desktop (Classic) — September 30
The 2019, pre-ARM release of Azure Virtual Desktop retired outright. Organizations that stood up virtual desktops during the pandemic and had not touched the deployment model since were the exact population still on Classic. The migration to ARM-based Azure Virtual Desktop is documented, but it is an infrastructure migration, not a checkbox — and the date was September 30, 2026.
Azure Functions 1.x — September 14
Functions 1.x dates from 2016–2017, and functions written then have a habit of still quietly running billing jobs and queue processors nobody has looked at in years. Note the separate deadline: the in-process .NET model for Functions retired November 10, 2026 — the same day .NET 8 and PowerShell 7.4 reached end of support — so a team modernizing old Functions has two moves to plan, not one.
And there was a third Functions deadline in this window that was harder than either: per Microsoft's Functions runtime-versions page, function apps still on the end-of-life v3 runtime on Linux in a Consumption plan stopped running after September 30, 2026. That is not "unsupported" — that is the app halting. Microsoft's stated path is migration to the v4 runtime.
Service Bus — September 30, twice
Both the 2014–2016 control-plane API versions and the Track 0/1 SDKs (with the SBMP protocol) retired the same day. Service Bus sits in the middle of order pipelines and integration buses; the client library pinned in a ten-year-old .NET service was precisely the dependency nobody wanted to upgrade in the last week of September.
The tail: October and November were not quieter
September was the cluster, but the same Microsoft page continues: October 1 retired Azure Anomaly Detector, Metrics Advisor, Personalizer and the Translator S2/S4 billing model. October 13 was the fixed-lifecycle giant — Office 2021, Windows 11 24H2 (Home/Pro), the final Windows Server 2012/R2 ESU year, and Windows Server 2022 leaving mainstream support. November 10 took the Functions in-process .NET model, .NET 8, PowerShell 7.4 and Azure IoT Edge 1.5. We cover the on-premises side of that pile-up in the 2026 EOL calendar and the Windows Server 2012 ESU cliff piece.
What to do with this list
Grep is your friend: the API and SDK retirements are findable in code (SharedAccessSignature sr= era Service Bus connection strings, vision/v2.0 and vision/v3.1 endpoints, Functions 1.x runtime settings, Microsoft.ServiceBus Track 0/1 package references). The service retirements are findable in the portal (AVD Classic workspaces, FXT Edge Filers, Gen1 Maps pricing, classic FHIR instances). If a scan of your estate turns up things on this list next to things past their EOL date generally, our Stack Scanner reads a pasted inventory against the full dataset.
Frequently Asked Questions
Which Azure services retired in September 2026?
Per Microsoft's 2026 end-of-support page: Computer Vision API v1.0-v3.1 (September 13); Azure Functions 1.x, the Azure Monitor Data Collector API and monitoring support for AKS-Engine (September 14); the activity-logs legacy connector and Azure Maps Gen1 price tier (September 15); Azure Maps Render V1 (September 17); Azure Maps Web SDK Map Controls v1.xx (September 19); the SMART on FHIR proxy in Azure Health Data Services (September 21); and on September 30: Azure API for FHIR, Azure Virtual Desktop (Classic), Azure FXT Edge Filer, the ACR 2017-03-01 API, Azure Maps Web SDK v2.0-v2.0.32 and its Service Module, Container Log V1, the Get AlertSummary API, Service Bus control-plane APIs v2014-09/v2015-08/v2016-07, the Single URL Ping Test in Application Insights, and Track 0/1 Service Bus SDKs with the SBMP protocol.
Did anything actually stop working on these dates?
For most of the list, yes - these were Modern Lifecycle retirements, not support endings. A retired API version stops answering, a retired SDK's protocol can be turned off, and a retired service offering is closed. That is a harder deadline than a typical end-of-support date, where software keeps running without patches. Check each service's own retirement notice for exactly what happened to existing deployments on the date.
Is Azure Virtual Desktop (Classic) the same as Azure Virtual Desktop?
No. Azure Virtual Desktop (Classic), the 2019 release that predates Azure Resource Manager integration, retired September 30, 2026. Current ARM-based Azure Virtual Desktop continues. Microsoft's guidance is to migrate Classic deployments to the current service.
Is the Azure Functions 1.x retirement the same as the .NET-in-process retirement?
No - three different deadlines. Support for the Functions 1.x runtime ended September 14, 2026. Function apps still running the end-of-life v3 runtime on Linux in a Consumption plan stopped running after September 30, 2026 - the hardest of the three, since the app itself halts. And the separate retirement of the in-process model for .NET apps in Azure Functions came November 10, 2026, the same day .NET 8 and PowerShell 7.4 reached end of support; apps on the in-process model move to the isolated worker model.
What retired right after September?
October 1, 2026: Azure Anomaly Detector, Azure Metrics Advisor, Azure Personalizer, and the Translator S2/S4 billing model. October 13, 2026 was Microsoft's giant fixed-lifecycle day - Office 2021, Windows 11 24H2 Home and Pro, the final Windows Server 2012/R2 Extended Security Update year, and Windows Server 2022's move out of mainstream support. November 10, 2026: the Azure Functions in-process .NET model, .NET 8, PowerShell 7.4 and Azure IoT Edge 1.5.
Where is the authoritative list?
Microsoft's lifecycle page "Ending Support in 2026" (learn.microsoft.com/en-us/lifecycle/end-of-support/end-of-support-2026) and, for each Azure item, the retirement notice linked from it on azure.microsoft.com/updates. Every date in this article was checked against that page on August 23, 2026.