MC1222981: SharePoint: Migrate the Maps web part to Azure Maps

The SharePoint Maps web part will migrate from Bing Maps to Azure Maps starting March 2026, completing by mid-April. Key changes include renaming, removal of business entity search, limited autosuggestions for some Asian languages, and removal of bird’s eye and street view. Admins should update a...

🚨
Major Update: This post contains a significant change that may impact your organisation.

[Introduction]

We’re updating the SharePoint Maps web part to use Azure Maps as its data provider. This migration modernizes the mapping experience, improves reliability, and aligns SharePoint with Microsoft’s long-term mapping platform strategy. Most existing functionality will continue to work as expected.

[When this will happen:]

General Availability (Worldwide, GCC): Rollout will begin in early March 2026 and complete by mid-April 2026.

[How this affects your organization:]

Who is affected:

  • Organizations using the SharePoint Maps web part (formerly Bing Maps) on modern SharePoint pages.
  • Admins responsible for allowlists, network security, or governance of SharePoint sites.

What will happen:

  • The Bing Maps web part will be renamed to Maps.
  • Azure Maps services are currently available except in China
  • Place and Address search will continue to work.
  • Business Entity search (searching for organizations or points of interest by name) will no longer be supported.
  • Autosuggestions will no longer support Chinese, Japanese, or Korean.
  • Bird’s eye and Street view modes will be removed, with automatic fallback to Road view.
  • No admin toggle is provided; migration occurs automatically.

[What you can do to prepare:]

  • Add atlas.microsoft.com to your organization’s allowlist if applicable.
  • Confirm network access, firewall, and proxy configurations allow traffic to this domain.
  • Review SharePoint pages that use the Maps web part.
  • Communicate this change to site owners or helpdesk staff.
  • Update internal documentation if needed.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.