diff --git a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md index c5057d67..777f87e3 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -33,13 +33,15 @@ In this task, you will create and configure Azure AD users. >**Note**: If you have previously used the Trial license for Azure AD Premium on this Azure AD Tenant you will need a new Azure AD Tenant or perform the Task 2 after Task 3 in that new Azure AD tenant. +1. Sign in to the [Azure portal](https://portal.azure.com). + 1. In the Azure portal, search for and select **Azure Active Directory**. 1. On the Azure Active Directory blade, scroll down to the **Manage** section, click **User settings**, and review available configuration options. 1. On the Azure Active Directory blade, in the **Manage** section, click **Users**, and then click your user account to display its **Profile** settings. -1. Click **edit**, in the **Settings** section, set **Usage location** to **United States** and save the change. +1. Click **edit**, in the **Settings** section, set **Usage location** to **United States** and click **save** to apply the change. >**Note**: This is necessary in order to assign an Azure AD Premium P2 license to your user account later in this lab. @@ -185,6 +187,11 @@ In this task, you will create a new Azure AD tenant. | Setting | Value | | --- | --- | | Directory type | **Azure Active Directory** | + +1. Click **Next : Configuration** + + | Setting | Value | + | --- | --- | | Organization name | **Contoso Lab** | | Initial domain name | any valid DNS name consisting of lower case letters and digits and starting with a letter | | Country/Region | **United States** | @@ -212,6 +219,8 @@ In this task, you will create Azure AD guest users and grant them access to reso | Job title | **System Administrator** | | Department | **IT** | +1. Click on the newly created profile. + >**Note**: **Copy to clipboard** the full **User Principal Name** (user name plus domain). You will need it later in this task. 1. Switch back to your default Azure AD tenant by using the **Directory + Subscription** button (directly to the right of the Cloud Shell button) in the Azure portal toolbar. @@ -223,7 +232,7 @@ In this task, you will create Azure AD guest users and grant them access to reso | Setting | Value | | --- | --- | | Name | **az104-01b-aaduser1** | - | Email address | any valid email address not matching any of user principal names in the current tenant or the copied User Principal Name from above | + | Email address | the User Principal Name you copied earlier in this task | | Usage location | **United States** | | Job title | **Lab Administrator** | | Department | **IT** | diff --git a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md index f51409e9..7e868b83 100644 --- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md +++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md @@ -55,6 +55,8 @@ In this task, you will create and assign a tag to an Azure resource group via th 1. On the storage account blade, click the link representing the name of the resource group containing the storage account. + **Note**: note what resource group the storage account is in, you'll need it later in the lab. + 1. On the resource group blade, click **Tags**. 1. Create a tag with the following settings and save your change: diff --git a/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md b/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md index ef19ad60..a2e8915f 100644 --- a/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md +++ b/Instructions/Labs/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md @@ -76,7 +76,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. In the **Resource group** text box, type **az104-03a-rg2**, 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 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**. >**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. @@ -89,7 +89,7 @@ In this task, you will apply a resource lock to an Azure resource group containi |Setting|Value| |---|---| |Subscription| the name of the subscription you are using in this lab | - |Resource Group| the name of a new resource group **az104-03a-rg3** | + |Resource Group| click **create new** resource group and name it **az104-03a-rg3** | |Disk name| **az104-03a-disk2** | |Region| the name of the Azure region where you created the other resource groups in this lab | |Availability zone| **None** | @@ -99,16 +99,16 @@ In this task, you will apply a resource lock to an Azure resource group containi 1. Click **Review + Create** and then click **Create**. -1. In the Azure portal, search for and select **Resource groups**. +1. Click Go to resouce. -1. In the list of resource groups, click the entry representing the **az104-03a-rg3** resource group. - -1. On the **az104-03a-rg3** resource group blade, click **Locks** and add a lock with the following settings: +1. On the **az104-03a-rg3** resource group blade, click **Locks** then **+ Add** and specify the following settings: |Setting|Value| |---|---| |Lock name| **az104-03a-delete-lock** | |Lock type| **Delete** | + +1. Click **OK** 1. On the **az104-03a-rg3** resource group blade, click **Overview**, in the list of resource group resources, select the entry representing the disk you created earlier in this task, and click **Delete** in the toolbar. @@ -120,7 +120,7 @@ In this task, you will apply a resource lock to an Azure resource group containi 1. Navigate back to the list of resources of the **az104-03a-rg3** resource group and click the entry representing the **az104-03a-disk2** resource. -1. On the **az104-03a-disk2** blade, in the **Settings** section, click **Size + performance**, set the disk type and size to **Premium SSD** and **64 GiB**, respectively, and apply the change. Verify that the change was successful. +1. On the **az104-03a-disk2** blade, in the **Settings** section, click **Size + performance**, set the disk type and size to **Premium SSD** and **64 GiB**, respectively, and click **Resize** to apply the change. Verify that the change was successful. >**Note**: This is expected, since the resource group-level lock applies to delete operations only. diff --git a/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md b/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md index ef951d83..fd5a7d38 100644 --- a/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md +++ b/Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md @@ -58,6 +58,8 @@ In this task, you will create an Azure disk resource by using an Azure Resource 1. In the Azure portal, search for and select **Deploy a custom template**. +1. Click **Template deployment (deploy using custom templates)** found under the **Marketplace** group. + 1. On the **Custom deployment** blade, click **Build your own template in the editor**. 1. On the **Edit template** blade, click **Load file** and upload the **template.json** file you downloaded in the previous task. diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index 92b259d2..ddf681e2 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -45,16 +45,25 @@ In this task, you will create a virtual network with multiple subnets by using t | Resource Group | the name of a **new** resource group **az104-04-rg1** | | Name | **az104-04-vnet1** | | Region | the name of any Azure region available in the subscription you will use in this lab | - | IPv4 address space | **10.40.0.0/20** | - | Subnet name | **subnet0** | - | Subnet address range | **10.40.0.0/24** | +1. Click **Next : IP Addresses** and enter the following values + + | Setting | Value | + | --- | --- | + | IPv4 address space | **10.40.0.0/20** | + +1. Click **+ Add subnet** enter the following values then click **Add** + + | Setting | Value | + | --- | --- | + | Subnet name | **subnet0** | + | Subnet address range | **10.40.0.0/24** | 1. Accept the defaults and click **Review and Create**. Let validation occur, and hit **Create** again to submit your deployment. >**Note:** Wait for the virtual network to be provisioned. This should take less than a minute. -1. Once the deployment completes browse for **Virtual Networks** in the portal search bar. Within **Virtual networks** blade, click on the newly created virtual network **az104-04-vnet1**. +1. Click on **Go to resource** 1. On the **az104-04-vnet1** virtual network blade, click **Subnets** and then click **+ Subnet**. @@ -66,6 +75,8 @@ In this task, you will create a virtual network with multiple subnets by using t | Address range (CIDR block) | **10.40.1.0/24** | | Network security group | **None** | | Route table | **None** | + +1. Click **Save** #### Task 2: Deploy virtual machines into the virtual network @@ -127,7 +138,24 @@ In this task, you will configure static assignment of public and private IP addr 1. Back on the **ipconfig1** blade, save the changes. -1. Navigate back to the **az104-04-vnet1** blade and repeat the previous six steps to change the IP address assignment of **ipconfig1** of **az104-04-nic1** to **Static** and associate **az104-04-nic1** with a new Standard SKU public IP address named **az104-04-pip1**. +1. Navigate back to the **az104-04-vnet1** blade + +1. Click **az104-04-nic1** and, on the **az104-04-nic1** blade, click **IP configurations**. + + >**Note**: Verify that **ipconfig1** is currently set up with a dynamic private IP address. + +1. In the list IP configurations, click **ipconfig1**. + +1. On the **ipconfig1** blade, set **Assignment** to **Static**, leave the default value of **IP address** set to **10.40.1.4**. + +1. On the **ipconfig1** blade, in the **Public IP address settings** section, select **Associate**, click **+ Create new**, specify the following settings, and click **OK**: + + | Setting | Value | + | --- | --- | + | Name | **az104-04-pip1** | + | SKU | **Standard** | + +1. Back on the **ipconfig1** blade, save the changes. 1. Navigate back to the **az104-04-rg1** resource group blade, in the list of its resources, click **az104-04-vm0**, and from the **az104-04-vm0** virtual machine blade, note the public IP address entry. @@ -158,6 +186,8 @@ In this task, you will configure network security groups in order to allow for r | Resource Group | **az104-04-rg1** | | Name | **az104-04-nsg01** | | Region | the name of the Azure region where you deployed all other resources in this lab | + +1. Click **Review and Create**. Let validation occur, and hit **Create** to submit your deployment. >**Note**: Wait for the deployment to complete. This should take about 2 minutes. @@ -210,6 +240,8 @@ In this task, you will configure DNS name resolution within a virtual network by | Subscription | the name of the Azure subscription you are using in this lab | | Resource Group | **az104-04-rg1** | | Name | **contoso.org** | + +1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment. >**Note**: Wait for the private DNS zone to be created. This should take about 2 minutes. @@ -217,7 +249,7 @@ In this task, you will configure DNS name resolution within a virtual network by 1. On the **contoso.org** private DNS zone blade, in the **Settings** section, click **Virtual network links** -1. Add a virtual network link with the following settings (leave others with their default values): +1. Click **+ Add** to create a virtual network link with the following settings (leave others with their default values): | Setting | Value | | --- | --- | @@ -225,6 +257,8 @@ In this task, you will configure DNS name resolution within a virtual network by | Subscription | the name of the Azure subscription you are using in this lab | | Virtual network | **az104-04-vnet1** | | Enable auto registration | enabled | + +1. Click **OK**. >**Note:** Wait for the virtual network link to be created. This should take less than 1 minute. @@ -260,6 +294,8 @@ In this task, you will configure external DNS name resolution by using Azure pub | Subscription | the name of the Azure subscription you are using in this lab | | Resource Group | **az104-04-rg1** | | Name | the DNS domain name you identified earlier in this task | + +1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment. >**Note**: Wait for the DNS zone to be created. This should take about 2 minutes. @@ -277,6 +313,10 @@ In this task, you will configure external DNS name resolution by using Azure pub | TTL | **1** | | TTL unit | **Hours** | | IP address | the public IP address of **az104-04-vm0** which you identified in the third exercise of this lab | + +1. Click **OK** + +1. On the DNS zone blade, click **+ Record set**. 1. Add a record set with the following settings (leave others with their default values): @@ -288,12 +328,14 @@ In this task, you will configure external DNS name resolution by using Azure pub | TTL | **1** | | TTL unit | **Hours** | | IP address | the public IP address of **az104-04-vm1** which you identified in the third exercise of this lab | + +1. Click **OK** 1. On the DNS zone blade, note the name of the **Name server 1** entry. 1. In the Azure portal, open the **PowerShell** session in **Cloud Shell** by clicking on the icon in the top right of the Azure Portal. -1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm0** DNS record set in the newly created DNS zone **(replace the placeholder `[Name server 1]` including the [] brackets**, with the name of **Name server 1** you noted earlier in this task and the `[domain name] placeholder with the name of the DNS domain you created earlier in this task): +1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm0** DNS record set in the the newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted earlier in this task and the `[domain name] placeholder with the name of the DNS domain you created earlier in this task): ```powershell nslookup az104-04-vm0.[domain name] [Name server 1] diff --git a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md index 6034a248..c36e6a3d 100644 --- a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md +++ b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md @@ -114,7 +114,7 @@ In this task, you will configure local and global peering between the virtual ne 1. On the **az104-05-vnet0** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. -1. Specify the following settings (leave others with their default values) and click **Add**: +1. Add a peering with the following settings (leave others with their default values) and click **Add**: | Setting | Value| | --- | --- | @@ -135,7 +135,7 @@ In this task, you will configure local and global peering between the virtual ne 1. On the **az104-05-vnet0** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. -1. Add a peering with the following settings (leave others with their default values): +1. Add a peering with the following settings (leave others with their default values) and click **Add**: | Setting | Value| | --- | --- | @@ -158,7 +158,7 @@ In this task, you will configure local and global peering between the virtual ne 1. On the **az104-05-vnet1** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. -1. Add a peering with the following settings (leave others with their default values): +1. Add a peering with the following settings (leave others with their default values) and click **Add**: | Setting | Value| | --- | --- | diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index 6cd791ae..ddaf6f7e 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -97,7 +97,7 @@ In this task, you will deploy four virtual machines into the same Azure region. -nameSuffix 3 ` -AsJob ``` - >**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 5 minutes. + >**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 5 - 15 minutes. >**Note**: To verify the status of the deployments, you can examine the properties of the resource groups you created in this task. @@ -117,19 +117,19 @@ In this task, you will configure local peering between the virtual networks you 1. On the **az104-06-vnet01** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. -1. Add a peering with the following settings (leave others with their default values): +1. Add a peering with the following settings (leave others with their default values) and click Add: | Setting | Value | | --- | --- | | This virtual network: Peering link name | **az104-06-vnet01_to_az104-06-vnet2** | - | Trafffic to remote virtual network | **Allow (default)** | + | Traffic to remote virtual network | **Allow (default)** | | Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** | | Virtual network gateway | **None (default)** | | Remote virtual network: Peering link name | **az104-06-vnet2_to_az104-06-vnet01** | | Virtual network deployment model | **Resource manager** | | Subscription | the name of the Azure subscription you are using in this lab | | Virtual network | **az104-06-vnet2** | - | Trafffic to remote virtual network | **Allow (default)** | + | Traffic to remote virtual network | **Allow (default)** | | Traffic forwarded from remote virtual network | **Allow (default)** | | Virtual network gateway | **None (default)** | @@ -141,19 +141,19 @@ In this task, you will configure local peering between the virtual networks you 1. On the **az104-06-vnet01** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. -1. Add a peering with the following settings (leave others with their default values): +1. Add a peering with the following settings (leave others with their default values) and click Add: | Setting | Value | | --- | --- | | This virtual network: Peering link name | **az104-06-vnet01_to_az104-06-vnet3** | - | Trafffic to remote virtual network | **Allow (default)** | + | Traffic to remote virtual network | **Allow (default)** | | Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** | | Virtual network gateway | **None (default)** | | Remote virtual network: Peering link name | **az104-06-vnet3_to_az104-06-vnet01** | | Virtual network deployment model | **Resource manager** | | Subscription | the name of the Azure subscription you are using in this lab | | Virtual network | **az104-06-vnet3** | - | Trafffic to remote virtual network | **Allow (default)** | + | Traffic to remote virtual network | **Allow (default)** | | Traffic forwarded from remote virtual network | **Allow (default)** | | Virtual network gateway | **None (default)** | @@ -280,17 +280,19 @@ In this task, you will configure and test routing between the two spoke virtual | Setting | Value | | --- | --- | - | Name | **az104-06-rt23** | | Subscription | the name of the Azure subscription you are using in this lab | | Resource group | **az104-06-rg2** | | Location | the name of the Azure region in which you created the virtual networks | + | Name | **az104-06-rt23** | | Propagate gateway routes | **No** | + +1. Click **Review and Create**. Let validation occur, and click **Create** to submit your deployment. > **Note**: Wait for the route table to be created. This should take about 3 minutes. 1. Back on the **Route tables** blade, click **Refresh** and then click **az104-06-rt23**. -1. On the **az104-06-rt23** route table blade, click **Routes** and then click **+ Add**. +1. On the **az104-06-rt23** route table blade, in the **Settings** section, click **Routes**, and then click **+ Add**. 1. Add a new route with the following settings (leave others with their default values): @@ -300,8 +302,10 @@ In this task, you will configure and test routing between the two spoke virtual | Address prefix | **10.63.0.0/20** | | Next hop type | **Virtual appliance** | | Next hop address | **10.60.0.4** | + +1. Click **OK** -1. Back on the **az104-06-rt23** route table blade, click **Subnets** and then click **+ Associate**. +1. Back on the **az104-06-rt23** route table blade, in the **Settings** section, click **Subnets**, and then click **+ Associate**. 1. Associate the route table **az104-06-rt23** with the following subnet: @@ -309,6 +313,8 @@ In this task, you will configure and test routing between the two spoke virtual | --- | --- | | Virtual network | **az104-06-vnet2** | | Subnet | **subnet0** | + +1. Click **OK** 1. Navigate back to **Route tables** blade and click **+ Add**. @@ -316,19 +322,21 @@ In this task, you will configure and test routing between the two spoke virtual | Setting | Value | | --- | --- | - | Name | **az104-06-rt32** | | Subscription | the name of the Azure subscription you are using in this lab | | Resource group | **az104-06-rg3** | - | Location | the name of the Azure region in which you created the virtual networks | - - + | Region | the name of the Azure region in which you created the virtual networks | + | Name | **az104-06-rt32** | + | Propagate gateway routes | **No** | + +1. Click Review and Create. Let validation occur, and hit Create to submit your deployment. + > **Note**: Wait for the route table to be created. This should take about 3 minutes. 1. Back on the **Route tables** blade, click **Refresh** and then click **az104-06-rt32**. -1. On the **az104-06-rt32** route table blade, click **Routes** and then click **+ Add**. +1. On the **az104-06-rt32** route table blade, in the **Settings** section, click **Routes**, and then click **+ Add**. -1. Add a new route with the following settings (leave others with their default values): +1. Add a new route with the following settings: | Setting | Value | | --- | --- | @@ -336,8 +344,10 @@ In this task, you will configure and test routing between the two spoke virtual | Address prefix | **10.62.0.0/20** | | Next hop type | **Virtual appliance** | | Next hop address | **10.60.0.4** | + +1. Click **OK** -1. Back on the **az104-06-rt32** route table blade, click **Subnets** and then click **+ Associate**. +1. Back on the **az104-06-rt32** route table blade, in the **Settings** section, click **Subnets**, and then click **+ Associate**. 1. Associate the route table **az104-06-rt32** with the following subnet: @@ -345,6 +355,8 @@ In this task, you will configure and test routing between the two spoke virtual | --- | --- | | Virtual network | **az104-06-vnet3** | | Subnet | **subnet0** | + +1.Click **OK** 1. In the Azure portal, navigate back to the **Network Watcher - Connection troubleshoot** blade. @@ -386,14 +398,15 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur | SKU | **Standard** | | Public IP address | **Create new** | | Public IP address name | **az104-06-pip4** | - | Availability zone | **Zone-redundant** | | Add a public IPv6 address | **No** | + +1. Click Review and Create. Let validation occur, and hit Create to submit your deployment. > **Note**: Wait for the Azure load balancer to be provisioned. This should take about 2 minutes. 1. On the deployment blade, click **Go to resource**. -1. On the **az104-06-lb4** load balancer blade, click **Backend pools** and click **+ Add**. +1. On the **az104-06-lb4** load balancer blade, in the **Settings** section, click **Backend pools**, and click **+ Add**. 1. Add a backend pool with the following settings (leave others with their default values): @@ -406,10 +419,12 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur | Virtual machine IP address | **ipconfig1 (10.60.0.4)** | | Virtual machine | **az104-06-vm1** | | Virtual machine IP address | **ipconfig1 (10.60.1.4)** | + +1. Click **Add** -1. Wait for the backend pool to be created, click **Health probes**, and then click **+ Add**. +1. Wait for the backend pool to be created, in the **Settings** section, click **Health probes**, and then click **+ Add**. -1. Add a health probe with the following settings (leave others with their default values): +1. Add a health probe with the following settings: | Setting | Value | | --- | --- | @@ -418,8 +433,10 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur | Port | **80** | | Interval | **5** | | Unhealthy threshold | **2** | + +1. Click **OK** -1. Wait for the health probe to be created, click **Load balancing rules**, and then click **+ Add**. +1. Wait for the health probe to be created, in the **Settings** section, click **Load balancing rules**, and then click **+ Add**. 1. Add a load balancing rule with the following settings (leave others with their default values): @@ -436,7 +453,8 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur | Idle timeout (minutes) | **4** | | TCP reset | **Disabled** | | Floating IP (direct server return) | **Disabled** | - | Use outbound rules to provide backend pool members access to the internet. | **Enabled** | + +1. Click **OK** 1. Wait for the load balancing rule to be created, click **Overview**, and note the value of the **Public IP address**. @@ -463,9 +481,9 @@ In this task, you will implement an Azure Application Gateway in front of the tw | Setting | Value | | --- | --- | | Name | **subnet-appgw** | - | Address range (CIDR block) | **10.60.3.224/27** | - | Network security group | **None** | - | Route table | **None** | + | Subnet address range | **10.60.3.224/27** | + +1. Click **Save** > **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. @@ -481,8 +499,6 @@ In this task, you will implement an Azure Application Gateway in front of the tw | Region | name of the Azure region into which you deployed all other resources in this lab | | Tier | **Standard V2** | | Enable autoscaling | **No** | - | Scale units | **1** | - | Availability zone | **1, 2, 3** | | HTTP2 | **Disabled** | | Virtual network | **az104-06-vnet01** | | Subnet | **subnet-appgw** | @@ -509,7 +525,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw 1. Click **Add**, click **Next: Configuration >** and, on the **Configuration** tab of the **Create an application gateway** blade, click **+ Add a routing rule**. -1. On the **Add a routing rule** blade, on the **Listener** tab, specify the following settings (leave others with their default values): +1. On the **Add a routing rule** blade, on the **Listener** tab, specify the following settings: | Setting | Value | | --- | --- | @@ -520,7 +536,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw | Port | **80** | | Listener type | **Basic** | | Error page url | **No** | - + 1. Switch to the **Backend targets** tab of the **Add a routing rule** blade and specify the following settings (leave others with their default values): | Setting | Value | @@ -528,11 +544,11 @@ In this task, you will implement an Azure Application Gateway in front of the tw | Target type | **Backend pool** | | Backend target | **az104-06-appgw5-be1** | -1. On the **Backend targets** tab of the **Add a routing rule** blade, click **Add new** next to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values): +1. Click **Add new** under to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values): | Setting | Value | | --- | --- | - | HTTP setting name | **az104-06-appgw5-http1** | + | HTTP setting | **az104-06-appgw5-http1** | | Backend protocol | **HTTP** | | Backend port | **80** | | Cookie-based affinity | **Disable** | diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index d60f573c..c9090fc2 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -16,7 +16,7 @@ You need to evaluate the use of Azure storage for storing files residing current In this lab, you will: + Task 1: Provision the lab environment -+ Task 2: Create and configure Azure Storage accounts ++ Task 2: Create and configure Azure Storage accounts + Task 3: Manage blob storage + Task 4: Manage authentication and authorization for Azure Storage + Task 5: Create and configure an Azure Files shares @@ -30,15 +30,15 @@ In this lab, you will: #### Task 1: Provision the lab environment -In this task, you will deploy an Azure virtual machine that you will use later in this lab. +In this task, you will deploy an Azure virtual machine that you will use later in this lab. 1. Sign in to the [Azure portal](https://portal.azure.com). 1. In the Azure portal, open the **Azure Cloud Shell** by clicking on the icon in the top right of the Azure Portal. -1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**. +1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**. - >**Note**: 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 **Create storage**. + >**Note**: 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 **Create storage**. 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 **\\Allfiles\\Module_07\\az104-07-vm-template.json** and **\\Allfiles\\Module_07\\az104-07-vm-parameters.json** into the Cloud Shell home directory. @@ -63,19 +63,19 @@ In this task, you will deploy an Azure virtual machine that you will use later i -AsJob ``` - >**Note**: Do not wait for the deployments to complete, but proceed to the next task. + >**Note**: Do not wait for the deployments to complete, but proceed to the next task. 1. Close the Cloud Shell pane. -#### Task 2: Create and configure Azure Storage accounts +#### Task 2: Create and configure Azure Storage accounts -In this task, you will create and configure an Azure Storage account. +In this task, you will create and configure an Azure Storage account. -1. In the Azure portal, search for and select **Storage accounts**, and then click **+ Add**. +1. In the Azure portal, search for and select **Storage accounts**, and then click **+ New**. 1. On the **Basics** tab of the **Create storage account** blade, specify the following settings (leave others with their default values): - | Setting | Value | + | Setting | Value | | --- | --- | | Subscription | the name of the Azure subscription you are using in this lab | | Resource group | the name of a **new** resource group **az104-07-rg1** | @@ -93,13 +93,13 @@ In this task, you will create and configure an Azure Storage account. >**Note**: Wait for the Storage account to be created. This should take about 2 minutes. -1. On the deployment blade, click **Go to resource** to display the Azure Storage account blade. +1. On the deployment blade, click **Go to resource** to display the Azure Storage account blade. 1. On the Azure Storage account blade, in the **Settings** section, click **Configuration**. -1. Click **Upgrade** to change the Storage account kind from **Storage (general purpose v1)** to **StorageV2 (general purpose v2)**. +1. Click **Upgrade** to change the Storage account kind from **Storage (general purpose v1)** to **StorageV2 (general purpose v2)**. -1. On the **Upgrade storage account** blade, review the warning stating that the upgrade is permanent and will result in billing charges, in the **Confirm upgrade** text box, type the name of the storage account, and click **Upgrade**. +1. On the **Upgrade storage account** blade, review the warning stating that the upgrade is permanent and will result in billing charges, in the **Confirm upgrade** text box, type the name of the storage account, and click **Upgrade**. > **Note**: You have the option to set the account kind to **StorageV2 (general purpose v2)** at the provisioning time. The previous two steps were meant to illustrate that you also have the option to upgrade existing general purpose v1 accounts. @@ -127,11 +127,11 @@ In this task, you will create and configure an Azure Storage account. #### Task 3: Manage blob storage -In this task, you will create a blob container and upload a blob into it. +In this task, you will create a blob container and upload a blob into it. 1. On the Storage account blade, in the **Blob service** section, click **Containers**. -1. Click **+ Container** and create a container with the following settings: +1. Click **+ Container** and create a container with the following settings: | Setting | Value | | --- | --- | @@ -140,7 +140,7 @@ In this task, you will create a blob container and upload a blob into it. 1. In the list of containers, click **az104-07-container** and then click **Upload**. -1. Browse to **\\Allfiles\\Module_07\\LICENSE** on your lab computer and click **Open**. +1. Browse to **\\Allfiles\\Module_07\\LICENSE** on your lab computer and click **Open**, then click **Upload**. 1. On the **Upload blob** blade, expand the **Advanced** section and specify the following settings (leave others with their default values): @@ -160,9 +160,9 @@ In this task, you will create a blob container and upload a blob into it. 1. Back on the **az104-07-container** blade, click **licenses** and then click **LICENSE**. -1. On the **licenses/LICENSE** blade, review the available options. +1. On the **licenses/LICENSE** blade, review the available options. - > **Note**: You have the option to download the blob, change its access tier (it is currently set to **Hot**), acquire a lease, which would change its lease status to **Locked** (it is currently set to **Unlocked**) and protect the blob from being modified or deleted, as well as assign custom metadata (by specifying an arbitrary key and value pairs). You also have the ability to **Edit** the file directly within the Azure portal interface, without downloading it first. You can also create snapshots, as well as generate a SAS token (you will explore this option in the next task). + > **Note**: You have the option to download the blob, change its access tier (it is currently set to **Hot**), acquire a lease, which would change its lease status to **Locked** (it is currently set to **Unlocked**) and protect the blob from being modified or deleted, as well as assign custom metadata (by specifying an arbitrary key and value pairs). You also have the ability to **Edit** the file directly within the Azure portal interface, without downloading it first. You can also create snapshots, as well as generate a SAS token (you will explore this option in the next task). #### Task 4: Manage authentication and authorization for Azure Storage @@ -170,7 +170,7 @@ In this task, you will configure authentication and authorization for Azure Stor 1. On the **licenses/LICENSE** blade, on the **Overview** tab, click **Copy to clipboard** button next to the **URL** entry. -1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step. +1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step. 1. You should be presented with an XML-formatted message stating **ResourceNotFound** or **PublicAccessNotPermitted**. @@ -182,24 +182,24 @@ In this task, you will configure authentication and authorization for Azure Stor | Setting | Value | | --- | --- | + | Signing key | **Key 1** | | Permissions | **Read** | | Start date | yesterday's date | | Start time | current time | | Expiry date | tomorrow's date | | Expiry time | current time | | Allowed IP addresses | leave blank | - | Allowed protocols | **HTTPS only** | - | Signing key | **Key 1** | + 1. Click **Generate SAS token and URL**. 1. Click **Copy to clipboard** button next to the **Blob SAS URL** entry. -1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step. +1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step. > **Note**: If you are using Microsoft Edge, you should be presented with the **The MIT License (MIT)** page. If you are using Chrome, Microsoft Edge (Chromium) or Firefox, you should be able to view the content of the file by downloading it and opening it with Notepad. - > **Note**: This is expected, since now your access is authorized based on the newly generated the SAS token. + > **Note**: This is expected, since now your access is authorized based on the newly generated the SAS token. > **Note**: Save the blob SAS URL. You will need it later in this lab. @@ -207,7 +207,7 @@ In this task, you will configure authentication and authorization for Azure Stor 1. Click the **Switch to the Azure AD User Account** link next to the **Authentication method** label. - > **Note**: At this point, you no longer have access to the container. + > **Note**: At this point, you no longer have access to the container. 1. On the **az104-07-container** blade, click **Access Control (IAM)**. @@ -224,12 +224,12 @@ In this task, you will configure authentication and authorization for Azure Stor 1. Save the change and return to the **Overview** blade of the **az104-07-container** container and verify that you can access to container again. > **Note**: It might take about 5 minutes for the change to take effect. - + #### Task 5: Create and configure an Azure Files shares In this task, you will create and configure Azure Files shares. - > **Note**: Before you start this task, verify that the virtual machine you provisioned in the first task of this lab is running. + > **Note**: Before you start this task, verify that the virtual machine you provisioned in the first task of this lab is running. 1. In the Azure portal, navigate back to the blade of the storage account you created in the first task of this lab and, in the **File service** section, click **File shares**. @@ -246,13 +246,13 @@ In this task, you will create and configure Azure Files shares. 1. In the Azure portal, search for and select **Virtual machines**, and, in the list of virtual machines, click **az104-07-vm0**. -1. On the **az104-07-vm0** blade, in the **Operations** section, click **Run command**. +1. On the **az104-07-vm0** blade, in the **Operations** section, click **Run command**. -1. On the **az104-07-vm0 - Run command** blade, click **RunPowerShellScript**. +1. On the **az104-07-vm0 - Run command** blade, click **RunPowerShellScript**. 1. On the **Run Command Script** blade, paste the script you copied earlier in this task into the **PowerShell Script** pane and click **Run**. -1. Verify that the script completed successfully. +1. Verify that the script completed successfully. 1. Replace the content of the **PowerShell Script** pane with the following script and click **Run**: @@ -262,9 +262,9 @@ In this task, you will create and configure Azure Files shares. New-Item -Type File -Path 'Z:\az104-07-folder\az-104-07-file.txt' ``` -1. Verify that the script completed successfully. +1. Verify that the script completed successfully. -1. Navigate back to the **az104-07-share** file share blade, click **Refresh**, and verify that **az104-07-folder** appears in the list of folders. +1. Navigate back to the **az104-07-share** file share blade, click **Refresh**, and verify that **az104-07-folder** appears in the list of folders. 1. Click **az104-07-folder** and verify that **az104-07-file.txt** appears in the list of files. @@ -276,11 +276,11 @@ In this task, you will configure network access for Azure Storage. 1. Click the **Selected networks** option and review the configuration settings that become available once this option is enabled. - > **Note**: You can use these settings to configure direct connectivity between Azure virtual machines on designated subnets of virtual networks and the storage account by using service endpoints. + > **Note**: You can use these settings to configure direct connectivity between Azure virtual machines on designated subnets of virtual networks and the storage account by using service endpoints. 1. Click the checkbox **Add your client IP address** and save the change. -1. Open another browser window by using InPrivate mode and navigate to the blob SAS URL you generated in the previous task. +1. Open another browser window by using InPrivate mode and navigate to the blob SAS URL you generated in the previous task. 1. You should be presented with the content of **The MIT License (MIT)** page. @@ -290,14 +290,14 @@ In this task, you will configure network access for Azure Storage. 1. In the Azure portal, open the **Azure Cloud Shell** by clicking on the icon in the top right of the Azure Portal. -1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**. +1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**. 1. From the Cloud Shell pane, run the following to attempt downloading of the LICENSE blob from the **az104-07-container** container of the storage account (replace the `[blob SAS URL]` placeholder with the blob SAS URL you generated in the previous task): ```powershell Invoke-WebRequest -URI '[blob SAS URL]' ``` -1. Verify that the download attempt failed. +1. Verify that the download attempt failed. > **Note**: You should receive the message stating **AuthorizationFailure: This request is not authorized to perform this operation**. This is expected, since you are connecting from the IP address assigned to an Azure VM hosting the Cloud Shell instance. @@ -328,7 +328,7 @@ In this task, you will configure network access for Azure Storage. In this lab, you have: - Provisioned the lab environment -- Created and configured Azure Storage accounts +- Created and configured Azure Storage accounts - Managed blob storage - Managed authentication and authorization for Azure Storage - Created and configured an Azure Files shares diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 471ff2b7..fdbdb1f8 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -128,7 +128,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, click **Containers** and then click **+ Container**. +1. On the storage account blade, in the **Blob service** 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**: @@ -163,6 +163,8 @@ In this task, you will install Windows Server Web Server role on the two Azure v 1. On the **Custom deployment** blade, click **Edit template**. + >**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, insert the following code starting with line **20** (directly underneath the `"resources": [` line): >**Note**: If you are using a tool that pastes the code in line by line intellisense may add extra brackets causing validation errors. You may want to paste the code into notepad first and then paste it into line 20. @@ -193,8 +195,6 @@ In this task, you will install Windows Server Web Server role on the two Azure v 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**. - >**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. - >**Note**: Wait for the template deployment to complete. You can monitor its progress from the **Extensions** blade of the **az104-08-vm0** and **az104-08-vm1** virtual machines. This should take no more than 3 minutes. 1. To verify that the Custom Script extension-based configuration was successful, navigate back on the **az104-08-vm1** blade, in the **Operations** section, click **Run command**, and, in the list of commands, click **RunPowerShellScript**. @@ -207,7 +207,7 @@ In this task, you will install Windows Server Web Server role on the two Azure v >**Note**: The **-UseBasicParsing** parameter is necessary to eliminate dependency on Internet Explorer to complete execution of the cmdlet - >**Note**: You can also connect to **az104-08-vm0** and run `Invoke-WebRequest -URI http://10.80.0.5` to access the web site hosted on **az104-08-vm1**. + >**Note**: You can also connect to **az104-08-vm0** and run `Invoke-WebRequest -URI http://10.80.0.5 -UseBasicParsing` to access the web site hosted on **az104-08-vm1**. #### Task 3: Scale compute and storage for Azure virtual machines @@ -342,7 +342,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**. +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. 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 >**: @@ -448,7 +448,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, click **Containers** and then click **+ Container**. +1. On the storage account blade, in the **Blob service** 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**: @@ -465,7 +465,7 @@ In this task, you will install Windows Server Web Server role on the instances o 1. In the Azure portal, navigate back to the **Virtual machine scale sets** blade and click **az10408vmss0**. -1. On the **az10408vmss0** blade, click **Extensions**, and the click **+ Add**. +1. On the **az10408vmss0** blade, in the **Settings** section, click **Extensions**, and the click **+ Add**. 1. On the **New resource** blade, click **Custom Script Extension** and then click **Create**. @@ -489,7 +489,7 @@ In this task, you will change the size of virtual machine scale set instances, c 1. In the Azure portal, search for and select **Virtual machine scale sets** and select the **az10408vmss0** scale set -1. In the **az10408vmss0** blade, click **Size**. +1. In the **az10408vmss0** blade, in the **Settings** section, click **Size**. 1. In the list of available sizes, select **Standard DS1_v2** and click **Resize**. @@ -499,7 +499,7 @@ In this task, you will change the size of virtual machine scale set instances, c 1. Return to the **az10408vmss0 - Instances** blade, click the entry representing the second instance and, on the scale set instance blade, note its **Location** (it should be one of the other two zones in the target Azure region into which you deployed the Azure virtual machine scale set). -1. Return to the **az10408vmss0 - Instances** blade and click **Scaling**. +1. Return to the **az10408vmss0 - Instances** blade, and in the **Settings** section, click **Scaling**. 1. On the **az10408vmss0 - Scaling** blade, select the **Custom autoscale** option and configure autoscale with the following settings (leave others with their default values): @@ -563,7 +563,7 @@ In this task, you will change the size of virtual machine scale set instances, c 1. Close Cloud Shell pane. -1. On the **az10408vmss0** blade, click **Disks**, click **+ Create and attach a new disk**, and attach a new managed disk with the following settings (leave others with their default values): +1. On the **az10408vmss0** blade, in the **Settings** section, click **Disks**, click **+ Create and attach a new disk**, and attach a new managed disk with the following settings (leave others with their default values): | Setting | Value | | --- | --- | diff --git a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md index ca59dfb9..ac287865 100644 --- a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md +++ b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md @@ -49,7 +49,7 @@ In this task, you will create an Azure web app. | Region | the name of an Azure region where you can provision Azure web apps | | App service plan | accept the default configuration | -1. Click **Review + create**, and then click **Create**. +1. Click **Review + create**. On the **Review + create** tab of the **Create Web App** blade, ensure that the validation passed and click **Create**. >**Note**: Wait until the web app is created before you proceed to the next task. This should take about a minute. diff --git a/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md b/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md index fd6e54ac..e0841fe9 100644 --- a/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md +++ b/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md @@ -30,7 +30,7 @@ In this task, you will create a new container instance for the web application. 1. Sign in to the [Azure portal](https://portal.azure.com). -1. In the Azure portal, search for locate **Container instances** and then, on the **Container instances** blade, click **+ Add**. +1. In the Azure portal, search for locate **Container instances** and then, on the **Container instances** blade, click **+ New**. 1. On the **Basics** tab of the **Create container instance** blade, specify the following settings (leave others with their default values): @@ -51,7 +51,7 @@ In this task, you will create a new container instance for the web application. >**Note**: Your container will be publicly reachable at dns-name-label.region.azurecontainer.io. If you receive a **DNS name label not available** error message, specify a different value. -1. Click **Next: Advanced >**, review the settings on the **Advanced** tab of the **Create container instance** blade without making any changes, click **Review + Create**, and then click **Create**. +1. Click **Next: Advanced >**, review the settings on the **Advanced** tab of the **Create container instance** blade without making any changes, click **Review + Create**, ensure that the validation passed and click **Create**. >**Note**: Wait for the deployment to complete. This should take about 3 minutes. diff --git a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md index 39aa8bdf..f6297ad7 100644 --- a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md +++ b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md @@ -15,9 +15,10 @@ Contoso has a number of multi-tier applications that are not suitable to run by In this lab, you will: -+ Task 1: Deploy an Azure Kubernetes Service cluster -+ Task 2: Deploy pods into the Azure Kubernetes Service cluster -+ Task 3: Scale containerized workloads in the Azure Kubernetes service cluster ++ Task 1: Register the Microsoft.Kubernetes and Microsoft.KubernetesConfiguration resource providers. ++ Task 2: Deploy an Azure Kubernetes Service cluster ++ Task 3: Deploy pods into the Azure Kubernetes Service cluster ++ Task 4: Scale containerized workloads in the Azure Kubernetes service cluster ## Estimated timing: 40 minutes @@ -86,7 +87,7 @@ In this task, you will deploy an Azure Kubernetes Services cluster by using the | Network configuration | **kubenet** | | DNS name prefix | any valid, globally unique DNS host name | -1. Click **Next: Integration >**, on the **Integration** tab of the **Create Kubernetes cluster** blade, set **Container monitoring** to **Disabled**, click **Review + create** and then click **Create**. +1. Click **Next: Integration >**, on the **Integration** tab of the **Create Kubernetes cluster** blade, set **Container monitoring** to **Disabled**, click **Review + create**, ensure that the validation passed and click Create. >**Note**: In production scenarios, you would want to enable monitoring. Monitoring is disabled in this case since it is not covered in the lab. diff --git a/Instructions/Labs/LAB_10-Implement_Data_Protection.md b/Instructions/Labs/LAB_10-Implement_Data_Protection.md index 5ac8ede0..e5761867 100644 --- a/Instructions/Labs/LAB_10-Implement_Data_Protection.md +++ b/Instructions/Labs/LAB_10-Implement_Data_Protection.md @@ -70,7 +70,7 @@ In this task, you will deploy two virtual machines that will be used to test dif In this task, you will create a recovery services vault. -1. In the Azure portal, search for and select **Recovery Services vaults** and, on the **Recovery Services vaults** blade, click **+ Add**. +1. In the Azure portal, search for and select **Recovery Services vaults** and, on the **Recovery Services vaults** blade, click **+ New**. 1. On the **Create Recovery Services vault** blade, specify the following settings: @@ -83,7 +83,7 @@ In this task, you will create a recovery services vault. >**Note**: Make sure that you specify the same region into which you deployed virtual machines in the previous task. -1. Click **Review + Create** and then click **Create**. +1. Click **Review + Create**, ensure that the validation passed and click **Create**. >**Note**: Wait for the deployment to complete. The deployment should take less than 1 minute. @@ -111,7 +111,7 @@ In this task, you will implement Azure virtual-machine level backup. 1. On the **az104-10-rsv1** Recovery Services vault blade, click **+ Backup**. -1. On the **Backup Goal** blade, specify the folowing settings: +1. On the **Backup Goal** blade, specify the following settings: | Settings | Value | | --- | --- | @@ -239,7 +239,7 @@ In this task, you will implement file and folder backup by using Azure Recovery 1. When the backup is complete, click **Close**, and then close Microsoft Azure Backup. -1. Switch to the web browser window displaying the Azure portal, navigate back to the Recovery Services vault blade and click **Backup items**. +1. Switch to the web browser window displaying the Azure portal, navigate back to the **Recovery Services vault** blade, in the **Protected items** section, and click **Backup items**. 1. On the **az104-10-rsv1 - Backup items** blade, click **Azure Backup Agent**. @@ -251,7 +251,7 @@ In this task, you will perform file restore by using Azure Recovery Services age 1. Within the Remote Desktop session to **az104-10-vm1**, open File Explorer, navigate to the **C:\\Windows\\System32\\drivers\\etc\\** folder and delete the **hosts** file. -1. Switch to the Microsoft Azure Backup window and click **Recover data**. This will start **Recover Data Wizard**. +1. Open Microsoft Azure Backup and click **Recover data** in the **Actions** pane. This will start **Recover Data Wizard**. 1. On the **Getting Started** page of **Recover Data Wizard**, ensue that **This server (az104-10-vm1.)** option is selected and click **Next**. @@ -373,7 +373,7 @@ In this task, you will restore a file from the Azure virtual machine-level snaps >**Note**: Make sure to include the trailing period when typing the server name -1. Enable the checkbox next to the label **There is backup data of 1 backup items associated with this server.I understand that clicking "Confirm" will permanently delete all the cloud backup data. This action cannot be undone. An alert may be sent to the administrators of this subscription notifying them of this deletion** and click **Delete**. +1. Enable the checkbox next to the label **There is backup data of 1 backup items associated with this server. I understand that clicking "Confirm" will permanently delete all the cloud backup data. This action cannot be undone. An alert may be sent to the administrators of this subscription notifying them of this deletion** and click **Delete**. 1. Navigate back to the **az104-10-rsv1 - Backup items** blade and click **Azure Virtual Machines**. diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index c520d8e9..58003275 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -210,7 +210,7 @@ In this task, you will configure Azure virtual machine diagnostic settings. | Aggregation granularity (Period) | **1 minute** | | Frequency of evaluation | **Every 1 Minute** | -1. On the **Create alert rule** blade, in the **Action group** section, click **Select action group** and then click the **+ Create action group** button. +1. On the **Create alert rule** blade, in the **Action group** section, click **Add action groups** and then click the **+ Create action group** button. 1. On the **Basics** tab of the **Create action group** blade, specify the following settings (leave others with their default values) and select **Next: Notifications >**: