From e3863dfca7bf59efa17fd76cd64d6edda6b8e748 Mon Sep 17 00:00:00 2001 From: Raymond Comvalius Date: Mon, 8 Jun 2020 10:39:32 +0200 Subject: [PATCH 01/25] Update az104-03b-md-parameters.json diskSizeGb value is not a string value. Added missing parameter diskEncryptionSetType --- Allfiles/Labs/03/az104-03b-md-parameters.json | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Allfiles/Labs/03/az104-03b-md-parameters.json b/Allfiles/Labs/03/az104-03b-md-parameters.json index d769e8ac..66690e92 100644 --- a/Allfiles/Labs/03/az104-03b-md-parameters.json +++ b/Allfiles/Labs/03/az104-03b-md-parameters.json @@ -12,10 +12,13 @@ "value": "Standard_LRS" }, "diskSizeGb": { - "value": "32" + "value": 32 }, "createOption": { "value": "empty" + }, + "diskEncryptionSetType": { + "value": "EncryptionAtRestWithPlatformKey" } } -} \ No newline at end of file +} From 774f701e9cc8c2f24e4a6a6637e94660dbff3c0d Mon Sep 17 00:00:00 2001 From: Raymond Comvalius Date: Mon, 8 Jun 2020 10:42:39 +0200 Subject: [PATCH 02/25] Update LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md Added Disk Encryption Set Type, which is a mandatory setting in the template. --- .../LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md | 1 + 1 file changed, 1 insertion(+) 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 eba7c0d2..a9dbe3c3 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 @@ -107,6 +107,7 @@ In this task, you will create an Azure disk resource by using an Azure Resource | Sku | **Standard_LRS** | | Disk Size Gb | **32** | | Create Option | **empty** | + | Disk Encryption Set Type | **EncryptionAtRestWithPlatformKey** | 1. Select the checkbox **I agree to the terms and conditions stated above** and click **Purchase**. From 9854e82fe7a290315d739276fa717bac246ca1d4 Mon Sep 17 00:00:00 2001 From: Raymond Comvalius Date: Tue, 9 Jun 2020 14:27:52 +0200 Subject: [PATCH 03/25] Update LAB_06-Implement_Network_Traffic_Management.md Typo in step 12 for task #6 --- .../Labs/LAB_06-Implement_Network_Traffic_Management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index fcf9fde0..0500c8ee 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -524,7 +524,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw | Target type | **Backend pool** | | Backend target | **az104-06-appgw5-be1** | -1. On the **Backend targets** tab of the **Add a routing rule** blade, click **Create new** next to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values): +1. On the **Backend targets** tab of the **Add a routing rule** blade, click **Add new** next to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values): | Setting | Value | | --- | --- | From b05e1cc3359fbd7e7f729fbabfead1a3d740db2a Mon Sep 17 00:00:00 2001 From: Yves Dhondt Date: Tue, 9 Jun 2020 21:41:24 +0200 Subject: [PATCH 04/25] Fix diskSizeGb type from String to Int --- Allfiles/Labs/03/az104-03b-md-template.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Allfiles/Labs/03/az104-03b-md-template.json b/Allfiles/Labs/03/az104-03b-md-template.json index 3eed07e1..4c9a6e2e 100644 --- a/Allfiles/Labs/03/az104-03b-md-template.json +++ b/Allfiles/Labs/03/az104-03b-md-template.json @@ -12,7 +12,7 @@ "type": "String" }, "diskSizeGb": { - "type": "String" + "type": "Int" }, "sourceResourceId": { "type": "String" From 12de0522865822c5ba4be5a7fb00a2335a106bed Mon Sep 17 00:00:00 2001 From: polichtm Date: Fri, 12 Jun 2020 19:32:02 -0400 Subject: [PATCH 05/25] addressing #91 --- 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 cc12991a..160237bf 100644 --- a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md +++ b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md @@ -105,7 +105,7 @@ In this task, you will configure web app deployment settings. | Setting | Value | | --- | ---| | User name | any unique name | - | Password | **Pa55w0rd1234** | + | Password | any password that satisfies complexity requirements | >**Note:** You will need these credentials in the next task of this lab. @@ -144,7 +144,7 @@ In this task, you will deploy code to the staging deployment slot. git push [deployment_user_name] master ``` -1. If prompted to authenticate, type the `[deployment_user_name]` and the corresponding password (**Pa55w0rd1234**). +1. If prompted to authenticate, type the `[deployment_user_name]` and the corresponding password (which you set in the previous task). 1. Close the Cloud Shell pane. From e557e3e2c21b2eab7dc6e9f7e93db31d94dc1e7d Mon Sep 17 00:00:00 2001 From: polichtm Date: Fri, 12 Jun 2020 19:34:16 -0400 Subject: [PATCH 06/25] addressing #90 --- Instructions/Labs/LAB_08-Manage_Virtual_Machines.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md index 7d611bf9..1adc14b5 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -270,6 +270,7 @@ In this task you will scale compute for Azure virtual machines by changing their >**Note**: This section of the template defines the same Azure virtual machine size as the one you specified for the first virtual machine via the Azure portal. + >**Note**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case. 1. On the **Edit template** blade, in the section displaying the content of the template, replace line **49** (` "dataDisks": [ ]` line) with the following code : @@ -296,8 +297,6 @@ 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**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case. - >**Note**: Wait for the template deployment to complete. You can monitor its progress from the **Extensions** blade of the **az104-08-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 978dc5bdd90e5249178bdbb5998421a2318975f1 Mon Sep 17 00:00:00 2001 From: polichtm Date: Fri, 12 Jun 2020 19:35:03 -0400 Subject: [PATCH 07/25] Update LAB_08-Manage_Virtual_Machines.md --- 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 1adc14b5..176d67e4 100644 --- a/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md +++ b/Instructions/Labs/LAB_08-Manage_Virtual_Machines.md @@ -261,6 +261,8 @@ In this task you will scale compute for Azure virtual machines by changing their 1. On the **Custom deployment** blade, click **Edit template**. + >**Note**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case. + 1. On the **Edit template** blade, in the section displaying the content of the template, replace the line **30** ` "vmSize": "Standard_D2s_v3"` with the following line): ```json @@ -270,8 +272,6 @@ In this task you will scale compute for Azure virtual machines by changing their >**Note**: This section of the template defines the same Azure virtual machine size as the one you specified for the first virtual machine via the Azure portal. - >**Note**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case. - 1. On the **Edit template** blade, in the section displaying the content of the template, replace line **49** (` "dataDisks": [ ]` line) with the following code : ```json From 975eae52baaf4525fa6069de84a3c98ca4a3b185 Mon Sep 17 00:00:00 2001 From: chhabrag87 <61169087+chhabrag87@users.noreply.github.com> Date: Tue, 16 Jun 2020 16:39:58 +1000 Subject: [PATCH 08/25] Update LAB_06-Implement_Network_Traffic_Management.md I have validated this exercise and "Allow forwarded traffic from az104-06-vnet3 to az104-06-vnet01" and Allow forwarded traffic from az104-06-vnet2 to az104-06-vnet01 need to be disabled as it is not playing role in defined exercise | **Disabled** | . it won't harm but misleading the service chaining fact. --- .../Labs/LAB_06-Implement_Network_Traffic_Management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md index 0500c8ee..6928f1c4 100644 --- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md +++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md @@ -126,7 +126,7 @@ In this task, you will configure local peering between the virtual networks you | Name of the peering from az104-06-vnet2 to az104-06-vnet01 | **az104-06-vnet2_to_az104-06-vnet01** | | Allow virtual network access from az104-06-vnet01 to az104-06-vnet2 | **Enabled** | | Allow virtual network access from az104-06-vnet2 to az104-06-vnet01 | **Enabled** | - | Allow forwarded traffic from az104-06-vnet2 to az104-06-vnet01 | **Enabled** | + | Allow forwarded traffic from az104-06-vnet2 to az104-06-vnet01 | **Disabled** | | Allow forwarded traffic from az104-06-vnet01 to az104-06-vnet2 | **Enabled** | | Allow gateway transit | **(Uncheck Box)** | @@ -149,7 +149,7 @@ In this task, you will configure local peering between the virtual networks you | Name of the peering from az104-06-vnet3 to az104-06-vnet01 | **az104-06-vnet3_to_az104-06-vnet01** | | Allow virtual network access from az104-06-vnet01 to az104-06-vnet3 | **Enabled** | | Allow virtual network access from az104-06-vnet3 to az104-06-vnet01 | **Enabled** | - | Allow forwarded traffic from az104-06-vnet3 to az104-06-vnet01 | **Enabled** | + | Allow forwarded traffic from az104-06-vnet3 to az104-06-vnet01 | **Disabled** | | Allow forwarded traffic from az104-06-vnet01 to az104-06-vnet3 | **Enabled** | | Allow gateway transit | **(Uncheck Box)** | From d2b97528148626d80c4bc7bb4301fe38cab0a1d5 Mon Sep 17 00:00:00 2001 From: polichtm Date: Tue, 16 Jun 2020 05:15:40 -0400 Subject: [PATCH 09/25] addressing #93 --- 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 032aa28c..e52ea27a 100644 --- a/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md +++ b/Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md @@ -118,7 +118,7 @@ In this task, you will create Azure Active Directory groups with assigned and dy | Group description | **Contoso IT cloud administrators** | | Membership type | **Dynamic User** | - >**Note**: If the **Membership type** drop-down list is grayed out, refresh the browser page. + >**Note**: If the **Membership type** drop-down list is grayed out, wait a few minutes and refresh the browser page. 1. Click **Add dynamic query**. From ac6aaa00330389e320c0a2991096e1273a8c6a29 Mon Sep 17 00:00:00 2001 From: polichtm Date: Tue, 23 Jun 2020 05:31:28 -0400 Subject: [PATCH 10/25] addressing #97 --- Instructions/Labs/LAB_09a-Implement_Web_Apps.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md index 160237bf..09567c04 100644 --- a/Instructions/Labs/LAB_09a-Implement_Web_Apps.md +++ b/Instructions/Labs/LAB_09a-Implement_Web_Apps.md @@ -104,8 +104,10 @@ In this task, you will configure web app deployment settings. | Setting | Value | | --- | ---| - | User name | any unique name | + | User name | any unique name (must not contain `@` character) | | Password | any password that satisfies complexity requirements | + + >**Note:** The password must be at least eight characters long, with two of the following three elements: letters, numbers, and non-alphanumeric characters. >**Note:** You will need these credentials in the next task of this lab. From 0592449e798affb6bb622a52a6b3cef726104201 Mon Sep 17 00:00:00 2001 From: polichtm Date: Tue, 23 Jun 2020 05:44:00 -0400 Subject: [PATCH 11/25] addressing #98 --- 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 aff2f259..0e849720 100644 --- a/Instructions/Labs/LAB_10-Implement_Data_Protection.md +++ b/Instructions/Labs/LAB_10-Implement_Data_Protection.md @@ -120,7 +120,7 @@ In this task, you will implement Azure virtual-machine level backup. 1. On the **Backup Goal** blade, click **Backup**. -1. On the **Backup policy**, review the **DefaultPolicy** settings, and, in the **Choose backup policy** drop-down list, select **Create New**. +1. On the **Backup policy**, review the **DefaultPolicy** settings and select **Create a new policy**. 1. Define a new backup policy with the following settings (leave others with their default values): @@ -132,7 +132,7 @@ In this task, you will implement Azure virtual-machine level backup. | Timezone | the name of your local time zone | | Retain instant recovery snapshot(s) for | **2** Days(s) | -1. Click **OK** to create the policy. This will automatically transition to the **Items to backup** step and open the **Select virtual machines** blade. +1. Click **OK** to create the policy and then, in the **Virtual Machines** section, select **Add**. 1. On the **Select virtual machines** blade, select **az-104-10-vm0**, click **OK**, and, back on the **Backup** blade, click **Enable backup**. From cc8242c6877bd5fc7bb39c58d214177d70b79db2 Mon Sep 17 00:00:00 2001 From: tofusgh <31666473+tofusgh@users.noreply.github.com> Date: Mon, 29 Jun 2020 15:14:06 -0400 Subject: [PATCH 12/25] Added note for management groups The steps should consider if a user has not created management groups as they will not have the "+Add Management Group" button. --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md index cb25599e..bc69261a 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -41,6 +41,9 @@ 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 you will see "Start using Management Groups. Once you select this the Tenant Root Group will be created and one child management group. + 1. Create a management group with the following settings: | Setting | Value | From 43dd206716443eb3b31d198b0018e5d380c6cdd0 Mon Sep 17 00:00:00 2001 From: polichtm Date: Tue, 30 Jun 2020 09:30:09 -0400 Subject: [PATCH 13/25] Update LAB_02a_Manage_Subscriptions_and_RBAC.md --- Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md | 3 +-- 1 file changed, 1 insertion(+), 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 bc69261a..510b14d5 100644 --- a/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md +++ b/Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md @@ -41,8 +41,7 @@ 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 you will see "Start using Management Groups. Once you select this the Tenant Root Group will be created and one child management group. + >**Note**: If you have not previously created Management Groups, select **Start using Management Groups** 1. Create a management group with the following settings: From 78557f2e05968b755c1956e4e412df3af47fb805 Mon Sep 17 00:00:00 2001 From: polichtm Date: Tue, 30 Jun 2020 09:32:37 -0400 Subject: [PATCH 14/25] addressing #100 --- 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 33cb4cb8..d5dde012 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -219,6 +219,8 @@ In this task, you will configure authentication and authorization for Azure Stor 1. Save the change and return to the **Overview** blade of the **az104-07-container** container and verify that you can access to container again. + > **Note**: It might take about 5 minutes for the change to take effect. + #### Task 5: Create and configure an Azure Files shares In this task, you will create and configure Azure Files shares. From 5a94ce248c402eecef20741bcbe2ba2595d21653 Mon Sep 17 00:00:00 2001 From: hopperlap <67262015+hopperlap@users.noreply.github.com> Date: Fri, 3 Jul 2020 15:55:42 +0200 Subject: [PATCH 15/25] Update LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md Change "deploy using custom templates" to "Deploy a custom template" to match with Azure Portal --- .../LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 a9dbe3c3..915cbd6f 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 @@ -48,7 +48,7 @@ In this task, you will create an Azure disk resource by using an Azure Resource #### Task 2: Create an Azure managed disk by using an ARM template -1. In the Azure portal, search for and select **Template deployment (deploy using custom templates)**. +1. In the Azure portal, search for and select **Template deployment (Deploy a custom template)**. 1. On the **Custom deployment** blade, click **Build your own template in the editor**. From 1167de4c722bdb2048b9cad169c121aeae40f19f Mon Sep 17 00:00:00 2001 From: polichtm Date: Fri, 3 Jul 2020 14:53:54 -0400 Subject: [PATCH 16/25] addressing #106 --- .../Labs/LAB_11-Implement_Monitoring.md | 47 +++++++++++-------- 1 file changed, 27 insertions(+), 20 deletions(-) diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index ed554459..c065ae00 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -84,15 +84,14 @@ In this task, you will create and configure an Azure Log Analytics workspace and 1. In the Azure portal, search for and select **Log Analytics workspaces** and, on the **Log Analytics workspaces** blade, click **+ Add**. -1. On the **Log Analytics workspace** blade, ensure that the **Create New** option is selected, specify the following settings, and click **OK**: +1. On the **Basics** tab of the **Create Log Analytics workspace** blade, the following settings, click **Review + Create** and then click **Create**: | Settings | Value | | --- | --- | - | Log Analytics Workspace | any unique name | | Subscription | the name of the Azure subscription you are using in this lab | | Resource group | the name of a new resource group **az104-11-rg1** | - | Location | the name of the Azure region into which you deployed the virtual machine in the previous task | - | Pricing tier | **Pay-as-you-go** | + | Log Analytics Workspace | any unique name | + | Region | the name of the Azure region into which you deployed the virtual machine in the previous task | >**Note**: Make sure that you specify the same region into which you deployed virtual machines in the previous task. @@ -136,15 +135,15 @@ In this task, you will review default monitoring settings of Azure virtual machi 1. On the **az104-11-vm0** blade, in the **Monitoring** section, click **Metrics**. -1. On the **az104-11-vm0 - Metrics** blade, on the default chart, note that the only available **METRICS NAMESPACE** is **Virtual Machine Host**. +1. On the **az104-11-vm0 | Metrics** blade, on the default chart, note that the only available **Metrics Namespace** is **Virtual Machine Host**. >**Note**: This is expected, since no guest-level diagnostic settings have been configured yet. -1. In the **METRICS** drop-down list, review the list of available metrics. +1. In the **Metric** drop-down list, review the list of available metrics. >**Note**: The list includes a range of CPU, disk, and network-related metrics that can be collected from the virtual machine host, without having access into guest-level metrics. -1. In the **METRICS** drop-down list, select **Percentage CPU**, in the **AGGREGATION** drop-down list, select **Avg**, and review the resulting chart. +1. In the **Metric** drop-down list, select **Percentage CPU**, in the **Aggregation** drop-down list, select **Avg**, and review the resulting chart. #### Task 5: Configure Azure virtual machine diagnostic settings @@ -152,15 +151,15 @@ In this task, you will configure Azure virtual machine diagnostic settings. 1. On the **az104-11-vm0** blade, in the **Monitoring** section, click **Diagnostic settings**. -1. On the **Overview** tab of the **az104-11-vm0 - Diagnostic settings** blade, click **Enable guest-level monitoring**. +1. On the **Overview** tab of the **az104-11-vm0 | Diagnostic settings** blade, click **Enable guest-level monitoring**. >**Note**: Wait for the operation to take effect. This might take about 3 minutes. -1. Switch to the **Performance counters** tab of the **az104-11-vm0 - Diagnostic settings** blade and review the available counters. +1. Switch to the **Performance counters** tab of the **az104-11-vm0 | Diagnostic settings** blade and review the available counters. >**Note**: By default, CPU, memory, disk, and network counters are enabled. You can switch to the **Custom** view for more detailed listing. -1. Switch to the **Logs** tab of the **az104-11-vm0 - Diagnostic settings** blade and review the available event log collection options. +1. Switch to the **Logs** tab of the **az104-11-vm0 | Diagnostic settings** blade and review the available event log collection options. >**Note**: By default, log collection includes critical, error, and warning entries from the Application Log and System log, as well as Audit failure entries from the Security log. Here as well you can switch to the **Custom** view for more detailed configuration settings. @@ -170,23 +169,21 @@ In this task, you will configure Azure virtual machine diagnostic settings. >**Note**: Do not wait for the operation to complete but instead proceed to the next step. The operation might take about 5 minutes. -1. On the **az104-11-vm0 - Logs** blade, in the **Monitoring** section, click **Metrics**. +1. On the **az104-11-vm0 | Logs** blade, in the **Monitoring** section, click **Metrics**. -1. On the **az104-11-vm0 - Metrics** blade, on the default chart, note that at this point, the **METRICS NAMESPACE** drop-down list, in addition to the **Virtual Machine Host** entry includes also the **Guest (classic)** entry. +1. On the **az104-11-vm0 | Metrics** blade, on the default chart, note that at this point, the **Metrics Namespace** drop-down list, in addition to the **Virtual Machine Host** entry includes also the **Guest (classic)** entry. >**Note**: This is expected, since you enabled guest-level diagnostic settings. -1. In the **METRICS** drop-down list, review the list of available metrics. +1. In the **Metric** drop-down list, review the list of available metrics. >**Note**: The list includes additional guest-level metrics not available when relying on the host-level monitoring only. -1. In the **METRICS** drop-down list, select **Memory\Available Bytes**, in the **AGGREGATION** drop-down list, select **Avg**, and review the resulting chart. +1. In the **Metric** drop-down list, select **Memory\Available Bytes**, in the **Aggregation** drop-down list, select **Avg**, and review the resulting chart. #### Task 6: Review Azure Monitor functionality -1. In the Azure portal, search for and select **Monitor** and, on the **Monitor - Overview** blade, click **Metrics**. - -1. In the chart pane on the right side of the blade, in the **SCOPE** drop-down list, click **+ Select a scope**. +1. In the Azure portal, search for and select **Monitor** and, on the **Monitor | Overview** blade, click **Metrics**. 1. On the **Select a scope** blade, on the **Browse** tab, navigate to the **az104-11-rg0** resource group, expand it, select the **az104-11-vm0** virtual machine within that resource group, and click **Apply**. @@ -194,11 +191,11 @@ In this task, you will configure Azure virtual machine diagnostic settings. 1. In the **Metric** drop-down list, select **Percentage CPU**, in the **Aggregation** drop-down list, select **Avg**, and review the resulting chart. -1. On the **Monitor - Metrics** blade, click **New alert rule**. +1. On the **Monitor | Metrics** blade, click **New alert rule**. >**Note**: Creating an alert rule from Metrics is not supported for metrics from the Guest (classic) metric namespace. This can be accomplished by using Azure Resource Manager templates, as described in the document [Send Guest OS metrics to the Azure Monitor metric store using a Resource Manager template for a Windows virtual machine](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/collect-custom-metrics-guestos-resource-manager-vm) -1. On the **Create alert rule** blade, in the **CONDITION** section, click the existing condition. +1. On the **Create alert rule** blade, in the **Condition** section, click the existing condition. 1. On the **Configure signal logic** blade, in the list of signals, in the **Alert logic** section, specify the following settings (leave others with their default values) and click **Done**: @@ -284,7 +281,17 @@ In this task, you will configure Azure virtual machine diagnostic settings. 1. On the **Select a scope** blade, navigate to the **az104-11-rg0** resource group, expand it, select **a104-11-vm0**, and click **Apply**. -1. Click **Example queries** in the toolbar, in the **Get started with sample queries** pane, review each tab, locate **Virtual machine available memory**, and click **Run**. +1. In the query window, paste the following query and click **Run**: + + ``` + // Virtual Machine available memory + // Chart the VM's available memory over the last hour. + InsightsMetrics + | where TimeGenerated > ago(1h) + | where Name == "AvailableMB" + | project TimeGenerated, Name, Val + | render timechart + ``` 1. Click **Example queries** in the toolbar, in the **Get started with sample queries** pane, review each tab, locate **Track VM availability**, and click **Run**. From 79cc20ab9d359a9c4cca7379ba7583f91bbd6ac1 Mon Sep 17 00:00:00 2001 From: polichtm Date: Sat, 4 Jul 2020 11:00:46 -0400 Subject: [PATCH 17/25] addressing #104 --- Allfiles/Labs/03/az104-03b-md-template.json | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Allfiles/Labs/03/az104-03b-md-template.json b/Allfiles/Labs/03/az104-03b-md-template.json index 4c9a6e2e..dceb3e86 100644 --- a/Allfiles/Labs/03/az104-03b-md-template.json +++ b/Allfiles/Labs/03/az104-03b-md-template.json @@ -29,6 +29,9 @@ "hyperVGeneration": { "defaultValue": "V1", "type": "String" + }, + "diskEncryptionSetType": { + "type": "String" } }, "resources": [ @@ -50,4 +53,4 @@ } } ] -} \ No newline at end of file +} From 284f1b81a87ded93d92cb84a1c4d57bc2f618cd8 Mon Sep 17 00:00:00 2001 From: hopperlap <67262015+hopperlap@users.noreply.github.com> Date: Sat, 4 Jul 2020 18:10:21 +0200 Subject: [PATCH 18/25] Update LAB_07-Manage_Azure_Storage.md --- Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index d5dde012..ed6c69b1 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -168,7 +168,7 @@ In this task, you will configure authentication and authorization for Azure Stor 1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step. -1. You should be presented with an XML-formatted message stating **ResourceNotFound**. +1. You should be presented with an XML-formatted message stating **ResourceNotFound** or **PublicAccessNotPermitted**. > **Note**: This is expected, since the container you created has the public access level set to **Private (no anonymous access)**. @@ -193,7 +193,7 @@ In this task, you will configure authentication and authorization for Azure Stor 1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step. - > **Note**: If you are using Microsoft Edge or Internet Explorer, you should be presented with the **The MIT License (MIT)** page. If you are using Chrome or Firefox, you should be able to view the content of the file by downloading it and opening it with Notepad. + > **Note**: If you are using Microsoft Edge or Internet Explorer, you should be presented with the **The MIT License (MIT)** page. If you are using Chrome, Microsoft Edge (Chromium) or Firefox, you should be able to view the content of the file by downloading it and opening it with Notepad. > **Note**: This is expected, since now your access is authorized based on the newly generated the SAS token. @@ -207,7 +207,7 @@ In this task, you will configure authentication and authorization for Azure Stor 1. On the **az104-07-container** blade, click **Access Control (IAM)**. -1. In the **Add a role assignment** section, click **Add**. +1. In the **Add** section, click **Add a role assignment**. 1. On the **Add role assignment** blade, specify the following settings: From 781de89fedbfb93f4ae863dff27f6560fc8e97e4 Mon Sep 17 00:00:00 2001 From: hopperlap <67262015+hopperlap@users.noreply.github.com> Date: Sun, 5 Jul 2020 20:29:50 +0200 Subject: [PATCH 19/25] Update LAB_09c-Implement_Azure_Kubernetes_Service.md --- .../Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md index 041b9152..16680bf0 100644 --- a/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md +++ b/Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md @@ -64,10 +64,10 @@ In this task, you will deploy an Azure Kubernetes Services cluster by using the | Setting | Value | | ---- | ---- | - | DNS name prefix | any valid, globally unique DNS host name | - | HTTP application routing | **No** | - | Load balancer | **Standard** | | Network configuration | **Advanced** | + | DNS name prefix | any valid, globally unique DNS host name | + | Load balancer | **Standard** | + | HTTP application routing | **No** | 1. Click **Next: Integration >**, on the **Integration** tab of the **Create Kubernetes cluster** blade, set **Container monitoring** to **Disabled**, click **Review + create** and then click **Create**. From 55fe87e40115284a2330fac45c03f9f583d5eb7e Mon Sep 17 00:00:00 2001 From: shanecribbs <46715670+shanecribbs@users.noreply.github.com> Date: Mon, 13 Jul 2020 10:46:43 -0400 Subject: [PATCH 20/25] Set theme jekyll-theme-slate --- _config.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_config.yml b/_config.yml index 91272fc7..c2acba46 100644 --- a/_config.yml +++ b/_config.yml @@ -15,3 +15,5 @@ markdown: kramdown kramdown: syntax_highlighter_opts: disable : true + +theme: jekyll-theme-slate \ No newline at end of file From 8939497d5f113cab5c2959d7cfac97a164952a1d Mon Sep 17 00:00:00 2001 From: shanecribbs <46715670+shanecribbs@users.noreply.github.com> Date: Mon, 13 Jul 2020 13:08:26 -0400 Subject: [PATCH 21/25] Added link to download project files Help learners download the required lab files without having to navigate out to a separate page. --- index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/index.md b/index.md index 77eb2ebe..fea40442 100644 --- a/index.md +++ b/index.md @@ -6,6 +6,8 @@ layout: home # Content Directory +[Required labs files can be DOWNLOADED HERE](https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator/archive/master.zip) + Hyperlinks to each of the lab exercises and demos are listed below. ## Labs From b189ffba1e9af617bef9cedad38434348066d72c Mon Sep 17 00:00:00 2001 From: shanecribbs <46715670+shanecribbs@users.noreply.github.com> Date: Mon, 13 Jul 2020 13:11:50 -0400 Subject: [PATCH 22/25] Update index.md --- index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.md b/index.md index fea40442..f2d3163d 100644 --- a/index.md +++ b/index.md @@ -6,7 +6,7 @@ layout: home # Content Directory -[Required labs files can be DOWNLOADED HERE](https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator/archive/master.zip) +Required labs files can be [DOWNLOADED HERE](https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator/archive/master.zip) Hyperlinks to each of the lab exercises and demos are listed below. From b09c535d5ab93450a994c63848cf302c4d04f43e Mon Sep 17 00:00:00 2001 From: shanecribbs <46715670+shanecribbs@users.noreply.github.com> Date: Mon, 13 Jul 2020 13:12:29 -0400 Subject: [PATCH 23/25] Update index.md --- index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.md b/index.md index f2d3163d..443332f7 100644 --- a/index.md +++ b/index.md @@ -8,7 +8,7 @@ layout: home Required labs files can be [DOWNLOADED HERE](https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator/archive/master.zip) -Hyperlinks to each of the lab exercises and demos are listed below. +Hyperlinks to each of the lab exercises are listed below. ## Labs From 54d700affbb6404870132b5cf656960e806412f8 Mon Sep 17 00:00:00 2001 From: tofusgh <31666473+tofusgh@users.noreply.github.com> Date: Tue, 14 Jul 2020 10:39:49 -0400 Subject: [PATCH 24/25] Bold new resource group in all labs Students continuously miss that the need for a new resource group in these labs based on the way it is written. I also missed this during my first few walkthroughs. If we could simple bold new resource group or make the users more aware in the steps that a new resource group is required --- 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 698f42fe..b344fb3a 100644 --- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md +++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md @@ -42,7 +42,7 @@ In this task, you will create a virtual network with multiple subnets by using t | Setting | Value | | --- | --- | | Subscription | the name of the Azure subscription you will be using in this lab | - | Resource Group | the name of a new resource group **az104-04-rg1** | + | Resource Group | the name of a **new** resource group **az104-04-rg1** | | Name | **az104-04-vnet1** | | Region | the name of any Azure region available in the subscription you will use in this lab | | IPv4 address space | **10.40.0.0/20** | From a5870c83487fc35093b35c439ec549c5994c081c Mon Sep 17 00:00:00 2001 From: tofusgh <31666473+tofusgh@users.noreply.github.com> Date: Wed, 15 Jul 2020 15:38:34 -0400 Subject: [PATCH 25/25] highlight new resource group needed If we could bold the step above to display the need for a new resource group this would be more clear a lot of users are missing the need to create a new resource group --- 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 ed6c69b1..a1bcf6c3 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 create and configure an Azure Storage account. | Setting | Value | | --- | --- | | Subscription | the name of the Azure subscription you are using in this lab | - | Resource group | the name of a new resource group **az104-07-rg1** | + | Resource group | the name of a **new** resource group **az104-07-rg1** | | 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** |