Hey everyone! I'm working on improving our Azure naming conventions and I'm particularly curious about how people handle naming for sub-resources (like Application Gateway rules, listeners, and backend pools) and resources that are only relevant in conjunction with other resources (such as an NSG attached to a specific subnet). I'm not looking for strict best practices, but I'd love to hear how you've structured this in your projects. Some specific things I'd like your input on are:
- Do you include the name of the parent resource?
- What delimiters do you use?
- How do you avoid name clashes and maintain readability?
Looking forward to hearing your strategies and examples! Thanks!
3 Answers
For resources that are seen as linked to another, I often name them with a prefix based on the primary resource. It simplifies naming because you just have to think of a straightforward suffix. It helps keep everything organized without making the naming scheme overly complicated.
Check out the CAF guidelines on resource naming! They discuss the practices you can apply to sub-resources too. Ultimately, your naming conventions should be set by your business needs. For example, you might name an NSG rule 'nsg-weballow-001', and then use a similar format for application gateway rules like 'appgw-rulename-001'. Avoid name collisions by incorporating workload names or adding incremental numbers for duplicates.
We follow a structured approach and divide our naming into three categories: Regional, Global, and Special. For Regional resources, the format is -----. For instance, an NSG in US West might be named 'nsg-usw-prd-i-appx-01'. For Global resources, the format is ----. Lastly, Special cases combine elements without any special characters for certain services. It keeps things clear!
Related Questions
Sports Team Randomizer
10 Uses For An Old Smartphone
Midjourney Launches An Exciting New Feature for Their Image AI
ShortlyAI Review
Is Copytrack A Scam?
Getting 100 on Pagespeed Insights for Mobile is Impossible