Merge pull request #177650 from davidsmatlak/ds-updates-troubleshooting

Updates ARM troubleshooting docs

Author: laurabren

articles/azure-resource-manager/troubleshooting/common-deployment-errors.md

@@ -1,46 +1,58 @@
 ---
 title: Storage account name errors
-description: Describes the errors you may encounter when specifying a storage account name.
+description: Describes errors that can occur when specifying a storage account name in an Azure Resource Manager template (ARM template) or Bicep file.
 ms.topic: troubleshooting
-ms.date: 03/09/2018
+ms.date: 10/26/2021
 ---
+
 # Resolve errors for storage account names
 
-This article describes naming errors you may encounter when deploying a storage account.
+This article describes naming errors that can occur when deploying a storage account with an Azure Resource Manager template (ARM template) or Bicep file.
 
 ## Symptom
 
-If your storage account name includes prohibited characters, you receive an error like:
+If your storage account name includes prohibited characters, like an uppercase letter or exclamation point, you receive an error:
 
-```
+```Output
 Code=AccountNameInvalid
 Message=S!torageckrexph7isnoc is not a valid storage account name. Storage account name must be
 between 3 and 24 characters in length and use numbers and lower-case letters only.
 ```
 
-For storage accounts, you must provide a name for the resource that is unique across Azure. If you do not provide a unique name, you receive an error like:
+For storage accounts, you must provide a resource name that's unique across Azure. If you don't provide a unique name, you receive an error:
 
-```
+```Output
 Code=StorageAccountAlreadyTaken
 Message=The storage account named mystorage is already taken.
 ```
 
-If you deploy a storage account with the same name as an existing storage account in your subscription, but provide a different location, you receive an error indicating the storage account already exists in a different location. Either delete the existing storage account, or provide the same location as the existing storage account.
+If you deploy a storage account with the same name as an existing storage account in your subscription, but in a different location, you receive an error. The error indicates the storage account already exists in a different location. Either delete the existing storage account or use the same location as the existing storage account.
 
 ## Cause
 
-Storage account names must be between 3 and 24 characters in length and use numbers and lower-case letters only. The name must be unique.
+Storage account names must be between 3 and 24 characters in length and only use numbers and lowercase letters. No uppercase letters or special characters. The name must be unique.
 
 ## Solution
 
-Make sure the storage account name is unique. You can create a unique name by concatenating your naming convention with the result of the [uniqueString](../templates/template-functions-string.md#uniquestring) function.
+You can create a unique name by concatenating your naming convention with the result of the `uniqueString` function.
+
+ARM templates use [concat](../templates/template-functions-string.md#concat) with [uniqueString](../templates/template-functions-string.md#uniquestring).
 
 ```json
 "name": "[concat('storage', uniqueString(resourceGroup().id))]",
 "type": "Microsoft.Storage/storageAccounts",
 ```
 
-Make sure your storage account name does not exceed 24 characters. The [uniqueString](../templates/template-functions-string.md#uniquestring) function returns 13 characters. If you concatenate a prefix or postfix to the **uniqueString** result, provide a value that is 11 characters or less.
+Bicep uses [string interpolation](../bicep/bicep-functions-string.md#concat) with [uniqueString](../bicep/bicep-functions-string.md#uniquestring).
+
+```bicep
+resource storageAccount 'Microsoft.Storage/storageAccounts@2021-04-01' = {
+  name: 'storage${uniqueString(resourceGroup().id)}'
+```
+
+Make sure your storage account name doesn't exceed 24 characters. The `uniqueString` function returns 13 characters. If you want to concatenate a prefix or suffix, provide a value that's 11 characters or less.
+
+The following examples use a parameter that creates a prefix with a maximum of 11 characters.
 
 ```json
 "parameters": {
@@ -49,10 +61,24 @@ Make sure your storage account name does not exceed 24 characters. The [uniqueSt
     "maxLength": 11,
     "defaultValue": "storage",
     "metadata": {
-    "description": "The value to use for starting the storage account name."
+    "description": "The prefix value for the storage account name."
     }
   }
 }
 ```
 
-Make sure your storage account name does not include any upper-case letters or special characters.
+```bicep
+@description('The prefix value for the storage account name.')
+@maxLength(11)
+param storageNamePrefix string = 'storage'
+```
+
+You then concatenate the parameter value with the `uniqueString` value to create a storage account name.
+
+```json
+"name": "[concat(parameters('storageNamePrefix'), uniquestring(resourceGroup().id))]"
+```
+
+```bicep
+name: '${storageNamePrefix}${uniqueString(resourceGroup().id)}'
+```