Bing Maps migration guide: everything you need to know before June 2028

If you’re planning a Bing Maps migration, now is the time to understand your position and take control of what comes next. 

Microsoft has confirmed that Bing Maps for Enterprise will retire on 30 June 2028. For clients that depend on mapping APIs, routing, geocoding, search, traffic intelligence or location-enabled applications, it’s a fixed deadline. It also creates an opportunity to make your location strategy work harder. 

A successful Bing Maps transition is not simply an endpoint swap. It starts with understanding where Bing Maps sits across your products and operations, which services matter most, how your usage is changing and what your future platform needs to deliver. 

This guide explains the Bing Maps retirement timeline, how to prepare, which replacement options to assess and why clarity should come before vendor selection. 

What is happening to Bing Maps for Enterprise? 

Bing Maps for Enterprise is deprecated. Microsoft states that Enterprise account clients can continue using its services until 30 June 2028, while free Basic accounts have already been retired. Enterprise clients using Bing Maps REST APIs and SDKs need to update their applications before the retirement date to avoid disruption. 

The change applies to Bing Maps for Enterprise, not the consumer-facing Bing Maps experience. Microsoft is directing enterprise mapping investment towards Azure Maps and provides migration guidance covering platform comparisons, licensing, billing and technical planning. 

If you need a quick view of the existing platform and the services that may be embedded in your application, review Bing Maps. 

Quick answer 

A Bing Maps migration is the process of moving applications, APIs, SDKs and location workloads away from Bing Maps for Enterprise before 30 June 2028.

Why Bing Maps retirement matters to your business  

Mapping often looks like one feature. In practice, it can support critical workflows across routing, address validation, geocoding, fleet management, logistics, asset tracking, field services, store locators and customer-facing applications. 

Those dependencies are not always documented in one place. An application may call several APIs, pass location data into downstream systems and rely on transaction volumes or licensing terms established years ago. A rushed replacement can expose gaps in performance, cost control, data quality or user experience. 

That’s why Bing Maps end of life is not only a developer issue. It can affect business continuity, product roadmaps, budgets and the experience you provide to your clients. The earlier you understand that exposure, the more choice you retain. 

What should you do before starting a Bing Maps migration? 

Don't begin by choosing a vendor. Begin by understanding what you already have. 

Your first task is to build a clear baseline of how Bing Maps supports your applications and operations.  

Review: 

• The Bing Maps APIs, SDKs and keys currently in use 

• The applications, workflows and clients that depend on them 

• Transaction volumes, regional usage and expected growth 

• Current performance, accuracy and reliability requirements 

• Security, compliance and data residency needs 

• Commercial terms, renewal dates and internal budgets 

• New features or markets on your product roadmap 

This discovery work shapes your entire Bing Maps migration plan. It helps you separate business-critical capabilities from features that are no longer needed, identify risks early, and compare platforms against evidence rather than assumptions. 

Our Location Intelligence Assessment provides a structured starting point. Our mapping experts review your current location stack, goals, cost model, performance requirements and readiness for change, then provide you with practical recommendations based on fit rather than vendor preference. 

How to start a Bing Maps migration 

A controlled Bing Maps migration can be approached in five clear stages: 

1. Inventory your current Bing Maps services, APIs, SDKs, keys and data flows. 
2. Define the technical, operational and commercial outcomes the replacement must support. 
3. Compare suitable mapping platforms against those requirements. 
4. Test priority services for accuracy, performance, behaviour and cost. 
5. Plan a phased rollout with monitoring, validation and a clear cutover path. 

Microsoft’s own migration overview also recommends taking an inventory, comparing Bing Maps features with Azure Maps, reviewing licensing and billing differences, updating application code, then testing before deployment. 

Understanding your Bing Maps migration options 

There ‘s no single platform that suits every mapping workload. Your strongest option will depend on your technology stack, data requirements, routes, regions, users and commercial priorities. Three platforms are likely to feature in many evaluations. 

Azure Maps 

Azure Maps Microsoft’s strategic enterprise mapping platform. It provides mapping and geospatial services for web, mobile and server-side solutions, including maps, geocoding, search, routing, real-time traffic, geolocation, time-zone information and weather. 

It’s a natural starting point if you want to remain within the Microsoft ecosystem or connect location services with wider Azure resources. However, its services, authentication, transaction calculations and billing should still be assessed against your current implementation. Explore the Azure Maps services or read Microsoft’s Bing Maps migration guidance.

HERE Technologies 

HERE Technologies offers map data, APIs, SDKs and location services that support mapping, search, routing, fleet operations, navigation and location-aware applications. HERE’s map data can be accessed in multiple formats and enriched with layers such as roads, points of interest, postal code points and dynamic datasets. 

