Compose CAF-compliant Azure resource names from workload, environment, region and instance, for one resource or a whole workload. Each name is checked against Microsoft's rules for its type, including the Windows host-name limit, global DNS uniqueness and the AKS node-pool limit.
Pick a resource type and fill the tokens. The name is checked against that type's Azure rules as you type.
The same tokens, applied to every resource a typical workload needs.
| Resource | Name | Length | Copy |
|---|
Length, characters, uniqueness scope and gotchas for each type, from Microsoft's naming rules. Also available as JSON.
No resource type matches that filter.
Rules from Microsoft Learn, “Naming rules and restrictions for Azure resources”, checked October 2026. Abbreviations from the Cloud Adoption Framework.
The Cloud Adoption Framework recommends a resource-type abbreviation followed by workload, environment, region and instance, for example kv-payments-prod-weu-001. This tool applies that pattern and then checks the result against the platform rules for the chosen type: length, allowed characters, casing and uniqueness scope.
Names that become part of a public DNS name: storage accounts, key vaults, App Service and function apps, SQL servers, container registries, Cosmos DB accounts, API Management, Service Bus and Event Hubs namespaces, AI Search and others. They're marked Global in the list below. A clash with any other Azure customer fails the deployment.
Storage accounts allow only lowercase letters and numbers, 3 to 24 characters. The generator joins the tokens without a separator for types that don't allow hyphens, and uses underscores where only those are allowed (compute galleries).
The resource name can be up to 64 characters, but the guest host name is limited to 15 characters on Windows and 64 on Linux, and underscores and periods aren't allowed in host names. The portal uses the same value for both, so the tool checks the 15-character limit when you pick Windows.
Partly. Azure Policy has no regular-expression operator, only like and match patterns, so it can reliably check the abbreviation prefix but not the full format. Full validation belongs in your pipeline or in a scheduled audit. Managed resource groups created by AKS, Databricks and other services also need exclusions, or deny policies break them.
Everything on this page is free, including the rules for all 79 resource types as JSON at /tools/azure-resource-naming/rules.json. The pack adds the enforcement around them: an Azure Policy initiative for prefixes, required tags and tag inheritance with managed-resource-group exclusions, a PowerShell audit of existing names, a bulk CSV generator, Bicep and Terraform modules, and an editable convention and tagging standard. It's €39, one-time.