Managed DevOps Pool naming convention

The CAF abbreviation for Managed DevOps Pool is mdp. Names can be 1 to 80 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the resource group.

Naming rules

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.

Naming DevOps resources

Azure Managed Grafana instances are usually a shared observability surface for a whole platform team rather than a single service, so name by team or platform, not by whichever dashboard prompted the first deployment. Managed DevOps Pools feed CI/CD agents back to Azure DevOps and are typically provisioned per major pipeline grouping rather than per repository.

For both resource types in this small but growing category, tie the name to the organizational boundary it serves (the platform team, the pipeline group) rather than to a single consuming project, since that boundary is far more stable than any one project inside it.

Example names

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

Naming in Terraform and Bicep

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

locals {
  managed_devops_pool_name = "mdp-${var.workload}-${var.environment}-${var.region}-001"
}

var managedDevopsPoolName = 'mdp-${workload}-${environment}-${region}-001'

Related DevOps resources

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