Merge pull request #320 from garjen55/master

Change Log: AZ-104: MicrosoftAzureAdministrator		1

Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md

@@ -147,7 +147,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro
 
 1. In the **InPrivate** browser window, in the Azure portal, search and select **Help + support** and then click **+ New support request**. 
 
-1. In the **InPrivate** browser window, on the **Basic** tab of the **Help + support - New support request** blade, select the **Service and subscription limits (quotas)** issue type and note that the subscription you are using in this lab is listed in the **Subscription** drop-down list.
+1. In the **InPrivate** browser window, on the **Basic** tab of the **Help + support - New support request** blade, type **Service and subscription limits** in the Summary field and select the **Service and subscription limits (quotas)** issue type. Note that the subscription you are using in this lab is listed in the **Subscription** drop-down list.
 
     >**Note**: The presence of the subscription you are using in this lab in the **Subscription** drop-down list indicates that the account you are using has the permissions required to create the subscription-specific support request.
 
@@ -187,13 +187,11 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro
 
 1. In the Azure portal, navigate back to the **Management groups** blade. 
 
-1. On the **Management groups** blade, in the **Child subscriptions** column, in the row representing the name of the management group to which you want to move the Azure subscription you used in this lab, select the link represeting its current number of subscriptions.
+1. On the **Management groups** blade, select the **ellipsis** icon next to your subscription under the **az104-02-mg1** management group and select **Move** to move the subscription to the **Tenant Root management group**.
 
    >**Note**: It is likely that the target management group is the **Tenant Root management group**, unless you created a custom management group hierarchy before running this lab.
    
-1. On the **Subscriptions** blade of the target management group, select **+ Add**.
-
-1. On the **Add subscription** blade, in the **Subscriptions** drop-down list, select the name of the Azure subscription you used in this lab and click **Save**.
+1. Select **Refresh** to verify that the subscription has successfully moved to the **Tenant Root management group**.
 
 1. Navigate back to the **Management groups** blade, right click the **ellipsis** icon to the right of the **az104-02-mg1** management group and click **Delete**.
 

Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md

@@ -118,11 +118,11 @@ In this task, you will assign the built-in *Require a tag and its value on resou
 
 1. Navigate back to the blade of the resource group hosting the storage account used for the Cloud Shell home drive, which you identified in the previous task.
 
-1. On the resource group blade, click **+ Add**.
+1. On the resource group blade, click **+ Add** and then **+ Marketplace**.
 
 1. On the **New** blade, search for and select **Storage account**, and click **Create**. 
 
-1. On the **Basics** tab of the **Create storage account** blade, specify the following settings (leave others with their defaults), click **Review + create** and then click **Create**:
+1. On the **Basics** tab of the **Create storage account** blade, verify that you are using the Resource Group that the Policy was applied to and specify the following settings (leave others with their defaults), click **Review + create** and then click **Create**:
 
     | Setting | Value |
     | --- | --- |
@@ -184,11 +184,11 @@ In this task, we will use a different policy definition to remediate any non-com
 
 1. Navigate back to the blade of the resource group hosting the storage account used for the Cloud Shell home drive, which you identified in the first task.
 
-1. On the resource group blade, click **+ Add**.
+1. On the resource group blade, click **+ Add** and **+ Marketplace**.
 
 1. On the **New** blade, search for and select **Storage account**, and click **Create**. 
 
-1. On the **Basics** tab of the **Create storage account** blade, specify the following settings (leave others with their defaults) and click **Review + create**:
+1. On the **Basics** tab of the **Create storage account** blade, verify that you are using the Resource Group that the Policy was applied to and specify the following settings (leave others with their defaults) and click **Review + create**:
 
     | Setting | Value |
     | --- | --- |

Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md

@@ -64,7 +64,7 @@ In this task, we will move the disk resource you created in the previous task to
 
 1. On the **Move resources** blade, click **Create a new group**.
 
