You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/how-to-verify-encryption-status.md
+15-16Lines changed: 15 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Verify encryption status for Linux - Azure Disk Encryption
3
-
description: This article provides instructions on verifying the encryption status from the platform and OS level.
3
+
description: This article provides instructions on verifying the encryption status from the platform and OS levels.
4
4
author: kailashmsft
5
5
ms.service: security
6
6
ms.topic: article
@@ -15,7 +15,7 @@ ms.custom: seodec18
15
15
16
16
# Verify encryption status for Linux
17
17
18
-
The scope of this article is to validate the encryption status of a virtual machine by using different methods: the Azure portal, PowerShell, the Azure CLI, or the OS of the virtual machine (VM).
18
+
The scope of this article is to validate the encryption status of a virtual machine by using different methods: the Azure portal, PowerShell, the Azure CLI, or the operating system of the virtual machine (VM).
19
19
20
20
You can validate the encryption status during or after the encryption, by either:
21
21
@@ -29,13 +29,11 @@ This scenario applies for Azure Disk Encryption dual-pass and single-pass extens
29
29
30
30
## Portal
31
31
32
-
Validate the encryption status by checking the extensions section on the Azure portal.
33
-
34
32
In the Azure portal, inside the **Extensions** section, select the Azure Disk Encryption extension in the list. The information for **Status message** indicates the current encryption status:
35
33
36
34

37
35
38
-
In the list of extensions, you'll see the corresponding Azure Disk Encryption extension version. Version 0.x corresponds to Azure Disk Encryption dual-pass, and version 1.x corresponds to Azure Disk Encryption single-pass.
36
+
In the list of extensions, you'll see the corresponding Azure Disk Encryption extension version. Version 0.x corresponds to Azure Disk Encryption dualpass, and version 1.x corresponds to Azure Disk Encryption singlepass.
39
37
40
38
You can get more details by selecting the extension and then selecting **View detailed status**. The detailed status of the encryption process appears in JSON format.
41
39
@@ -48,11 +46,11 @@ Another way to validate the encryption status is by looking at the **Disk settin
48
46

49
47
50
48
>[!NOTE]
51
-
> This status means the disks have encryption settings stamped but not that they were actually encrypted at the OS level.
49
+
> This status means the disks have encryption settings stamped, not that they were actually encrypted at the OS level.
52
50
>
53
51
> By design, the disks are stamped first and encrypted later. If the encryption process fails, the disks may end up stamped but not encrypted.
54
52
>
55
-
> To confirm if the disks are truly encrypted, you can double check the encryption of each disk at OS level.
53
+
> To confirm if the disks are truly encrypted, you can double check the encryption of each disk at the OS level.
56
54
57
55
## PowerShell
58
56
@@ -68,7 +66,7 @@ You can validate the *general* encryption status of an encrypted VM by using the
68
66
You can capture the encryption settings from each disk by using the following PowerShell commands.
69
67
70
68
### Single pass
71
-
In a single pass, the encryption settings are stamped on each of the disks (OS and data). You can capture the encryption settings for an OS disk in a single pass, as follows:
69
+
In a single pass, the encryption settings are stamped on each of the disks (OS and data). You can capture the encryption settings for an OS disk in a single pass as follows:
Unmanaged disks are VHD files that are stored as page blobs in Azure storage accounts.
268
267
269
-
To get the details of a specific disk, you need to provide:
268
+
To get the details for a specific disk, you need to provide:
270
269
271
270
- The ID of the storage account that contains the disk.
272
271
- A connection string for that particular storage account.
@@ -308,7 +307,7 @@ Use this command to list all the blobs on a particular container:
308
307
```bash
309
308
az storage blob list -c ${ContainerName} --connection-string $ConnectionString --query [].[name] -o tsv
310
309
```
311
-
Choose the disk you want to query and store its name on a variable:
310
+
Choose the disk that you want to query and store its name on a variable:
312
311
```bash
313
312
DiskName="diskname.vhd"
314
313
```
@@ -328,14 +327,14 @@ lsblk
328
327
329
328

330
329
331
-
You can get more details using the following **lsblk** variant.
330
+
You can get more details by using the following **lsblk** variant.
332
331
333
332
You'll see a **crypt** type layer that is mounted by the extension. The following example shows logical volumes and normal disks having **crypto\_LUKS FSTYPE**.
0 commit comments