Before your organization leaps into any significant Azure adoption, one of many important planning exercises should be adoption of a standardized naming system for services and resources. Skipping this important planning step is sure to unnecessarily increase your management overhead as the object collection expands over time. Fortunately, there are several good resources I’ve used to accomplish this and these should also help to simplify your efforts in this activity.
A good start is a visit to the Recommended Naming Conventions for Azure Resources page located in the Patterns & Practices Best Practices section of Azure documentation. This page provides several recommendations and guidance points.
- Subscription Naming – recommended pattern is a four-part value denoting Company, Department (optional), Product Line (optional), and Environment
- Name Affixes – prefixes and suffixes to denote type and context helps to avoid ambiguity when scrolling thru a long list objects
- Naming Rules & Restrictions – a handy table showing name length and casing constraints but also scope (some names must be unique to all of Azure, others only unique to the subscription)
- Tags – a valuable feature that allows linking and correlating entities across disparate deployments but also provides an excellent approach to manage billing and access control
Another excellent resource is Naming and Referencing Containers, Blobs, and Metadata. This page gives valuable naming guidance for containers, blobs, metadata, and snapshots. This is especially important because endpoints to these resources are uri-based.
Finally, overview guidance is provided on the Azure Infrastructure Naming Guidelines page. It also provides links to several other guideline pages as well.