updates content and error codes

Author: davidsmatlak

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

@@ -1,23 +1,23 @@
 ---
 title: Troubleshoot common Azure deployment errors
-description: Describes common deployment errors for Azure resources that are deployed with Azure Resource Manager templates (ARM templates) or Bicep files.
+description: Describes common Azure deployment errors for resources that are deployed with Bicep files or Azure Resource Manager templates (ARM templates).
 tags: top-support-issue
 ms.topic: troubleshooting
-ms.date:  05/16/2022
+ms.date:  08/05/2022
 ms.custom: devx-track-azurepowershell
 ---
 
 # Troubleshoot common Azure deployment errors
 
-This article describes common Azure deployment errors, and provides information about solutions. Azure resources can be deployed with Azure Resource Manager templates (ARM templates) or Bicep files. If you can't find the error code for your deployment error, see [Find error code](find-error-code.md).
+This article describes common Azure deployment errors, and provides information about solutions. Azure resources can be deployed with Bicep files or Azure Resource Manager templates (ARM templates). If you can't find the error code for your deployment error, see [Find error code](find-error-code.md).
 
 If your error code isn't listed, submit a GitHub issue. On the right side of the page, select **Feedback**. At the bottom of the page, under **Feedback** select **This page**. Provide your documentation feedback but **don't include confidential information** because GitHub issues are public.
 
 ## Error codes
 
 | Error code | Mitigation | More information |
 | ---------- | ---------- | ---------------- |
-| AccountNameInvalid | Follow naming restrictions for storage accounts. | [Resolve storage account name](error-storage-account-name.md) |
+| AccountNameInvalid | Follow naming guidelines for storage accounts. | [Resolve errors for storage account names](error-storage-account-name.md) |
 | AccountPropertyCannotBeSet | Check available storage account properties. | [storageAccounts](/azure/templates/microsoft.storage/storageaccounts) |
 | AllocationFailed | The cluster or region doesn't have resources available or can't support the requested VM size. Retry the request at a later time, or request a different VM size. | [Provisioning and allocation issues for Linux](/troubleshoot/azure/virtual-machines/troubleshoot-deployment-new-vm-linux) <br><br> [Provisioning and allocation issues for Windows](/troubleshoot/azure/virtual-machines/troubleshoot-deployment-new-vm-windows) <br><br> [Troubleshoot allocation failures](/troubleshoot/azure/virtual-machines/allocation-failure)|
 | AnotherOperationInProgress | Wait for concurrent operation to complete. | |
@@ -33,7 +33,7 @@ If your error code isn't listed, submit a GitHub issue. On the right side of the
 | DeploymentJobSizeExceeded | Simplify your template to reduce size. | [Resolve template size errors](error-job-size-exceeded.md) |
 | DnsRecordInUse | The DNS record name must be unique. Enter a different name. | |
 | ImageNotFound | Check VM image settings. |  |
-| InaccessibleImage | Azure Container Instance deployment fails. You might need to include the image's tag with the syntax `registry/image:tag` to deploy the container. For a private registry, verify your credentials are correct. | [Find error code](find-error-code.md) | 
+| InaccessibleImage | Azure Container Instance deployment fails. You might need to include the image's tag with the syntax `registry/image:tag` to deploy the container. For a private registry, verify your credentials are correct. | [Find error code](find-error-code.md) |
 | InternalServerError | Caused by a temporary problem. Retry the deployment. | |
 | InUseSubnetCannotBeDeleted | This error can occur when you try to update a resource, if the request process deletes and creates the resource. Make sure to specify all unchanged values. | [Update resource](/azure/architecture/guide/azure-resource-manager/advanced-templates/update-resource) |
 | InvalidAuthenticationTokenTenant | Get access token for the appropriate tenant. You can only get the token from the tenant that your account belongs to. | |
@@ -42,7 +42,7 @@ If your error code isn't listed, submit a GitHub issue. On the right side of the
 | InvalidParameter | One of the values you provided for a resource doesn't match the expected value. This error can result from many different conditions. For example, a password may be insufficient, or a blob name may be incorrect. The error message should indicate which value needs to be corrected. | [ARM template parameters](../templates/parameters.md) <br><br> [Bicep parameters](../bicep/parameters.md) |
 | InvalidRequestContent | The deployment values either include values that aren't recognized, or required values are missing. Confirm the values for your resource type. | [Template reference](/azure/templates/) |
 | InvalidRequestFormat | Enable debug logging when running the deployment, and verify the contents of the request. | [Debug logging](enable-debug-logging.md) |
-| InvalidResourceLocation | Provide a unique name for the storage account. | [Resolve storage account name](error-storage-account-name.md) |
+| InvalidResourceLocation | Provide a unique name for the storage account. | [Resolve errors for storage account names](error-storage-account-name.md) |
 | InvalidResourceNamespace | Check the resource namespace you specified in the **type** property. | [Template reference](/azure/templates/) |
 | InvalidResourceReference | The resource either doesn't yet exist or is incorrectly referenced. Check whether you need to add a dependency. Verify that your use of the **reference** function includes the required parameters for your scenario. | [Resolve dependencies](error-not-found.md) |
 | InvalidResourceType | Check the resource type you specified in the **type** property. | [Template reference](/azure/templates/) |
@@ -73,7 +73,8 @@ If your error code isn't listed, submit a GitHub issue. On the right side of the
 | ResourceNotFound | Your deployment references a resource that can't be resolved. Verify that your use of the **reference** function includes the parameters required for your scenario. | [Resolve references](error-not-found.md) |
 | ResourceQuotaExceeded | The deployment is trying to create resources that exceed the quota for the subscription, resource group, or region. If possible, revise your infrastructure to stay within the quotas. Otherwise, consider requesting a change to your quotas. | [Resolve quotas](error-resource-quota.md) |
 | SkuNotAvailable | Select SKU (such as VM size) that is available for the location you've selected. | [Resolve SKU](error-sku-not-available.md) |
-| StorageAccountAlreadyExists <br> StorageAccountAlreadyTaken | Provide a unique name for the storage account. | [Resolve storage account name](error-storage-account-name.md)  |
+| StorageAccountAlreadyTaken <br> StorageAccountAlreadyExists | Provide a unique name for the storage account. | [Resolve errors for storage account names](error-storage-account-name.md)  |
+| StorageAccountInAnotherResourceGroup | Provide a unique name for the storage account. | [Resolve errors for storage account names](error-storage-account-name.md)  |
 | StorageAccountNotFound | Check the subscription, resource group, and name of the storage account that you're trying to use. | |
 | SubnetsNotInSameVnet | A virtual machine can only have one virtual network. When deploying several NICs, make sure they belong to the same virtual network. | [Windows VM multiple NICs](../../virtual-machines/windows/multiple-nics.md) <br><br> [Linux VM multiple NICs](../../virtual-machines/linux/multiple-nics.md) |
 | SubnetIsFull | There aren't enough available addresses in the subnet to deploy resources. You can release addresses from the subnet, use a different subnet, or create a new subnet. | [Manage subnets](../../virtual-network/virtual-network-manage-subnet.md) and [Virtual network FAQ](../../virtual-network/virtual-networks-faq.md#are-there-any-restrictions-on-using-ip-addresses-within-these-subnets) <br><br> [Private IP addresses](../../virtual-network/ip-services/private-ip-addresses.md) |

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

@@ -1,47 +1,76 @@
 ---
-title: Storage account name errors
-description: Describes errors that can occur when specifying a storage account name in an Azure Resource Manager template (ARM template) or Bicep file.
+title: Resolve errors for storage account names
+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).
 ms.topic: troubleshooting
-ms.date: 11/12/2021
+ms.date: 08/05/2022
 ---
 
 # Resolve errors for storage account names
 
-This article describes naming errors that can occur when deploying a storage account with an Azure Resource Manager template (ARM template) or Bicep file.
+This article 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). Common causes for an error are a storage account name with invalid characters or a storage account that uses the same name as an existing storage account. Storage account names must be globally unique across Azure.
 
 ## Symptom
 
-If your storage account name includes prohibited characters, like an uppercase letter or exclamation point, you receive an error:
+An invalid storage account name causes an error code during deployment. The following are some examples of errors for storage account names.
+
+### Account name invalid
+
+If your storage account name includes prohibited characters, like an uppercase letter or special character like an exclamation point.
 
 ```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 resource name that's unique across Azure. If you don't provide a unique name, you receive an error:
+### Invalid resource location
+
+If you try to deploy a new storage account with the same name and in the same resource group, but use a different location as an existing storage account in your Azure subscription. The error indicates the storage account already exists and can't be created in the new location. Select a different name to create the new storage account.
 
 ```Output
-Code=StorageAccountAlreadyTaken
-Message=The storage account named mystorage is already taken.
+Code=InvalidResourceLocation
+Message=The resource 'storageckrexph7isnoc' already exists in location 'westus'
+in resource group 'demostorage'. A resource with the same name cannot be created in location 'eastus'.
+Please select a new resource name.
+```
+
+### Storage account in another resource group
+
+If you try to deploy a new storage account with the same name and location as an existing storage account but in a different resource group in your subscription.
+
+```Output
+Code=StorageAccountInAnotherResourceGroup
+Message=The account storageckrexph7isnoc is already in another resource group in this subscription.
 ```
 
-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.
+### Storage account already taken
+
+If you try to deploy a new storage account with the same name as a storage account that already exists in Azure. The existing storage account name might be in your subscription or tenant, or anywhere across Azure. Storage account names must be globally unique across Azure.
+
+```Output
+Code=StorageAccountAlreadyTaken
+Message=The storage account named storageckrexph7isnoc is already taken.
+```
 
 ## Cause
 
-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.
+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:
+
+- Length between 3 and 24 characters with only lowercase letters and numbers.
+- Must be globally unique across Azure. Storage account names can't be duplicated in Azure.
 
 ## Solution
 
-You can create a unique name by concatenating your naming convention with the result of the `uniqueString` function.
+You can create a unique name by concatenating a prefix or suffix with a value from the `uniqueString` function.
+
+The following examples specify a prefix with the string `storage` that's concatenated with the value from `uniqueString`.
 
 # [Bicep](#tab/bicep)
 
 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' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2021-09-01' = {
   name: 'storage${uniqueString(resourceGroup().id)}'
 ```
 
@@ -58,7 +87,7 @@ ARM templates use [concat](../templates/template-functions-string.md#concat) wit
 
 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.
+The following examples use a parameter named `storageNamePrefix` that creates a prefix with a maximum of 11 characters.
 
 # [Bicep](#tab/bicep)
 
@@ -85,7 +114,7 @@ param storageNamePrefix string = 'storage'
 
 ---
 
-You then concatenate the parameter value with the `uniqueString` value to create a storage account name.
+You then concatenate the `storageNamePrefix` parameter's value with the `uniqueString` value to create a storage account name.
 
 # [Bicep](#tab/bicep)
 

articles/azure-resource-manager/troubleshooting/toc.yml

@@ -22,7 +22,7 @@
     items:
     - name: Common deployment errors
       href: common-deployment-errors.md
-    - name: Account name invalid
+    - name: Storage account name invalid
       href: error-storage-account-name.md
     - name: Deployment quota exceeded
       href: deployment-quota-exceeded.md