Set up your bannerConfigure Your ToolsMaps

Bing Maps

How to configure Bing Maps at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement Bing Maps and how to reflect it in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configuration is a comparative example, not a guarantee of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. Interactive maps embedded through Bing Maps for Enterprise web controls or REST APIs.

Service status — deprecated. Microsoft has retired Bing Maps for Enterprise. Free and Basic accounts stopped working after 30 June 2025; existing Enterprise licence holders can continue until 30 June 2028; no new customers have been accepted since 30 June 2024. Microsoft directs all customers to migrate to Azure Maps. This guide therefore documents only the remaining Enterprise use and recommends migration planning.

Simplified format. Microsoft publishes no privacy configuration options for Bing Maps web controls (such as IP truncation, cookie control or retention settings) in the sources reviewed. The guide therefore uses a single fixed-behaviour table.

Consent. Loading a map sends the visitor's IP address and request headers to Microsoft. Load the map only after consent (for example, behind a click-to-load placeholder).

Step 1 — Configure Bing Maps

Configuration areaFixed behaviour / required action
Processing purposesUnlock additional website features (interactive map)
Account typeEnterprise licence only; Free/Basic keys no longer function after 30 June 2025
LoadingBlocked by Consenter until consent; static placeholder before consent
Privacy settings in the serviceNot documented
Retention at MicrosoftNot documented
End of service30 June 2028 at the latest

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresMap display.
Tracking methodNo trackingNo identifier documented for the map control. Re-assess if browser inspection shows Microsoft cookies set by the map.
IdentifierIP addressTransmitted with each tile and API request.
Data categoriesIP address, Device characteristics, Non-precise location dataMap viewport and search queries reveal approximate locations of interest; add "Precise location data" if the browser location is passed to the map.
Legal role of data recipientIndividual ControllerNo processor terms for map display were found in the sources reviewed; verify against your Enterprise licence agreement.
Personalisation modelNo personalisation—
Maximum storage durationNot documented—
Processing locationUnited States as potential processing and access locationMicrosoft Corporation is a US company subject to the US CLOUD Act.

Privacy-policy follow-up

  • Microsoft as recipient; data transmitted when the map loads; consent; US transfer and potential access by US authorities; planned migration to Azure Maps.

Verification checklist

  • No request to Bing Maps domains before consent.
  • Browser inspection after consent: record any cookies set and update the mapping.
  • Migration to Azure Maps scheduled before the licence ends.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page