This makes HERE relevant where global map data, logistics, commercial vehicle routing, mobility or flexible data use are central to the requirement. Review the official HERE map data platform for its current map data options. 

TomTom 

TomTom provides application-ready maps, routing, real-time traffic, APIs and SDKs. Its location intelligence services include geocoding, map display and traffic insights, supporting use cases across fleets, mobility, public services, insurance, retail and software products. 

TomTom may be relevant when routing, traffic data, place information or location analytics are central to the workload. Explore the official TomTom location intelligence solutions for more detail. 

What replaces Bing Maps? 

Azure Maps is Microsoft’s recommended enterprise successor, but that doesn't make it the automatic answer for every use case. HERE Technologies, TomTom and other location platforms may align differently with your architecture, routing requirements, data strategy or cost model. 

The right Bing Maps replacement is the platform that protects continuity while supporting your next stage of growth. That decision should be based on your requirements, not the broadest feature list or the loudest vendor claim. 

Our upcoming What replaces Bing Maps? and Best Bing Maps alternatives articles will explore these discovery questions in more detail. 

How to evaluate a Bing Maps alternative 

Use a consistent decision framework so every platform is assessed against the same priorities. 

Coverage and data quality 

Confirm coverage across the regions you serve and test the map, address, road, point-of-interest and traffic data that your use case depends on. 

Routing and geocoding 

Validate route behaviour, commercial vehicle requirements, matrix calculations, address matching and reverse geocoding against real scenarios. 

Developer experience 

Review APIs, SDKs, documentation, authentication, response formats, samples and the effort required to maintain the integration. 

Performance and scale 

Test expected and peak volumes. Consider latency, availability, batch workloads and how the service behaves as your usage grows. 

Security and compliance 

Assess identity, access, data handling, governance, residency and compliance requirements with your technical and security teams. 

Commercial model 

Compare how transactions are counted, how usage is billed and how growth could affect cost predictability. 

Roadmap and fit 

Choose for the product and operation you are building, not only the application you are replacing. 

For a broader decision framework, use the future How to choose a Bing Maps replacement guide. 

Why Bing Maps migration planning should start now 

Starting now does not mean rushing into development. It means creating enough space to make decisions on your terms. 

A migration can involve discovery, procurement, architecture, development, testing, security review, client communication and deployment. Compressing that work increases pressure and reduces your room to resolve unexpected differences between platforms. 

Early Bing Maps migration planning gives you time to test services side by side, understand cost behaviour, phase the rollout and protect customer experience. It also creates space to improve what you have rather than recreate legacy decisions on a new platform. 

For the deeper timing and delivery discussion,refer to Bing Maps migration planning. 

Use migration to improve location intelligence 

A Bing Maps migration protects continuity. A stronger location strategy can create wider value. 

Location data provides geographic context. Location intelligence combines that data with mapping, spatial analysis and business context to help you make better decisions. That may mean improving routes, strengthening asset visibility, identifying service gaps, enriching analytics or building more useful location-aware products. 

If you want to build that wider understanding, start with What is location data? and What is location intelligence?. For the next stage of the conversation, explore how AI and location intelligence can connect geographic context with analytics and AI-driven decisions. 

Common Bing Maps migration mistakes 

Treating migration as a simple API swap 

Endpoints may be only one part of the change. Authentication, formats, transaction calculations, data flows and user experience also need review. 

Comparing vendors before defining requirements 

A feature comparison is weak if you have not agreed what the platform must achieve. 

Testing only the happy path 

Use real addresses, routes, regions, traffic conditions and peak workloads to expose meaningful differences. 

Focusing only on the headline price 

Model cost alongside capability, implementation effort, reliability and expected growth. 

Waiting for the deadline 

Late planning turns a controlled decision into a forced one. 

Start with a Location Intelligence Assessment 

Every successful Bing Maps migration starts with a clear view of the current environment. 

Our Location Intelligence Assessment is designed for development teams that need location services to remain reliable, scalable and commercially viable. We review how location intelligence is implemented across your stack today, what it needs to support next and where risk, inefficiency or opportunity may exist. 

The assessment can cover: 

• Platform architecture, APIs, SDKs, data sources and integrations 

• Product, operational and commercial goals 

• Current usage, billing and cost exposure 

• Capability, performance and regional requirements 

• Bing Maps dependencies and migration readiness 

• Suitable platforms and practical next steps 

You receive an impartial view of the options and practical recommendations aligned with your roadmap and budget. You can take those recommendations forward internally or ask us to support the next stage. The decision stays with you.