'How to name Azure Storage Accounts?
Azure Storage Account name length restriction throws a wrench in what could be something easy. Being able to name my resources per tenant, like rg{tenant-guid} for a resource group, or fa{tenant-guid} for a function app is nice and easy, but a 24-character limit on azure storage accounts really mucks it all up. Why put a requirement for a globally-unique name on Azure Storage Accounts and not allow administrators to use GUID's for naming Azure Storage Accounts?
Partly question, mostly rant.
Solution 1:[1]
This is just a limitation like all the other services . There are different factors considered and this is common with any clound vendor as well.
The only reason these naming restrictions exist are because the storage account name gets put in the URL so it has to be unique and should not contain GUIDs. You can use uniqueString() to generate storage account names
Solution 2:[2]
I wonder who is the dimwit product manager who approved this limitation, instead of just using the account ID or name as a prefix to the field.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Sajeetharan |
| Solution 2 | Dovi Lilling |