Azure Naming Convention Generator
Build a Cloud Adoption Framework-style Azure resource name from resource type, workload, environment, region, and instance, runs entirely in your browser.
About this tool
Pick a resource type, enter a workload/app name, environment, region, and instance number, and get a name following the Microsoft Cloud Adoption Framework’s recommended pattern: <resource-abbreviation>-<workload>-<environment>-<region>-<instance>, e.g. "vm-myapp-prod-eastus-001". A consistent naming convention is what makes a subscription with hundreds of resources searchable and understandable at a glance instead of guesswork.
Storage accounts and container registries are handled as the special case they actually are in Azure: both require a globally unique, lowercase-alphanumeric-only name with no hyphens and a 24-character limit, so this tool strips the hyphens and lowercases the result for those two resource types specifically, rather than generating a name Azure would reject outright.
Frequently asked questions
- Why do storage account names look different from other generated names?
- Azure enforces a stricter rule for storage accounts and container registries: lowercase letters and numbers only, no hyphens, 3-24 characters, because the name becomes part of a globally unique DNS endpoint. Every other resource type in this tool uses the standard hyphen-separated pattern.
- What if my generated storage account name is longer than 24 characters?
- The tool rejects it with a clear error rather than silently truncating, since truncating could produce a different name than you expected or a collision with another resource. Shorten the workload, environment, or region segment and try again.
- Can I use hyphens or spaces in the workload/environment/region fields?
- No, each segment must be alphanumeric only; the tool supplies the hyphen separators itself between segments. This keeps the generated name valid across every Azure resource type, since a few resource types (like the ones above) cannot contain hyphens at all.
- Is my input sent anywhere?
- No. The name is assembled entirely in your browser, no network request is made.
Continue learning
- DocumentationAzure FundamentalsHow Azure management groups, subscriptions, resource groups, and Resource Manager fit together, with practical deployment troubleshooting.
- BlogTerraform Troubleshooting Guide: Fix the Errors Engineers Actually HitDiagnose Terraform initialization, validation, provider, authentication, state, drift, import, replacement, timeout, and CI failures with a safe workflow.
- ToolAzure CLI Command BuilderBuild a correct az command for common resources (resource group, VM, storage account, AKS, web app) from a simple form, runs entirely in your browser.
- DocumentationAzure StorageHow Blob, File, and Disk storage fit different access patterns, what LRS, ZRS, and GRS protect against, and why tiers change cost, not durability.
- BlogTerraform Azure VMSS: Load Balancer, Key Vault, and MonitorProvision an Azure VM Scale Set with Terraform behind a Standard Load Balancer, then add managed identity, Key Vault RBAC, monitoring, and verification.
- ToolBicep GeneratorScaffold a basic Bicep file for a Storage Account, Virtual Network, or App Service, runs entirely in your browser.