Prod

Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md

@@ -133,7 +133,7 @@ In this task, you work with the Azure Cloud Shell and Azure PowerShell. Azure Cl
 
 1. On mount storage account page, select **I want to create a storage account**. click on Next.
 
-1. Provide the below details to create the storage account and click on **Next**.
+1. Provide the below details to create the storage account and click on **Create**.
 
     >**Note:** As you work with the Cloud Shell a storage account and file share is required. 
 
@@ -184,14 +184,15 @@ In this task, you work with the Azure Cloud Shell and Azure PowerShell. Azure Cl
 
 ## Task 4: Deploy a template with the CLI 
 
-1. Continue in the **Cloud Shell** select **Bash**. **Confirm** your choice.
+1. Continue in the **Cloud Shell** select **Switch to Bash**. **Confirm** your choice.
 
 1. Verify your files are available in the Cloud Shell storage. If you completed the previous task your template files should be available. 
 
     ```sh
     ls
     ```
-
+    >**Note**: If you are not able to see the files, click on **Manage Files**, click on **Upload** and upload the file.
+
 1. Select the **Editor** (curly brackets) icon and navigate to the template JSON file.
 
 1. Make a change. For example, change the disk name to **az104-03b-disk4**. Use **Ctrl +S** to save your changes. 

Instructions/Labs/LAB_04-Implement_Virtual_Networking.md

@@ -225,11 +225,11 @@ You can configure Azure DNS to resolve host names in your public domain. For exa
 
     ![image](../media/l4i11.png)
 
-1. Select **Review create** and then **Create**.
+1. Select **Review + create** and then **Create**.
 
 1. Wait for the DNS zone to deploy and then select **Go to resource**.
 
-1. On the **Overview** blade select **Recordsets** and notice the names of the four Azure DNS name servers assigned to the zone. **Copy** one of the name server addresses. You will need it in a future step. 
+1. On the **Overview** blade select **Recordsets** under DNS Management and notice the names of the four Azure DNS name servers assigned to the zone. **Copy** one of the name server addresses. You will need it in a future step. 
 
     ![image](../media/l4i12.png)
 
@@ -275,13 +275,13 @@ A private DNS zone provides name resolution services within virtual networks. A
     | Name | `private.contoso.com` (adjust if you had to rename) |
     | Region | **<inject key="Region" enableCopy="false" />** |
 
-1. Select **Review create** and then **Create**.
+1. Select **Review + create** and then **Create**.
 
 1. Wait for the DNS zone to deploy and then select **Go to resource**.
 
 1. Notice on the **Overview** blade there are no name server records. 
 
-1. Select **Virtual network links** from the left navigation pane and then select **+ Add**. 
+1. Select **Virtual network links** from the left navigation pane under DNS Management and then select **+ Add**. 
 
     | Property | Value    |
     |:---------|:---------|
@@ -290,7 +290,7 @@ A private DNS zone provides name resolution services within virtual networks. A
 
 1. Select **OK** and wait for the link to create. 
 
-1. From the **Overview** blade select **+ Record set**. You would now add a record for each virtual machine that needs private name-resolution support.
+1. Select **Recordsets** under DNS Management. Click on **+ Add**.
 
     | Property | Value    |
     |:---------|:---------|

Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md

@@ -26,15 +26,21 @@ In this task, you will deploy three virtual machines, each into a separate virtu
     ![Image](./Images/cloudshell.png)
 
 1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**. 
-1. If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Show Advanced Settings**. 
-
-    ![image](../media/advancesetting.png)
-
-1. Under **Advanced Settings**, you need to select an existing resource group from the **Resource group (1)** dropdown and enter under the **Storage Account (2)** section as **cloudshell<inject key="DeploymentID" enableCopy="false" />**, and under the **File share (3)** section type **none** as shown in the below image.
 
-1. Click **Create storage (4)**, and wait until the Azure Cloud Shell pane is displayed. 
+1. On the **You have no storage mounted** screen select **Mount Storage Account**, select the storage account subscription from drop down and click on **Apply**
+
+1. On mount storage account page, select **I want to create a storage account**. click on Next.
+
+1. Provide the below details to create the storage account and click on **Create**.
 
-    ![image](../media/crtstr.png)
+    >**Note:** As you work with the Cloud Shell a storage account and file share is required. 
+
+    | Settings | Values |
+    |  -- | -- |
+    | Resource Group | **az104-05-rg0-<inject key="DeploymentID" enableCopy="false" />** |
+    | Storage account (Create new) | **cloudshell<inject key="DeploymentID" enableCopy="false" />** |
+    | Region | **<inject key="Region" enableCopy="false" />** |
+    | File share (Create new) | **none** |
 
 1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **C:\AllFiles\AZ-104-MicrosoftAzureAdministrator-Lab-Files\Allfiles\Labs\05\\az104-05-vnetvm-loop-template.json** and **C:\AllFiles\AZ-104-MicrosoftAzureAdministrator-Lab-Files\Allfiles\Labs\05\\az104-05-vnetvm-loop-parameters.json** into the Cloud Shell home directory.
 
