Cloud Naming Convention

Consistent naming strategy is important and should be an essential part of any cloud effort, especially as the number of managed resources grows in an organization. Unfortunately, it is often overlooked by users across domains. Consistent cloud naming strategy is the first step in achieving even basic levels of consistency and prerequisite to establishing any sort of cloud governance. Good could naming conventions also help associate cloud usage costs with business teams via chargeback and showback accounting mechanisms.

Naming standard

One of the main benefits of the cloud is that you can deploy and tear down whole environments rapidly, spinning up environments only when needed. Incorporating that into the culture, is key to keeping cloud costs down.  Since environments are "temporal" having a naming convention that incorporates the environment will help you with readability, so you know what application, a set of resources belong to, and where in the lifecycle are they. In addition to discoverability, a well thought out naming convention consistently applied, allows you to leverage automation to better manage your environment for both deployment and maintenance.

Naming Convention

If you walk away with only one thought from this article, it should be that a good naming convention has to be ordered by significance and should be unique.

What does ordered by significance mean?

From left to right your elements in the name should be of decreasing significance. For example – Division-Group-Member-status.

A division is comprised of many groups, which have several members and each member has a status.

By using decreasing significance resources that work together and are sorted together by name enhances readability.

The next key aspect of a naming convention is uniqueness. Your naming convention must allow you to uniquely name both globally named resources like storage accounts and locally named resources in a resource group, so you don’t have a naming conflict that would prevent deployment. An example of this is, if you create a resource group to house a hub of virtual networks used to peer multiple geographies, you will need to add the region element into your naming convention so the virtual network names are unique.

If you need a naming convention that is cross-cloud or independent of deployment environment (subscription), you might want to consider adding those elements to the below convention.

When considering adding elements, add them only if they are necessary. The more you add, the harder it is to gain adoption and to use them consistently with character constrained lengths. For example, Virtual Machines have a limitation of 15 characters.

This convention applies to all Cloud elements (management groups, subscription names, resource groups and all the resources). It does not apply to names of elements within a resource like Storage Account containers, SQL Database names or Network Security Rule names.

Note: Some Azure services deploy their own resources and use a default naming convention (e.g., Network Watcher creates the NetworkWatcherRG resource group). 

Naming convention recommendation

In this example, elements of the name are in order of significance as this will naturally group similar resources by what you deem most significant. Unless otherwise advised, the proposed naming convention for all foundational deployed resources will be used as follows:

[ ] means optional