Any recommendations about naming convention for an Azure resource

Yep - in general, there are two considerations

1. You need to be aware of the restrictions applicable to different Azure resources. Details at https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules
2. Recommendations based on CAF - details at https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Not really. The problem is that some resources are global (to all of Azure) while others are specific to your subscription/resource group. Some resources must be allowable in a URL, others restrict the characters allowed (I think one even mandates lower case letters only), and yet others allow anything. On top of that some resources are limited to small sizes (e.g. 32). It is really frustrating. I recommend that for each resource you review the docs to see if they make a recommendation when they list the resource naming restrictions.

The general recommendation, limited by the resource rules you are defining, is to use something descriptive and ideally include the environment (e.g. prod, staging). For example a calculator website might be called calculator-staging and calculator-prod whereas a storage container for books might be books-staging and books-prod. Since Azure Portal shows all resources it can get very confusing if you have a bunch of them so you must either filter by the type (e.g. storage container, storage account) or include that in the name as well. For example it is pretty common to see -rg added to resource group names.

Bear in mind that some resource names may be publicly visible in URLs so don't put in anything sensitive.

+1 on the reply @Amira Bedhiafi where the naming convention describe under the Cloud Adoption Framework is a good start. We follow it with slight modifications. However, it is good to know that Azure Services can suddenly create resource groups and other resources that are violating your naming convention policies and you can't do anything about it. Kind of annoying.