From feddeb2190251315889fce2ec13103f53cb5c801 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sun, 21 Feb 2021 08:08:28 -0500 Subject: [PATCH 01/44] Update LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md addressing #245 --- .../LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md | 3 +++ 1 file changed, 3 insertions(+) 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 fd5a7d38..063fb077 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 @@ -73,6 +73,9 @@ In this task, you will create an Azure disk resource by using an Azure Resource "sourceUri": { "type": "String" }, + "sourceImageVersionId": { + "type": "String" + }, "osType": { "type": "String" }, From c8a1f7fd8d3fa6ac12144357fc710e9895f6d34c Mon Sep 17 00:00:00 2001 From: polichtm Date: Mon, 22 Feb 2021 08:06:40 -0500 Subject: [PATCH 02/44] addressing #246 --- .../Labs/04/az104-04-vms-loop-parameters.json | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 Allfiles/Labs/04/az104-04-vms-loop-parameters.json diff --git a/Allfiles/Labs/04/az104-04-vms-loop-parameters.json b/Allfiles/Labs/04/az104-04-vms-loop-parameters.json new file mode 100644 index 00000000..a8c85916 --- /dev/null +++ b/Allfiles/Labs/04/az104-04-vms-loop-parameters.json @@ -0,0 +1,15 @@ +{ + "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", + "contentVersion": "1.0.0.0", + "parameters": { + "vmSize": { + "value": "Standard_D2s_v3" + }, + "adminUsername": { + "value": "Student" + }, + "adminPassword": { + "value": "Pa55w.rd1234" + } + } +} From 59b4086bedc63844a63688e2fd46b5e42c9d04ff Mon Sep 17 00:00:00 2001 From: polichtm Date: Mon, 22 Feb 2021 08:07:02 -0500 Subject: [PATCH 03/44] addressing #246 --- .../Labs/04/az104-04-vms-loop-parameters .json | 15 --------------- 1 file changed, 15 deletions(-) delete mode 100644 Allfiles/Labs/04/az104-04-vms-loop-parameters .json diff --git a/Allfiles/Labs/04/az104-04-vms-loop-parameters .json b/Allfiles/Labs/04/az104-04-vms-loop-parameters .json deleted file mode 100644 index fabe43e9..00000000 --- a/Allfiles/Labs/04/az104-04-vms-loop-parameters .json +++ /dev/null @@ -1,15 +0,0 @@ -{ - "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "1.0.0.0", - "parameters": { - "vmSize": { - "value": "Standard_D2s_v3" - }, - "adminUsername": { - "value": "Student" - }, - "adminPassword": { - "value": "Pa55w.rd1234" - } - } -} \ No newline at end of file From 70179ca13b3439fc74bbc4c4b830ac31b2e0f453 Mon Sep 17 00:00:00 2001 From: tofusgh <31666473+tofusgh@users.noreply.github.com> Date: Tue, 23 Feb 2021 13:06:47 -0500 Subject: [PATCH 04/44] Move up portal refresh for dynamic groups It would be more helpful to give this tip at step 18 rather than 19 --- Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md index 777f87e3..caa265cc 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -172,10 +172,10 @@ In this task, you will create Azure Active Directory groups with assigned and dy 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-01a-aaduser2** appears in the list of group members. - >**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. +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. + #### Task 3: Create an Azure Active Directory (AD) tenant In this task, you will create a new Azure AD tenant. From 5ba909fa48a03efa433de6d97b4f275af2900f31 Mon Sep 17 00:00:00 2001 From: tofusgh <31666473+tofusgh@users.noreply.github.com> Date: Tue, 23 Feb 2021 13:18:27 -0500 Subject: [PATCH 05/44] portal updated licenses is no longer found in search yay --- 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 777f87e3..3d501a2a 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -250,7 +250,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** search for **Licenses** in the search bar. Within Licenses under **Products** select the **Azure Active Directory Premium P2** item in the below list and then select **Licensed Users**. Select the user accounts **az104-01a-aaduser1** and **az104-01a-aaduser2** to which you assigned licenses in this lab, click **Remove license**, and, when prompted to confirm, click **OK**. +1. In the **Azure Portal** search for **Azure Active Directory** in the search bar. Within **Azure Activity Directory** under **Manage** select **Licenses**. Once at **Licenses** under **Manage** select **All Products** and then select **Azure Active Directory Premium P2** item in the list. Proceed by then selecting **Licensed Users**. Select the user accounts **az104-01a-aaduser1** and **az104-01a-aaduser2** to which you assigned licenses in this lab, click **Remove license**, 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**. From c90a7dd0f5e5388b8b22144f57e9ac4fb24e215a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20Schw=C3=A4rzl?= Date: Thu, 25 Feb 2021 13:56:27 +0100 Subject: [PATCH 06/44] Fix paths in LAB_07-Manage_Azure_Storage.md #252 --- Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index c9090fc2..70b22989 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -40,7 +40,7 @@ In this task, you will deploy an Azure virtual machine that you will use later i >**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Create storage**. -1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Module_07\\az104-07-vm-template.json** and **\\Allfiles\\Module_07\\az104-07-vm-parameters.json** into the Cloud Shell home directory. +1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Labs\\07\\az104-07-vm-template.json** and **\\Allfiles\\Labs\\07\\az104-07-vm-parameters.json** into the Cloud Shell home directory. 1. From the Cloud Shell pane, run the following to create the resource group that will be hosting the virtual machine (replace the `[Azure_region]` placeholder with the name of an Azure region where you intend to deploy the Azure virtual machine) @@ -140,7 +140,7 @@ In this task, you will create a blob container and upload a blob into it. 1. In the list of containers, click **az104-07-container** and then click **Upload**. -1. Browse to **\\Allfiles\\Module_07\\LICENSE** on your lab computer and click **Open**, then click **Upload**. +1. Browse to **\\Allfiles\\Labs\\07\\LICENSE** on your lab computer and click **Open**, then click **Upload**. 1. On the **Upload blob** blade, expand the **Advanced** section and specify the following settings (leave others with their default values): From 1e4c604f925430ed36125ec4d66995514a3cbce2 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 27 Feb 2021 14:46:51 -0500 Subject: [PATCH 07/44] formatting --- 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 fdbdb1f8..dcac2320 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -167,7 +167,7 @@ In this task, you will install Windows Server Web Server role on the two Azure v 1. On the **Edit template** blade, in the section displaying the content of the template, insert the following code starting with line **20** (directly underneath the `"resources": [` line): - >**Note**: If you are using a tool that pastes the code in line by line intellisense may add extra brackets causing validation errors. You may want to paste the code into notepad first and then paste it into line 20. + >**Note**: If you are using a tool that pastes the code in line by line intellisense may add extra brackets causing validation errors. You may want to paste the code into notepad first and then paste it into line 20. ```json { @@ -191,7 +191,7 @@ In this task, you will install Windows Server Web Server role on the two Azure v ``` - >**Note**: This section of the template defines the same Azure virtual machine custom script extension that you deployed earlier to the first virtual machine via Azure PowerShell. + >**Note**: This section of the template defines the same Azure virtual machine custom script extension that you deployed earlier to the first virtual machine via Azure PowerShell. 1. Click **Save** and, back on the **Custom template** blade, enable the checkbox **I agree to the terms and conditions stated above** and click **Purchase**. From e72079a748e2634c842129b5f65a5df6ff993630 Mon Sep 17 00:00:00 2001 From: Fabian Fingerle <2011@fabian-fingerle.de> Date: Tue, 2 Mar 2021 13:42:05 +0100 Subject: [PATCH 08/44] Update LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md --- ...ge_Azure_Resources_by_Using_the_Azure_Portal.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) 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 a2e8915f..332717fc 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 @@ -31,24 +31,12 @@ In this task, you will use the Azure portal to create resource groups and create 1. Sign in to the [Azure portal](https://portal.azure.com). -1. Search for and select **Resource groups**. - -1. On the **Resource groups** blade, click **+ Add** and create a resource group with the following settings: - - |Setting|Value| - |---|---| - |Subscription| the name of the Azure subscription you will use in this lab | - |Resource Group| **az104-03a-rg1**| - |Region| the name of any Azure region available in the subscription you will use in this lab | - -1. Click **Review + Create** and then click **Create**. - 1. In the Azure portal, search for and select **Disks**, click **+ Add**, and specify the following settings: |Setting|Value| |---|---| |Subscription| the name of the Azure subscription where you created the resource group | - |Resource Group| **az104-03a-rg1** | + |Resource Group| Click "Create new" and create a new Resource Group with name **az104-03a-rg1** | |Disk name| **az104-03a-disk1** | |Region| the name of the Azure region where you created the resource group | |Availability zone| **None** | From 0b193cbef95520b0c3548c90511b76da6e98e078 Mon Sep 17 00:00:00 2001 From: Fabian Fingerle <2011@fabian-fingerle.de> Date: Tue, 2 Mar 2021 14:15:49 +0100 Subject: [PATCH 09/44] Update LAB_04-Implement_Virtual_Networking.md --- Instructions/Labs/LAB_04-Implement_Virtual_Networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index f2635d20..14487d6f 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -169,7 +169,7 @@ In this task, you will configure network security groups in order to allow for r 1. In the Azure portal, navigate back to the **az104-04-rg1** resource group blade, and in the list of its resources, click **az104-04-vm0**. -1. On the **az104-04-vm0** blade, click **Connect**, in the drop-down menu, click **RDP**, on the **Connect with RDP** blade, click **Download RDP File** and follow the prompts to start the Remote Desktop session. +1. On the **az104-04-vm0** blade, click **Connect**, click **RDP**, on the **Connect with RDP** blade, click **Download RDP File** using the Public IP address and follow the prompts to start the Remote Desktop session. 1. Note that the connection attempt fails. From 5f41656cb3c065c8197a987564d25a4f07efd17e Mon Sep 17 00:00:00 2001 From: Fabian Fingerle <2011@fabian-fingerle.de> Date: Tue, 2 Mar 2021 14:22:52 +0100 Subject: [PATCH 10/44] Update LAB_04-Implement_Virtual_Networking.md --- Instructions/Labs/LAB_04-Implement_Virtual_Networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index 14487d6f..8aaa5b05 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -216,7 +216,7 @@ In this task, you will configure network security groups in order to allow for r >**Note**: Now verify that you can successfully connect 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 **Connect**, in the drop-down menu, click **RDP**, on the **Connect with RDP** blade, click **Download RDP File** and follow the prompts to start the Remote Desktop session. +1. On the **az104-04-vm0** blade, click **Connect**, click **RDP**, on the **Connect with RDP** blade, click **Download RDP File** using the Public IP address and follow the prompts to start the Remote Desktop session. >**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. From dc0a70f87417bf826402caeb2b9d8877231c465f Mon Sep 17 00:00:00 2001 From: polichtm Date: Wed, 3 Mar 2021 05:45:18 -0500 Subject: [PATCH 11/44] Update LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md --- .../LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 332717fc..98f9c1be 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 @@ -36,7 +36,7 @@ In this task, you will use the Azure portal to create resource groups and create |Setting|Value| |---|---| |Subscription| the name of the Azure subscription where you created the resource group | - |Resource Group| Click "Create new" and create a new Resource Group with name **az104-03a-rg1** | + |Resource Group| the name of a new resource group **az104-03a-rg1** | |Disk name| **az104-03a-disk1** | |Region| the name of the Azure region where you created the resource group | |Availability zone| **None** | From 5af5bd178ee15f2b670a8b3b160c4756cff01374 Mon Sep 17 00:00:00 2001 From: polichtm Date: Wed, 3 Mar 2021 08:03:41 -0500 Subject: [PATCH 12/44] Update LAB_08-Manage_Virtual_Machines.md --- Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index dcac2320..6081df80 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -90,6 +90,7 @@ In this task, you will deploy Azure virtual machines into different availability | --- | --- | | Boot diagnostics | **Enable with custom storage account** | | Diagnostics storage account | accept the default value | + | Patch orchestration options | **Manual updates** | >**Note**: If necessary, select an existing storage account in the dropdown list. Record the name of the storage account. You will use it in the next task. @@ -114,6 +115,7 @@ In this task, you will deploy Azure virtual machines into different availability | Virtual Machine Computer Name | **az104-08-vm1** | | Admin Username | **Student** | | Admin Password | **Pa55w.rd1234** | + | Enable Hotpatching | **false** | | Zone | **2** | >**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. From d0a120897468434359bcc8c0abbb8b990f7a83ca Mon Sep 17 00:00:00 2001 From: Fabian Fingerle <2011@fabian-fingerle.de> Date: Thu, 4 Mar 2021 12:34:50 +0100 Subject: [PATCH 13/44] Update LAB_09c-Implement_Azure_Kubernetes_Service.md Task2 --- .../Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md index f6297ad7..12111d7c 100644 --- a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md +++ b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md @@ -64,21 +64,21 @@ In this task, you will deploy an Azure Kubernetes Services cluster by using the | Region | the name of a region where you can provision a Kubernetes cluster | | Kubernetes version | accept the default | | Node size | accept the default | - | Node count | **1** | + | Node count | **3** | 1. Click **Next: Node Pools >** and, on the **Node Pools** tab of the **Create Kubernetes cluster** blade, specify the following settings (leave others with their default values): | Setting | Value | | ---- | ---- | - | Virtual nodes | **Disabled** | - | VM scale sets | **Enabled** | + | Enable virtual nodes | **Disabled** (default) | + | Enable virtual machine scale sets | **Enabled** (default) | 1. Click **Next: Authentication >** and, on the **Authentication** tab of the **Create Kubernetes cluster** blade, specify the following settings (leave others with their default values): | Setting | Value | | ---- | ---- | - | Service principal | accept the default | - | Enable RBAC | **Yes** | + | Authentication method | **Service principal** (accept the defaults) | + | Role-based access control (RBAC) | **Enabled** | 1. Click **Next: Networking >** and, on the **Networking** tab of the **Create Kubernetes cluster** blade, specify the following settings (leave others with their default values): From bca485237fb172ebe2656e665fd78550fb30a5ad Mon Sep 17 00:00:00 2001 From: Fabian Fingerle <2011@fabian-fingerle.de> Date: Thu, 4 Mar 2021 13:08:51 +0100 Subject: [PATCH 14/44] Update LAB_04-Implement_Virtual_Networking.md --- Instructions/Labs/LAB_04-Implement_Virtual_Networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index 8aaa5b05..e3783908 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -169,7 +169,7 @@ In this task, you will configure network security groups in order to allow for r 1. In the Azure portal, navigate back to the **az104-04-rg1** resource group blade, and in the list of its resources, click **az104-04-vm0**. -1. On the **az104-04-vm0** blade, click **Connect**, click **RDP**, on the **Connect with RDP** blade, click **Download RDP File** using the Public IP address and follow the prompts to start the Remote Desktop session. +1. On the **az104-04-vm0** overview blade, click **Connect**, click **RDP** in the drop-down menu, on the **Connect with RDP** blade, click **Download RDP File** using the Public IP address and follow the prompts to start the Remote Desktop session. 1. Note that the connection attempt fails. From cf3af40dc7ffc633da8541a4488f5f7153aac442 Mon Sep 17 00:00:00 2001 From: polichtm Date: Fri, 5 Mar 2021 15:53:15 -0500 Subject: [PATCH 15/44] Update LAB_09c-Implement_Azure_Kubernetes_Service.md --- .../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 12111d7c..855c49b8 100644 --- a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md +++ b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md @@ -64,7 +64,7 @@ In this task, you will deploy an Azure Kubernetes Services cluster by using the | Region | the name of a region where you can provision a Kubernetes cluster | | Kubernetes version | accept the default | | Node size | accept the default | - | Node count | **3** | + | Node count | **1** | 1. Click **Next: Node Pools >** and, on the **Node Pools** tab of the **Create Kubernetes cluster** blade, specify the following settings (leave others with their default values): @@ -77,7 +77,7 @@ In this task, you will deploy an Azure Kubernetes Services cluster by using the | Setting | Value | | ---- | ---- | - | Authentication method | **Service principal** (accept the defaults) | + | Authentication method | **System-assigned managed identity** (default) | | Role-based access control (RBAC) | **Enabled** | 1. Click **Next: Networking >** and, on the **Networking** tab of the **Create Kubernetes cluster** blade, specify the following settings (leave others with their default values): From acd4345e5d7db59dee940ef911660c00bf70b596 Mon Sep 17 00:00:00 2001 From: polichtm Date: Wed, 10 Mar 2021 07:23:04 -0500 Subject: [PATCH 16/44] addressing #264 --- Instructions/Labs/LAB_04-Implement_Virtual_Networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index e3783908..fdb25dd2 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -214,7 +214,7 @@ 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 connect to the target virtual machine and sign in by using the **Student** username and **Pa55w.rd1234** password. + >**Note**: In the subsequent steps, you will verify that you can successfully connect 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 **RDP**, on the **Connect with RDP** blade, click **Download RDP File** using the Public IP address and follow the prompts to start the Remote Desktop session. From e0bdbce4aa1445db9ecfe2cf87904469c773e1b7 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 13 Mar 2021 11:12:20 -0500 Subject: [PATCH 17/44] addressing #261 and #265 --- ...06-Implement_Network_Traffic_Management.md | 30 ++++++++++++++----- 1 file changed, 23 insertions(+), 7 deletions(-) diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index ecaeca21..95050c3f 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -54,19 +54,37 @@ In this task, you will deploy four virtual machines into the same Azure region. New-AzResourceGroup -Name $rgName -Location $location ``` -1. From the Cloud Shell pane, run the following to create the three virtual networks and four virtual machines into them by using the template and parameter files you uploaded: +1. From the Cloud Shell pane, run the following to create the three virtual networks and four Azure VMs into them by using the template and parameter files you uploaded: ```powershell New-AzResourceGroupDeployment ` -ResourceGroupName $rgName ` -TemplateFile $HOME/az104-06-vms-loop-template.json ` - -TemplateParameterFile $HOME/az104-06-vms-loop-parameters.json ` - -AsJob + -TemplateParameterFile $HOME/az104-06-vms-loop-parameters.json ``` - >**Note**: Wait for the deployment to complete before proceeding to the next task. This should take about 5 minutes. + >**Note**: Wait for the deployment to complete before proceeding to the next step. This should take about 5 minutes. - >**Note**: To verify the status of the deployment, you can examine the properties of the resource group you created in this task. +1. From the Cloud Shell pane, run the following to install the Network Watcher extension on the Azure VMs deployed in the previous step: + + ```powershell + $rgName = 'az104-06-rg1' + $location = (Get-AzResourceGroup -ResourceGroupName $rgName).location + $vmNames = (Get-AzVM -ResourceGroupName $rgName).Name + + foreach ($vmName in $vmNames) { + Set-AzVMExtension ` + -ResourceGroupName $rgName ` + -Location $location ` + -VMName $vmName ` + -Name 'networkWatcherAgent' ` + -Publisher 'Microsoft.Azure.NetworkWatcher' ` + -Type 'NetworkWatcherAgentWindows' ` + -TypeHandlerVersion '1.4' + } + ``` + + >**Note**: Wait for the deployment to complete before proceeding to the next step. This should take about 5 minutes. 1. Close the Cloud Shell pane. @@ -157,8 +175,6 @@ In this task, you will test transitivity of virtual network peering by using Net > **Note**: This is expected, since the hub virtual network is peered directly with the first spoke virtual network. - > **Note**: The initial check can take about 2 minutes because it requires installation of the Network Watcher Agent virtual machine extension on **az104-06-vm0**. - 1. On the **Network Watcher - Connection troubleshoot** blade, initiate a check with the following settings (leave others with their default values): | Setting | Value | From 4a642831a16f423e656d20e91cc89c4aa12befc0 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 13 Mar 2021 11:23:16 -0500 Subject: [PATCH 18/44] Update LAB_05-Implement_Intersite_Connectivity.md --- .../Labs/LAB_05-Implement_Intersite_Connectivity.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md index 94619d4a..f909667c 100644 --- a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md +++ b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md @@ -59,13 +59,10 @@ In this task, you will deploy three virtual machines, each into a separate virtu -TemplateFile $HOME/az104-05-vnetvm-loop-template.json ` -TemplateParameterFile $HOME/az104-05-vnetvm-loop-parameters.json ` -location1 $location1 ` - -location2 $location2 ` - -AsJob + -location2 $location2 ``` - >**Note**: Wait for the deployment to complete before proceeding to the next task. This should take about 2 minutes. - - >**Note**: To verify the status of the deployment, you can examine the properties of the resource group you created in this task. + >**Note**: Wait for the deployment to complete before proceeding to the next step. This should take about 2 minutes. 1. Close the Cloud Shell pane. From 2a1647c5222730be7b66f779730bab9ba973e5c7 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 13 Mar 2021 11:50:19 -0500 Subject: [PATCH 19/44] addressing #260 --- ...LAB_05-Implement_Intersite_Connectivity.md | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md index f909667c..875a1610 100644 --- a/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md +++ b/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md @@ -99,6 +99,20 @@ In this task, you will configure local and global peering between the virtual ne >**Note**: This step establishes two local peerings - one from az104-05-vnet0 to az104-05-vnet1 and the other from az104-05-vnet1 to az104-05-vnet0. + >**Note**: In case you run into an issue with the Azure portal interface not displaying the virtual networks created in the previous task, you can configure peering by running the following PowerShell commands from Cloud Shell: + + ```powershell + $rgName = 'az104-05-rg1' + + $vnet0 = Get-AzVirtualNetwork -Name 'az104-05-vnet0' -ResourceGroupName $rgname + + $vnet1 = Get-AzVirtualNetwork -Name 'az104-05-vnet1' -ResourceGroupName $rgname + + Add-AzVirtualNetworkPeering -Name 'az104-05-vnet0_to_az104-05-vnet1' -VirtualNetwork $vnet0 -RemoteVirtualNetworkId $vnet1.Id + + Add-AzVirtualNetworkPeering -Name 'az104-05-vnet1_to_az104-05-vnet0' -VirtualNetwork $vnet1 -RemoteVirtualNetworkId $vnet0.Id + ``` + 1. On the **az104-05-vnet0** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. 1. Add a peering with the following settings (leave others with their default values) and click **Add**: @@ -120,6 +134,20 @@ In this task, you will configure local and global peering between the virtual ne >**Note**: This step establishes two global peerings - one from az104-05-vnet0 to az104-05-vnet2 and the other from az104-05-vnet2 to az104-05-vnet0. + >**Note**: In case you run into an issue with the Azure portal interface not displaying the virtual networks created in the previous task, you can configure peering by running the following PowerShell commands from Cloud Shell: + + ```powershell + $rgName = 'az104-05-rg1' + + $vnet0 = Get-AzVirtualNetwork -Name 'az104-05-vnet0' -ResourceGroupName $rgname + + $vnet2 = Get-AzVirtualNetwork -Name 'az104-05-vnet2' -ResourceGroupName $rgname + + Add-AzVirtualNetworkPeering -Name 'az104-05-vnet0_to_az104-05-vnet2' -VirtualNetwork $vnet0 -RemoteVirtualNetworkId $vnet2.Id + + Add-AzVirtualNetworkPeering -Name 'az104-05-vnet2_to_az104-05-vnet0' -VirtualNetwork $vnet2 -RemoteVirtualNetworkId $vnet0.Id + ``` + 1. Navigate back to the **Virtual networks** blade and, in the list of virtual networks, click **az104-05-vnet1**. 1. On the **az104-05-vnet1** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. @@ -143,6 +171,20 @@ In this task, you will configure local and global peering between the virtual ne >**Note**: This step establishes two global peerings - one from az104-05-vnet1 to az104-05-vnet2 and the other from az104-05-vnet2 to az104-05-vnet1. + >**Note**: In case you run into an issue with the Azure portal interface not displaying the virtual networks created in the previous task, you can configure peering by running the following PowerShell commands from Cloud Shell: + + ```powershell + $rgName = 'az104-05-rg1' + + $vnet1 = Get-AzVirtualNetwork -Name 'az104-05-vnet1' -ResourceGroupName $rgname + + $vnet2 = Get-AzVirtualNetwork -Name 'az104-05-vnet2' -ResourceGroupName $rgname + + Add-AzVirtualNetworkPeering -Name 'az104-05-vnet1_to_az104-05-vnet2' -VirtualNetwork $vnet1 -RemoteVirtualNetworkId $vnet2.Id + + Add-AzVirtualNetworkPeering -Name 'az104-05-vnet2_to_az104-05-vnet1' -VirtualNetwork $vnet2 -RemoteVirtualNetworkId $vnet1.Id + ``` + #### Task 3: Test intersite connectivity In this task, you will test connectivity between virtual machines on the three virtual networks that you connected via local and global peering in the previous task. From 31f383ee2f6f8fafb0172c508ffbd82b6d7b56e9 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 13 Mar 2021 12:09:31 -0500 Subject: [PATCH 20/44] addressing #260 --- ...06-Implement_Network_Traffic_Management.md | 24 +++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-) diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index 95050c3f..1bc88312 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -98,6 +98,22 @@ In this task, you will configure local peering between the virtual networks you >**Note**: The template you used for deployment of the three virtual networks ensures that the IP address ranges of the three virtual networks do not overlap. +1. In the list of virtual networks, select **az104-06-vnet2**. + +1. On the **az104-06-vnet2** blade, select **Properties**. + +1. On the **az104-06-vnet2 \| Properties** blade, record the value of the **Resource ID** property. + +1. Navigate back to the list of virtual networks and select **az104-06-vnet3**. + +1. On the **az104-06-vnet3** blade, select **Properties**. + +1. On the **az104-06-vnet3 \| Properties** blade, record the value of the **Resource ID** property. + + >**Note**: You will need the values of the ResourceID property for both virtual networks later in this task. + + >**Note**: This is a workaround that addresses the issue with the Azure portal occasionally not displaying the newly provisioned virtual network when creating virtual network peerings. + 1. In the list of virtual networks, click **az104-06-vnet01**. 1. On the **az104-06-vnet01** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**. @@ -112,8 +128,8 @@ In this task, you will configure local peering between the virtual networks you | Virtual network gateway | **None (default)** | | Remote virtual network: Peering link name | **az104-06-vnet2_to_az104-06-vnet01** | | Virtual network deployment model | **Resource manager** | - | Subscription | the name of the Azure subscription you are using in this lab | - | Virtual network | **az104-06-vnet2** | + | I know my resource ID | enabled | + | Resource ID | the value of resourceID parameter of **az104-06-vnet2** you recorded earlier in this task | | Traffic to remote virtual network | **Allow (default)** | | Traffic forwarded from remote virtual network | **Allow (default)** | | Virtual network gateway | **None (default)** | @@ -136,8 +152,8 @@ In this task, you will configure local peering between the virtual networks you | Virtual network gateway | **None (default)** | | Remote virtual network: Peering link name | **az104-06-vnet3_to_az104-06-vnet01** | | Virtual network deployment model | **Resource manager** | - | Subscription | the name of the Azure subscription you are using in this lab | - | Virtual network | **az104-06-vnet3** | + | I know my resource ID | enabled | + | Resource ID | the value of resourceID parameter of **az104-06-vnet3** you recorded earlier in this task | | Traffic to remote virtual network | **Allow (default)** | | Traffic forwarded from remote virtual network | **Allow (default)** | | Virtual network gateway | **None (default)** | From 332996f626f08e2f7e354469a883799c1c35ca3a Mon Sep 17 00:00:00 2001 From: Mr-Chenn Date: Tue, 16 Mar 2021 19:50:16 +0000 Subject: [PATCH 21/44] Update LAB_08-Manage_Virtual_Machines.md --- Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 6081df80..adecbcfc 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -306,7 +306,7 @@ In this task you will scale compute for Azure virtual machines by changing their 1. Click **Save** and, back on the **Custom template** blade, enable the checkbox **I agree to the terms and conditions stated above** and click **Purchase**. - >**Note**: Wait for the template deployment to complete. You can monitor its progress from the **Extensions** blade of the **az104-08-vm1** virtual machine. This should take no more than 3 minutes. + >**Note**: Wait for the template deployment to complete. You can monitor its progress from the **Disks** blade of the **az104-08-vm1** virtual machine. This should take no more than 3 minutes. 1. Back on the **az104-08-vm1** blade, in the **Operations** section, click **Run command**, and, in the list of commands, click **RunPowerShellScript**. From 9002df338d207765f635768d1e25f36acf643737 Mon Sep 17 00:00:00 2001 From: Ricardo Chu Date: Sun, 28 Mar 2021 13:59:49 -0400 Subject: [PATCH 22/44] Create new disk from Disk blade The button to create a new disk from the Disk blade is labeled "+ New", not "+ Add". --- ...AB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 98f9c1be..9281e713 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 @@ -31,7 +31,7 @@ In this task, you will use the Azure portal to create resource groups and create 1. Sign in to the [Azure portal](https://portal.azure.com). -1. In the Azure portal, search for and select **Disks**, click **+ Add**, and specify the following settings: +1. In the Azure portal, search for and select **Disks**, click **+ New**, and specify the following settings: |Setting|Value| |---|---| @@ -72,7 +72,7 @@ In this task, we will move the disk resource you created in the previous task to In this task, you will apply a resource lock to an Azure resource group containing a disk resource. -1. In the Azure portal, search for and select **Disks**, click **+ Add**, and specify the following settings: +1. In the Azure portal, search for and select **Disks**, click **+ New**, and specify the following settings: |Setting|Value| |---|---| From 767074b2641042bd2a92474afe6007b819be74d1 Mon Sep 17 00:00:00 2001 From: MPrentice Date: Mon, 5 Apr 2021 17:10:56 -0400 Subject: [PATCH 23/44] Clarify tenant initial domain name I wonder how many people have used their own company domain as part of the tenant initial domain, and therefore prevented their company from actually having access to a tenant domain that matches closely with their Internet domain. My suggestion may not be the best but something should be put in to help ensure students don't accidentally take their corporate tenant domain or another organizations. --- 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 4f4ca208..3cbada06 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -196,7 +196,7 @@ In this task, you will create a new Azure AD tenant. | Initial domain name | any valid DNS name consisting of lower case letters and digits and starting with a letter | | Country/Region | **United States** | - > **Note**: The green check mark in the **Initial domain name** text box will indicate that the domain name you typed in is valid and unique. + > **Note**: The **Initial domain name** should not be a legitimate name that potentially matches your organization or another. The green check mark in the **Initial domain name** text box will indicate that the domain name you typed in is valid and unique. 1. Click **Review + create** and then click **Create**. From b230ba02e8a3e24ace3f349f68b6e705d788a9ee Mon Sep 17 00:00:00 2001 From: Sakari Kouti Date: Tue, 6 Apr 2021 20:00:48 +0300 Subject: [PATCH 24/44] UI has changed from directory to tenant --- 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 3cbada06..1a389cd9 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -200,7 +200,7 @@ In this task, you will create a new Azure AD tenant. 1. Click **Review + create** and then click **Create**. -1. Display the blade of the newly created Azure AD tenant by using the **Click here to navigate to your new directory: Contoso Lab** link or the **Directory + Subscription** button (directly to the right of the Cloud Shell button) in the Azure portal toolbar. +1. Display the blade of the newly created Azure AD tenant by using the **Click here to navigate to your new tenant: Contoso Lab** link or the **Directory + Subscription** button (directly to the right of the Cloud Shell button) in the Azure portal toolbar. #### Task 4: Manage Azure AD guest users. From 72dc32048fb2fa196ceb18123e702fad4d92f00e Mon Sep 17 00:00:00 2001 From: Sakari Kouti Date: Tue, 6 Apr 2021 20:31:16 +0300 Subject: [PATCH 25/44] UI has changed from directory to tenant, case 2 --- Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md index 1a389cd9..ae4a6d61 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -262,11 +262,11 @@ 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 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**. +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. Sign out from the Azure portal and sign in back. -1. Navigate back to the **Delete directory 'Contoso Lab'** blade and click **Delete**. +1. Navigate back to the **Delete tenant 'Contoso Lab'** blade and click **Delete**. > **Note**: You will have to wait for license expiration before you can delete the tenant. This does not incur any additional cost. From 6abec62903104a517514c5425d93417c725919fb Mon Sep 17 00:00:00 2001 From: Massimo Bonanni Date: Fri, 9 Apr 2021 08:27:45 +0200 Subject: [PATCH 26/44] Lab 02a - Exercise 1 - Task 1 - Step 05 The portal ui allows user to add subscriptions to management group in the Subscriptions blade, not in the overview --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index 05804929..173fc322 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -56,7 +56,7 @@ In this task, you will create and configure management groups. 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-02-mg1** blade, click **+ Add subscription** and add the subscription you are using in this lab to the management group. +1. From the **Subscriptions** 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. From 3871491318d61fcbb9ff710617a811daaddce27a Mon Sep 17 00:00:00 2001 From: Massimo Bonanni Date: Fri, 9 Apr 2021 08:29:57 +0200 Subject: [PATCH 27/44] Lab02a - Exercise 01 - Cleanup - Step 08 The portal UI allows users to move subscriptions in the Subscriptions blade, not in the overview --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index 173fc322..f9203bde 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -173,7 +173,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro 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. In the **Subscriptions** blade, 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**. From 956ec3cb0e811575e4dd3f909446e50e9e05e21b Mon Sep 17 00:00:00 2001 From: Massimo Bonanni Date: Fri, 9 Apr 2021 08:46:02 +0200 Subject: [PATCH 28/44] Lab 07 - Exercise 01 - Task 03 - Step 04 Remove "click on Upload" istruction. If the student click on Upload, the blob is uploaded in the container and the student need to select the file again. The student select the file, set the properties in the advanced section and then upload the blob. --- 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 70b22989..501b93c7 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -140,7 +140,7 @@ In this task, you will create a blob container and upload a blob into it. 1. In the list of containers, click **az104-07-container** and then click **Upload**. -1. Browse to **\\Allfiles\\Labs\\07\\LICENSE** on your lab computer and click **Open**, then click **Upload**. +1. Browse to **\\Allfiles\\Labs\\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): From 647539c4259ff7c525edee2f33fdbcfb6aec54b6 Mon Sep 17 00:00:00 2001 From: Massimo Bonanni Date: Fri, 9 Apr 2021 08:52:31 +0200 Subject: [PATCH 29/44] Lab 07 - Exercise 01 - Task 04 - Step 10 When the student change the Authentication Method, the portal returns an error in the blade. The students can be frustrated because the lab doesn't explain the error. The error is expected but the lab instruction doesn't mention this thing. --- Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index 501b93c7..cee47fb4 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -207,6 +207,8 @@ In this task, you will configure authentication and authorization for Azure Stor 1. Click the **Switch to the Azure AD User Account** link next to the **Authentication method** label. + > **Note**: You can see an error when you change the authentication method (the error is *"You do not have permissions to list the data using your user account with Azure AD"*). It is expected. + > **Note**: At this point, you no longer have access to the container. 1. On the **az104-07-container** blade, click **Access Control (IAM)**. From 16907177f0c266fd51ab7601ff547e2fa348daae Mon Sep 17 00:00:00 2001 From: tonypai Date: Sat, 10 Apr 2021 16:10:57 +0800 Subject: [PATCH 30/44] Update the outdated error identification flow **Review + create** can not validate the policy rule now, it will happened until deployment submitted. --- .../Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 7e868b83..d78c3c52 100644 --- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md +++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md @@ -122,13 +122,13 @@ In this task, you will assign the built-in *Require a tag and its value on resou 1. On the **New** blade, search for and select **Storage account**, and click **Create**. -1. On the **Basics** tab of the **Create storage account** blade, specify the following settings (leave others with their defaults) and click **Review + create**: +1. On the **Basics** tab of the **Create storage account** blade, specify the following settings (leave others with their defaults), click **Review + create** and then click **Create**: | Setting | Value | | --- | --- | | 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. +1. After deployment submitted, you will see **Deployment failed** in the **Notifications** list, navigate to the deployment overview and click the **Deployment failed. Click here for details** to see the reason of failure. >**Note**: The error message states that the resource deployment was disallowed by the policy. From 25e43763a9bdcfa46dd1f547229cf0067e2d7cf0 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 10 Apr 2021 05:55:55 -0400 Subject: [PATCH 31/44] Update LAB_02b-Manage_Governance_via_Azure_Policy.md --- .../Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 d78c3c52..456f597f 100644 --- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md +++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md @@ -128,9 +128,9 @@ In this task, you will assign the built-in *Require a tag and its value on resou | --- | --- | | Storage account name | any globally unique combination of between 3 and 24 lower case letters and digits, starting with a letter | -1. After deployment submitted, you will see **Deployment failed** in the **Notifications** list, navigate to the deployment overview and click the **Deployment failed. Click here for details** to see the reason of failure. +1. Once you create the deployment, you should see the **Deployment failed** message in the **Notifications** list of the portal. From the **Notifications** list, navigate to the deployment overview and click the **Deployment failed. Click here for details** message to identify the reason for the failure. - >**Note**: The error message states that the resource deployment was disallowed by the policy. + >**Note**: Verify whether the error message states that the resource deployment was disallowed by the policy. >**Note**: By clicking the **Raw Error** tab, you can find more details about the error, including the name of the role definition **Require Role tag with Infra value**. The deployment failed because the storage account you attempted to create did not have a tag named **Role** with its value set to **Infra**. From a0bb38e33dbe2042014b19d1da51038927ccc346 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 10 Apr 2021 06:08:48 -0400 Subject: [PATCH 32/44] Update LAB_02a_Manage_Subscriptions_and_RBAC.md --- .../Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index f9203bde..cf62bdc0 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -45,20 +45,22 @@ In this task, you will create and configure management groups. 1. Search for and select **Management groups** and then, on the **Management groups** blade, click **+ Add management group**. - >**Note**: If you have not previously created Management Groups, select **Start using Management Groups** + >**Note**: If you have not previously created Management Groups, select **Start using management groups** 1. Create a management group with the following settings: | Setting | Value | | --- | --- | - | Management group ID | **az104-02-mg1**| - | Management group display name | **az104-02-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. In the list of management groups, click the entry representing the newly created management group. -1. From the **Subscriptions** blade, click **+ Add subscription** and add the subscription you are using in this lab to the management group. +1. On the **az104-02-mg1** blade, click **Subscriptions**. - >**Note**: Copy the ID of your Azure subscription into Clipboard. You will need it in the next task. +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**. + + >**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. #### Task 2: Create custom RBAC roles From 6cc0a97f3fa56e4d679c3f8f700445cd3331ae04 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 10 Apr 2021 11:21:45 -0400 Subject: [PATCH 33/44] Update LAB_02a_Manage_Subscriptions_and_RBAC.md --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index cf62bdc0..f21db9b5 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -173,9 +173,9 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro 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-02-mg1** management group and display its **details**. +1. In the Azure portal, navigate back to the **az104-02-mg1** management group blade and click **Subsciptions**. -1. In the **Subscriptions** blade, right-click the **ellipsis** icon to the right of the entry representing your Azure subscription and click **Move**. +1. On the **Subscriptions** blade, 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**. From 680b715b679d40f6e3400bb7f2f47eb9361b7f21 Mon Sep 17 00:00:00 2001 From: polichtm Date: Mon, 12 Apr 2021 19:31:43 -0400 Subject: [PATCH 34/44] addressing #276 --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index f21db9b5..4be59078 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -175,7 +175,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro 1. In the Azure portal, navigate back to the **az104-02-mg1** management group blade and click **Subsciptions**. -1. On the **Subscriptions** blade, right-click the **ellipsis** icon to the right of the entry representing your Azure subscription and click **Move**. +1. On the **Subscriptions** blade, 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**. From f1ffaa4a37b92d237fb31ccf23bacd9540324271 Mon Sep 17 00:00:00 2001 From: Dieter Rauscher <10585486+DieterRauscher@users.noreply.github.com> Date: Tue, 13 Apr 2021 16:07:10 +0200 Subject: [PATCH 35/44] Update LAB_01-Manage_Azure_AD_Identities.md Corrected "Azure Activity Directory" to "Azure Active Directory". --- 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 4f4ca208..8abece91 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -250,7 +250,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** search for **Azure Active Directory** in the search bar. Within **Azure Activity Directory** under **Manage** select **Licenses**. Once at **Licenses** under **Manage** select **All Products** and then select **Azure Active Directory Premium P2** item in the list. Proceed by then selecting **Licensed Users**. Select the user accounts **az104-01a-aaduser1** and **az104-01a-aaduser2** to which you assigned licenses in this lab, click **Remove license**, and, when prompted to confirm, click **OK**. +1. In the **Azure Portal** search for **Azure Active Directory** in the search bar. Within **Azure Active Directory** under **Manage** select **Licenses**. Once at **Licenses** under **Manage** select **All Products** and then select **Azure Active Directory Premium P2** item in the list. Proceed by then selecting **Licensed Users**. Select the user accounts **az104-01a-aaduser1** and **az104-01a-aaduser2** to which you assigned licenses in this lab, click **Remove license**, 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**. From 29e48fde864434674d4c64b3e364fbe4f243cf26 Mon Sep 17 00:00:00 2001 From: Clifford Brent Smith <78555251+clifford-smith@users.noreply.github.com> Date: Wed, 14 Apr 2021 12:20:14 -0600 Subject: [PATCH 36/44] Update LAB_02a_Manage_Subscriptions_and_RBAC.md edit to match interface changes --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index 4be59078..64d3e960 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -43,7 +43,7 @@ In this task, you will create and configure management groups. 1. Sign in to the [Azure portal](https://portal.azure.com). -1. Search for and select **Management groups** and then, on the **Management groups** blade, click **+ Add management group**. +1. Search for and select **Management groups** and then, on the **Management groups** blade, click **+ Add**. >**Note**: If you have not previously created Management Groups, select **Start using management groups** From e1da2594d7e436259657b0018f62ba608b80e5ee Mon Sep 17 00:00:00 2001 From: Clifford Brent Smith <78555251+clifford-smith@users.noreply.github.com> Date: Wed, 14 Apr 2021 12:22:50 -0600 Subject: [PATCH 37/44] Update LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md edit to match potential interface options --- ...AB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 9281e713..16abda1a 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 @@ -31,7 +31,7 @@ In this task, you will use the Azure portal to create resource groups and create 1. Sign in to the [Azure portal](https://portal.azure.com). -1. In the Azure portal, search for and select **Disks**, click **+ New**, and specify the following settings: +1. In the Azure portal, search for and select **Disks**, click **+ Add, + Create, or + New**, and specify the following settings: |Setting|Value| |---|---| @@ -72,7 +72,7 @@ In this task, we will move the disk resource you created in the previous task to In this task, you will apply a resource lock to an Azure resource group containing a disk resource. -1. In the Azure portal, search for and select **Disks**, click **+ New**, and specify the following settings: +1. In the Azure portal, search for and select **Disks**, click **+ Add, + Create, or + New**, and specify the following settings: |Setting|Value| |---|---| From 65401e865039b89a0a5c426d9b17b996e21aaf37 Mon Sep 17 00:00:00 2001 From: Clifford Brent Smith <78555251+clifford-smith@users.noreply.github.com> Date: Wed, 14 Apr 2021 12:26:42 -0600 Subject: [PATCH 38/44] Update LAB_04-Implement_Virtual_Networking.md reordered list to match interface changes --- Instructions/Labs/LAB_04-Implement_Virtual_Networking.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md index fdb25dd2..e5bcf393 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -127,8 +127,6 @@ In this task, you will configure static assignment of public and private IP addr 1. In the list IP configurations, click **ipconfig1**. -1. On the **ipconfig1** blade, set **Assignment** to **Static**, leave the default value of **IP address** set to **10.40.0.4**. - 1. On the **ipconfig1** blade, in the **Public IP address settings** section, select **Associate**, click **+ Create new**, specify the following settings, and click **OK**: | Setting | Value | @@ -136,6 +134,8 @@ In this task, you will configure static assignment of public and private IP addr | Name | **az104-04-pip0** | | SKU | **Standard** | +1. On the **ipconfig1** blade, set **Assignment** to **Static**, leave the default value of **IP address** set to **10.40.0.4**. + 1. Back on the **ipconfig1** blade, save the changes. 1. Navigate back to the **az104-04-vnet1** blade @@ -146,8 +146,6 @@ In this task, you will configure static assignment of public and private IP addr 1. In the list IP configurations, click **ipconfig1**. -1. On the **ipconfig1** blade, set **Assignment** to **Static**, leave the default value of **IP address** set to **10.40.1.4**. - 1. On the **ipconfig1** blade, in the **Public IP address settings** section, select **Associate**, click **+ Create new**, specify the following settings, and click **OK**: | Setting | Value | @@ -155,6 +153,8 @@ In this task, you will configure static assignment of public and private IP addr | Name | **az104-04-pip1** | | SKU | **Standard** | +1. On the **ipconfig1** blade, set **Assignment** to **Static**, leave the default value of **IP address** set to **10.40.1.4**. + 1. Back on the **ipconfig1** blade, save the changes. 1. Navigate back to the **az104-04-rg1** resource group blade, in the list of its resources, click **az104-04-vm0**, and from the **az104-04-vm0** virtual machine blade, note the public IP address entry. From c051f193cd9dfd3b3fad2d64f59d3e02bbaaa4e7 Mon Sep 17 00:00:00 2001 From: Clifford Brent Smith <78555251+clifford-smith@users.noreply.github.com> Date: Wed, 14 Apr 2021 12:30:47 -0600 Subject: [PATCH 39/44] Update LAB_06-Implement_Network_Traffic_Management.md minor edits to correct code and change "Ok" to "Add" to match interface changes --- .../Labs/LAB_06-Implement_Network_Traffic_Management.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index 1bc88312..7bcc4a64 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -355,7 +355,7 @@ In this task, you will configure and test routing between the two spoke virtual | Virtual network | **az104-06-vnet3** | | Subnet | **subnet0** | -1.Click **OK** +1. Click **OK** 1. In the Azure portal, navigate back to the **Network Watcher - Connection troubleshoot** blade. @@ -433,7 +433,7 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur | Interval | **5** | | Unhealthy threshold | **2** | -1. Click **OK** +1. Click **Add** 1. Wait for the health probe to be created, in the **Settings** section, click **Load balancing rules**, and then click **+ Add**. @@ -453,7 +453,7 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur | TCP reset | **Disabled** | | Floating IP (direct server return) | **Disabled** | -1. Click **OK** +1. Click **Add** 1. Wait for the load balancing rule to be created, click **Overview**, and note the value of the **Public IP address**. From e36481f4d71da867cf0a0a6691efe6befa7def06 Mon Sep 17 00:00:00 2001 From: s-iv-a <66815461+s-iv-a@users.noreply.github.com> Date: Sat, 24 Apr 2021 21:38:18 +0530 Subject: [PATCH 40/44] Update LAB_08-Manage_Virtual_Machines.md Updated "Purchase" option to "Create", in the **Review+Create** blade of template deployment. --- Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index adecbcfc..9714459a 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -120,7 +120,7 @@ In this task, you will deploy Azure virtual machines into different availability >**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. -1. Enable the checkbox **I agree to the terms and conditions stated above** and click **Purchase**. +1. Click **Review + Create**, on the **Review + Create** blade, click **Create**. >**Note**: Wait for both deployments to complete before you proceed to the next task. This might take about 5 minutes. From 7f1df22e690332afac06ec8ab1e165e6236e66e5 Mon Sep 17 00:00:00 2001 From: s-iv-a <66815461+s-iv-a@users.noreply.github.com> Date: Sat, 24 Apr 2021 22:03:51 +0530 Subject: [PATCH 41/44] Update LAB_08-Manage_Virtual_Machines.md Updated "Purchase" to "Create" in Custom template blade. --- Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 9714459a..5ac5d700 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -195,7 +195,7 @@ In this task, you will install Windows Server Web Server role on the two Azure v >**Note**: This section of the template defines the same Azure virtual machine custom script extension that you deployed earlier to the first virtual machine via Azure PowerShell. -1. Click **Save** and, back on the **Custom template** blade, enable the checkbox **I agree to the terms and conditions stated above** and click **Purchase**. +1. Click **Save** and, back on the **Custom template** blade, click **Review + Create** and, on the **Review + Create** blade, click **Create** >**Note**: Wait for the template deployment to complete. You can monitor its progress from the **Extensions** blade of the **az104-08-vm0** and **az104-08-vm1** virtual machines. This should take no more than 3 minutes. From 44e111f3adef09791382e7eec37496434b3c9a55 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sun, 25 Apr 2021 05:38:41 -0400 Subject: [PATCH 42/44] addressing #284 --- 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 12eaf6bf..69c53dec 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -268,7 +268,7 @@ In this task, you will create Azure AD guest users and grant them access to reso 1. Navigate back to the **Delete tenant 'Contoso Lab'** blade and click **Delete**. -> **Note**: You will have to wait for license expiration before you can delete the tenant. This does not incur any additional cost. +> **Note**: You will have to wait for the trial license expiration before you can delete the tenant. This does not incur any additional cost. #### Review From 685797925d6da5c0a80a3012574e8512b7b2a0bb Mon Sep 17 00:00:00 2001 From: polichtm Date: Wed, 28 Apr 2021 21:44:29 -0400 Subject: [PATCH 43/44] addressing #286 and #287 --- .../Labs/LAB_07-Manage_Azure_Storage.md | 33 ++++--------------- 1 file changed, 6 insertions(+), 27 deletions(-) diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index cee47fb4..47c38aa5 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -71,7 +71,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 **+ Add**. 1. On the **Basics** tab of the **Create storage account** blade, specify the following settings (leave others with their default values): @@ -82,40 +82,19 @@ In this task, you will create and configure an Azure Storage account. | Storage account name | any globally unique name between 3 and 24 in length consisting of letters and digits | | Location | the name of an Azure region where you can create an Azure Storage account | | Performance | **Standard** | - | Account kind | **Storage (general purpose v1)** | - | Replication | **Read-access geo-redundant storage (RA-GRS)** | + | Redundancy | **Geo-redundant storage (GRS)** | -1. Click **Next: Networking >**, on the **Networking** tab of the **Create storage account** blade, review the available options, accept the default option **Public endpoint (all networks}** and click **Next: Data protection >**. +1. Click **Next: Advanced >**, on the **Advanced** tab of the **Create storage account** blade, review the available options, accept the defaults, and click **Next: Networking >**. -1. On the **Data protection** tab of the **Create storage account** blade, review the available options, accept the defaults, and click **Next: Advanced >**. +1. On the **Networking** tab of the **Create storage account** blade, review the available options, accept the default option **Public endpoint (all networks}** and click **Next: Data protection >**. -1. On the **Advanced** tab of the **Create storage account** blade, review the available options, accept the defaults, click **Review + Create**, wait for the validation process to complete and click **Create**. +1. On the **Data protection** tab of the **Create storage account** blade, review the available options, accept the defaults, click **Review + Create**, wait for the validation process to complete and click **Create**. >**Note**: Wait for the Storage account to be created. This should take about 2 minutes. 1. On the deployment blade, click **Go to resource** to display the Azure Storage account blade. -1. On the Azure Storage account blade, in the **Settings** section, click **Configuration**. - -1. Click **Upgrade** to change the Storage account kind from **Storage (general purpose v1)** to **StorageV2 (general purpose v2)**. - -1. On the **Upgrade storage account** blade, review the warning stating that the upgrade is permanent and will result in billing charges, in the **Confirm upgrade** text box, type the name of the storage account, and click **Upgrade**. - - > **Note**: You have the option to set the account kind to **StorageV2 (general purpose v2)** at the provisioning time. The previous two steps were meant to illustrate that you also have the option to upgrade existing general purpose v1 accounts. - - > **Note**: **StorageV2 (general purpose v2)** offers a number of features, such as, for example, access tiering, not available in with general purpose v1 accounts. - - > **Note**: Review the other configuration options, including **Access tier (default)**, currently set to **Hot**, which you can change, the **Performance**, currently set to **Standard**, which can be set only during account provisioning, and the **Identity-based Directory Service for Azure File Authentication**, which requires Azure Active Directory Domain Services. - -1. On the Storage account blade, in the **Settings** section, click **Geo-replication** and note the secondary location. Click the **View all** link under the **Storage endpoints** label and review the **Storage account endpoints** blade. - - > **Note**: As expected, the **Storage account endpoints** blade contains both primary and secondary endpoints. - -1. Switch to the Configuration blade of the Storage account and, in the **Replication** drop-down list, select **Geo-redundant storage (GRS)** and save the change. - -1. Switch back to the **Geo-replication** blade and note that the secondary location is still specified. Click the **View all** link under the **Storage endpoints** label and review the **Storage account endpoints** blade. - - > **Note**: As expected, the **Storage account endpoints** blade contains only primary endpoints. +1. On the Storage account blade, in the **Settings** section, click **Geo-replication** and note the secondary location. 1. Display again the **Configuration** blade of the Storage account, in the **Replication** drop-down list select **Locally redundant storage (LRS)** and save the change. From 546d8f47d83f9865abc9dfd274e572a25fd9c40e Mon Sep 17 00:00:00 2001 From: polichtm Date: Wed, 5 May 2021 07:50:04 -0400 Subject: [PATCH 44/44] addressing #289 --- .../Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 10 ++++++---- 1 file changed, 6 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 64d3e960..eda11d29 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -173,13 +173,15 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro 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 back to the **az104-02-mg1** management group blade and click **Subsciptions**. +1. In the Azure portal, navigate back to the **Management groups** blade. -1. On the **Subscriptions** blade, click the **ellipsis** icon to the right of the entry representing your Azure subscription and click **Move**. +1. On the **Management groups** blade, in the **Child subscriptions** column, in the row representing the name of the management group to which you want to move the Azure subscription you used in this lab, select the link represeting its current number of subscriptions. -1. On the **Move** blade, select the management group which the subscription was originally part of and click **Save**. + >**Note**: It is likely that the target management group is the **Tenant Root management group**, unless you created a custom management group hierarchy before running this lab. + +1. On the **Subscriptions** blade of the target management group, select **+ Add**. - >**Note**: This is the **Tenant Root management group**, unless you created a custom management group hierarchy before running this lab. +1. On the **Add subscription** blade, in the **Subscriptions** drop-down list, select the name of the Azure subscription you used in this lab and click **Save**. 1. 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**.