Skip to content

Commit accc2aa

Browse files
Merge pull request #297048 from mumian/0326-troubleshoot-storage-account-name
Refresh the article
2 parents 611a68b + 2820caf commit accc2aa

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

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

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Resolve errors for storage account names
33
description: Describes how to resolve errors for Azure storage account names that can occur during deployment with a Bicep file or Azure Resource Manager template (ARM template).
44
ms.topic: troubleshooting
55
ms.custom: devx-track-arm-template, devx-track-bicep
6-
ms.date: 06/20/2024
6+
ms.date: 03/26/2025
77
---
88

99
# Resolve errors for storage account names
@@ -58,8 +58,9 @@ There are two main causes for this error.
5858
## Cause 1
5959

6060
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.
61+
62+
- Length between 3 and 24 characters with only lowercase letters and numbers.
63+
- Must be globally unique across Azure. Storage account names can't be duplicated in Azure.
6364

6465
## Solution 1
6566

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

134+
---
135+
133136
## Cause 2
134137

135138
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](/azure/security/fundamentals/subdomain-takeover).
139+
140+
If a request to create the storage account comes from a different subscription and tenant than where it was previously located, it is denied for security purposes as described here, [Prevent dangling DNS entries and avoid subdomain takeover](/azure/security/fundamentals/subdomain-takeover).
137141

138142
## Solution 2
139143

140-
[Create a Support Request](/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-
142-
---
144+
[Create a Support Request](/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. Make sure to include the name of the storage account and the approximate time when account creation failed.

0 commit comments

Comments
 (0)