From 08a6f513a11a29c460628e34644c8a68b7dd453f Mon Sep 17 00:00:00 2001 From: Your Name Date: Thu, 13 Feb 2020 19:53:13 -0500 Subject: [PATCH] updates (2) --- .../az104-02a-customRoleDefinition.json} | 2 +- ...d => LAB_01-Manage_Azure_AD_Identities.md} | 36 +++++++-------- ... LAB_02a_Manage_Subscriptions_and_RBAC.md} | 44 +++++++++---------- ...02b-Manage_Governance_via_Azure_Policy.md} | 28 ++++++------ ...ure_Resources_by_Using the Azure Portal.md | 2 +- ..._Azure_Resources_by_Using_ARM_Templates.md | 8 ++-- ...nage_Azure_Resources_by_Using_Azure_CLI.md | 2 +- .../LAB_04-Implement_Virtual_Networking.md | 20 ++++++--- ...LAB_05-Implement_Intersite_Connectivity.md | 6 +-- ...06-Implement_Network_Traffic_Management.md | 18 ++++---- .../Labs/LAB_07-Manage_Azure_Storage.md | 8 ++-- .../Labs/LAB_08-Manage_Virtual_Machines.md | 13 +++--- .../Labs/LAB_09a-Implement_Web_Apps.md | 8 ++-- ...09b-Implement_Azure_Container_Instances.md | 4 +- ..._09c-Implement_Azure_Kubernetes_Service.md | 6 +-- .../Labs/LAB_10-Implement_Data_Protection.md | 16 +++---- .../Labs/LAB_11-Implement_Monitoring.md | 8 ++-- 17 files changed, 122 insertions(+), 107 deletions(-) rename Allfiles/Labs/{01/az104-01a-customRoleDefinition.json => 02/az104-02a-customRoleDefinition.json} (98%) rename Instructions/Labs/{LAB_02-Manage_Azure_AD_Identities.md => LAB_01-Manage_Azure_AD_Identities.md} (92%) rename Instructions/Labs/{LAB_01a_Manage_Subscriptions_and_RBAC.md => LAB_02a_Manage_Subscriptions_and_RBAC.md} (84%) rename Instructions/Labs/{LAB_01b-Manage_Governance_via_Azure_Policy.md => LAB_02b-Manage_Governance_via_Azure_Policy.md} (88%) diff --git a/Allfiles/Labs/01/az104-01a-customRoleDefinition.json b/Allfiles/Labs/02/az104-02a-customRoleDefinition.json similarity index 98% rename from Allfiles/Labs/01/az104-01a-customRoleDefinition.json rename to Allfiles/Labs/02/az104-02a-customRoleDefinition.json index b57bb515..df58bc09 100644 --- a/Allfiles/Labs/01/az104-01a-customRoleDefinition.json +++ b/Allfiles/Labs/02/az104-02a-customRoleDefinition.json @@ -9,7 +9,7 @@ "NotActions": [ ], "AssignableScopes": [ - "/providers/Microsoft.Management/managementGroups/az104-01-mg1", + "/providers/Microsoft.Management/managementGroups/az104-02-mg1", "/subscriptions/SUBSCRIPTION_ID" ] } \ No newline at end of file diff --git a/Instructions/Labs/LAB_02-Manage_Azure_AD_Identities.md b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md similarity index 92% rename from Instructions/Labs/LAB_02-Manage_Azure_AD_Identities.md rename to Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md index 02ce91f7..cec66179 100644 --- a/Instructions/Labs/LAB_02-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -1,10 +1,10 @@ --- lab: - title: '02 - Manage Azure Active Directory Identities' - module: 'Module 02 - Identity' + title: '01 - Manage Azure Active Directory Identities' + module: 'Module 01 - Identity' --- -# Lab 02 - Manage Azure Active Directory Identities +# Lab 01 - Manage Azure Active Directory Identities # Student lab manual @@ -45,8 +45,8 @@ In this task, you will create and configure Azure AD users. | Setting | Value | | --- | --- | - | User name | **az104-02a-aaduser1** | - | Name | **az104-02a-aaduser1** | + | User name | **az104-01a-aaduser1** | + | Name | **az104-01a-aaduser1** | | Let me create the password | enabled | | Initial password | **Pa55w.rd124** | | Usage location | **United States** | @@ -59,7 +59,7 @@ In this task, you will create and configure Azure AD users. 1. Review the options available in the **Manage** section and note that you can identify the Azure AD roles assigned to the user account as well as the user account's permissions to Azure resources. -1. In the **Manage** section, click **Assigned roles**, then click **+ Add assignment** button and assign the **User administrator** role to **az104-02a-aaduser1**. +1. In the **Manage** section, click **Assigned roles**, then click **+ Add assignment** button and assign the **User administrator** role to **az104-01a-aaduser1**. >**Note**: You also have the option of assigning Azure AD roles when provisioning a new user. @@ -79,15 +79,15 @@ In this task, you will create and configure Azure AD users. | Setting | Value | | --- | --- | - | User name | **az104-02a-aaduser2** | - | Name | **az104-02a-aaduser2** | + | User name | **az104-01a-aaduser2** | + | Name | **az104-01a-aaduser2** | | Let me create the password | enabled | | Initial password | **Pa55w.rd124** | | Usage location | **United States** | | Job title | **System Administrator** | | Department | **IT** | -1. Sign out as the az104-02a-aaduser1 user from the Azure portal and close the InPrivate browser window. +1. Sign out as the az104-01a-aaduser1 user from the Azure portal and close the InPrivate browser window. #### Task 2: Create Azure AD groups with assigned and dynamic membership @@ -164,11 +164,11 @@ In this task, you will create Azure Active Directory groups with assigned and dy 1. From the **Add members** blade, search and select the **IT Cloud Administrators** and **IT System Administrators** groups and, back on the **New Group** blade, click **Create**. -1. Back on the **Groups - All groups** blade, click the entry representing the **IT Cloud Administrators** group and, on then display its **Members** blade. Verify that the **az104-02a-aaduser1** appears in the list of group members. +1. Back on the **Groups - All groups** blade, click the entry representing the **IT Cloud Administrators** group and, on then display its **Members** blade. Verify that the **az104-01a-aaduser1** appears in the list of group members. -1. Navigate back to the **Groups - All groups** blade, click the entry representing the **IT System Administrators** group and, on then display its **Members** blade. Verify that the **az104-02a-aaduser2** appears in the list of group members. +1. Navigate back to the **Groups - All groups** blade, click the entry representing the **IT System Administrators** group and, on then display its **Members** blade. Verify that the **az104-01a-aaduser2** appears in the list of group members. - >**Note**: You might experience delays with updates of the dynamic membership groups. To expedate the update, navigate to the group blade, display its **Dynamic membership rules** blade, **Edit** the rule listed in the **Rule syntax** textbox by adding a whitespace at the end, and **Save** the change. + >**Note**: You might experience delays with updates of the dynamic membership groups. To expedite the update, navigate to the group blade, display its **Dynamic membership rules** blade, **Edit** the rule listed in the **Rule syntax** textbox by adding a whitespace at the end, and **Save** the change. #### Task 3: Create an Azure Active Directory (AD) tenant @@ -201,8 +201,8 @@ In this task, you will create Azure AD guest users and grant them access to reso | Setting | Value | | --- | --- | - | User name | **az104-02b-aaduser1** | - | Name | **az104-02b-aaduser1** | + | User name | **az104-01b-aaduser1** | + | Name | **az104-01b-aaduser1** | | Let me create the password | enabled | | Initial password | **Pa55w.rd124** | | Job title | **System Administrator** | @@ -218,7 +218,7 @@ In this task, you will create Azure AD guest users and grant them access to reso | Setting | Value | | --- | --- | - | Name | **az104-02b-aaduser1** | + | Name | **az104-01b-aaduser1** | | Email address | paste the value you copied into Clipboard earlier in this task | | Usage location | **United States** | | Job title | **Lab Administrator** | @@ -228,7 +228,7 @@ In this task, you will create Azure AD guest users and grant them access to reso 1. Back on the **Users - All users** blade, click the entry representing the newly created guest user account. -1. On the **az104-02b-aaduser1 - Profile** blade, click **Groups**. +1. On the **az104-01b-aaduser1 - Profile** blade, click **Groups**. 1. Click **+ Add membership** and add the guest user account to the **IT Lab Administrators** group. @@ -237,7 +237,7 @@ In this task, you will create Azure AD guest users and grant them access to reso >**Note**: Remember to remove any newly created Azure resources that you no longer use. Removing unused resources ensures you will not incur unexpected costs. While, in this case, there are no additional charges associated with Azure Active Directory tenants and their objects, you might want to consider removing the user accounts, the group accounts, and the Azure Active Directory tenant you created in this lab. -1. In the Azure portal, navigate to the **Users - All users** blade, click the entry representing the **az104-02b-aaduser1** guest user account, on the **az104-02b-aaduser1 - Profile** blade click **Delete**, and, when prompted to confirm, click **OK**. +1. In the Azure portal, navigate to the **Users - All users** blade, click the entry representing the **az104-01b-aaduser1** guest user account, on the **az104-01b-aaduser1 - Profile** blade click **Delete**, and, when prompted to confirm, click **OK**. 1. Repeat the same sequence of steps to delete the remaining user accounts you created in this lab. @@ -247,7 +247,7 @@ In this task, you will create Azure AD guest users and grant them access to reso 1. In the Azure portal, display the blade of the Contoso Lab Azure AD tenant by using the **Directory + Subscription** button (directly to the right of the Cloud Shell button) in the Azure portal toolbar. -1. Navigate to the **Users - All users** blade, click the entry representing the **az104-02b-aaduser1** user account, on the **az104-02b-aaduser1 - Profile** blade click **Delete**, and, when prompted to confirm, click **OK**. +1. Navigate to the **Users - All users** blade, click the entry representing the **az104-01b-aaduser1** user account, on the **az104-01b-aaduser1 - Profile** blade click **Delete**, and, when prompted to confirm, click **OK**. 1. Navigate to the **Contoso Lab - Overview** blade of the Contoso Lab Azure AD tenant, click **Delete directory**, on the **Delete directory 'Contoso Lab'** blade, click the **Get permission to delete Azure resources** link, on the **Properties** blade of Azure Active Directory, set **Access management for Azure resources** to **Yes** and click **Save**. diff --git a/Instructions/Labs/LAB_01a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md similarity index 84% rename from Instructions/Labs/LAB_01a_Manage_Subscriptions_and_RBAC.md rename to Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index 65827d3d..ae0ccbb5 100644 --- a/Instructions/Labs/LAB_01a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -1,10 +1,10 @@ --- lab: - title: '01a - Manage Subscriptions and RBAC' - module: 'Module 01 - Subscriptions and Governance' + title: '02a - Manage Subscriptions and RBAC' + module: 'Module 02 - Governance and Compliance' --- -# Lab 01a - Manage Subscriptions and RBAC +# Lab 02a - Manage Subscriptions and RBAC # Student lab manual ## Lab scenario @@ -42,12 +42,12 @@ In this task, you will create and configure management groups. | Setting | Value | | --- | --- | - | Management group ID | **az104-01-mg1**| - | Management group display name | **az104-01-mg1**| + | Management group ID | **az104-02-mg1**| + | Management group display name | **az104-02-mg1**| 1. In the list of management groups, click the entry representing the newly created management group and then display its **details**. -1. From the **az104-01-mg1** blade, click **+ Add subscription** and add the subscription you are using in this lab to the management group. +1. From the **az104-02-mg1** blade, click **+ Add subscription** and add the subscription you are using in this lab to the management group. >**Note**: Copy the ID of your Azure subscription into Clipboard. You will need it in the next task. @@ -55,7 +55,7 @@ In this task, you will create and configure management groups. In this task, you will create a definition of a custom RBAC role. -1. From the lab computer, open the file **\\Allfiles\\Labs\\01\\az104-01a-customRoleDefinition.json** in Notepad and review its content: +1. From the lab computer, open the file **\\Allfiles\\Labs\\02\\az104-02a-customRoleDefinition.json** in Notepad and review its content: ```json { @@ -69,7 +69,7 @@ In this task, you will create a definition of a custom RBAC role. "NotActions": [ ], "AssignableScopes": [ - "/providers/Microsoft.Management/managementGroups/az104-01-mg1", + "/providers/Microsoft.Management/managementGroups/az104-02-mg1", "/subscriptions/SUBSCRIPTION_ID" ] } @@ -83,12 +83,12 @@ In this task, you will create a definition of a custom RBAC role. >**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 file **\\Allfiles\\Labs\\01\\az104-01a-customRoleDefinition.json** into the Cloud Shell home directory. +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 file **\\Allfiles\\Labs\\02\\az104-02a-customRoleDefinition.json** into the Cloud Shell home directory. 1. From the Cloud Shell pane, run the following to create the custom role definition: ```pwsh - New-AzRoleDefinition -InputFile $HOME/az104-01a-customRoleDefinition.json + New-AzRoleDefinition -InputFile $HOME/az104-02a-customRoleDefinition.json ``` 1. Close the Cloud Shell pane. @@ -103,14 +103,14 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro | Setting | Value | | --- | --- | - | User name | **az104-01-aaduser1**| - | Name | **az104-01-aaduser1**| + | User name | **az104-02-aaduser1**| + | Name | **az104-02-aaduser1**| | Let me create the password | enabled | | Initial password | **Pa55w.rd124** | >**Note**: **Copy to clipboard** the full **User name**. You will need it later in this lab. -1. In the Azure portal, navigate back to the **az104-01-mg1** management group and display its **details**. +1. In the Azure portal, navigate back to the **az104-02-mg1** management group and display its **details**. 1. Click **Access control (IAM)**, click **+ Add** followed by **Role assignment**, and assign the **Support Request Contributor (Custom)** role to the newly created user account. @@ -118,9 +118,9 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro >**Note**: Rather than typing the user name, you can paste the content of Clipboard. -1. In the **InPrivate** browser window, in the Azure portal, search and select **Resource groups** to verify that the az104-01-aaduser1 user can see all resource groups. +1. In the **InPrivate** browser window, in the Azure portal, search and select **Resource groups** to verify that the az104-02-aaduser1 user can see all resource groups. -1. In the **InPrivate** browser window, in the Azure portal, search and select **All resources** to verify that the az104-01-aaduser1 user cannot see any resources. +1. In the **InPrivate** browser window, in the Azure portal, search and select **All resources** to verify that the az104-02-aaduser1 user cannot see any resources. 1. In the **InPrivate** browser window, in the Azure portal, search and select **Help + support** and then click **+ New support request**. @@ -130,7 +130,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro >**Note**: If you do not see the **Service and subscription limits (quotas)** option, sign out from the Azure portal and sign in back. -1. Do not continue with creating the support request. Instead, sign out as the az104-01-aaduser1 user from the Azure portal and close the InPrivate browser window. +1. Do not continue with creating the support request. Instead, sign out as the az104-02-aaduser1 user from the Azure portal and close the InPrivate browser window. #### Clean up resources @@ -140,13 +140,13 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro 1. In the Azure portal, search for and select **Azure Active Directory**, on the Azure Active Directory blade, click **Users**. -1. On the **Users - All users** blade, click **az104-01-aaduser1**. +1. On the **Users - All users** blade, click **az104-02-aaduser1**. -1. On the **az104-01-aaduser1 - Profile** blade, copy the value of **Object ID** attribute. +1. On the **az104-02-aaduser1 - Profile** blade, copy the value of **Object ID** attribute. 1. In the Azure portal, start a **PowerShell** session within the **Cloud Shell**. -1. From the Cloud Shell pane, run the following to remove the assignment of the custom role definition (replace the `[object_ID]` placeholder with the value of the **object ID** attribute of the **az104-01-aaduser1** Azure Active Directory user account you copied earlier in this task): +1. From the Cloud Shell pane, run the following to remove the assignment of the custom role definition (replace the `[object_ID]` placeholder with the value of the **object ID** attribute of the **az104-02-aaduser1** Azure Active Directory user account you copied earlier in this task): ```pwsh $scope = (Get-AzRoleAssignment -RoleDefinitionName 'Support Request Contributor (Custom)').Scope @@ -160,15 +160,15 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro Remove-AzRoleDefinition -Name 'Support Request Contributor (Custom)' -Force ``` -1. In the Azure portal, navigate back to the **Users - All users** blade of the **Azure Active Directory**, and delete the **az104-01-aaduser1** user account. +1. In the Azure portal, navigate back to the **Users - All users** blade of the **Azure Active Directory**, and delete the **az104-02-aaduser1** user account. -1. In the Azure portal, navigate to the **az104-01-mg1** management group and display its **details**. +1. In the Azure portal, navigate to the **az104-02-mg1** management group and display its **details**. 1. Right-click the **ellipsis** icon to the right of the entry representing your Azure subscription and click **Move**. 1. On the **Move** blade, select the management group which the subscription was originally part of and click **Save**. -1. Navigate back to the **Management groups** blade, right click the **ellipsis** icon to the rigth of the **az104-01-mg1** management group and click **Delete**. +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**. #### Review diff --git a/Instructions/Labs/LAB_01b-Manage_Governance_via_Azure_Policy.md b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md similarity index 88% rename from Instructions/Labs/LAB_01b-Manage_Governance_via_Azure_Policy.md rename to Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md index 88f807dd..8fe1c118 100644 --- a/Instructions/Labs/LAB_01b-Manage_Governance_via_Azure_Policy.md +++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md @@ -1,19 +1,19 @@ --- lab: - title: '01b - Manage Governance via Azure Policy' - module: 'Module 01 - Subscriptions and Governance' + title: '02b - Manage Governance via Azure Policy' + module: 'Module 02 - Governance and Compliance' --- -# Lab 01b - Manage Governance via Azure Policy +# Lab 02b - Manage Governance via Azure Policy # Student lab manual ## Lab scenario In order to improve management of Azure resources in Contoso, you have been tasked with implementing the following functionality: -- tagging resource groups that include only infrastructure resources (such as Cloud Shell storage acccounts) +- tagging resource groups that include only infrastructure resources (such as Cloud Shell storage accounts) -- ensuring that only properly tagged infrastructure resoures can be added to infrastructure resource groups +- ensuring that only properly tagged infrastructure resources can be added to infrastructure resource groups - remediating any non-compliant resources @@ -62,10 +62,12 @@ In this task, you will create and assign a tag to an Azure resource group via th | Name | **Role** | | Value | **Infra** | -1. Navigate back to the storage account blade and note that tag is not automatically assigned to the storage account. +1. Navigate back to the storage account blade. Review the **Overview** information and note that the new tag was not automatically assigned to the storage account. #### Task 2: Enforce tagging via an Azure policy +In this task, you will assign the built-in *Require tag and its value* policy to the resource group and evaluate the outcome. + 1. In the Azure portal, search for and select **Policy**. 1. In the **Authoring** section, click **Definitions**. Take a moment to browse through the list of built-in policy definitions that are available for you to use. List all built-in policies that involve the use of tags by selecting the **Tags** entry (and de-selecting all other entries) in the **Category** drop-down list. @@ -112,13 +114,13 @@ In this task, you will create and assign a tag to an Azure resource group via th 1. On the resource group blade, click **+ Add**. -1. On the **New** blade, search for and select **Storage account - blob, file, table, queue**. +1. On the **New** blade, search for and select **Storage account - blob, file, table, queue**, and click **Create**. -1. On the **Basics** tab of the **Creat 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, specify the following settings (leave others with their defaults) and click **Review + create**: | Setting | Value | | --- | --- | - | Storage account name | any globally unique combination of between 3 and 24 lower case leters and digits, starting with a letter | + | Storage account name | any globally unique combination of between 3 and 24 lower case letters and digits, starting with a letter | 1. Note that the validation failed. Click the link **Validation failed. Click here to view details** to display the **Errors** blade and identify the reason for the failure. @@ -136,7 +138,7 @@ In this task, we will use a different policy definition to remediate any non-com 1. In the list of assignments, right click the ellipsis icon in the row representing the **Require Role tag with Infra value** policy assignment and use the **Delete assignment** menu item to delete the assignment. -1. Click **Assign policy** and specify the **Scope** by clicking the ellipsis button and selecting the following values:: +1. Click **Assign policy** and specify the **Scope** by clicking the ellipsis button and selecting the following values: | Setting | Value | | --- | --- | @@ -176,13 +178,13 @@ In this task, we will use a different policy definition to remediate any non-com 1. On the resource group blade, click **+ Add**. -1. On the **New** blade, search for and select **Storage account - blob, file, table, queue**. +1. On the **New** blade, search for and select **Storage account - blob, file, table, queue**, and click **Create**. -1. On the **Basics** tab of the **Creat 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, specify the following settings (leave others with their defaults) and click **Review + create**: | Setting | Value | | --- | --- | - | Storage account name | any globally unique combination of between 3 and 24 lower case leters and digits, starting with a letter | + | Storage account name | any globally unique combination of between 3 and 24 lower case letters and digits, starting with a letter | 1. Verify that this time the validation passed and click **Create**. 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 1bb54ecf..fcebe163 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 @@ -25,7 +25,7 @@ In this lab, we will: #### Task 1: Create resource groups and deploy resources to resource groups -In this task, you will use the Azure portal to create resorce groups and create a disk in the resource group. +In this task, you will use the Azure portal to create resource groups and create a disk in the resource group. 1. Sign in to the [Azure portal](https://portal.azure.com). 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 d2b06476..87b23ae6 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 @@ -34,9 +34,9 @@ In this task, you will create an Azure disk resource by using an Azure Resource 1. On the **az104-03a-rg1** resource group blade, in the **Settings** section, click **Deployments**. -1. On the **az104-03a-rg1 - Deployments** blade, click the first entry in the list of deployments and, on the overview blade of the deployment, click **Template**. +1. On the **az104-03a-rg1 - Deployments** blade, click the first entry in the list of deployments and then click **Template**. - >**Note**: Review the content of the template and note that you have the option to download it to the local computer, add it to the libary, and re-deploy it. + >**Note**: Review the content of the template and note that you have the option to download it to the local computer, add it to the library, and re-deploy it. 1. Click **Download** and save the compressed file containing the template and parameters files to the **Downloads** folder on your lab computer. @@ -46,7 +46,7 @@ In this task, you will create an Azure disk resource by using an Azure Resource #### Task 2: Create an Azure managed disk by using an ARM template -1. In the Azure portal, search for and select **Template deployment**. +1. In the Azure portal, search for and select **Template deployment (deploy using custom templates)**. 1. On the **Custom deployment** blade, click **Build your own template in the editor**. @@ -77,7 +77,7 @@ In this task, you will create an Azure disk resource by using an Azure Resource "osType": "[parameters('osType')]" ``` - >**Note**: These parameters are removed since the are not applicable to the current deployment. In particular, souceResourceId, sourceUri, osType, and hyperVGeneration parameters are applicable to creating an Azure disk from an existing VHD file. + >**Note**: These parameters are removed since they are not applicable to the current deployment. In particular, sourceResourceId, sourceUri, osType, and hyperVGeneration parameters are applicable to creating an Azure disk from an existing VHD file. 1. In addition, remove the trailing comma from the following line: diff --git a/Instructions/Labs/LAB_03d-Manage_Azure_Resources_by_Using_Azure_CLI.md b/Instructions/Labs/LAB_03d-Manage_Azure_Resources_by_Using_Azure_CLI.md index ba53ed37..31618a89 100644 --- a/Instructions/Labs/LAB_03d-Manage_Azure_Resources_by_Using_Azure_CLI.md +++ b/Instructions/Labs/LAB_03d-Manage_Azure_Resources_by_Using_Azure_CLI.md @@ -120,7 +120,7 @@ In this task, you will managing configuration of the Azure managed disk by using az group list --query "[?starts_with(name,'az104-03')].[name]" --output tsv | xargs -L1 bash -c 'az group delete --name $0 --no-wait --yes' ``` - >**Note**: The command command executes asynchronously (as determined by the --nowait parameter), so while you will be able to run another Azure CLI command immediately afterwards within the same Bash session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the --nowait parameter), so while you will be able to run another Azure CLI command immediately afterwards within the same Bash session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index 07a0ff2b..06e6daed 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -141,6 +141,8 @@ In this task, you will configure network security groups in order to allow for r >**Note**: This step refers to connecting via Remote Desktop from a Windows computer. On a Mac, you can use Remote Desktop Client from the Mac App Store and on Linux computers you can use an open source RDP client software. +1. Click **Open** to open the downloaded RDP file and, when prompted, click **Connect**. + 1. Note that the connection attempt fails. >**Note**: This is expected, because public IP addresses of the Standard SKU, by default, require that the network interfaces to which they are assigned are protected by a network security group. In order to allow Remote Desktop connections, you will create a network security group explicitly allowing inbound RDP traffic from Internet and assign it to network interfaces of both virtual machines. @@ -181,11 +183,19 @@ In this task, you will configure network security groups in order to allow for r 1. Navigate back to the **az104-04-vm0** virtual machine blade. + >**Note**: Now verify that you can successfully to the target virtual machine and sign in by using the **Student** username and **Pa55w.rd1234** password. + 1. On the **az104-04-vm0** blade, click **Connect**, click **Download RDP File** and follow the prompts to start the Remote Desktop session. - >**Note**: Accept any warning prompts when connecting to the target virtual machines. +1. Click **Open** to open the downloaded RDP file and, when prompted, click **Connect**. -1. Verify that you can successfully connect to the target virtual machine and sign in by using the **Student** username and **Pa55w.rd1234** password. +1. In the **Windows Security** window, click **More choices** and, if needed, click **Use a different account**. + +1. Type the username **Student** and the password **Pa55w.rd1234**. + +1. Click **OK** to connect. + +1. You may receive a certificate warning during the sign-in process. If so, click **Yes**. >**Note**: Leave the Remote Desktop session open. You will need it in the next task. @@ -228,7 +238,7 @@ In this task, you will configure DNS name resolution within a virtual network by 1. Switch to the Remote Desktop session to **az104-04-vm0**, right-click the **Start** button and, in the right-click menu, click **Windows PowerShell (Admin)**. -1. In the Windows PowerShell console window, run the following to test internal name resolution of the **az104-04-vm1** DNS record set in the the newly created private DNS zone: +1. In the Windows PowerShell console window, run the following to test internal name resolution of the **az104-04-vm1** DNS record set in the newly created private DNS zone: ```pwsh nslookup az104-04-vm1.contoso.org @@ -281,7 +291,7 @@ In this task, you will configure external DNS name resolution by using Azure pub 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 the newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted 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 newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted earlier in this task): ```pwsh nslookup az104-04-vm0.contoso.org [Name server 1] @@ -313,7 +323,7 @@ In this task, you will configure external DNS name resolution by using Azure pub Get-AzResourceGroup -Name 'az104-04*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md index 5a9b6d04..115c911e 100644 --- a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md +++ b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md @@ -9,7 +9,7 @@ lab: ## Lab scenario -Contoso has its datacenters in Boston, New York, and Seattle offices connected via a mesh wide-area network links, with full connectivity between them. You need to implement a lab environment that will reflect the the topology of the Contoso's on-premises networks and verify its functionality. +Contoso has its datacenters in Boston, New York, and Seattle offices connected via a mesh wide-area network links, with full connectivity between them. You need to implement a lab environment that will reflect the topology of the Contoso's on-premises networks and verify its functionality. ## Objectives @@ -90,7 +90,7 @@ In this task, you will deploy three virtual machines, each into a separate virtu ``` >**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 2 minutes. - >**Note**: To verify the status of the deployments, you can examine the the properties of the resource groups you created in this task. + >**Note**: To verify the status of the deployments, you can examine the properties of the resource groups you created in this task. 1. Close the Cloud Shell pane. @@ -238,7 +238,7 @@ In this task, you will test connectivity between virtual machines on the three v Get-AzResourceGroup -Name 'az104-05*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index 2fb0d4fd..e613705d 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -95,7 +95,7 @@ In this task, you will deploy four virtual machines into the same Azure region. ``` >**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 2 minutes. - >**Note**: To verify the status of the deployments, you can examine the the properties of the resource groups you created in this task. + >**Note**: To verify the status of the deployments, you can examine the properties of the resource groups you created in this task. 1. Close the Cloud Shell pane. @@ -357,7 +357,9 @@ In this task, you will configure and test routing between the two spoke virtual 1. Click **Check** and wait until results of the connectivity check are returned. Verify that the status is **Reachable**. Review the network path and note that the traffic was routed via **10.60.0.4**, assigned to the **az104-06-nic0** network adapter. - > **Note**: This is expected, since the traffic between spoke virtual networks is now routed via the virtual machine located in the hub virtual network, which functions as a router. + > **Note**: This is expected, since the traffic between spoke virtual networks is now routed via the virtual machine located in the hub virtual network, which functions as a router. + + > **Note**: You can use **Network Watcher** to view topology of the network. #### Task 5: Implement Azure Load Balancer @@ -398,7 +400,7 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur | Virtual machine | **az104-06-vm1** | | Virtual machine IP address | **ipconfig1 (10.60.1.4)** | -1. Wait for the backend pool to be creted, click **Health probes**, and then click **+ Add**. +1. Wait for the backend pool to be created, click **Health probes**, and then click **+ Add**. 1. Add a health probe with the following settings (leave others with their default values): @@ -519,7 +521,7 @@ 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 click **Create 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. On the **Backend targets** tab of the **Add a routing rule** blade, click **Create 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): | Setting | Value | | --- | --- | @@ -528,8 +530,8 @@ In this task, you will implement an Azure Application Gateway in front of the tw | Backend port | **80** | | Cookie-based affinity | **Disable** | | Connection draining | **Disable** | - | Request time-out (seconds) | **20** - + | Request time-out (seconds) | **20** | +f 1. Click **Add** on the **Add an HTTP setting** blade, and back on the **Add a routing rule** blade, clik **Add**. 1. Click **Next: Tags >**, followed by **Next: Review + create >** and then click **Create**. @@ -548,7 +550,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw > **Note**: You might need to refresh the browser window or open it again by using InPrivate mode. - > **Note**: Targeting virtual machines on multiple virtual networks is not a common configuration, but it is meant to illustrate the point that Application Gateway is capable of targeting virtual machiens on multiple virtual networks (as well as endpoints in other Azure regions or even outside of Azure), unlike Azure Load Balancer, which load balances across virtual machines in the same virtual network. + > **Note**: Targeting virtual machines on multiple virtual networks is not a common configuration, but it is meant to illustrate the point that Application Gateway is capable of targeting virtual machines on multiple virtual networks (as well as endpoints in other Azure regions or even outside of Azure), unlike Azure Load Balancer, which load balances across virtual machines in the same virtual network. #### Clean up resources @@ -568,7 +570,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw Get-AzResourceGroup -Name 'az104-06*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index a266f9d3..c83df18d 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -134,7 +134,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**. 1. On the **Upload blob** blade, expand the **Advanced** section and specify the following settings (leave others with their default values): @@ -166,9 +166,9 @@ In this task, you will configure authentication and authorization for Azure Stor 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 mesage stating **ResourceNotFound**. +1. You should be presented with an XML-formatted message stating **ResourceNotFound**. - > **Note**: This is expected, since the container you crated has the public access level set to **Private (no anonymous access)**. + > **Note**: This is expected, since the container you created has the public access level set to **Private (no anonymous access)**. 1. Close the InPrivate mode browser window, return to the browser window showing the **licenses/LICENSE** blade of the Azure Storage container, and switch to the the **Generate SAS** tab. @@ -313,7 +313,7 @@ In this task, you will configure network access for Azure Storage. Get-AzResourceGroup -Name 'az104-07*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 5d9f1467..f6824e1e 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -18,9 +18,9 @@ In this lab, you will: + Task 1: Deploy zone-resilient Azure virtual machines by using the Azure portal and an Azure Resource Manager template + Task 2: Configure Azure virtual machines by using virtual machine extensions + Task 3: Scale compute and storage for Azure virtual machines -+ Task 4: Deploy zone-reslient Azure virtual machine scale sets by using the Azure portal ++ Task 4: Deploy zone-resilient Azure virtual machine scale sets by using the Azure portal + Task 5: Configure Azure virtual machine scale sets by using virtual machine extensions -+ Task 6: Scale compute and storage for Azure virtual machine scale sets ++ Task 6: Scale compute and storage for Azure virtual machine scale sets (optional) ## Instructions @@ -106,7 +106,7 @@ In this task, you will deploy Azure virtual machines into different availability | Admin Password | **Pa55w.rd1234** | | Zone | **2** | - >**Note**: You need to modify parameteres corresponding to the properties of the distinct resources you are deploying by using the template, including the virtual machine and its network interface. You also need to specify a different availability zone if you want your deployment consisting of two virtual machines to be zone redundant. + >**Note**: You need to modify parameters corresponding to the properties of the distinct resources you are deploying by using the template, including the virtual machine and its network interface. You also need to specify a different availability zone if you want your deployment consisting of two virtual machines to be zone redundant. 1. Enable the checkbox **I agree to the terms and conditions stated above** and click **Purchase**. @@ -172,7 +172,7 @@ In this task, you will install Windows Server Web Server role on the two Azure v Invoke-WebRequest -URI http://10.80.0.4 -UseBasicParsing ``` - >**Note**: The **-UseBasicParsing** parameter is necessary to eliminate depenency on Internet Explorer to complete execution of the cmdlet + >**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**. @@ -289,7 +289,7 @@ In this task you will scale compute for Azure virtual machines by changing their ``` > **Note**: Wait for the confirmation that the commands completed successfully. -#### Task 4: Deploy zone-reslient Azure virtual machine scale sets by using the Azure portal +#### Task 4: Deploy zone-resilient Azure virtual machine scale sets by using the Azure portal In this task, you will deploy Azure virtual machine scale set across availability zones by using the Azure portal. @@ -384,6 +384,7 @@ In this task, you will install Windows Server Web Server role on the instances o >**Note**: Verify that the browser page displays the name of one of the instances of the Azure virtual machine scale set **az10408vmss0**. + #### Task 6: Scale compute and storage for Azure virtual machine scale sets In this task, you will change the size of virtual machine scale set instances, configure their autoscaling settings, and attach disks to them. @@ -524,7 +525,7 @@ In this task, you will change the size of virtual machine scale set instances, c Get-AzResourceGroup -Name 'az104-08*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md index 5543c084..f753175d 100644 --- a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md +++ b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md @@ -82,7 +82,7 @@ In this task, you will create a staging deployment slot. In this task, you will configure web app deployment settings. -1. On the staging deployment slot blade, in the **Deployment** section, click **Deploymnent Center**. +1. On the staging deployment slot blade, in the **Deployment** section, click **Deployment Center**. >**Note:** Make sure you are on the staging slot blade (rather than the production slot). @@ -129,7 +129,7 @@ In this task, you will deploy code to the staging deployment slot. Set-Location -Path $HOME/php-docs-hello-world/ ``` -1. From the Cloud Shell pane, run the following to add the remote git (make sure to replace the `[deployment_name]` and `[git_clone_url]` placeholders with the the value of the **Deployment Credentials** user name and **Git Clone Url**, respectively, which you identified in previous task): +1. From the Cloud Shell pane, run the following to add the remote git (make sure to replace the `[deployment_name]` and `[git_clone_url]` placeholders with the value of the **Deployment Credentials** user name and **Git Clone Url**, respectively, which you identified in previous task): ``` git remote add [deployment_user_name] [git_clone_url] @@ -152,7 +152,7 @@ In this task, you will deploy code to the staging deployment slot. #### Task 5: Swap the staging slots -In this task, you wil swap the staging slot with the production slot +In this task, you will swap the staging slot with the production slot 1. Navigate back to the blade displaying the production slot of the web app. @@ -252,7 +252,7 @@ In this task, you will configure and test autoscaling of Azure web app. Get-AzResourceGroup -Name 'az104-09a*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md b/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md index bf1aa923..99f84812 100644 --- a/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md +++ b/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md @@ -64,7 +64,7 @@ In this task, you will review the deployment of the container instance. 1. On the **Overview** blade of the container instance, verify that **Status** is reported as **Running**. -1. Copy the value of the container instance **FQDN**, open an new browser tab, and navigate to the corresponding URL. +1. Copy the value of the container instance **FQDN**, open a new browser tab, and navigate to the corresponding URL. 1. Verify that the **Welcome to Azure Container Instance** page is displayed. @@ -90,7 +90,7 @@ In this task, you will review the deployment of the container instance. Get-AzResourceGroup -Name 'az104-09b*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md index 2c7468d4..1aa01d03 100644 --- a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md +++ b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md @@ -69,7 +69,7 @@ In this task, you will deploy an Azure Kubernetes Services cluster by using the 1. Click **Next: Monitoring >**, on the **Monitoring** tab of the **Create Kubernetes cluster** blade, set **Enable container monitoring** to **No**, click **Review + create** and then click **Create**. - >**Note**: In production scenarios, you would want to enable montioring. Monitoring is disabled in this case since it is not covered in the lab. + >**Note**: In production scenarios, you would want to enable monitoring. Monitoring is disabled in this case since it is not covered in the lab. >**Note**: Wait for the deployment to complete. This should take about 10 minutes. @@ -140,7 +140,7 @@ In this task, you will deploy a pod into the Azure Kubernetes Service cluster. kubectl get service ``` -1. Re-run the command until the value in the **EXTERNAL-IP** column for the **nginx-deployment** entry changes from **\** to a public IP address, then press the **Ctrl-C** key combination. Note the public IP address in the **EXTERNAL-IP** column for **nginx-deployment**. +1. Re-run the command until the value in the **EXTERNAL-IP** column for the **nginx-deployment** entry changes from **\** to a public IP address. Note the public IP address in the **EXTERNAL-IP** column for **nginx-deployment**. 1. Open a browser window and navigate to the IP address you obtained in the previous step. Verify that the browser page displays the **Welcome to nginx!** message. @@ -227,7 +227,7 @@ In this task, you will scale horizontally the number of pods and then number of az group list --query "[?starts_with(name,'az104-09c')].[name]" --output tsv | xargs -L1 bash -c 'az group delete --name $0 --no-wait --yes' ``` - >**Note**: The command command executes asynchronously (as determined by the --nowait parameter), so while you will be able to run another Azure CLI command immediately afterwards within the same Bash session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the --nowait parameter), so while you will be able to run another Azure CLI command immediately afterwards within the same Bash session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_10-Implement_Data_Protection.md b/Instructions/Labs/LAB_10-Implement_Data_Protection.md index c85ff893..5352d598 100644 --- a/Instructions/Labs/LAB_10-Implement_Data_Protection.md +++ b/Instructions/Labs/LAB_10-Implement_Data_Protection.md @@ -20,8 +20,8 @@ In this lab, you will: + Task 3: Implement Azure virtual machine-level backup + Task 4: Implement File and Folder backup + Task 5: Perform file recovery by using Azure Recovery Services agent -+ Task 6: Perform file recovery by using Azure virtual machine snapshots -+ Task 7: Review the Azure Recovery Services soft delete functionality ++ Task 6: Perform file recovery by using Azure virtual machine snapshots (optional) ++ Task 7: Review the Azure Recovery Services soft delete functionality (optional) ## Instructions @@ -136,7 +136,7 @@ In this task, you will implement Azure virtual-machine level backup. >**Note**: Wait for the backup to be enabled. This should take about 2 minutes. -1. Navigate back to the **az104-10-rsv1** Recovery Services vault blade, in the **Protected items** section, click **Backup items**, and then click the **Azure virtal machines** entry. +1. Navigate back to the **az104-10-rsv1** Recovery Services vault blade, in the **Protected items** section, click **Backup items**, and then click the **Azure virtual machines** entry. 1. On the **Backup Items (Azure Virtual Machine)** blade of **az104-10-vm0**, review the values of the **Backup Pre-Check** and **Last Backup Status** entries, and click the **az104-10-vm0** entry. @@ -164,7 +164,7 @@ In this task, you will implement file and folder backup by using Azure Recovery 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 | | --- | --- | @@ -241,7 +241,7 @@ In this task, you will implement file and folder backup by using Azure Recovery 1. On the **Backup Items (Azure Backup Agent)** blade, verify that there is an entry referencing the **C:\\** drive of **az104-10-vm1.**. -#### Task 5: Perform file recovery by using Azure Recovery Services agent +#### Task 5: Perform file recovery by using Azure Recovery Services agent (optional) In this task, you will perform file restore by using Azure Recovery Services agent. @@ -271,7 +271,7 @@ In this task, you will perform file restore by using Azure Recovery Services age 1. Terminate the Remote Desktop session. -#### Task 6: Perform file recovery by using Azure virtual machine snapshots +#### Task 6: Perform file recovery by using Azure virtual machine snapshots (optional) In this task, you will restore a file from the Azure virtual machine-level snapshot-based backup. @@ -309,7 +309,7 @@ In this task, you will restore a file from the Azure virtual machine-level snaps 1. On the **az104-10-vm0** Backup Item blade, click **File Recovery**. - >**Note**: You have the option of running recovery shortly after backup starts besed on the application consistent snapshot. + >**Note**: You have the option of running recovery shortly after backup starts based on the application consistent snapshot. 1. On the **File Recovery** blade, accept the default recovery point and click **Download Executable**. @@ -440,7 +440,7 @@ In this task, you will restore a file from the Azure virtual machine-level snaps Get-AzResourceGroup -Name 'az104-10*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index eb76090d..d9c206b7 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -96,7 +96,7 @@ In this task, you will create and configure an Azure Log Analytics workspace and | Subscription | the name of the Azure subscription you are using in this lab | | Resource group | **az104-11-rg1** | | Location | the name of the Azure region determined based on [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings) | - | Creat Azure Run As account | **Yes** | + | Create Azure Run As account | **Yes** | >**Note**: Make sure that you specify the Azure region based on the [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings) @@ -172,9 +172,9 @@ In this task, you will configure Azure virtual machine diagnostic settings. #### Task 5: Review Azure Monitor functionality -1. In the Azure portal, search for and select **Monitor** and, on the **Montor - Overview** blade, click **Metrics**. +1. In the Azure portal, search for and select **Monitor** and, on the **Monitor - Overview** blade, click **Metrics**. -1. In the chart pane on the right hand side of the blade, in the **SCOPE** drop-down list, click **+ Select a scope**. +1. In the chart pane on the right side of the blade, in the **SCOPE** drop-down list, click **+ Select a scope**. 1. On the **Select a scope** blade, on the **Browse** tab, navigate to the **az104-11-rg0** resource group, expand it, select the **az104-11-vm0** virtual machine within that resource group, and click **Apply**. @@ -316,7 +316,7 @@ In this task, you will configure Azure virtual machine diagnostic settings. Get-AzResourceGroup -Name 'az104-11*' | Remove-AzResourceGroup -Force -AsJob ``` - >**Note**: The command command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. + >**Note**: The command executes asynchronously (as determined by the -AsJob parameter), so while you will be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed. #### Review