📞 720.836.7201 ✉ Info@OnTerraSystems.com | ⭐ Trusted Partner: Bing Maps · Azure Maps · HERE Technologies

Bing Maps WPF Control Discontinuation Occurs On June 30, 2028Will Your Business & Applications Be Affected?

Microsoft is retiring Bing Maps for Enterprise on June 30, 2028. After that date, desktop applications built on the Bing Maps WPF Control won’t be able to reach the services on which they depend. OnTerra Systems helps you move to Azure Maps – without rewriting your WPF application.

Assess My Situation – Contact OnTerra Systems →
Bing Maps WPF Control Retiring June 30, 2028

What’s Changing? The Bing Maps WPF Control Is Being Retired Along With Bing Maps For Enterprise

Microsoft has deprecated the Bing Maps WPF Control as part of its broader move to retire Bing Maps for Enterprise and unify its mapping services under Azure Maps. The control still functions today, but it no longer receives updates.

As stated in Microsoft’s Bing Maps WPF Control documentation, support for Bing Maps for Enterprise customers ends on June 30, 2028. After that date, applications built on the Bing Maps WPF Control will no longer be able to load maps or connect to the Bing Maps services behind them.

Microsoft’s recommended path is to migrate to Azure Maps, typically by hosting the Azure Maps Web SDK in a WebView2 control inside the WPF application. That covers most of what the Bing Maps WPF Control does. But not every Bing Maps capability has a direct Azure Maps equivalent.

What Functions Will Be Affected By The Bing Maps WPF Control Discontinuation?

  • Road, Aerial, and AerialWithLabels map modes
  • Pushpins, polylines, and polygons
  • Images and other media on the map
  • Tile overlays and map events
  • Bing Maps REST and Spatial Data Services for geocoding, routing and data storage – all retiring on the same schedule

Bing Maps Retirement Timeline

  1. June 30, 2025Passed

    Support ended for free Bing Maps Basic accounts.

  2. November 30, 2026Upcoming

    Backend services for the Windows UWP Map control are retired.

  3. June 30, 2028Upcoming

    Bing Maps for Enterprise and the Bing Maps WPF Control are retired. Applications can no longer load maps.

How OnTerra Systems Can Help With the Bing Maps WPF Control Discontinuation

OnTerra Systems has the expertise & credentials to provide migration support for a whole solution, not just API calls. OnTerra Systems has been a trusted partner of Microsoft since 2005 – with 20+ years of web mapping and geospatial development, including proof-of-concept work, pilot programs and migration implementation done directly with Microsoft customers.

Here’s a step-by-step look at how OnTerra Systems can help:

Step 1: Assess your implementation

We inventory what your WPF applications actually use – map modes, pushpins and shapes, media, tile overlays, REST and Spatial Data Services calls – so we know exactly what needs to move and what needs a workaround before June 30, 2028.

Step 2: Manage migration to Azure Maps

API mapping, WebView2 implementation for your WPF application, data and layer conversion, and testing. This is the same approach we’ve used to move other customers onto Azure Maps, so the parts of your application that transfer cleanly do, without a rebuild from scratch.

Step 3: Solve the remaining gaps

For anything Azure Maps doesn’t cover – specific imagery, map styles, or Bing Maps services on which your application relies – we design and build alternatives using other imagery providers or custom geospatial services.

Also running a Windows UWP application built on the UWP Map control? Its backend services are being retired much sooner, on November 30, 2026, per Microsoft’s announcement. OnTerra Systems also builds alternative solutions for UWP applications, so you are covered with that too. Read our UWP Map Control retirement guide →

Frequently Asked Questions About The Bing Maps WPF Control Retirement

When does the Bing Maps WPF Control stop working?

Support for Bing Maps for Enterprise customers ends on June 30, 2028. After that, applications built on the control can’t load maps or connect to Bing Maps services. Support for free Basic accounts already ended on June 30, 2025.

Our application works fine today. Why act now?

The control still functions, but it no longer receives updates. Starting assessment and migration planning well ahead of the deadline leaves time to evaluate options, test the new implementation and address any feature gaps.

What does Microsoft recommend instead?

Microsoft recommends migrating to Azure Maps, its modern maps and geospatial platform – typically by hosting the Azure Maps Web SDK in a WebView2 control inside your WPF application.

Do we need to rewrite our app in WinUI, .NET MAUI, Blazor or for the browser?

Not necessarily. A full rewrite can be very time-consuming and often is unnecessary. The OnTerra Systems WPF Map Control lets you keep your WPF application and move its maps to Azure Maps.

How much of our code will have to change?

Very little. You replace the Bing Maps WPF Control NuGet package with the OnTerra Systems package, and its middle-layer wrapper translates your existing Bing Maps calls into Azure Maps equivalents — no refactoring of your map logic.

What if Azure Maps doesn’t support a feature we need?

Not every Bing Maps capability has a direct Azure Maps equivalent, such as specific imagery, map styles or services that don’t carry forward. In those scenarios, we design and build alternatives using other imagery providers or custom geospatial services.

Are the Bing Maps REST and Spatial Data Services affected too?

Yes. The geocoding, routing and data storage services WPF applications typically call are being retired on the same schedule, and we include them in the assessment.

How do we get access to the OnTerra Systems WPF Map Control?

Contact OnTerra Systems to get access or to talk through how it fits your application.

Plan Your Migration While There’s Still Time To Do It Right.Contact OnTerra Systems today!

Start with an assessment of your WPF application. We’ll map what moves cleanly to Azure Maps, what needs a workaround, and how to get there with minimal changes to your code.

Contact OnTerra Systems →