Azure Migrate project naming convention

The CAF abbreviation for Azure Migrate project is migr. Names can be 2 to 60 characters long and allow alphanumerics and hyphens. 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 Migration resources

Migrate projects, Database Migration Service instances, and Recovery Services vaults are typically scoped to a migration wave rather than to any single resource, a migration project often spans dozens of source virtual machines or databases and outlives every one of them individually. Name for the wave or the source environment being migrated, for example the legacy datacenter it replaces, rather than for a single target resource.

Recovery Services vaults commonly outlive the migration itself, once cutover is done the same vault is often reused for ongoing backup and disaster recovery. If that is the plan, name it for the protected environment it will serve long term, not for the one time migration event that created 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 {
  migrate_project_name = "migr-${var.workload}-${var.environment}-${var.region}-001"
}

var migrateProjectName = 'migr-${workload}-${environment}-${region}-001'

Related Migration resources

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