Azure Maps
/route/directions/* version retirement
Stops workingSubscribe to Azure MapsShare
On March 31, 2028, Azure Maps will retire Route v1 directions endpoints. After this date, requests to /route/directions/* will fail. Calls must be transitioned to the newer service version to avoid disruptions.
Calls it hits
/route/directions/*
What to use instead of these calls
Update requests to call POST /route/directions?api-version=2025-01-01 with a GeoJSON body. Send batch requests to /route/directions:batch instead.
In Azure Maps's words
The Azure Maps Route v1 service is now deprecated and will be retired on 3/31/28. To avoid service disruptions, all calls to Route v1 service will need to be updated to use Route v2025-01-01 service by 3/31/28.
Facts
- API
- Azure Maps
atlas.microsoft.com - Kind
- Version retirement
- Takes effect
- March 31, 2028
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Azure Maps's own pages
Questions
When does this change take effect?
Calls to /route/directions/* on Azure Maps stop working on March 31, 2028.
What happens to calls after March 31, 2028?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Azure Maps 6
-
GET /map/imagery/*Version retirement Stopped working -
GET /map/tile/*Version retirement Stopped working -
/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
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before March 31, 2028.