From 1ebe167f905c677efd86326aecef6d2f49b8e7df Mon Sep 17 00:00:00 2001 From: staleycyn <45440075+staleycyn@users.noreply.github.com> Date: Sun, 3 Dec 2023 08:49:44 -0800 Subject: [PATCH] Update LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md --- ...ure_Resources_by_Using_the_Azure_Portal.md | 52 +++++++++++-------- 1 file changed, 29 insertions(+), 23 deletions(-) diff --git a/New Instructions/Lab/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md b/New Instructions/Lab/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md index 021734c4..9e676efa 100644 --- a/New Instructions/Lab/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md +++ b/New Instructions/Lab/LAB_03a-Manage_Azure_Resources_by_Using_the_Azure_Portal.md @@ -33,7 +33,7 @@ In this lab, we will: ## Task 1: Create resource groups and deploy resources to resource groups -In this task, you will use the Azure portal to create resource groups and create a disk in the resource group. Resource groups provide logical seperation of resources, and allow for RBAC, locks, billing reporting, and other governance benefits. +In this task, you will use the Azure portal to create a managed disk. In the next task, we will move this disk to another resource group. 1. Sign in to the [**Azure portal**](http://portal.azure.com). @@ -42,15 +42,13 @@ In this task, you will use the Azure portal to create resource groups and create |Setting|Value| |---|---| |Subscription| the name of your Azure subscription | - |Resource Group| click **create new** resource group and name it `az104-rg1`| + |Resource Group| select **create new** resource group - `az104-rg3a`| |Disk name| `az104-disk1` | |Region| **(US) East US** | |Availability zone| **No infrastructure redundancy required** | |Source type| **None** | - >**Note**: When creating a resource, you have the option of creating a new resource group or using an existing one. If **az104-rg1** already exists, select it. - -1. Change the disk type and size to **Standard HDD** and **32 GiB**, respectively. +1. Select **Change size** and choose **Standard HDD** and **32 GiB**. Select **OK** when complete. ![Screenshot of the create a disk page.](../media/az104-lab03a-createdisk1.png) @@ -64,15 +62,19 @@ In this task, we will move the disk resource you created in the previous task to 1. Search for and select **Resource groups**. -1. On the **Resource groups** blade, click the entry representing the **az104-rg1** resource group you created in the previous task. +1. On the **Resource groups** blade, click the entry representing the **az104-rg3a** resource group you created in the previous task. -1. From the **Overview** blade of the resource group, in the list of resource group resources, select the entry representing the newly created disk, click **Move** in the toolbar, and, in the drop-down list, select **Move to another resource group**. +1. From the **Overview** blade of the resource group, in the list of resource group resources, select the entry representing the newly created disk. - >**Note**: This method allows you to move multiple resources at the same time. If you do not see the Move menu option, you might need to first select the elipses. +1. Use the tool bar ellipses (...) to select **Move**, and then in the drop-down list, select **Move to another resource group**. Notice your choices to move to another subscription or region. ![Screenshot to move the resource.](../media/az104-lab03a-moverg.png) -1. Below the **Resource group** text box, click **Create new** then type `az104-rg2` in the text box. On the Review tab, select the checkbox **I understand that tools and scripts associated with moved resources will not work until I update them to use new resource IDs**, and click **Move**. +1. Below the **Resource group** text box, click **Create new** then type `az104-rg3move` in the text box. Select **OK** to create the new resource group. + +1. On the **Resources to move** tab, verify **Succeeded** is the validation status. It may take a minute for the validation to finish. In the meantime, review the [list of supported move operations](https://learn.microsoft.com/azure/azure-resource-manager/management/move-support-resources). Select **Next** to proceed. + +1. On the Review tab, select the checkbox **I understand that tools and scripts associated with moved resources will not work until I update them to use new resource IDs**, and click **Move**. >**Note**: Do not wait for the move to complete but instead proceed to the next task. The move might take about 10 minutes. You can determine that the operation was completed by monitoring activity log entries of the source or target resource group. Revisit this step once you complete the next task. @@ -80,6 +82,8 @@ 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. A resource lock can either prevent any types of changes to a resource, such as the size of a disk. Or, a resource lock can prevent accidental deletions. These two lock types are *Delete* locks and *Read-Only* locks. +### Create a new managed disk. + 1. In the Azure portal, search for and select **Disks**, click **+ Create** and specify the following settings: |Setting|Value| @@ -91,42 +95,44 @@ In this task, you will apply a resource lock to an Azure resource group containi |Availability zone| **No infrastructure redundancy required** | |Source type| **None** | -1. Set the disk type and size to **Standard HDD** and **32 GiB**, respectively. +1. Select **Change size** and choose **Standard HDD** and **32 GiB**. Select **OK** when complete. ![Screenshot of setting the disk type and size.](,./media/az104-lab03a-createdisk2.png) 1. Click **Review + Create** and then click **Create**. -1. Click **Go to resource**. +1. Wait for the disk to deploy, then select **Go to resource**. -1. On the Overview page of the disk, click the name of the resource group, **az104-rg3**. +### Lock the resource group so resources cannot be delected. -1. On the **az104-rg3** resource group blade, click **Locks** then **+ Add** and specify the following settings: +1. From the **Overview** blade, select your resource group. + +1. In the **Settings** section, select **Locks**, and then select **+ Add**. Specify the following settings and then select **OK**. |Setting|Value| |---|---| - |Lock name| `az104-lock` | + |Lock name| `az104-rglock` | |Lock type| **Delete** | - -1. Click **OK** ![Screenshot of resource locks screen.](../media/az104-lab03a-deletelock.png) -1. On the **az104-rg3** resource group blade, click **Overview**, in the list of resource group resources, select the entry representing the disk you created earlier in this task, and click **Delete** in the toolbar. +1. From the resource group **Overview** blade, select the managed disk, and then select **Delete** in the toolbar. -1. When prompted **Do you want to delete all the selected resources?**, in the **Confirm delete** text box, type `delete` and click **Delete**. +1. On the **Delete resources** page, in the **Confirm delete** text box, type `delete` and click **Delete**. Confirm your **Delete confirmation**. -1. You should see an error message, notifying about the failed delete operation. +1. You should see an error message, notifying you that the delete operation failed. - >**Note**: As the error message states, this is expected due to the delete lock applied on the resource group level. + >**Note**: This is expected. The message states there is a lock on the resource group. ![Screenshot of error message.](../media/az104-lab03a-deleteerror.png) -1. Navigate back to the list of resources of the **az104-rg3** resource group and click the entry representing the **az104-disk2** resource. +1. Select the **az104-disk2** resource. -1. On the **az104-disk2** blade, in the **Settings** section, click **Size + performance**, set the disk type and size to **Premium SSD** and **64 GiB**, respectively, and click **Save** to apply the change. Verify that the change was successful. +1. In the **Settings** section, click **Size + performance**. Change to **Premium SSD** and **64 GiB**. Click **Save** to apply the change. - >**Note**: This is expected, since the resource group-level lock applies to delete operations only. +1. From the **Overview** blade, confirm you were able to change the disk size. + + >**Note**: This is expected. The resource group-level lock applies to delete operations only. ![Screenshot of successful message](./media/az104-lab03a-premium.png)