What is the logic behind Azure resources naming restrcitions ?

Question

Hello,

I am curious to know why there are some limitations when we name Azure resources. For example

• Azure resource name can not have Capital letter in it
• No blank spaces are allowed in names of Azure resources

What the logic behind it ? why does it matter to Azure if resource names are in all lower case or lower cases and capital letters. There must be something I am unable to think of.

Appreciate your insightful response, thank you !!

P.S.
Couldn't find correct tags for this question. Sorry about that.

Answer 1

Hello @anil kumar ,

Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.
Most of this resource naming restrictions for case/char sensitive in azure resource naming convention are for the fact that each resource in the backend as a string created for it.
Example - Storage account, if we check the properties, we have a URI and a Host name cannot support space OR capital letters as per the RFC's. Otherwise it will result in URL Character Encoding Issues.
Reference : RFC 1738 - Uniform Resource Locators (URL) (RFC1738) (faqs.org)

Regarding the Capital letters, it is only for storage accounts and some resources. VMs, NIC interfaces and Disks etc., have capital letters in them.
This article summarizes naming rules and restrictions for Azure resources. For recommendations about how to name resources, see Naming rules and restrictions for Azure resources

(If the response was helpful, please accept my response as answer so that the relevancy of this post will improve when anyone in the community search for similar query.)
(Accept Answer and Upvote)