If you’re looking at establishing Azure subscriptions & resources, a naming convention is crucial to keeping organized.
Here’s some references to consider:
- SHAREGATE: What does a good Azure naming convention look like?
https://sharegate.com/blog/what-does-a-good-azure-naming-convention-look-like - IRONSTONE: Naming Conventions In Azure
https://www.ironstoneit.com/blog/naming-conventions-for-azure - PREMIER: Naming convention for Azure Resources
https://www.liammoat.com/blog/2019/naming-convention-for-azure-resources - GALLERY: Azure Governance Design Guide – Build Your Azure Naming Convention
https://gallery.technet.microsoft.com/Azure-Governance-Design-bed3558a
It’s hopefully obvious how important doing this from day 1 is to your public cloud implementation. This is documentation for yourself, your organization, and those supporting your institution in the years to come. (Not to mention, leaving your Azure subscription with the default name of “MICROSOFT AZURE ENTERPRISE” isn’t very indicative of having applied much thought or experience to your cloud to management or future administrators)
For example, a basic rule for Azure subscription naming conventions is highlighted in the first link:
- AZURE SUBSCRIPTION NAME FORMAT:
<Company>-<Department>-<Product Line(optional)>-sub-<Environment>
A simple example of this would be:
- ENVIRONMENT:
Company: Contoso
Department: Finance
Product Line: Internal Applications
Environment: Production - AZURE SUBSCRIPTION NAME:
Con-Fin-Int-Sub-Prd
kurtsh
Kurt Shintaku's Blog 