Telemetry

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": []
        }
    }
}

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