Does your application use the Windows Maps Platform or UWP Map Control? 

A separate Microsoft mapping deadline needs a focused migration plan 

Most conversations about Microsoft mapping focus on the wider Bing Maps retirement timeline. But if your application uses the Windows Maps Platform APIs or UWP Map Control, you have a separate deadline to plan around. 

Microsoft deprecated these technologies on 8 April 2025 and has confirmed that their supporting backend services will no longer be available after 30 November 2026. Microsoft has directed affected organisations towards an Azure Maps-based replacement. 

That validates the direction. It does not create the migration plan. 

The important work now is understanding how your application uses mapping, what needs to change, and how to move forward without introducing unnecessary cost, complexity, or risk. 

Start with the technology you actually use 

This announcement does not affect every Bing Maps customer. It specifically applies to applications using: 

• Windows Maps Platform APIs 

• Windows UWP Map Control 

Other Bing Maps implementations sit within Microsoft’s broader migration and retirement plans. That distinction is essential. Before committing budget or development time, confirm which APIs, SDKs and controls are present in your application estate. 

A migration built on assumptions can quickly become expensive. A migration built on evidence gives you choices. 

Why dependency discovery comes first 

Windows-native mapping may sit inside an application that has worked reliably for years. The original developers may no longer own it. Documentation may not reflect the current build. Mapping may also support only one part of a much larger workflow. 

Our recommendation is to begin with a structured review of the application and its mapping dependencies. 

 Establish: 

• Where mapping and location services appear in the application 

• Whether the Windows Maps Platform APIs or UWP Map Control are in use 

• Which features and workflows depend on those components 

• Who owns the application, source code and deployment process 

• Which application versions need to be supported 

• How current usage and licensing influence the commercial model 

This gives your technical and commercial teams a shared view of the problem before they start designing the answer. 

Azure Maps is the logical route to assess 

Microsoft has established Azure Maps as the direction for affected applications. For many organisations, assessing an Azure Maps migration is therefore the logical next step. 

But this should not be treated as a simple product swap. A good migration plan needs to consider the application architecture, required services, user experience, authentication, testing, deployment and ongoing commercial model. 

Our mapping specialists can help translate the current implementation into an Azure Maps requirement, identify the relevant services, and shape a migration approach around the way your application actually works. 

Balance the migration with cost and usage 

The technical solution is only part of the decision. Mapping platforms can differ in how services are packaged, consumed, and charged. Existing usage patterns therefore matter. 

Before finalising the target design, we recommend reviewing: 

• Current and expected transaction volumes 

• The services the application genuinely needs 

• Usage peaks, growth plans and geographic requirements 

• Licensing and purchasing options 

• Opportunities to remove unused services or simplify the design 

• The development, testing and operational costs of the proposed approach 

This helps avoid two common mistakes: recreating the existing solution without questioning it or selecting a target design before understanding its ongoing cost. 

Use the deadline to improve the application 

A mandatory technology change can be approached as a like-for-like replacement. It can also be used to strengthen the application. 

Once the dependency is understood, we can help you explore whether the migration should also reduce technical debt, simplify the architecture, improve maintainability, or support future location requirements. The right outcome is not simply a working map after November 2026. It’ is a solution that remains technically and commercially sustainable. 

Build a roadmap your teams can act on 

A useful roadmap connects the announcement to real delivery decisions. It should define: 

• The applications and components in scope 

• The target Azure Maps services and architecture to investigate 

• Technical dependencies and development effort 

• Testing, deployment and application-version considerations 

• Usage, licensing and cost assumptions that need validating 

• Ownership, priorities and a practical delivery sequence 

This is where Grey Matter adds value. We bring mapping knowledge, Microsoft expertise and licensing insight together, helping your stakeholders make one joined-up decision rather than treating technology and cost as separate conversations. 

Start with a Location Intelligence Assessment 

Our Location Intelligence Assessment creates the foundation for that roadmap. We help you: 

• Identify the mapping technologies and dependencies in use today 

• Confirm whether the Windows Maps Platform APIs or UWP Map Control are present 

• Understand the application features and workflows that need further assessment 

• Map current requirements to relevant Azure Maps capabilities 

• Review usage, licensing and cost considerations 

• Create a practical migration roadmap aligned to your technical and commercial priorities 

You leave with clarity on what is affected, what needs investigating, and how to move forward with confidence. 

Do not let the deadline dictate the design 

If your application uses the Windows Maps Platform APIs or UWP Map Control, 30 November 2026 is the date that matters for the supporting backend services. 

Acting early creates space to make deliberate choices. You can understand the dependency, validate the Azure Maps approach, model the cost, and plan the migration around your application and customers. 

The deadline is fixed. The quality of your response is not. 

Ready to plan your migration? 

Talk to our mapping specialists about a Location Intelligence Assessment. We’ll help you identify your dependencies, assess the Azure Maps route, and build a practical migration plan that balances technical requirements with licensing, usage and cost