@@ -127,16 +133,16 @@ In this task, you will configure local and global peering between the virtual ne
 
     | Setting | Value|
     | --- | --- |
-    | This virtual network: Peering link name | **az104-05-vnet0_to_az104-05-vnet1** |
-    | Settings to **allow** access, forwarded traffic, and gateway | **Ensure only the first three boxes are checked** |
     | Remote virtual network: Peering link name | **az104-05-vnet1_to_az104-05-vnet0** |
     | Virtual network deployment model | **Resource manager** |
     | I know my resource ID | unselected |
     | Subscription | the name of the Azure subscription you are using in this lab |
     | Virtual network | **az104-05-vnet1** |
+    | Settings to **allow** access, forwarded traffic, and gateway | **Ensure only the first three boxes are checked** |
+    | This virtual network: Peering link name | **az104-05-vnet0_to_az104-05-vnet1** |
     | Settings to **allow** access, forwarded traffic, and gateway | **Ensure only the first three boxes are checked** |
 
-     ![Image](./Images/peering.png)
+     ![Image](./Images/peering-1.png)
 
 
     >**Note**: This step establishes two local peerings - one from az104-05-vnet0 to az104-05-vnet1 and the other from az104-05-vnet1 to az104-05-vnet0.
@@ -164,14 +170,14 @@ In this task, you will configure local and global peering between the virtual ne
 
     | Setting | Value|
     | --- | --- |
-    | This virtual network: Peering link name | **az104-05-vnet0_to_az104-05-vnet2** |
-    | Settings to **allow** access, forwarded traffic, and gateway | **Ensure the box is checked** |
     | Remote virtual network: Peering link name | **az104-05-vnet2_to_az104-05-vnet0** |
     | Virtual network deployment model | **Resource manager** |
     | I know my resource ID | unselected |
     | Subscription | the name of the Azure subscription you are using in this lab |
     | Virtual network | **az104-05-vnet2** |
     | Settings to **allow** access, forwarded traffic, and gateway | **Ensure the box is checked** |
+    | This virtual network: Peering link name | **az104-05-vnet0_to_az104-05-vnet2** |
+    | Settings to **allow** access, forwarded traffic, and gateway | **Ensure the box is checked** |
 
     >**Note**: This step establishes two global peerings - one from az104-05-vnet0 to az104-05-vnet2 and the other from az104-05-vnet2 to az104-05-vnet0.
 
@@ -200,13 +206,13 @@ In this task, you will configure local and global peering between the virtual ne
 
     | Setting | Value|
     | --- | --- |
-    | This virtual network: Peering link name | **az104-05-vnet1_to_az104-05-vnet2** |
-    | Settings to **allow** access, forwarded traffic, and gateway | **Ensure the box is checked** |
     | Remote virtual network: Peering link name | **az104-05-vnet2_to_az104-05-vnet1** |
     | Virtual network deployment model | **Resource manager** |
     | I know my resource ID | unselected |
     | Subscription | the name of the Azure subscription you are using in this lab |
     | Virtual network | **az104-05-vnet2** |
+    | Settings to **allow** access, forwarded traffic, and gateway | **Ensure the box is checked** | 
+    | This virtual network: Peering link name | **az104-05-vnet1_to_az104-05-vnet2** |
     | Settings to **allow** access, forwarded traffic, and gateway | **Ensure the box is checked** |
 
     >**Note**: This step establishes two global peerings - one from az104-05-vnet1 to az104-05-vnet2 and the other from az104-05-vnet2 to az104-05-vnet1.
@@ -327,14 +333,14 @@ In this task, you want to control network traffic between the perimeter subnet a
     | Setting | Value | 
     | --- | --- |
     | Subscription | your subscription |
-    | Resource group | `az104-05-rg0-`  |
+    | Resource group | `az104-05-rg0-<inject key="DeploymentID" enableCopy="false" />`  |
     | Region | **East US** |
     | Name | `az104-05-vm0` |
     | Propagate gateway routes | **No** |
 
 1. After the route table deploys, select **Go to resource**.
 
-1. Select **Routes** and then **+ Add**. Create a route from the future NVA to the CoreServices virtual network. 
+1. Select **Routes** under Settings and then **+ Add**. Create a route from the future NVA to the CoreServices virtual network. 
 
     | Setting | Value | 
     | --- | --- |

Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md

@@ -115,9 +115,9 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
     | Setting | Value |
     | --- | --- |
     | Name | **az104-06-pip4** |
