atlas.microsoft.com · DataSubscribeShare
Azure Maps breaking changes
The breaking changes Azure Maps announced that Okapi tracks: 7 in all.
Do you run the Azure Maps API? Make sure your users call it right →
At a glance
- API host
atlas.microsoft.com- Kind
- Data
- Next breaking change
- /route/directions/* version retirement,
- Breaking changes tracked
- 5 breaking changes coming up and 2 already in effect
- Last updated
Coming up 5
-
/route/directions/*Version retirement Stops workingin 511 days -
/route/matrix/*Version retirement Stops workingin 511 days -
/route/range/*Version retirement Stops workingin 511 days -
/traffic/flow/*Version retirement Stops workingin 511 days -
/traffic/incident/*Version retirement Stops workingin 511 days
Already in effect 2
-
GET /map/imagery/*Version retirement Stopped working -
GET /map/tile/*Version retirement Stopped working
Where Okapi reads it
- OpenAPI spec raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/maps/data-plane/Render/stable/2024-04-01/render.json
- OpenAPI spec raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/maps/data-plane/Route/stable/2025-01-01/route.json
- OpenAPI spec raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/maps/data-plane/Search/stable/2026-01-01/search.json
- Announcement learn.microsoft.com/en-us/azure/azure-maps/migrate-render-v1-api
- Announcement learn.microsoft.com/en-us/rest/api/maps/route/get-route-directions?view=rest-maps-1.0
- Announcement learn.microsoft.com/en-us/rest/api/maps/traffic/get-traffic-flow-tile?view=rest-maps-1.0
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub