Skip to content

Commit 8a329ef

Browse files
authored
Merge pull request #125845 from justingross-msft/patch-4
Update error-storage-account-name.md
2 parents e4907d6 + 8e0177b commit 8a329ef

File tree

1 file changed

+16
-6
lines changed

1 file changed

+16
-6
lines changed

articles/azure-resource-manager/troubleshooting/error-storage-account-name.md

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -53,14 +53,15 @@ Code=StorageAccountAlreadyTaken
5353
Message=The storage account named storageckrexph7isnoc is already taken.
5454
```
5555

56-
## Cause
56+
There are two main causes for this error.
5757

58-
Common reasons for an error are because the storage account name uses invalid characters or is a duplicate name. Storage account names must meet the following criteria:
58+
## Cause 1
5959

60-
- Length between 3 and 24 characters with only lowercase letters and numbers.
61-
- Must be globally unique across Azure. Storage account names can't be duplicated in Azure.
62-
63-
## Solution
60+
The storage account name uses invalid characters or is a duplicate name. Storage account names must meet the following criteria:
61+
- Length between 3 and 24 characters with only lowercase letters and numbers.
62+
- Must be globally unique across Azure. Storage account names can't be duplicated in Azure.
63+
64+
## Solution 1
6465

6566
You can create a unique name by concatenating a prefix or suffix with a value from the `uniqueString` function.
6667

@@ -129,4 +130,13 @@ name: '${storageNamePrefix}${uniqueString(resourceGroup().id)}'
129130
"name": "[concat(parameters('storageNamePrefix'), uniquestring(resourceGroup().id))]"
130131
```
131132

133+
## Cause 2
134+
135+
The storage account was recently deleted.
136+
- If a request to create the storage account comes from a different subscription and tenant than where it was previously located, it will be denied for security purposes as described here, [Prevent dangling DNS entries and avoid subdomain takeover](https://docs.microsoft.com/azure/security/fundamentals/subdomain-takeover).
137+
138+
## Solution 2
139+
140+
[Create a Support Request](https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request#create-a-support-request****) and choose **Create new storage account** for the problem type, and **Failure(s) during new account creation** for the Problem subtype. Please make sure to include the name of the storage account and the approximate time when account creation failed.
141+
132142
---

0 commit comments

Comments
 (0)