From c9b09c4a5697677ac9b4a37b751838b5f3f63cde Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Tue, 5 Dec 2023 16:24:17 -0800
Subject: [PATCH] Update
 LAB_03-Manage_Azure_Resources_by_Using_ARM_Templates.md

---
 ..._Azure_Resources_by_Using_ARM_Templates.md | 31 +++++++++++++++++--
 1 file changed, 28 insertions(+), 3 deletions(-)

diff --git a/New Instructions/Lab/LAB_03-Manage_Azure_Resources_by_Using_ARM_Templates.md b/New Instructions/Lab/LAB_03-Manage_Azure_Resources_by_Using_ARM_Templates.md
index 2920b3d7..41c51a50 100644
--- a/New Instructions/Lab/LAB_03-Manage_Azure_Resources_by_Using_ARM_Templates.md	
+++ b/New Instructions/Lab/LAB_03-Manage_Azure_Resources_by_Using_ARM_Templates.md	
@@ -146,7 +146,7 @@ In this task, you verify that the deployment has finished successfuly. All prior
 
 1. As you have time, try the deployment again. Be sure to make a change, like disk name, before you deploy.
    
-## Task 4: Experiment with Azure PowerShell (optional)
+## Task 4: Experiment with using Azure PowerShell to deploy a template (optional)
 
 1. Open the Cloud Shell, and select **PowerShell**.
 
@@ -163,7 +163,7 @@ In this task, you verify that the deployment has finished successfuly. All prior
     ```powershell
     dir
     ```
-    >**Note**: You can target your template deployment to a resource group, subscription, management group, or tenant. Depending on the scope of the deployment, you use different commands.
+>**Note**: You can target your template deployment to a resource group, subscription, management group, or tenant. Depending on the scope of the deployment, you use different commands.
 
 1. To deploy to a resource group, use **New-AzResourceGroupDeployment**.
 
@@ -172,7 +172,32 @@ In this task, you verify that the deployment has finished successfuly. All prior
     ```
 1. Ensure the command completes and the ProvisioningState is **Succeeded**.
    
-## Task 5: Experiment with CLI (optional)
+## Task 5: Experiment with using the CLI to deploy a template (optional)
+
+1. Open the Cloud Shell, and select **Bash**.
+
+1. If necessary, use the **Advanced** settings to create disk storage for the Cloud Shell.
+
+1. On the local drive, locate the parameters JSON file.
+
+1. Edit the file and change the disk name. For example, change the disk name to **az104-disk2**.
+
+1. In the Cloud Shell, use the **Upload** icon to upload the template and parameters files. You will need to each separately.
+
+1. Verify your files are available in the Cloud Shell storage.
+
+    ```sh
+    dir
+    ```
+
+>**Note**: You can target your template deployment to a resource group, subscription, management group, or tenant. Depending on the scope of the deployment, you use different commands.
+
+1. To deploy to a resource group, use **az deployment group create**.
+
+    ```sh
+    az deployment group create --resource-group az104-rg3 --template-file template.json --parameters parameters.json
+    ```
+1. Ensure the command completes and the ProvisioningState is **Succeeded**.
 
 ## Review