Management and governance dcr

Azure Monitor data collection rule naming convention

The CAF abbreviation for Azure Monitor data collection rule is dcr. Names can be 1 to 260 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the resource group.

Naming rules

CAF abbreviation	dcr
Length	1 to 260 characters
Allowed characters	Alphanumerics (a-z, A-Z, 0-9), hyphens, underscores
Scope of uniqueness	Unique within the resource group
CAF pattern	dcr-{workload}-{environment}-{region}-{instance}

Rules follow Microsoft's resource naming rules and CAF abbreviations. Some resource types have extra start/end character restrictions, so verify against the official docs before locking in a convention.

Example names

Generated by the same engine as the name generator, so length and character rules are already applied.

Scenario	Generated name	Length
Payments API, production	`dcr-payments-prod-eus-001`	25/260
Web app, development	`dcr-webapp-dev-weu-002`	22/260
Analytics with company prefix	`dcr-contoso-analytics-stage-uks-001`	35/260

Naming in Terraform and Bicep

Build the name from variables so one module produces the right name in every environment.

Terraform

locals {
  data_collection_rule_name = "dcr-${var.workload}-${var.environment}-${var.region}-001"
}

Bicep

var dataCollectionRuleName = 'dcr-${workload}-${environment}-${region}-001'

Generate Azure Monitor data collection rule names for your workload

Free, no login. Validation and Terraform, Bicep, or CSV export included.

Open in the generator →

Related Management and governance resources

aa Automation account policy Azure Policy definition appi Application Insights ag Azure Monitor action group apr Azure Monitor alert processing rule dce Data collection endpoint script Deployment script log Log Analytics workspace

See the full list of Azure resource naming rules or read the complete CAF naming guide.