Azure Monitor Baseline Alerts
Download AlertsGlossaryGitHubGitHub IssuesToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeBack to homepage

Telemetry

Telemetry Tracking Using Customer Usage Attribution (PID)

Microsoft can identify the deployments of the Azure Resource Manager and Bicep templates with the deployed Azure resources. Microsoft can correlate these resources used to support the deployments. Microsoft collects this information to provide the best experiences with their products and to operate their business. The telemetry is collected through customer usage attribution. The data is collected and governed by Microsoft’s privacy policies, located at the trust center.

To disable this tracking, we have included a parameter called telemetryOptOut to the deployment template in this repo with a simple boolean flag. The default value No which does not disable the telemetry. If you would like to disable this tracking, then simply set this value to Yes and this module will not be included in deployments and therefore disables the telemetry tracking.

If you are happy with leaving telemetry tracking enabled, no changes are required.

For example, in the alzArm.json file, you will see the following:

"telemetryOptOut": {
    "type": "string",
    "defaultValue": "No",
    "allowedValues": [
       "Yes",
       "No"
    ],
    "metadata": {
        "description": "The customer usage identifier used for telemetry purposes. The default value of False enables telemetry. The value of True disables telemetry."
    }
}

The default value is No, but can be changed to Yes in the parameter file. If set to Yes the deployment below will be ignored and therefore telemetry will not be tracked.

{
  "condition": "[equals(parameters('telemetryOptOut'), 'No')]",
  "apiVersion": "2020-06-01",
  "name": "[variables('deploymentNames').pidCuaDeploymentName]",
  "location": "[deployment().location]",
  "type": "Microsoft.Resources/deployments",
  "properties": {
    "mode": "Incremental",
    "template": {
      "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
      "contentVersion": "1.0.0.0",
      "resources": []
    }
  }
}

Module PID Value Mapping

The following are the unique ID’s (also known as PIDs) used in the AMBA deployment

NamePIDTelemetry for
Azure Monitor Baseline Alerts - AMBA ARM Deploymentd6b3b08c-5825-4b89-a62b-e3168d3d8fb0Deplyments performed through PowerShell, Az CLI, Azure DevOps, GitHub pipelines
Azure Monitor Baseline Alerts - ALZ Portal Accelerator Deployments5f0e5693-3998-4ae2-8115-ee96e38dac62Deplyments performed through the ALZ Portal Accelerator
Azure Monitor Baseline Alerts - AMBA Portal Accelerator Deploymentsdddb1f42-f9d8-48e3-9e6b-f1ce3e9c2c76Deplyments performed through the AMBA Portal Accelerator
Azure Monitor Baseline Alerts - Bicep Deployments8fdd7c49-68f6-4e35-8ba3-ee0dd2979bc0Deplyments performed through Bicep
Azure Monitor Baseline Alerts - Terraform Deploymentsda02c554-db8c-4029-96dd-d4ab9abf4dc4Deplyments performed through Terraform
Connectivity Policy Initiative2d69aa07-8780-4697-a431-79882cb9f00eUsage of Connectivity Policy initiative
Identity Policy Initiative8d257c20-97bf-4d14-acb3-38dd1436d13aUsage of Identity Policy initiative
Management Policy Initiatived87415c4-01ef-4667-af89-0b5adc14af1bUsage of Management Policy initiative
LandingZone Policy Initiative (Initiative has been deprecated)7bcfc615-be78-43da-b81d-98959a9465a5Usage of LandingZone Policy initiative
Hybrid VM Policy Initiativeb5c25c0c-dfbf-4414-bedb-f48ab00d0f9eUsage of Hybrid VM Policy initiative
ServiceHealth Policy Initiative860d2afd-b71e-452f-9d3a-e56196cba570Usage of ServiceHealth Policy initiative
Notification Assets Policy Initiativeeabaaf0b-eed4-48a9-9f91-4f7e431ba807Usage of Notification Assets Policy initiative
Key Management Policy Initiative65cb78a2-0744-4785-9093-aeb772ecdd7bUsage of Key Management Policy initiative
Load Balancing Policy Initiative5156f7d1-8543-49c0-ac09-76db1170d42aUsage of Load Balancing Policy initiative
Network Changes Policy Initiativee61a27ea-ed9e-496e-8fd2-489bfa3b6e4fUsage of Network Changes Policy initiative
Recovery Services Policy Initiativeb45e8b7b-e0a2-4af4-b3af-8b2af4020dccUsage of Recovery Services Policy initiative
Storage Policy Initiativec0eb5ea9-033b-4c1b-be71-b3088e7a2e2bUsage of Storage Policy initiative
VM Policy Initiative3ace674d-9502-4f4a-98ba-a2277c01ccf8Usage of VM Policy initiative
Web Policy Initiativea80aedbd-3157-4335-94c7-7e7db459a647Usage of Web Policy initiative