Azure Maps Traffic APIs v1.0 to Retire March 31, 2028
Microsoft will retire Azure Maps Traffic APIs version 1.0 on March 31, 2028. This impacts specific Traffic Flow and Traffic Incident APIs, requiring users to migrate to newer versions. To avoid service disruptions, customers should transition to the Azure Maps Traffic Incident API version 2025-01-01 and/or Azure Maps Get Map Tile API version 2024-04-01 before the retirement date. All other Azure Maps services remain unaffected.
- →Retirement of Azure Maps Traffic APIs v1.0
- →Recommended Migration Path
- →Impact Scope
Deprecations (1) ›
- Retirement of Azure Maps Traffic APIs v1.0
The Azure Maps Traffic APIs version 1.0, including Get Traffic Flow Segment, Get Traffic Flow Tile, Get Traffic Incident Detail, Get Traffic Incident Tile, and Get Traffic Incident Viewport, will be retired on March 31, 2028. After this date, these APIs will no longer be available or supported, and calls will fail.
Notes (2) ›
- Recommended Migration Path
Users are encouraged to migrate to Azure Maps Traffic Incident API version 2025-01-01 and/or Azure Maps Get Map Tile API version 2024-04-01. Migration instructions are available, and the transition should be completed before the retirement date to ensure continued service.
- Impact Scope
This retirement announcement specifically affects Azure Maps Traffic APIs version 1.0. All other Azure Maps services are not impacted by this change.
https://azure.microsoft.com/en-us/updates/?id=485810
Related releases
- Designing Scalable and Secure Agent-First Platforms with Azure Container Apps Sandboxes Microsoft Azure Blog ·
- Azure on Ensuring Resilience in the AI Era: Beyond Static Diagrams Microsoft Azure Blog ·
- Microsoft Foundry Expands AI Agent Capabilities with New Models, Voice, and Resilient Workflows Microsoft Azure Blog ·
- Azure AI Foundry model Kimi-K2.7-Code 2026-06-12 reaches end of life in 7 days endoflife.date ·
- Azure HorizonDB adds PostgreSQL 18 support in public preview Azure Updates ·
- Azure AI Foundry model gpt-4o 2024-05-13 end-of-life date moved to 2026-12-09 endoflife.date ·