Having defined the Azure hierarchy, the next step is setting up a naming standard definition for all Azure resources. This is one of the most important steps within the governance, as in the future there may be hundreds and thousands of resources defined in Azure. If no naming definition has been set when starting, the risk of getting lost in there is quite high. There are hundreds of naming definitions—each consultant around the world may have set one—but following the Microsoft best practice would make life easier.
The set of Microsoft naming conventions and patterns can be found at: https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions.
As defined, the following naming conventions should have been set:
<Company> <Department (optional)> <Product Line (optional)> <Environment>
Structuring your resources this way provides an out-of-the-box solution for documentation, scalability, and generality...