From 604f9caa153ec0f4687d70610e7fa3f2d34d93ff Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 00:36:58 +0500 Subject: [PATCH 01/11] Update LAB_01-Manage_Azure_AD_Identities.md minor change --- Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md index f538ba0d..bdef32ba 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -230,7 +230,7 @@ In this task, you will create Azure AD guest users and grant them access to reso 1. Navigate back to the **Users - All users** blade, and then click **+ New guest user**. -1. Create a new guest user with the following settings (leave others with their defaults): +1. Invite a new guest user with the following settings (leave others with their defaults): | Setting | Value | | --- | --- | From 6a03653c73feaf9f51e92cfc0ac4bc67fc738e36 Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 00:44:13 +0500 Subject: [PATCH 02/11] Update LAB_02a_Manage_Subscriptions_and_RBAC.md few changes incorporated --- .../Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index 8fa50564..6843a860 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -60,7 +60,7 @@ In this task, you will create and configure management groups. 1. Navigate back to the **Management groups** blade, and select **Refresh**. -1. On the **Management groups** blade, click **+ Add**. +1. On the **Management groups** blade, click **+ Create**. >**Note**: If you have not previously created Management Groups, select **Start using management groups** @@ -75,7 +75,7 @@ In this task, you will create and configure management groups. 1. On the **az104-02-mg1** blade, click **Subscriptions**. -1. On the **az104-02-mg1 \| Subscriptions** blade, click **+ Add**, on the **Add subscription** blade, in the **Subscription** drop-down list, seletc the subscription you are using in this lab and click **Save**. +1. On the **az104-02-mg1 \| Subscriptions** blade, click **+ Add**, on the **Add subscription** blade, in the **Subscription** drop-down list, select the subscription you are using in this lab and click **Save**. >**Note**: On the **az104-02-mg1 \| Subscriptions** blade, copy the ID of your Azure subscription into Clipboard. You will need it in the next task. @@ -150,9 +150,9 @@ 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 **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**. +1. In the **InPrivate** browser window, in the Azure portal, search and select **Help + support** and then click **+ Create a support request**. -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. +1. In the **InPrivate** browser window, on the **Problem Desription/Summary** 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. From 5dc45706a1b3bca713ea9e8b728f0f681d3c5364 Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 00:57:33 +0500 Subject: [PATCH 03/11] Update LAB_04-Implement_Virtual_Networking.md minor word changes --- Instructions/Labs/LAB_04-Implement_Virtual_Networking.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index 279f99ea..f87ae2a3 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -39,7 +39,7 @@ In this task, you will create a virtual network with multiple subnets by using t 1. Sign in to the [Azure portal](https://portal.azure.com). -1. In the Azure portal, search for and select **Virtual networks**, and, on the **Virtual networks** blade, click **+ Add**. +1. In the Azure portal, search for and select **Virtual networks**, and, on the **Virtual networks** blade, click **+ Create**. 1. Create a virtual network with the following settings (leave others with their default values): @@ -179,7 +179,7 @@ In this task, you will configure network security groups in order to allow for r >**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. -1. In the Azure portal, search for and select **Network security groups**, and, on the **Network security groups** blade, click **+ Add**. +1. In the Azure portal, search for and select **Network security groups**, and, on the **Network security groups** blade, click **+ Create**. 1. Create a network security group with the following settings (leave others with their default values): @@ -234,7 +234,7 @@ In this task, you will configure network security groups in order to allow for r In this task, you will configure DNS name resolution within a virtual network by using Azure private DNS zones. -1. In the Azure portal, search for and select **Private DNS zones** and, on the **Private DNS zones** blade, click **+ Add**. +1. In the Azure portal, search for and select **Private DNS zones** and, on the **Private DNS zones** blade, click **+ Create**. 1. Create a private DNS zone with the following settings (leave others with their default values): From 2b5e77eefe1799ed82b2fdc8da7d910d9aeac19a Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:08:57 +0500 Subject: [PATCH 04/11] Update LAB_06-Implement_Network_Traffic_Management.md word changes --- .../LAB_06-Implement_Network_Traffic_Management.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index b75987e1..1936f397 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -278,7 +278,7 @@ In this task, you will configure and test routing between the two spoke virtual > **Note**: Now you need to create and configure user defined routes on the spoke virtual networks. -1. In the Azure portal, search and select **Route tables** and, on the **Route tables** blade, click **+ Add**. +1. In the Azure portal, search and select **Route tables** and, on the **Route tables** blade, click **+ Create**. 1. Create a route table with the following settings (leave others with their default values): @@ -320,7 +320,7 @@ In this task, you will configure and test routing between the two spoke virtual 1. Click **OK** -1. Navigate back to **Route tables** blade and click **+ Add**. +1. Navigate back to **Route tables** blade and click **+ Create**. 1. Create a route table with the following settings (leave others with their default values): @@ -387,7 +387,7 @@ In this task, you will configure and test routing between the two spoke virtual In this task, you will implement an Azure Load Balancer in front of the two Azure virtual machines in the hub virtual network -1. In the Azure portal, search and select **Load balancers** and, on the **Load balancers** blade, click **+ Add**. +1. In the Azure portal, search and select **Load balancers** and, on the **Load balancers** blade, click **+ Create**. 1. Create a load balancer with the following settings (leave others with their default values): @@ -492,7 +492,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw > **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. -1. In the Azure portal, search and select **Application Gateways** and, on the **Application Gateways** blade, click **+ Add**. +1. In the Azure portal, search and select **Application Gateways** and, on the **Application Gateways** blade, click **+ Create**. 1. On the **Basics** tab of the **Create an application gateway** blade, specify the following settings (leave others with their default values): @@ -549,11 +549,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. 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): +1. Click **Add new** under to the **HTTP settings** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values): | Setting | Value | | --- | --- | - | HTTP setting | **az104-06-appgw5-http1** | + | HTTP settings Name | **az104-06-appgw5-http1** | | Backend protocol | **HTTP** | | Backend port | **80** | | Cookie-based affinity | **Disable** | From 0eece967c554562a1c452445c2af295606cdaa66 Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:11:04 +0500 Subject: [PATCH 05/11] Update LAB_07-Manage_Azure_Storage.md 1 change --- Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index 87008ff6..bc6698fe 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -76,7 +76,7 @@ In this task, you will deploy an Azure virtual machine that you will use later i 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 **+ New**. +1. In the Azure portal, search for and select **Storage accounts**, and then click **+ Create**. 1. On the **Basics** tab of the **Create storage account** blade, specify the following settings (leave others with their default values): From c237277933170420e5469409900c79cb3bd66c7e Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:12:35 +0500 Subject: [PATCH 06/11] Update LAB_08-Manage_Virtual_Machines.md 2 changes --- Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 1dca6086..b70ab11e 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -40,7 +40,7 @@ In this task, you will deploy Azure virtual machines into different availability 1. Sign in to the [Azure portal](http://portal.azure.com). -1. In the Azure portal, search for and select **Virtual machines** and, on the **Virtual machines** blade, click **+ Add**. +1. In the Azure portal, search for and select **Virtual machines** and, on the **Virtual machines** blade, click **+ Create**. 1. On the **Basics** tab of the **Create a virtual machine** blade, specify the following settings (leave others with their default values): @@ -52,7 +52,7 @@ In this task, you will deploy Azure virtual machines into different availability | Region | select one of the regions that support availability zones and where you can provision Azure virtual machines | | Availability options | **Availability zone** | | Availability zone | **1** | - | Image | **Windows Server 2019 Datacenter - Gen1** | + | Image | **Windows Server 2019 Datacenter - Gen1/Gen2** | | Azure Spot instance | **No** | | Size | **Standard D2s v3** | | Username | **Student** | From bafaa531c2da39a8004ee618b76eff8fa04f25cf Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:14:16 +0500 Subject: [PATCH 07/11] Update LAB_09a-Implement_Web_Apps.md changes --- Instructions/Labs/LAB_09a-Implement_Web_Apps.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md index 128c8352..7691fea7 100644 --- a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md +++ b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md @@ -38,7 +38,7 @@ In this task, you will create an Azure web app. 1. Sign in to the [**Azure portal**](http://portal.azure.com). -1. In the Azure portal, search for and select **App services**, and, on the **App Services** blade, click **+ Add**. +1. In the Azure portal, search for and select **App services**, and, on the **App Services** blade, click **+ Create**. 1. On the **Basics** tab of the **Web App** blade, specify the following settings (leave others with their default values): @@ -65,7 +65,7 @@ In this task, you will create a staging deployment slot. 1. On the blade of the newly deployed web app, click the **URL** link to display the default web page in a new browser tab. -1. Close the new browser tab and, back in the Azure portal, in the **Deployment** section of the web app blade, click **Deployment slots**. +1. Close the new browser tab and, back in the Azure portal, in the **Deployment** section of the web app blade, click **Add a Deployment slot**. >**Note**: The web app, at this point, has a single deployment slot labeled **PRODUCTION**. From 6caa25b4f4a2694b34ff3a3eecdb11b3fc43c4d6 Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:15:31 +0500 Subject: [PATCH 08/11] Update LAB_09b-Implement_Azure_Container_Instances.md minor --- .../Labs/LAB_09b-Implement_Azure_Container_Instances.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md b/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md index 47939789..833ab6f5 100644 --- a/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md +++ b/Instructions/Labs/LAB_09b-Implement_Azure_Container_Instances.md @@ -34,7 +34,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 **+ New**. +1. In the Azure portal, search for locate **Container instances** and then, on the **Container instances** blade, click **+ Create**. 1. On the **Basics** tab of the **Create container instance** blade, specify the following settings (leave others with their default values): From d1b756246c12c6273ce28c92812d8104c4203a7d Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:18:16 +0500 Subject: [PATCH 09/11] Update LAB_09c-Implement_Azure_Kubernetes_Service.md changes --- .../Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md index 3ef01ae7..c999a5e5 100644 --- a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md +++ b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md @@ -56,7 +56,7 @@ In this task, you will register resource providers necessary to deploy an Azure In this task, you will deploy an Azure Kubernetes Services cluster by using the Azure portal. -1. In the Azure portal, search for locate **Kubernetes services** and then, on the **Kubernetes services** blade, click **+ Add**, and then click **+ Add Kubernetes cluster**. +1. In the Azure portal, search for locate **Kubernetes services** and then, on the **Kubernetes services** blade, click **+ Create**, and then click **+ Create a Kubernetes cluster**. 1. On the **Basics** tab of the **Create Kubernetes cluster** blade, specify the following settings (leave others with their default values): @@ -92,7 +92,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**, ensure that the validation passed and click Create. +1. Click **Next: Integrations >**, on the **Integrations** 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. From c9b9eb8880622b4a8b02cfead1c2ab2c62c338f9 Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:19:45 +0500 Subject: [PATCH 10/11] Update LAB_10-Implement_Data_Protection.md minor change --- Instructions/Labs/LAB_10-Implement_Data_Protection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_10-Implement_Data_Protection.md b/Instructions/Labs/LAB_10-Implement_Data_Protection.md index b93ddfae..bd3b7d18 100644 --- a/Instructions/Labs/LAB_10-Implement_Data_Protection.md +++ b/Instructions/Labs/LAB_10-Implement_Data_Protection.md @@ -71,7 +71,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 **+ New**. +1. In the Azure portal, search for and select **Recovery Services vaults** and, on the **Recovery Services vaults** blade, click **+ Create**. 1. On the **Create Recovery Services vault** blade, specify the following settings: @@ -79,7 +79,7 @@ In this task, you will create a recovery services vault. | --- | --- | | Subscription | the name of the Azure subscription you are using in this lab | | Resource group | the name of a new resource group **az104-10-rg1** | - | Name | **az104-10-rsv1** | + | Vault Name | **az104-10-rsv1** | | Region | the name of a region where you deployed the two virtual machines in the previous task | >**Note**: Make sure that you specify the same region into which you deployed virtual machines in the previous task. From 32da440928872b96da72ea2f5c7d6152b91c5927 Mon Sep 17 00:00:00 2001 From: zainHaseeb Date: Thu, 23 Sep 2021 01:20:57 +0500 Subject: [PATCH 11/11] Update LAB_11-Implement_Monitoring.md changes --- Instructions/Labs/LAB_11-Implement_Monitoring.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index c187e045..cdc2b8e5 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -82,7 +82,7 @@ In this task, you will deploy a virtual machine that will be used to test monito In this task, you will create and configure an Azure Log Analytics workspace and Azure Automation-based solutions -1. In the Azure portal, search for and select **Log Analytics workspaces** and, on the **Log Analytics workspaces** blade, click **+ Add**. +1. In the Azure portal, search for and select **Log Analytics workspaces** and, on the **Log Analytics workspaces** blade, 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**: @@ -97,7 +97,7 @@ In this task, you will create and configure an Azure Log Analytics workspace and >**Note**: Wait for the deployment to complete. The deployment should take about 1 minute. -1. In the Azure portal, search for and select **Automation Accounts**, and on the **Automation Accounts** blade, click **+ Add**. +1. In the Azure portal, search for and select **Automation Accounts**, and on the **Automation Accounts** blade, click **+ Create**. 1. On the **Add Automation Account** blade, specify the following settings, and click **Create**: