Resource templates are a great concept, but are fraught with danger. Badly named resources and naming inconsistency across resources in different subscriptions can make it difficult to determine purpose.
If a resource such as a Virtual Network or a Storage Account is badly named in a resource template file, you may find that you have to rely on the icon pictures in the Azure portal to indicate what type of resources you are looking at.
What if you need to see at a glance:
- What region the resource belongs to i.e. Australia East or Australia Southeast?
- What environment the resource belongs to i.e. Production or Testing?
- What type of resource it is?
The problem comes from trying to keep the names meaningful and consistent. How do you ensure that your naming standards are adhered to?
In my case I would like to name resources as follows:
"Vnet_Prod_auSoutheast" Continue reading