Every Azure team needs a naming convention, and Microsoft’s Cloud Adoption Framework defines a good one. The annoying part is that the rules are scattered and every resource type is different. Storage accounts: 3 to 24 characters, lowercase, no hyphens, globally unique. Key Vault: 24 characters, and soft delete reserves a deleted vault’s name for 90 days. Container registries: alphanumeric only.
I got tired of cross-referencing the docs and still hitting name errors at deploy time, so I put together AzureNamer.
What it does:
- Generates CAF compliant names for 204 resource types, each with its real length and character rules applied
- Exports the whole set as Terraform, Bicep, JSON, Markdown or CSV
- The Terraform and Bicep exports have a parameterized mode: variable blocks plus derived name expressions, so one file produces correct names for dev, staging and prod. Names the engine had to shorten stay literal with a comment instead of silently drifting
- Parses an existing name back into its components (type, workload, environment, region)
- Includes a naming rules reference page for every resource type and a searchable CAF abbreviations cheat sheet
It’s free, no login, and fully static, so your inputs never leave the browser.
It started as a side project to scratch my own itch, so feedback is genuinely welcome, especially wrong abbreviations or missing resource types. Hope it saves someone a 2am deploy failure over a name that’s one character too long.
Try it: https://azurenamingconventions.com
If you want the background on the CAF standard itself, I wrote a full guide: https://azurenamingconventions.com/blog/azure-naming-conventions-complete-guide/
답글 남기기