Bing Maps for Enterprise stops working on Basic (free) account keys
Stopped workingSubscribe to Bing Maps APIShare
Calls to its endpoints on Bing Maps API stopped working on June 30, 2025.
What to use instead of these calls
Move geocoding, routing, and map calls to Azure Maps (atlas.microsoft.com) using an Azure Maps account key or Microsoft Entra ID. Staying on Bing Maps requires a paid Enterprise licence, whereas moving to Azure Maps requires an Azure subscription and a new key.
Staying on Bing Maps needs a paid Enterprise licence; moving to Azure Maps needs an Azure subscription and a new key.
In Bing Maps API's words
After June 30, 2025, Basic keys in Basic accounts will no longer function. This includes access to APIs like Geocoding, Routing, and Spatial Data Services and the Bing Maps SDKs
Facts
- API
- Bing Maps API
dev.virtualearth.net - Kind
- Removal
- Takes effect
- June 30, 2025
- Calls after that day
- Fail
- Who it affects
- Basic (free) account keys
- Source
- Announcement
- Last updated
- Verified
- , against Bing Maps API's own pages
Questions
When does this change take effect?
Calls to its endpoints on Bing Maps API stopped working on June 30, 2025.
What happens to calls after June 30, 2025?
They have failed since June 30, 2025.
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 Bing Maps API 5
-
/REST/v1/Routes/DistanceMatrixParameter removal Stopped working -
/REST/v1/Routes/FromMajorRoadsEndpoint removal Stopped working -
/REST/v1/Routes/LocalInsightsEndpoint removal Stopped working -
/REST/v1/Routes/DistanceMatrixParameter removal Stopped working - Bing Maps for Enterprise stops working Stops workingin 602 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.