Skip to content

Commit 7512a1f

Browse files
authored
Merge pull request #177724 from tfitzmac/1026qs1
add links to troubleshooting topics
2 parents 058514f + c0ecb85 commit 7512a1f

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-bicep-deployment.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,9 @@ New-AzResourceGroupDeployment `
121121

122122
---
123123

124-
Azure Resource Manager determines that the name of the storage account contains characters that aren't allowed. It doesn't attempt the deployment. You see an error message that indicates preflight validation failed. You also get a message that says the storage account name must be between 3 and 24 characters in length and use numbers and lower-case letters only.
124+
Azure Resource Manager determines that the name of the storage account contains characters that aren't allowed. It doesn't attempt the deployment.
125+
126+
You see an error message that indicates preflight validation failed. You also get a message that says the storage account name must be between 3 and 24 characters in length and use numbers and lower-case letters only. The prefix you provided didn't meet that requirement. For more information about this error code, see [Resolve errors for storage account names](error-storage-account-name.md).
125127

126128
Because the error was caught in preflight, no deployment exists in the history.
127129

@@ -153,7 +155,9 @@ New-AzResourceGroupDeployment -ResourceGroupName troubleshootRG -TemplateFile tr
153155

154156
---
155157

156-
The deployment starts but fails with a message that the virtual network wasn't found. Notice in the portal that the deployment appears in the history.
158+
The deployment starts but fails with a message that the virtual network wasn't found. Typically, you would fix this error by changing the reference to the resource. In this quickstart, you'll delete the reference. For more information about this error code, see [Resolve resource not found errors](error-not-found.md).
159+
160+
Notice in the portal that the deployment appears in the history.
157161

158162
:::image type="content" source="media/quickstart-troubleshoot-bicep-deployment/view-deployment-history.png" alt-text="Screenshot of deployment history in portal.":::
159163

0 commit comments

Comments
 (0)