-1. Below the **Resource group** text box, click **Create a new group** then type **az104-03a-rg2** in the text box, select the checkbox **I understand that tools and scripts associated with moved resources will not work until I update them to use new resource IDs**, and click **OK**.
+1. Below the **Resource group** text box, click **Create new** then type **az104-03a-rg2** in the text box. On the Review tab, select the checkbox **I understand that tools and scripts associated with moved resources will not work until I update them to use new resource IDs**, and click **Move**.
 
     >**Note**: Do not wait for the move to complete but instead proceed to the next task. The move might take about 10 minutes. You can determine that the operation was completed by monitoring activity log entries of the source or target resource group. Revisit this step once you complete the next task.
 

Instructions/Labs/LAB_04-Implement_Virtual_Networking.md

@@ -282,7 +282,7 @@ In this task, you will configure DNS name resolution within a virtual network by
 
 In this task, you will configure external DNS name resolution by using Azure public DNS zones.
 
-1. In the web browser, open a new tab and navigate to <https://www.godaddy.com/domains/domain-name-search>.
+1. In the web browser on the **SEA-DEV** lab system, open a new tab and navigate to <https://www.godaddy.com/domains/domain-name-search>.
 
 1. Use the domain name search to identify a domain name which is not in use.
 

Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md

@@ -443,6 +443,7 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
     | --- | --- |
     | Name | **az104-06-lb4-lbrule1** |
     | IP Version | **IPv4** |
+    | Frontend IP Address | **select the LoadBalancerFrontEnd from the drop down**
     | Protocol | **TCP** |
     | Port | **80** |
     | Backend port | **80** |
@@ -507,7 +508,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
     | Setting | Value |
     | --- | --- |
     | Frontend IP address type | **Public** |
-    | Firewall public IP address| the name of a new public ip address **az104-06-pip5** |
+    | Public IP address| the name of a new public ip address **az104-06-pip5** |
 
 1. Click **Next: Backends >**, on the **Backends** tab of the **Create an application gateway** blade, click **Add a backend pool**, and, on the **Add a backend pool** blade, specify the following settings (leave others with their default values):
 

Instructions/Labs/LAB_08-Manage_Virtual_Machines.md

@@ -130,7 +130,7 @@ In this task, you will install Windows Server Web Server role on the two Azure v
 
 1. In the Azure portal, search for and select **Storage accounts** and, on the **Storage accounts** blade, click the entry representing the diagnostics storage account you created in the previous task.
 
-1. On the storage account blade, in the **Blob service** section, click **Containers** and then click **+ Container**.
+1. On the storage account blade, in the **Data Storage** section, click **Containers** and then click **+ Container**.
 
 1. On the **New container** blade, specify the following settings (leave others with their default values) and click **Create**:
 
@@ -269,7 +269,7 @@ In this task you will scale compute for Azure virtual machines by changing their
 
     >**Note**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case.
 
