updates

Author: v-albemi

articles/devtest-labs/encrypt-disks-customer-managed-keys.md

@@ -12,26 +12,26 @@ ms.custom: subject-rbac-steps, UpdateFrequency2
 
 # Encrypt disks with customer-managed keys in Azure DevTest Labs
 
-Server-side encryption (SSE) protects your data and helps you meet your organizational security and compliance commitments. SSE automatically encrypts data stored on managed disks in Azure (OS and data disks) at rest by default when it's persisted to the cloud. For more information about disk encryption on Azure, see [disk encryption](/azure/virtual-machines/disk-encryption). 
+Server-side encryption (SSE) protects your data and helps you meet your organizational security and compliance commitments. SSE automatically encrypts data stored on managed disks in Azure (OS and data disks) at rest by default when it's persisted to the cloud. For more information about disk encryption on Azure, see [disk encryption](/azure/virtual-machines/disk-encryption).
 
 In Azure DevTest Labs, all OS disks and data disks created in a lab are encrypted via platform-managed keys. However, as a lab owner, you can choose to manage the encryption of lab virtual machine disks by using your own keys. If you choose to manage encryption by using your own keys, you can specify a *customer-managed key* to use for encrypting data in lab disks. To learn more about SSE with customer-managed keys, and other managed disk encryption types, see [Customer-managed keys](/azure/virtual-machines/disk-encryption#customer-managed-keys). Also, see [restrictions with using customer-managed keys](/azure/virtual-machines/disks-enable-customer-managed-keys-portal#restrictions).
 
 > [!NOTE]
-> The disk encryption setting applies to newly created disks in the lab. If you change the disk encryption set at some point, older disks in the lab will continue to be encrypted with the previous disk encryption set. 
+> The disk encryption setting applies to newly created disks in the lab. If you change the disk encryption set at some point, older disks in the lab continue to be encrypted with the previous disk encryption set.
 
 The following section shows how a lab owner can set up encryption with a customer-managed key.
 
 ## Prerequisites
 
-- If you don't have a disk encryption set, [complete the steps in this article to set up a key vault and a disk encryption set](/azure/virtual-machines/disks-enable-customer-managed-keys-portal). Note the following requirements for the disk encryption set: 
+- If you don't have a disk encryption set, [complete the steps in this article to set up a key vault and a disk encryption set](/azure/virtual-machines/disks-enable-customer-managed-keys-portal). Note the following requirements for the disk encryption set:
 
-    - The disk encryption set needs to be in same region and subscription as your lab. 
-    - The lab owner needs to have at least reader-level access to the disk encryption set that will be used to encrypt lab disks. 
+    - The disk encryption set needs to be in same region and subscription as your lab.
+    - The lab owner needs to have at least reader-level access to the disk encryption set that will be used to encrypt lab disks.
 
-- For labs created before 8/1/2020, the lab owner needs to ensure that lab system-assigned identity is enabled. To do so, the lab owner can go to the lab, select **Configuration and policies**, select **Identity (Preview)** in the left menu, change the system-assigned identity **Status** to **On**, and then select **Save**. For labs created after 8/1/2020, the system-assigned identity is enabled by default. 
+- For labs created before 8/1/2020, the lab owner needs to ensure that lab system-assigned identity is enabled. To do so, the lab owner can go to the lab, select **Configuration and policies**, select **Identity (Preview)** in the left menu, change the system-assigned identity **Status** to **On**, and then select **Save**. For labs created after 8/1/2020, the system-assigned identity is enabled by default.
 
     > [!div class="mx-imgBorder"]
-    > :::image type="content" source="./media/encrypt-disks-customer-managed-keys/managed-keys.png" alt-text="Screenshot that shows the steps for enabling system-assigned identity." lightbox="./media/encrypt-disks-customer-managed-keys/managed-keys.png":::
+    > :::image type="content" source="./media/encrypt-disks-customer-managed-keys/managed-keys.png"alt-text="Screenshot that shows the steps for enabling system-assigned identity." lightbox="./media/encrypt-disks-customer-managed-keys/managed-keys.png":::
 
 - For the lab to handle encryption for all lab disks, the lab owner needs to explicitly grant the lab's system-assigned identity reader role on the disk encryption set and the virtual machine contributor role on the underlying Azure subscription. The lab owner can do that by completing the following steps:
 
@@ -45,24 +45,24 @@ The following section shows how a lab owner can set up encryption with a custome
 
     1. Assign the Virtual Machine Contributor role to the lab (system-assigned identity for the lab).
 
-## Encrypt lab OS disks with a customer-managed key 
+## Encrypt lab OS disks with a customer-managed key
 
-1. On the overview page for your lab in the Azure portal, select **Configuration and policies** in the left pane. 
+1. On the overview page for your lab in the Azure portal, select **Configuration and policies** in the left pane.
 1. In the left pane of the **Configuration and policies** page, select **Disks (Preview)** in the **Encryption** section. By default, **Encryption type** is set to **Encryption at-rest with a platform managed key**.
 
     :::image type="content" source="./media/encrypt-disks-customer-managed-keys/disks-page.png" alt-text="Screenshot that shows the Disks pane in Configuration and policies." lightbox="./media/encrypt-disks-customer-managed-keys/disks-page.png":::
 
 1. In the **Encryption type** box, select **Encryption at-rest with a customer managed key**. 
 1. In the **Disk encryption set** box, select the disk encryption set you created earlier. It's the same disk encryption set that the system-assigned identity of the lab can access.
-1. Select **Save** at the top of the pane. 
+1. Select **Save** at the top of the pane.
 
     :::image type="content" source="./media/encrypt-disks-customer-managed-keys/disk-encryption-set.png" alt-text="Screenshot that shows the steps to complete in Configuration and policies." lightbox="./media/encrypt-disks-customer-managed-keys/disk-encryption-set.png":::
 
-1. A message box appears with the following message: *This setting will apply to newly created machines in the lab. Old OS disk will remain encrypted with the old disk encryption set*. Select **OK**. 
+1. A message box appears with the following message: *This setting will apply to newly created machines in the lab. Old OS disk will remain encrypted with the old disk encryption set*. Select **OK**.
 
-    After this configuration, lab disks are encrypted with the customer-managed key provided in the disk encryption set. 
+    After this configuration, lab disks are encrypted with the customer-managed key provided in the disk encryption set.
 
-## How to validate that disks are being encrypted
+## Validate that disks are being encrypted
 
 1. Go to a lab virtual machine that you created after enabling disk encryption with a customer-managed key on the lab.
 
@@ -81,5 +81,5 @@ The following section shows how a lab owner can set up encryption with a custome
   
 ## Related content
 
-- [Azure disk encryption](/azure/virtual-machines/disk-encryption) 
+- [Azure disk encryption](/azure/virtual-machines/disk-encryption)
 - [Customer-managed keys](/azure/virtual-machines/disk-encryption#customer-managed-keys)