Set up your bannerConfigure Your ToolsMonitoring and Performance

Azure Application Insights

How to configure Azure Application Insights at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service

Overview

This guide explains how to implement different privacy configurations for Azure Application Insights and how to reflect them in the Consenter Manager.

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

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. This guide covers the Application Insights JavaScript SDK (browser monitoring: page views, performance, exceptions, dependency calls) as part of Azure Monitor. Server-side telemetry from the operator's own backend is out of scope.

What the service does in this scope. The SDK sends page views, timings and errors to the operator's Application Insights resource. By default it uses cookies to recognise users and sessions; the disableCookiesUsage setting stops the SDK storing or reading any cookie data. Microsoft notes that without cookies some features are lost, as each page view is treated separately.

Legal role. Application Insights is an Azure service used under the operator's Azure subscription; Microsoft processes customer data as processor under the Microsoft Products and Services Data Protection Addendum (DPA).

Configurations included.

ConfigurationSummary
Configuration A — Lower riskCookies disabled (disableCookiesUsage: true); performance and error monitoring without persistent identifiers; resource in an EU region.
Configuration B — Medium risk (default)Cookies enabled (default); users and sessions recognised across page views and visits; loaded only after consent.

⚠ Recommendation — Configuration A without consent is legally uncertain. With cookies disabled, the SDK does not store or read cookie data, so § 25 TDDDG may not be triggered by cookies. The script still runs in the browser and transmits page and device data. Whether loading it without consent is permissible depends on your assessment of the GDPR legal basis (legitimate interest in error and performance monitoring) and on whether any other storage (such as session storage buffering) is used. Document the reasoning and have it reviewed by your DPO or independent counsel; otherwise load A only after consent.

ActionConfiguration A — Lower riskConfiguration B — Medium risk (default)
disableCookiesUsagetruefalse (default)
LoadingSee ⚠ recommendationBlocked until consent
Resource regionEU regionEU region (recommended)
Consenter Manager entriesOne entry (Microsoft as Processor)One entry (Microsoft as Processor)

Step 1 — Configure Application Insights

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium risk (default)
1Processing purposesOperator decisionImprove the serviceImprove the service
2CookiesSDK configuration disableCookiesUsagetruefalse (default)
3Cookie scopecookieCfg, cookieDomain, cookiePathNot applicableRestrict to the site's own domain
4Resource regionAzure portal, when creating the Application Insights / Log Analytics resourceEU regionEU region
5Data retentionLog Analytics workspace retention settings in the Azure portalShort period, e.g. 30 days (illustrative)Longer period, e.g. 90 days (illustrative)
6Custom user identifiersSDK setAuthenticatedUserContextNot usedNot used (if used, add "Authentication-derived identifiers")

Step 2 — Map the configuration in the Consenter Manager

Processing location. Data is stored in the Azure region chosen for the resource. Microsoft Corporation is a US company and can be required to disclose data in its possession, custody or control regardless of storage location.

Configuration A — Lower risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesImprove the servicePerformance and error monitoring.
Tracking methodFirst party tracking (single session)No cookies; each page view stands alone. If even the single-session link is absent in your setup, select "No tracking".
IdentifierIP addressTransmitted with each telemetry request.
Data categoriesBrowsing and interaction data, Device characteristics, IP address, Aggregated site statisticsPage views, timings, errors.
Legal role of data recipientProcessorMicrosoft DPA.
Personalisation modelNo personalisation—
Maximum storage duration30 days (illustrative)Per workspace retention setting.
Processing locationChosen EU Azure region; United States as potential access locationSee note above.

Configuration B — Medium risk (default)

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesImprove the serviceAs A.
Tracking methodFirst party tracking (cross-session)User and session cookies on the site's domain.
IdentifierDevice identifiers, IP addressCookie-based user ID.
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP address, Aggregated site statistics—
Legal role of data recipientProcessor—
Personalisation modelNo personalisation—
Maximum storage duration90 days (illustrative)Per workspace retention setting.
Processing locationAs ASee note above.

Privacy-policy follow-up

  • Microsoft as processor; telemetry collected; cookies (B); retention period chosen; Azure region; potential access by US authorities.

Verification checklist

  • A: no Application Insights cookies set (disableCookiesUsage effective).
  • B, before consent: no request to the Application Insights ingestion endpoint.
  • Workspace region and retention match the mapping.

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