I'm fairly new to Azure and still getting familiar with all the different resource types and services. In on-premises environments, I usually named devices and objects according to their location, type—physical or virtual—and role. What naming patterns do you use for Azure resources so they stay clear, consistent, and easy to document?
4 Answers
A straightforward pattern is resource-type, application, environment, location, and instance number. For example: afw-hub-prod-uks-01. A reference list of common Azure resource abbreviations can also help keep names consistent, although you’ll probably need to fill in gaps for less common services.
A hybrid approach works well: combine your internal naming standard with Microsoft’s Cloud Adoption Framework guidance. Keep the name focused on stable identifiers such as workload, environment, region, and resource type, and use tags for ownership, cost center, business unit, and other metadata.
We use company-system-location-environment-resource. For example, an ordering application might have resources named acme-order-uscentral-prd-rg, acme-order-uscentral-prd-cosmos, and acme-order-uscentral-prd-appsvc. Having a predictable structure makes infrastructure-as-code and deployment pipelines much easier to manage, and it helps people identify resources quickly in the Azure portal.
That’s close to what we do too, although we leave out parts of the name when they’re obvious and use tags for details that don’t need to be embedded in every resource name.
A good place to start is Microsoft’s Azure resource-naming guidance, including its recommended abbreviations. Use it as a baseline, then adapt it to your organization’s needs. One important caveat is that some resource names become part of globally unique public hostnames, so you may not be able to apply the same template to every resource type.
The abbreviation list is useful, but it doesn’t cover every resource type and some entries may not stay current, so I’d treat it as a reference rather than a strict standard.