Azure naming · Microsoft.Network/trafficManagerProfiles

traf Traffic Manager profile

DNS-based traffic routing. The name backs <name>.trafficmanager.net.

Naming constraints

CAF abbreviationtraf
Resource typeMicrosoft.Network/trafficManagerProfiles
Length1–63 characters
CaseMixed case
Allowed charactersAlphanumerics and hyphens. Start and end with alphanumeric. No periods.
Uniqueness Global
SeparatorHyphen

Source: Microsoft Learn, “Naming rules and restrictions for Azure resources”, checked October 2026. Abbreviation from the Cloud Adoption Framework.

Example & copy-ready

A worked name for workload app, env prod, region weu, instance 001.

Example name
traf-app-prod-weu-001 Valid
Validation regex for CI checks or pre-commit hooks (.NET and JavaScript)
^(?=.{1,63}$)[A-Za-z0-9](?:[A-Za-z0-9-]*[A-Za-z0-9])?$
Bicep naming expression
var name = take('traf-${workload}-${env}-${region}-${instance}', 63)
Terraform local
locals {
  name = substr(join("-", compact(["traf", var.workload, var.env, var.region, var.instance])), 0, 63)
}

Azure Policy can't evaluate regular expressions, so a policy can check the traf prefix but not the full format. Run the regex in your pipeline, or audit existing names on a schedule.

Uniqueness scope

Globally unique across all of Azure — the name backs a public DNS label, so a clash with any other tenant's resource fails the deployment. Build in enough entropy (org/region/instance) to avoid collisions.

Open in the name generator