Before creating anything in Azure Stack, we need a good naming convention in place. A naming convention ensures that all the resources have a predictable name, which helps lower the administrative burden associated with managing these resources.

You might choose to follow a specific set of naming conventions defined for your entire organization or for a specific Azure subscription or account. Although it is easy for individuals within organizations to establish implicit rules when working with Azure Stack, when a team needs to work on a project on Azure Stack, that model does not scale well. The good thing is that you will maybe already have these conventions with Azure and as Azure Stack is relying on the same design concepts, they may be already set and just need to be modified to fit to Azure Stack design specifications.

Agree on a set of naming conventions up front; there are some considerations regarding naming conventions that cut across that sets of rules.

You should have naming conventions for the following Azure Stack resources:

• Subscriptions
• Storage accounts
• Virtual networks
• VPN gateway
• Subnets
• Availability sets
• Resource groups
• Virtual machines
• Network security groups
• Public IP address name

You also should consider some abbreviations for Azure Stack resources in common use.

We recommend that you follow abbreviations for some of the common Azure Stack resources listed earlier: