Skip to content

Commit b219025

Browse files
committed
Formatting
1 parent e8f81cc commit b219025

File tree

1 file changed

+16
-19
lines changed

1 file changed

+16
-19
lines changed

azure-managed-lustre/vnet-encryption.md

Lines changed: 16 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ ms.author: pauljewell
77
ms.reviewer: brianl
88
ms.date: 07/18/2025
99
ms.lastreviewed: 07/21/2023
10-
zone_pivot_groups: select-os
1110
---
1211

1312
# Enable and Validate VNet Encryption with Azure Managed Lustre
@@ -35,27 +34,25 @@ To enable VNet Encryption with AMLFS:
3534
```
3635

3736
1. Ensure Client VM Compatibility
37+
Only specific VM series support VNet Encryption:
3838

39-
Only specific VM series support VNet Encryption:
39+
- Dsv6-series
40+
- Ebsv5-series
4041

41-
- Dsv6-series
42-
- Ebsv5-series
42+
> [!IMPORTANT]
43+
> Unsupported VMs will not encrypt traffic, even if the VNet is encrypted.
44+
> Existing VMs must be rebooted for encryption to be enabled.
4345
44-
> [!IMPORTANT]
45-
> Unsupported VMs will not encrypt traffic, even if the VNet is encrypted.
46-
> Existing VMs must be rebooted for encryption to be enabled.
46+
1. Deploy AMLFS into an Encrypted VNet
47+
You can deploy Azure Managed Lustre (AMLFS) into:
4748

48-
3. Deploy AMLFS into an Encrypted VNet
49+
- An encrypted VNet
50+
- A peered VNet that also has encryption enabled
4951

50-
You can deploy Azure Managed Lustre (AMLFS) into:
51-
52-
- An encrypted VNet
53-
- A peered VNet that also has encryption enabled
54-
55-
> [!NOTE]
56-
> If you enable VNet Encryption on a VNet after deploying AMLFS, the cluster will not immediately support encrypted traffic.
57-
> Encryption capability is activated only after a maintenance event and cluster reboot.
58-
> Refer to the AMLFS maintenance window documentation for guidance on scheduling and managing updates.
52+
> [!NOTE]
53+
> If you enable VNet Encryption on a VNet after deploying AMLFS, the cluster will not immediately support encrypted traffic.
54+
> Encryption capability is activated only after a maintenance event and cluster reboot.
55+
> Refer to the AMLFS maintenance window documentation for guidance on scheduling and managing updates.
5956
6057
## Enforcement Mode
6158

@@ -84,8 +81,8 @@ To confirm that traffic between AMLFS and client VMs is encrypted:
8481
az vm show --name <vm-name> --resource-group <rg-name> --query "storageProfile.osDisk.managedDisk.encryptionSettingsCollection"
8582
```
8683

87-
> [!TIP]
88-
> For more information on verifying encryption, understanding performance impact, and managing certificate handling, see the #.
84+
[!TIP]
85+
> For more information on verifying encryption, understanding performance impact, and managing certificate handling, see the #.
8986
9087
## Caveats and Limitations
9188

0 commit comments

Comments
 (0)