none
Naming Azure Storage

    Question

  • Hi,

    When I give a name to my storage account I get "You used a word that may be considered offensive, or the word is embedded in another word." First of all the word isn't offensive at all. When using the same word for naming eg a Service Bus Namespace there's no problem at all.

    Why can't I use it for a storage account and for other services without problems?

    Thanks.
    Guy

    Wednesday, June 24, 2015 10:07 PM

Answers

  • Hi,

     You are right, I guess this is something that needs to be looked into by Azure.
     I Would suggest, if possible, create a support ticket and have an Azure support professional look into this issue as your Subscription information and Access to backend logs might be required.
     you can create a support ticket here.
     
    Regards,
    Nithin Rathnakar

    Friday, June 26, 2015 11:37 AM

All replies

  • Hi,
     
     Windows Azure uses URL’s to address and locate services and objects in the cloud. Most of the naming rules follow standard DNS naming rules. The uniqueness constraint of URL addresses will make naming objects in different development environments difficult without a consistent strategy.
     
     Storage account names must be between 3 and 24 characters in length and use numbers and lower-case letters only. This name is the DNS prefix name and can be used to access blobs, queues, and tables in the storage account. The name should follow the following format: ProjectName + CompanyName + Environment.
      Example: projectname + CompanyName + dev

      For example:

      Service Endpoint
      • Blobs http://projectnameCompanyNamedev.blob.core.windows.net/
      • Tables http:// projectnameCompanyNamedev.table.core.windows.net/
      • Queues http:// projectnameCompanyNamedev.queue.core.windows.net/

     The storage account name should match the Cloud Services name.

     Reference: http://www.adamjwolf.com/posts/azure-paas-naming-guidelines.html
     
    Regards,
    Nithin Rathnakar

    Thursday, June 25, 2015 6:54 AM
  • Hi,

    The "general" naming of my storage account isn't the problem (I use already something similar, I use companyname + projectjname + environment). The problem is with the project name I use. The same project name works with eg Service Bus (=same principle as with Storage Account: URL must be unique within Azure etc.).

    Thanks.

    Guy

    Thursday, June 25, 2015 8:10 AM
  • Hi,

     You are right, I guess this is something that needs to be looked into by Azure.
     I Would suggest, if possible, create a support ticket and have an Azure support professional look into this issue as your Subscription information and Access to backend logs might be required.
     you can create a support ticket here.
     
    Regards,
    Nithin Rathnakar

    Friday, June 26, 2015 11:37 AM