Merge pull request #109544 from mumian/0330-add-debug

0330 add debug

Author: PRMerger8

articles/azure-resource-manager/templates/template-tutorial-add-functions.md

@@ -67,6 +67,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.

articles/azure-resource-manager/templates/template-tutorial-add-outputs.md

@@ -85,6 +85,9 @@ In the output for the deployment command, you'll see an object similar to:
 }
 ```
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Review your work
 
 You've done a lot in the last six tutorials. Let's take a moment to review what you have done. You created a template with parameters that are easy to provide. The template is reusable in different environments because it allows for customization and dynamically creates needed values. It also returns information about the storage account that you could use in your script.

articles/azure-resource-manager/templates/template-tutorial-add-parameters.md

@@ -107,6 +107,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 To see the flexibility of your template, let's deploy again. This time set the SKU parameter to **Standard_GRS**. You can either pass in a new name to create a different storage account, or use the same name to update your existing storage account. Both options work.
 
 # [PowerShell](#tab/azure-powershell)

articles/azure-resource-manager/templates/template-tutorial-add-resource.md

@@ -21,7 +21,7 @@ You must have Visual Studio Code with the Resource Manager Tools extension, and
 
 To add a storage account definition to the existing template, look at the highlighted JSON in the following example. Instead of trying to copy sections of the template, copy the whole file and replace your template with its contents.
 
-Replace **{provide-unique-name}** with a unique storage account name.
+Replace **{provide-unique-name}** (including the curly brackets) with a unique storage account name.
 
 > [!IMPORTANT]
 > The storage account name must be unique across Azure. The name must have only lowercase letters or numbers. It can be no longer than 24 characters. You might try a naming pattern like using **store1** as a prefix and then adding your initials and today's date. For example, the name you use could look like **store1abc09092019**.
@@ -78,6 +78,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 Two possible deployment failures that you might encounter:
 
 - Error: Code=AccountNameInvalid; Message={provide-unique-name} is not a valid storage account name. Storage account name must be between 3 and

articles/azure-resource-manager/templates/template-tutorial-add-tags.md

@@ -65,6 +65,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.

articles/azure-resource-manager/templates/template-tutorial-add-variables.md

@@ -76,6 +76,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.

articles/azure-resource-manager/templates/template-tutorial-create-first-template.md

@@ -123,7 +123,7 @@ $templateFile = "{provide-the-path-to-the-template-file}"
 New-AzResourceGroupDeployment `
   -Name blanktemplate `
   -ResourceGroupName myResourceGroup `
-  -TemplateFile $templateFile
+  -TemplateFile $templateFile 
 ```
 
 # [Azure CLI](#tab/azure-cli)
@@ -152,6 +152,9 @@ The deployment command returns results. Look for `ProvisioningState` to see whet
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.

articles/azure-resource-manager/templates/template-tutorial-export-template.md

@@ -104,6 +104,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Verify deployment
 
 You can verify the deployment by exploring the resource group from the Azure portal.

articles/azure-resource-manager/templates/template-tutorial-quickstart-template.md

@@ -84,6 +84,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Clean up resources
 
 If you're moving on to the next tutorial, you don't need to delete the resource group.

articles/azure-resource-manager/templates/template-tutorial-use-parameter-file.md

@@ -115,6 +115,9 @@ az deployment group create \
 
 ---
 
+> [!NOTE]
+> If the deployment failed, use the **debug** switch with the deployment command to show the debug logs.  You can also use the **verbose** switch to show the full debug logs.
+
 ## Verify deployment
 
 You can verify the deployment by exploring the resource groups from the Azure portal.