Merge branch 'master' into MOC-Labs-Review-patch-34

This commit is contained in:
staleycyn 2022-02-04 08:33:16 -08:00 committed by GitHub
commit b91856acf7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
10 changed files with 25 additions and 29 deletions

View File

@ -141,7 +141,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 and display its **details**.
1. Click **Access control (IAM)**, click **+ Add** followed by **Role assignment**, and assign the **Support Request Contributor (Custom)** role to the newly created user account.
1. Click **Access control (IAM)**, click **+ Add** followed by **Add role assignment**, and assign the **Support Request Contributor (Custom)** role to the newly created user account.
1. Open an **InPrivate** browser window and sign in to the [Azure portal](https://portal.azure.com) using the newly created user account. When prompted to update the password, change the password for the user.

View File

@ -61,7 +61,7 @@ In this task, you will create and assign a tag to an Azure resource group via th
**Note**: note what resource group the storage account is in, you'll need it later in the lab.
1. On the resource group blade, click **Tags**.
1. On the resource group blade, click **Click here to add tags**.
1. Create a tag with the following settings and Apply your change:
@ -212,7 +212,7 @@ In this task, we will use a different policy definition to remediate any non-com
1. In the list of storage accounts, select the resource group corresponding to the storage account you created in the last task of this lab. Select **Tags** and click **Delete** (Trash can to the right) to the **Role:Infra** tag and press **Apply**.
1. Click **Delete**, when prompted for the confirmation, in the **Delete storage account** blade, type the name of the storage account to confirm and click **Delete**.
1. Click **Overview** and click **Delete** on the top of the storage account blade. When prompted for the confirmation, in the **Delete storage account** blade, type the name of the storage account to confirm and click **Delete**.
#### Review

View File

@ -35,7 +35,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, + Create, or + New**, and specify the following settings:
1. In the Azure portal, search for and select **Disks**, click **+ Create** and specify the following settings:
|Setting|Value|
|---|---|
@ -74,7 +74,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, + Create, or + New**, and specify the following settings:
1. In the Azure portal, search for and select **Disks**, click **+ Create** and specify the following settings:
|Setting|Value|
|---|---|

View File

@ -62,8 +62,6 @@ In this task, you will create an Azure disk resource by using an Azure Resource
1. In the Azure portal, search for and select **Deploy a custom template**.
1. Click **Template deployment (deploy using custom templates)** found under the **Marketplace** group.
1. On the **Custom deployment** blade, click **Build your own template in the editor**.
1. On the **Edit template** blade, click **Load file** and upload the **template.json** file you downloaded in the previous task.

View File

@ -178,7 +178,7 @@ In this task, you will test transitivity of virtual network peering by using Net
1. In the Azure portal, search for and select **Network Watcher**.
1. On the **Network Watcher** blade, expand the listing of Azure regions and verify that the service is enabled in the Azure into which you deployed resources in the first task of this lab.
1. On the **Network Watcher** blade, expand the listing of Azure regions and verify the service is enabled in region you are using.
1. On the **Network Watcher** blade, navigate to the **Connection troubleshoot**.
@ -412,8 +412,6 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| Name | any unique name |
| Public IP address | **Create new** |
| Public IP address name | **az104-06-pip4** |
| Availability zone | **No Zone** |
| Add a public IPv6 address | **No** |
1. Click **Review and Create**. Let validation occur, and hit **Create** to submit your deployment.

View File

@ -91,7 +91,7 @@ In this task, you will create and configure an Azure Storage account.
| 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** |
| 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 |
| Region | the name of an Azure region where you can create an Azure Storage account |
| Performance | **Standard** |
| Redundancy | **Geo-redundant storage (GRS)** |
@ -203,7 +203,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** section, click **Add a role assignment**.
1. On the **Check access** tab, click **Add role assignment**.
1. On the **Add role assignment** blade, specify the following settings:
@ -213,7 +213,7 @@ In this task, you will configure authentication and authorization for Azure Stor
| Assign access to | **User, group, or service principal** |
| Members | the name of your user account |
1. Click 'Review+Assign' and then 'Review+ assign', and return to the **Overview** blade of the **az104-07-container** container and verify that you can change the Authentication method to (Switch to Azure AD User Account).
1. Click **Review + Assign** and then **Review + assign**, and return to the **Overview** blade of the **az104-07-container** container and verify that you can change the Authentication method to (Switch to Azure AD User Account).
> **Note**: It might take about 5 minutes for the change to take effect.
@ -277,7 +277,7 @@ In this task, you will configure network access for Azure Storage.
> **Note**: This is expected, since you are connecting from your client IP address.
1. Close the InPrivate mode browser window, return to the browser window showing the **licenses/LICENSE** blade of the Azure Storage container.
1. Close the InPrivate mode browser window, return to the browser window showing the **Networking** blade of the Azure Storage account.
1. In the Azure portal, open the **Azure Cloud Shell** by clicking on the icon in the top right of the Azure Portal.

View File

@ -283,7 +283,7 @@ In this task you will scale compute for Azure virtual machines by changing their
>**Note**: This section of the template defines the same Azure virtual machine size as the one you specified for the first virtual machine via the Azure portal.
1. On the **Edit template** blade, in the section displaying the content of the template, replace line **50** (`"dataDisks": [ ]` line) with the following code :
1. On the **Edit template** blade, in the section displaying the content of the template, replace line **51** (`"dataDisks": [ ]` line) with the following code :
```json
"dataDisks": [

View File

@ -40,7 +40,7 @@ In this task, you will create an Azure web app.
1. In the Azure portal, search for and select **App services**, and, on the **App Services** blade, click **+ Create**.
1. On the **Basics** tab of the **Web App** blade, specify the following settings (leave others with their default values):
1. On the **Basics** tab of the **Create Web App** blade, specify the following settings (leave others with their default values):
| Setting | Value |
| --- | ---|

View File

@ -102,7 +102,7 @@ In this task, you will create a recovery services vault.
1. Back on the **az104-10-rsv1 - Properties** blade, click the **Update** link under **Security Settings** label.
1. On the **Security Settings** blade, note that **Soft Delete (For Azure Virtual Machines)** is **Enabled**.
1. On the **Security Settings** blade, note that **Soft Delete (For workload running in Azure)** is **Enabled**.
1. Close the **Security Settings** blade and, back on the **az104-10-rsv1** Recovery Services vault blade, click **Overview**.
@ -143,7 +143,7 @@ In this task, you will implement Azure virtual-machine level backup.
1. Navigate back to the **az104-10-rsv1** Recovery Services vault blade, in the **Protected items** section, click **Backup items**, and then click the **Azure virtual machines** entry.
1. On the **Backup Items (Azure Virtual Machine)** blade of **az104-10-vm0**, review the values of the **Backup Pre-Check** and **Last Backup Status** entries.
1. On the **Backup Items (Azure Virtual Machine)** blade click **az104-10-vm0**, and review the values of the **Backup Pre-Check** and **Last Backup Status** entries.
1. On the **az104-10-vm0** Backup Item blade, click **Backup now**, accept the default value in the **Retain Backup Till** drop-down list, and click **OK**.

View File

@ -104,10 +104,10 @@ In this task, you will create and configure an Azure Log Analytics workspace and
| Settings | Value |
| --- | --- |
| Name | any unique name |
| Automation account name | any unique name |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | **az104-11-rg1** |
| Location | the name of the Azure region determined based on [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings) |
| Region | the name of the Azure region determined based on [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings) |
>**Note**: Make sure that you specify the Azure region based on the [Workspace mappings documentation](https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings)
@ -210,7 +210,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
| Aggregation granularity (Period) | **1 minute** |
| Frequency of evaluation | **Every 1 Minute** |
1. On the **Create alert rule** blade, in the **Action group** section, click **Add action groups** and then click the **+ Create action group** button.
1. Click **Next: Actions >**, on the **Create an alert rule** blade, in the **Action group** section, click the **+ Create action group** button.
1. On the **Basics** tab of the **Create action group** blade, specify the following settings (leave others with their default values) and select **Next: Notifications >**:
@ -221,24 +221,24 @@ In this task, you will configure Azure virtual machine diagnostic settings.
| Action group name | **az104-11-ag1** |
| Display name | **az104-11-ag1** |
1. On the **Notifications** tab of the **Create action group** blade, in the **Notification type** drop-down list, select **Email/SMS/Push/Voice**. In the **Name** text box, type **admin email**. Click the **Edit details** (pencil) icon.
1. On the **Notifications** tab of the **Create an action group** blade, in the **Notification type** drop-down list, select **Email/SMS message/Push/Voice**. In the **Name** text box, type **admin email**. Click the **Edit details** (pencil) icon.
1. On the **Email/SMS/Push/Voice** blade, select the **Email** checkbox, type your email address in the **Email** textbox, leave others with their default values, click **OK**, back on the **Notifications** tab of the **Create action group** blade, select **Next: Actions >**.
1. On the **Email/SMS message/Push/Voice** blade, select the **Email** checkbox, type your email address in the **Email** textbox, leave others with their default values, click **OK**, back on the **Notifications** tab of the **Create an action group** blade, select **Next: Actions >**.
1. On the **Actions** tab of the **Create action group** blade, review items available in the **Action type** drop-down list without making any changes and select **Review + create**.
1. On the **Review + create** tab of the **Create action group** blade, select **Create**.
1. Back on the **Create alert rule** blade, in the **Alert rule details** section, specify the following settings (leave others with their default values):
1. Back on the **Create alert rule** blade, click **Next: Details >**, and in the **Alert rule details** section, specify the following settings (leave others with their default values):
| Settings | Value |
| --- | --- |
| Alert rule name | **CPU Percentage above the test threshold** |
| Description | **CPU Percentage above the test threshold** |
| Alert rule description | **CPU Percentage above the test threshold** |
| Severity | **Sev 3** |
| Enable rule upon creation | **Yes** |
| Enable upon creation | **Yes** |
1. Click **Create alert rule**.
1. Click **Review + create** and on the **Review + create** tab click **Create**.
>**Note**: It can take up to 10 minutes for a metric alert rule to become active.
@ -278,7 +278,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
>**Note**: You might need to click **Get Started** if this is the first time you access Log Analytics.
1. If necessary, click **Select scope**, on the **Select a scope** blade, select the **Recent** tab, select **az104-11-vm0**, and click **Apply**.
1. If necessary, click **Select scope**, on the **Select a scope** blade, select the **Recent** tab, select **az104-11-rg0**, and click **Apply**.
1. In the query window, paste the following query, click **Run**, and review the resulting chart:
@ -292,7 +292,7 @@ In this task, you will configure Azure virtual machine diagnostic settings.
| render timechart
```
1. Click **Queries** in the toolbar, on the **Queries** pane, locate the **Track VM availability** tile, click the **Run** command button in the tile, and review the results.
1. Click **Queries** in the toolbar, on the **Queries** pane, locate the **Track VM availability** tile and double-click it to fill the query window, click the **Run** command button in the tile, and review the results.
1. On the **New Query 1** tab, select the **Tables** header, and review the list of tables in the **Virtual machines** section.