-1. On the **Edit template** blade, in the section displaying the content of the template, replace the line **30** `"vmSize": "Standard_D2s_v3"` with the following line):
+1. On the **Edit template** blade, in the section displaying the content of the template, replace the line **35** `"vmSize": "Standard_D2s_v3"` with the following line):
 
    ```json
                     "vmSize": "Standard_DS1_v2"
@@ -278,7 +278,7 @@ In this task you will scale compute for Azure virtual machines by changing their
 
     >**Note**: This section of the template defines the same Azure virtual machine size as the one you specified for the first virtual machine via the Azure portal.
 
-1. On the **Edit template** blade, in the section displaying the content of the template, replace line **50** (`"dataDisks": [ ]` line) with the following code :
+1. On the **Edit template** blade, in the section displaying the content of the template, replace line **55** (`"dataDisks": [ ]` line) with the following code :
 
    ```json
                     "dataDisks": [
@@ -304,7 +304,7 @@ In this task you will scale compute for Azure virtual machines by changing their
     >**Note**: This section of the template creates two managed disks and attaches them to **az104-08-vm1**, similarly to the storage configuration of the first virtual machine via the Azure portal.
 
 
-1. Click **Save** and, back on the **Custom template** blade, enable the checkbox **I agree to the terms and conditions stated above** and click **Purchase**.
+1. Click Save and, back on the Custom template blade, click Review + Create and, on the Review + Create blade, click Create.
 
     >**Note**: Wait for the template deployment to complete. You can monitor its progress from the **Disks** blade of the **az104-08-vm1** virtual machine. This should take no more than 3 minutes.
 
@@ -344,7 +344,7 @@ In this task you will scale compute for Azure virtual machines by changing their
 
 In this task, you will deploy Azure virtual machine scale set across availability zones by using the Azure portal.
 
-1. In the Azure portal, search for and select **Virtual machine scale sets** and, on the **Virtual machine scale sets** blade, click **+ Add**, click **+ Virtual machine**.
+1. In the Azure portal, search for and select **Virtual machine scale sets** and, on the **Virtual machine scale sets** blade, click **+ Add** (or **+ Create**).
 
 1. On the **Basics** tab of the **Create a virtual machine scale set** blade, specify the following settings (leave others with their default values) and click **Next : Disks >**:
 
@@ -450,7 +450,7 @@ In this task, you will install Windows Server Web Server role on the instances o
 
 1. In the Azure portal, search for and select **Storage accounts** and, on the **Storage accounts** blade, click the entry representing the diagnostics storage account you created in the previous task.
 
-1. On the storage account blade, in the **Blob service** section, click **Containers** and then click **+ Container**.
+1. On the storage account blade, in the **Data Storage** section, click **Containers** and then click **+ Container**.
 
 1. On the **New container** blade, specify the following settings (leave others with their default values) and click **Create**:
 
@@ -573,7 +573,7 @@ In this task, you will change the size of virtual machine scale set instances, c
     | Storage type | **Standard HDD** |
     | Size (GiB) | **32** |
 
-1. Save the change, in the **Settings** section of the **az10408vmss0** blade, click **Instances**, select the checkboxes next to the two instances of the virtual machine scale set, click **Upgrade**, and then, when prompted for confirmation, click **Yes**.
+1. Save the change, in the **Settings** section of the **az10408vmss0** blade, click **Instances**, select the checkboxes next to the instances of the virtual machine scale set, click **Upgrade**, and then, when prompted for confirmation, click **Yes**.
 
     >**Note**: The disk attached in the previous step is a raw disk. Before it can be used, it is necessary to create a partition, create a filesystem, and mount it. To accomplish this, you will use Azure virtual machine Custom Script extension. First, you will need to remove the existing Custom Script Extension.
 
@@ -605,7 +605,7 @@ In this task, you will change the size of virtual machine scale set instances, c
 
 1. Close the Cloud Shell pane.
 
-1. In the **Settings** section of the **az10408vmss0** blade, click **Instances**, select the checkboxes next to the two instances of the virtual machine scale set, click **Upgrade**, and then, when prompted for confirmation, click **Yes**.
+1. In the **Settings** section of the **az10408vmss0** blade, click **Instances**, select the checkboxes next to the instances of the virtual machine scale set, click **Upgrade**, and then, when prompted for confirmation, click **Yes**.
 
 #### Clean up resources
 

Instructions/Labs/LAB_10-Implement_Data_Protection.md

@@ -406,7 +406,7 @@ In this task, you will restore a file from the Azure virtual machine-level snaps
 
 1. On the **az104-10-rsv1 - Properties** blade, click the **Update** link under **Security Settings** label.
 
-1. On the **Security Settings** blade, Disable **Soft Delete (For Azure Virtual Machines)** and click **Save**.
+1. On the **Security Settings** blade, Disable **Soft Delete (For eligible Backup Management Types)** and click **Save**.
 
     >**Note**: This will not affect items already in soft delete state.