Azure 360. Governance in Azure

Hi Everyone. Thanks for taking the time to read my blog. I will be writing weekly about Microsoft Azure public cloud. This blog is not aimed at comparing other clouds to Azure, or promoting it over other clouds. I strongly believe that the choice should be with the public, and that there is space for multiple players in the cloud arena. I am going to write about Azure because that is where I spent most of my time lately.

I am not going to write about how good the cloud is, and use big words like Agility, Flexibility, Unlimited Resources etc. I will leave that for the marketing team. I assume that if you are reading this blog, you understand that the future is with cloud technologies and you are ready to try it.

Before diving into technical details I would like to discuss governance in the Azure. Azure is an amazing playground shared by many. As long as we all play by the rules – we will all be safe in the playground. In order to play by the rules we need to know them.

The first rule is naming convention. Organisation that will spend time thinking and planning the naming standards in Azure will benefit from a well organised and easy to manage environment in the future. There are at least 10 different rules in regards to naming different assets in azure. For example:

Service or Entity Length Casing Valid Characters
Resource Group 1-64 Case Sensitive Alphanumeric, underscore and hyphen
Storage Account 3-24 Lower case Alphanumeric
Network Interface 1-80 Case-Insensitive Alphanumeric, dash, underscore and period


To make it a little bit more complicated, some names have to be  globally unique!

And… you cannot rename assets.

For further information and for all the details about naming standards please refer to the following article:


Next week, I will discuss some options and tools (like: tags) that can help with organising objects in Azure.

Tune in then!