Resource Namespace Pollution
Currently, all resources (storage, redis, websites, etc.) require that I come up with a unique name for the service that will be suffixed by something related to the resource type. The naming restrictions on these varies but tends to be short and often disallows anything other than alphabetic characters.
After creating a handful of Azure resources, I quickly run into problems with coming up with new names for my resources that are meaningful yet not already taken by someone else. I am very close to just generating random character sequences for names and giving up on having them be usefully named. However, I know this will lead to an incredibly poor user experience for myself but it isn't much better than the random names I am having to come up with to avoid collision.
As a web developer, I have my own domain name and have no need to have these services available on a shared domain. Randomly generated names would not be so bad if my resources showed up in the Azure portal with my personal domain name (*.mydomain.com). Also, when I go to get a connection string for a resource I would want the connection string to be for my personal domain name, not the randomly generated one.
Alternatively, allow users to pay some fee to purchase a subdomain namespace on all Azure resources. This way, I could purchase mysubdomain and all of my resources would be under mysubdomain.core.windows.net etc. This way, at least I only have to come up with a good subdomain once (just like coming up with a good .com domain name) and all of my resources could be named reasonably (and displayed reasonably) under that subdomain.
We name all ours with the domain in the sub part. Example if I work for acmerubber.com then I make:
What irritates me intensely is I can't have dashes in a storage accountname, so I end up with **** names like:
for my media storage account. Lame, but yeah - try suffixing your domain-name-with-dashes-instead-of-dots onto your desired name for whatever resource
I've noticed the same thing. They poorly structured their resource naming conventions, so it's all muddied between different resources.
They should do what other cloud providers do and make the subdomain name less important, and have a resource label that is used throughout the UI (instead of the subdomain). This would mean that even if the resource subdomain is "shfui994j2lfsd.windowsblahblah.com" in the UI you would have a nice title of "business-res-001" or something.