Relax the restrictions on storage account name
Unlike most other azure resources, storage accounts have an overly strict naming restriction (must be globally unique, 3-24 length of lowercase letters and numbers only).
This means Azure users cannot add any meaningful naming conventions to them compared to other azure resources - e.g. they can't contain hyphens, must be less than 24 characters, they can't have the same storage account name per environment, and have to be different GLOBALLY, etc.
This restriction is overly limiting and means storage accounts are a pain to manage.
I think this restriction only exists because the storage account name is put in the URL currently. Assuming the cause is this, one suggestion for solving this could be to have some sort of 'URL name' field for storage accounts, which can be used in the scenario where a storage account name is NOT globally unique. Existing storage account URLs would still work fine this way. Alternatively another solution could be to have a randomly generated URL.
Raphael Cardoso commented
hyphen! hyphen! hyphen!
Simon Michaud commented
We really need more than 24 chars...
Can we have a ratoinal explanation for not allowing hyphens ? URLs generated from the name are not broken by hyphens, so what's the reason ? This would help a lot to clarify name of blobs ex: <CustomerCode>-<EnvironmentCode>-<CountryCode>-reports, no hyphens means reading the storage names 4-5 times to figure out the purpose.
Sean G. Wright commented