The use of a consistent, shared naming convention throughout the Azure environment is one of the key points you should follow when building and deploying solutions to the cloud. With a consistent naming convention, it is easy to navigate through and locate your resources in the cloud, and it helps us to build a robust continuous integration and deployment pipeline in Azure.
In this section, we will go through some of the guidelines that can be followed for proper naming standards with integration resources. You can use these recommendations to build your own enterprise-level naming convention. In the following table, we have listed Azure artifacts along with a standard naming pattern:
Entity |
Scope |
Patterns |
Example |
Resource group |
Resource group |
<service short name>-<environment>-rg |
enterprisegraph-dev-rg |
Logic Apps |
Resource group |
la-<region>-<orgsortname>-<onsourceprocessname>-destination |
la-ause-contoso-salesorder-sn |
Functions app |
Resource group |
func-<orgsortname>-<processname>-<env> |
func-contoso-propfi-dev |
Functions |
|
fc_<ontriggername>_<operationname>_<destination> |
fc_userupdate_getuserdetails_la |
Storage |
Resource group |
sa<region><processshortname><env><number> |
saausecontosodata01 |
API Management |
Resource group |
{name}.azure-api.net |
contoso.azure-api.net |
API |
Resource group |
API : <service name>-api |
contosofinance-api |
API connection |
Resource group |
<env>.<connectiontype> |
dev.office365 |
Microsoft also came up with a list of patterns and practices that should be followed when you create resources in Microsoft Azure. These recommendations help enterprises to have fine control over billing and resources running on the cloud. For more details on general resource naming conventions, you can look at the Microsoft documentation: https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions.