What replaces Bing Maps? Why Azure Maps is the natural successor
Blog|by Jamie Carruthers|3 September 2026
What replaces Bing Maps? Why Azure Maps is the natural successor
If your applications or operations rely on Bing Maps, you need a clear plan for what comes next.
Bing Maps for Enterprise will retire on 30 June 2028. That creates a firm deadline, but it also presents an opportunity to protect business continuity, reduce technical risk and build greater value into your location strategy. Microsoft encourages existing Bing Maps for Enterprise clients to move to Azure Maps, where its latest mapping developer innovation is focused.
Whether you use Bing Maps for routing, geocoding, traffic information, asset tracking or customer-facing applications, the choices you make now will shape how smoothly your transition unfolds.
The good news is that Microsoft’s recommended successor is already here.
Azure Maps carries forward many of the mapping and geospatial services available through Bing Maps while adding new options for authentication, compliance, weather, geolocation and integration with the wider Azure ecosystem.
This means you can approach Bing Maps end of life as more than a replacement project. You can use it to reassess performance, control costs, modernise your applications and turn location data into a stronger source of business insight.
What does Bing Maps end of life mean for you?
Bing Maps often sits quietly behind important applications and workflows. It works in the background, so its reach isn’t always obvious.
Your dependency could extend beyond a map on a screen. It may include API endpoints, authentication, routing logic, search, data models, usage limits, reporting processes and client commitments. Over time, these dependencies can become deeply established and poorly documented.
That makes the key question bigger than “What replaces Bing Maps?” You also need to ask:
- Where is Bing Maps used across our applications and services?
- Which capabilities are business-critical?
- What happens if those services are disrupted?
- How will alternative pricing models affect our costs?
- Can we improve performance, scalability or security as we move?
- What will our products and operations need over the next few years?
Answering those questions early gives you more control. Waiting until the deadline is close restricts your options and can turn a planned transition into an urgent technical exercise.
Why is Bing Maps for Enterprise being retired?
Microsoft is unifying its enterprise mapping products under Azure Maps. Bing Maps for Enterprise services and product support will end on 30 June 2028, while the consumer-facing Bing Maps service remains separate.
The change gives Microsoft one strategic enterprise mapping platform through which to deliver ongoing innovation, Azure integration and location-based services. Microsoft describes Azure Maps as its best-in-class Maps API platform and the focus for its newest developer innovation.
For you, this creates a clear direction. If you want to remain within the Microsoft ecosystem, Azure Maps is the natural place to begin your evaluation.
What is Azure Maps?
Azure Maps is a collection of mapping and geospatial services designed for web, mobile and server-side solutions.
It can bring maps, geocoding, location search, routing, real-time traffic, geolocation, time-zone information and weather into your applications. As an Azure service, it also benefits from Azure security and compliance capabilities.
Azure Maps supports services including:
- Maps and visualisation
- Geocoding and reverse geocoding
- Location and points-of-interest search
- Routing and truck routing
- Route matrices and isochrones
- Real-time traffic information
- Weather maps and APIs
- Geolocation
- Time-zone information
- Spatial operations and analytics
This makes Azure Maps more than a visual map control. It provides the building blocks to add location context to applications, products, data and operational decisions.
Azure Maps vs Bing Maps: what do you lose and gain?
A migration will involve change. APIs, SDKs, authentication, response formats, licensing and transaction calculations may differ, so Azure Maps shouldn’t be treated as a direct drop-in replacement without assessment and testing. Microsoft recommends taking an inventory of the Bing Maps APIs and SDKs in use, comparing them with Azure Maps services and evaluating licensing and billing differences.
However, the move also gives you access to capabilities and controls that Bing Maps for Enterprise doesn’t provide.
| Area | What changes with Bing Maps | What you gain with Azure Maps |
|---|---|---|
| Product lifecycle | Bing Maps for Enterprise retires on 30 June 2028 | Microsoft’s strategic enterprise Maps API platform |
| Innovation | New developer innovation is no longer centred on Bing Maps | Microsoft’s strategic enterprise Maps API platform |
| Authentication | Bing Maps commonly uses API-key authentication | Shared Key, Microsoft Entra ID and Shared Access Signature options |
| Mapping services | Existing implementations may require new endpoints, parameters or formats | Maps, geocoding, routing, search, traffic and related geospatial services |
| Compliance | Existing requirements need to be reassessed during migration | Azure compliance capabilities and data residency support |
| Weather | Existing implementations may need separate review | Azure Maps weather maps and Weather APIs |
| Geolocation | Current Bing Maps usage needs to be mapped to an equivalent service | Azure Maps Geolocation APIs |
| Azure management | Bing Maps agreements and administration use a different model | Azure resource management and programmatic account management |
| Commercial model | Existing Bing Maps licensing doesn’t transfer on a like-for-like basis | Azure consumption-based licensing and billing |
| Wider ecosystem | Integration depends on your existing architecture | Direct access to other Azure services and Azure Marketplace options |
The real value isn’t simply that Azure Maps can cover much of the same functional ground. It’s that you can use the transition to improve how your location services are secured, managed, scaled and connected to your wider technology estate.
Why Azure Maps is more than a Bing Maps replacement
A like-for-like replacement may keep an application running. It doesn’t necessarily make the application better.
The strongest migration strategies review what location technology needs to achieve now, not what it was configured to do several years ago.
Build on a platform with a future
Azure Maps is where Microsoft is focusing its enterprise mapping innovation. Moving gives you a clearer long-term direction than continuing to invest in a platform with a confirmed retirement date.
Strengthen authentication and access
Azure Maps supports multiple authentication methods, including Shared Key, Microsoft Entra ID and Shared Access Signature tokens. This gives you more options for aligning access to your application architecture and security requirements.
Connect location services with Azure
Because Azure Maps sits within Azure, you can manage it alongside other Azure resources and integrate it with additional Azure services where they support your use case.
Turn location data into practical insight
Azure Maps adds further geospatial capabilities, including weather, geolocation and spatial operations. These can help you move beyond displaying location and start using it to enrich applications and support operational decisions.
This doesn’t mean you need to undertake a full cloud transformation. If your immediate priority is continuity, you can take a focused API-level approach by replacing Bing Maps services with their Azure Maps equivalents.
The value will depend on your use case. That’s why migration should begin with discovery rather than a predetermined technical answer.
Is Azure Maps the best Bing Maps alternative?
For many clients already using Microsoft technologies, Azure Maps will be the natural successor. It offers familiar core services, sits within the Azure ecosystem and represents Microsoft’s strategic direction for enterprise mapping.
But the right platform should be based on fit, not assumption.
Your decision should account for:
- The APIs and SDKs you use today
- Geographic coverage and data requirements
- Routing and traffic needs
- Application architecture
- Security and data residency requirements
- Expected transaction volumes
- Cost predictability
- Future product and market plans
Azure Maps is the focus of this article because it’s Microsoft’s recommended route forward. However, our role is to help you choose the platform that best supports your technical, operational and commercial requirements.
When should you start your Bing Maps migration?
Now is the right time to start assessing your position.
That doesn’t mean rushing into development. It means gaining enough clarity to make decisions on your terms.
Microsoft’s suggested migration approach begins with taking an inventory of the Bing Maps APIs and SDKs your application uses, comparing available Azure Maps services, reviewing licensing and billing, updating the application, then testing before deployment.
Starting early gives you space to:
- Identify dependencies across applications and services
- Confirm which features are essential
- Compare Azure Maps services with your current Bing Maps implementation
- Understand potential transaction and pricing differences
- Test accuracy, performance and behaviour
- Plan a controlled migration
- Avoid unnecessary pressure as 30 June 2028 approaches
A fixed deadline. A controlled route - The deadline is fixed. Your route towards it doesn’t need to be rushed.
Before you migrate, understand what you’re really using
One of the biggest risks is underestimating how deeply location services are embedded across your products, applications and operations.
Mapping is rarely isolated. It can extend across workflows, APIs and data pipelines, with dependencies that may not be obvious until migration work begins. Discovery brings those connections into focus before you commit to a platform or project plan.
That’s why we recommend starting with our free Location Intelligence Assessment.
Start with a Location Intelligence Assessment
Our Location Intelligence Assessment gives you clarity before change.
We review how location services support your applications and systems today, explore your future goals and assess whether your current approach will remain reliable, scalable and commercially viable. You’ll also speak with our mapping specialists to work through the findings, trade-offs and opportunities in practical terms.
What the assessment helps you understand
- Map where Bing Maps is used across your applications and services
- Identify business-critical APIs, SDKs and data dependencies
- Surface technical, operational and commercial risks
- Assess Azure Maps readiness
- Compare migration and optimisation paths
- Review cost, scale and performance considerations
- Explore where location intelligence could create more value
- Define practical next steps that support continuity
The goal isn’t to steer you towards a platform before understanding your requirements. It’s to give you an expert, impartial view of your current location stack and a sensible direction forward.
Why the assessment matters
A Bing Maps migration affects more than code.
It can influence application performance, infrastructure, budgets, product roadmaps and the experience you deliver to your own clients. Treating the move as a basic API swap risks carrying old inefficiencies into a new platform.
The assessment helps you step back and ask better questions:
- Are you paying for services you no longer need?
- Does your architecture reflect current usage?
- Will your chosen platform scale predictably?
- Could better location intelligence improve your products or operations?
- Which risks need to be resolved before development begins?
You leave with clear guidance based on fit, not vendor preference. No guesswork. No unnecessary complexity. Just a stronger starting point for the decisions ahead.
What should you do next?
If you use Bing Maps for Enterprise, start by confirming:
- Which applications and services depend on it
- Which APIs, SDKs and capabilities are in use
- How your existing agreement aligns with the retirement timeline
- What your transaction volumes and growth plans look like
- Which technical, commercial and compliance requirements a replacement must meet
From there, you can compare Azure Maps with your requirements, test the services that matter and build a migration roadmap around business continuity and long-term value.
The clock is ticking, but so is the opportunity
Bing Maps for Enterprise retirement creates a deadline. Azure Maps creates a way forward.
Microsoft’s strategic platform offers many of the services Bing Maps clients already use, alongside additional authentication, compliance, weather, geolocation and Azure management capabilities.
But choosing a successor is only part of the decision.
The bigger opportunity is to understand how location technology supports your business, where risk or inefficiency exists and how a modern location strategy could deliver more value.
Our free Location Intelligence Assessment gives you that clarity. We’ll help you review your current environment, assess Azure Maps readiness and define practical next steps, so you can move before the deadline without being driven by it.