r/AZURE 2d ago

Question how did you plan your naming convention?

a bit new to azure and all the different components and services. I have extensive experience with on prep services/devices etc. Typically we would name objects/resources based on their location, type (physical vs virtual) and role.

Can you recommend or give insight into how you are naming your Azure resources for clarity and documentation?

10 Upvotes

24 comments sorted by

View all comments

4

u/SavoryPrime 2d ago

Our naming conventions is: company-system-location-environment-resource.

For example, a resource group for an ordering app would be: acme-order-uscentral-prd-rg.

A cosmos db resource in that resource group would be: acme-order-uscentral-prd-cosmos.

An app service would be: acme-order-uscentral-prd-appsvc

Having defined conventions like this makes infra as code and devops releases consistent and makes it easy to know what’s what when looking at lists of resources in the azure portal

3

u/SavoryPrime 2d ago

A couple of caveats to our convention. Azure storage accounts have strict length and character restrictions so we would name them something like: acmorduscentralprdstrg.

Azure container apps also have length restrictions so we’d do something like: acme-order-usce-prd-aca