-    | Availability zone | **No Zone** and click **Ok** |
+    | Availability zone | **No Zone** and click **Save** |
 
-1. Back on **Add frontend IP configuration** click on **Add** and click on **Next : Backend pools>**
+1. Back on **Add frontend IP configuration** click on **Save** and click on **Next : Backend pools>**
 
 1. On **Backend pools** tab, and click **+ Add a Backend pools**.
 
@@ -198,14 +198,13 @@ In this task, you will implement an Azure Application Gateway in front of the tw
 
     ![](../Labs/media/l6-image16.png)
 
-1. Add a subnet with the following settings (leave others with their default values) and click **Save**.
+1. Add a subnet with the following settings (leave others with their default values) and click **Add**.
 
     | Setting | Value |
     | --- | --- |
     | Name | **subnet-appgw** |
-    | Subnet address range | **10.60.3.224/27** |
-
-    ![](../Labs/media/l6-image17.png)
+    | Starting address | **10.60.3.224** |
+    | Size | **/27** |
 
     > **Note**: This subnet will be used by the Azure Application Gateway instances, which you will deploy later in this task. The Application Gateway requires a dedicated subnet of /27 or larger size.
 
@@ -345,7 +344,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
 
 1. Start another browser window and navigate to the IP address you identified in the previous step.
 
-1. Verify that the browser window displays the message **Hello World from az104-06-vm2** or **Hello World from az104-06-vm3**.
+1. Verify that the browser window displays the message **Hello World from az104-06-vm1** or **Hello World from az104-06-vm2**.
 
    ![image](../media/az-104(9).png)
 

Instructions/Labs/LAB_07-Manage_Azure_Storage.md

@@ -53,9 +53,9 @@ In this task, you will create and configure an Azure Storage account.
     | Performance | **Standard** |
     | Redundancy | **Geo-redundant storage (GRS)** |
 
-1. Click **Next: Advanced >**, on the **Advanced** tab of the **Create a storage account** blade, review the available options, accept the defaults, and click **Next: Networking >**.
+1. Click **Next**, on the **Advanced** tab of the **Create a storage account** blade, review the available options, accept the defaults, and click **Next**.
 
-1. On the **Networking** tab of the **Create a storage account** blade, review the available options and select Disable public access and use private access under network access. Click **Next: Data protection >**.
+1. On the **Networking** tab of the **Create a storage account** blade, review the available options and select Disable public access and use private access under network access. Click **Next**.
 
 1. On the **Data protection** tab of the **Create a storage account** blade, review the available options and accept the defaults. Click **Review + Create** and wait for the validation process to complete. Then click on **Create**.
 
@@ -263,7 +263,7 @@ In this task, you will create and configure Azure Files shares.
 
 1. In the **Settings** section, select the **Subnets** blade.
     + Select the **default** subnet.
-    + In the **Service endpoints** section choose **Microsoft.Storage** in the **Services** drop-down.
+    + In the **Service endpoints** section choose **Microsoft.Storage.Global** in the **Services** drop-down.
     + Do not make any other changes.    
     + Be sure to **Save** your changes. 
 
@@ -273,7 +273,7 @@ In this task, you will create and configure Azure Files shares.
 
 1. Under **Firewalls and virtual networks** tab, for **Public network access** select **Enabled from selected virtual networks and IP addresses**. 
 
-1. Select **add existing virtual network** and select **vnet1** and **default** subnet, select **Add**.
+1. Select **add existing virtual network** and select **vnet1** and **default** subnet, select **Enable**.
 
 1. Be sure to **Save** your changes.
 

Instructions/Labs/LAB_08-Manage_Virtual_Machines.md

@@ -366,6 +366,7 @@ In this task, you scale the virtual machine scale set using a custom scale rule.
     | Region         | **<inject key="Region" enableCopy="false"/>** |
     | Storage account name | **str<inject key="DeploymentID" enableCopy="false" />** |
     | File share  | **none** |
+    | Location  | **East US** |
 
 1. Run the following command to create a virtual machine. When prompted, provide a username and password for the VM. While you wait check out the [New-AzVM](https://learn.microsoft.com/powershell/module/az.compute/new-azvm?view=azps-11.1.0) command reference for all the parameters associated with creating a virtual machine.
 

Instructions/Labs/LabIntro2.md

@@ -68,9 +68,7 @@ Feel free to start, stop, or restart your virtual machine as needed from the **R
 
 1. First-time users are often prompted to Stay Signed In, if you see any such pop-up, click on No.
 
-1. If a **Welcome to Microsoft Azure** popup window appears, click Maybe Later to skip the tour.
-
-     ![](../Labs/Images/maybelater.png)   
+1. If a **Welcome to Microsoft Azure** popup window appears, click **Cancel** to skip the tour.
 
 1. Click "Next" from the bottom right corner to embark on your Lab journey!