A common task for Azure administrators is to ensure that resources in their Azure subscriptions are configured accordingly to some business requirements or standards’ regulations. So, how to accomplish this in practice?

At some point, an organization might end up with Azure subscriptions that contain a bunch of resources named in a completely different manner. To bring some order in this mess, people usually try to come up with a naming convention to ensure a standard user experience across the teams.