diff --git a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md index e95dc375..f538ba0d 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -185,7 +185,7 @@ In this task, you will create a new Azure AD tenant. 1. In the Azure portal, search for and select **Azure Active Directory**. -1. Click **+ Create a tenant** and specify the following setting: +1. Click **Manage tenant**, and then on the next screen, click **+ Create**, and specify the following setting: | Setting | Value | | --- | --- | @@ -265,7 +265,7 @@ In this task, you will create Azure AD guest users and grant them access to reso 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 tenant**, on the **Delete tenant '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**. +1. Navigate to the **Contoso Lab - Overview** blade of the Contoso Lab Azure AD tenant, click **Manage tenant** and then on the next screen, click **Delete tenant**, 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**. 1. Sign out from the Azure portal and sign in back. diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index e53be368..8fa50564 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -152,7 +152,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro 1. In the **InPrivate** browser window, in the Azure portal, search and select **Help + support** and then click **+ New support request**. -1. In the **InPrivate** browser window, on the **Basic** tab of the **Help + support - New support request** blade, type **Service and subscription limits** in the Summary field and select the **Service and subscription limits (quotas)** issue type. Note that the subscription you are using in this lab is listed in the **Subscription** drop-down list. +1. In the **InPrivate** browser window, on the **Problem Description** tab of the **Help + support - New support request** blade, type **Service and subscription limits** in the Summary field and select the **Service and subscription limits (quotas)** issue type. Note that the subscription you are using in this lab is listed in the **Subscription** drop-down list. >**Note**: The presence of the subscription you are using in this lab in the **Subscription** drop-down list indicates that the account you are using has the permissions required to create the subscription-specific support request. 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 5790e879..93210926 100644 --- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md +++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md @@ -122,9 +122,7 @@ In this task, you will assign the built-in *Require a tag and its value on resou 1. Navigate back to the blade of the resource group hosting the storage account used for the Cloud Shell home drive, which you identified in the previous task. -1. On the resource group blade, click **+ Add** and then **+ Marketplace**. - -1. On the **New** blade, search for and select **Storage account**, and click **Create**. +1. On the resource group blade, click **+ Create** and then search for Storage Account, and click **+Create**. 1. On the **Basics** tab of the **Create storage account** blade, verify that you are using the Resource Group that the Policy was applied to and specify the following settings (leave others with their defaults), click **Review + create** and then click **Create**: @@ -176,7 +174,7 @@ In this task, we will use a different policy definition to remediate any non-com | Setting | Value | | --- | --- | | Create a remediation task | enabled | - | Policy to remediate | **Inherit a tag from the resource group if missing** | + | Policy to remediate | **Inherit a tag from the subscription if missing** | >**Note**: This policy definition includes the **Modify** effect. @@ -188,9 +186,7 @@ In this task, we will use a different policy definition to remediate any non-com 1. Navigate back to the blade of the resource group hosting the storage account used for the Cloud Shell home drive, which you identified in the first task. -1. On the resource group blade, click **+ Add** and **+ Marketplace**. - -1. On the **New** blade, search for and select **Storage account**, and click **Create**. +1. On the resource group blade, click **+ Create** and then search for Storage Account, and click **+Create**. 1. On the **Basics** tab of the **Create storage account** blade, verify that you are using the Resource Group that the Policy was applied to and specify the following settings (leave others with their defaults) and click **Review + 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 da127af1..3656c02e 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 @@ -66,8 +66,6 @@ In this task, we will move the disk resource you created in the previous task to >**Note**: This method allows you to move multiple resources at the same time. -1. On the **Move resources** blade, click **Create a new group**. - 1. Below the **Resource group** text box, click **Create new** then type **az104-03a-rg2** in the text box. On the Review tab, select the checkbox **I understand that tools and scripts associated with moved resources will not work until I update them to use new resource IDs**, and click **Move**. >**Note**: Do not wait for the move to complete but instead proceed to the next task. The move might take about 10 minutes. You can determine that the operation was completed by monitoring activity log entries of the source or target resource group. Revisit this step once you complete the next task. 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 c04f52aa..51bdd207 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 @@ -77,9 +77,6 @@ In this task, you will create an Azure disk resource by using an Azure Resource "sourceUri": { "type": "String" }, - "sourceImageVersionId": { - "type": "String" - }, "osType": { "type": "String" }, diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index 9c545122..87008ff6 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -224,7 +224,6 @@ In this task, you will create and configure Azure Files shares. | Setting | Value | | --- | --- | | Name | **az104-07-share** | - | Quota | **1024** | 1. Click the newly created file share and click **Connect**. diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 7058ee54..1dca6086 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -274,7 +274,7 @@ In this task you will scale compute for Azure virtual machines by changing their >**Note**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case. -1. On the **Edit template** blade, in the section displaying the content of the template, replace the line **35** `"vmSize": "Standard_D2s_v3"` with the following line): +1. On the **Edit template** blade, in the section displaying the content of the template, replace the line **30** `"vmSize": "Standard_D2s_v3"` with the following line): ```json "vmSize": "Standard_DS1_v2" @@ -283,7 +283,7 @@ In this task you will scale compute for Azure virtual machines by changing their >**Note**: This section of the template defines the same Azure virtual machine size as the one you specified for the first virtual machine via the Azure portal. -1. On the **Edit template** blade, in the section displaying the content of the template, replace line **55** (`"dataDisks": [ ]` line) with the following code : +1. On the **Edit template** blade, in the section displaying the content of the template, replace line **50** (`"dataDisks": [ ]` line) with the following code : ```json "dataDisks": [ diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index a49f2577..c187e045 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -84,7 +84,7 @@ In this task, you will create and configure an Azure Log Analytics workspace and 1. In the Azure portal, search for and select **Log Analytics workspaces** and, on the **Log Analytics workspaces** blade, click **+ Add**. -1. On the **Basics** tab of the **Create Log Analytics workspace** blade, the following settings, click **Review + Create** and then click **Create**: +1. On the **Basics** tab of the **Create Log Analytics workspace** blade, enter the following settings, click **Review + Create** and then click **Create**: | Settings | Value | | --- | --- | @@ -298,7 +298,7 @@ In this task, you will configure Azure virtual machine diagnostic settings. >**Note**: The names of several tables correspond to the solutions you installed earlier in this lab. -1. Hover the mouse over the **VMComputer** entry and click the **Preview data** icon. +1. Hover the mouse over the **VMComputer** entry and click the **See Preview data** icon. 1. If any data is available, in the **Update** pane, click **Use in editor**.