Allow special characters in Storage Account naming (especially "-", "_" or ".") for readability and easy identification.
Allow special characters in Storage Account naming (especially "-", "_" or ".") for readability and easy identification. It is very hard to work with all lower case naming that has to be run together without special characters. This would also allow for more versatility in the Azure naming space since SA naming is "shared" throughout the entire Azure instance for all Azure clients.
David Simmons
shared this idea
7 comments
-
Jack S
commented
The only reason these naming restrictions exist are because the storage account name gets put in the URL. I think decoupling the storage account name from the URL will mean that they can relax the restrictions on the name, which will mean we can all name these whatever we want!
-
Jan Barelds
commented
I'd also like to know where this suggestion has been moved to. I cannot find it, and would like to give it 3 votes. Right now, company naming conventions cannot be applied to Azure Storage.
-
Alexander Batishchev commented
Moved to where?
-
Jessica Janiuk
commented
I was going to add this exact suggestion today, and then I realized it was already here. It makes me sad to see that there's been no movement on this suggestion since October 12, 2016 though.
-
Almiro Alves
commented
I really miss that a lot. I think this is the basics and should have Azure for all services. It is not possible for Azure to use the services name as a key not to allow its change. Something terrible to believe!
-
Nick Gailloux (Softlanding)
commented
If you like this suggestion then please also vote for my similar suggestion:
-
Nick Gailloux (Softlanding)
commented
Make all Azure object names simply a tag with a key of "Name" and a value of your chosen name. Think of this like a friendly name that is displayed throughout the portal. This tag could be modified at any time, allowing users to rename any object easily. No need to use fqdn's or limits on length.
A guid or id would be generated for every object to make it them globally unique and easy to reference in a unique manner.
Currently in Azure, it is not possible to rename most objects, in many places we have to use an fqdn (like storage account names), and there are limitations on name length. This makes it very hard to implement and follow a naming convention.