Skip to content

Commit 1188a68

Browse files
committed
Add links and clarify limitations
1 parent f89e873 commit 1188a68

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

azure-managed-lustre/vnet-encryption.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.lastreviewed: 07/21/2023
1111

1212
# Enable and Validate VNet Encryption with Azure Managed Lustre
1313

14-
Azure Managed Lustre (AMLFS) supports Virtual Network (VNet) Encryption, enabling encryption of data in transit between AMLFS and client virtual machines (VMs). This feature is valuable for customers in regulated industries such as finance, healthcare, and government, where data confidentiality is paramount.
14+
Azure Managed Lustre (AMLFS) supports [Virtual Network (VNet) Encryption](/azure/virtual-network/virtual-network-encryption-overview), enabling encryption of data in transit between AMLFS and client virtual machines (VMs). This feature is valuable for customers in regulated industries such as finance, healthcare, and government, where data confidentiality is paramount.
1515

1616
## How VNet Encryption Works
1717

@@ -35,14 +35,9 @@ To enable VNet Encryption with AMLFS:
3535

3636
1. Ensure Client VM Compatibility
3737

38-
Only specific VM series support VNet Encryption:
38+
Azure only supports specific VM series for VNet Encryption. Unsupported VMs do not encrypt traffic, even if the VNet is encrypted. See [Azure Virtual Network encryption requirements](/azure/virtual-network/virtual-network-encryption-overview#requirements) for requirements and a list of VM SKUs that support encryption.
3939

40-
- Dsv6-series
41-
- Ebsv5-series
42-
43-
> [!IMPORTANT]
44-
> Unsupported VMs do not encrypt traffic, even if the VNet is encrypted.
45-
> Existing VMs must be rebooted for encryption to be enabled.
40+
Existing VMs must be rebooted for encryption to be enabled.
4641

4742
1. Deploy AMLFS into an Encrypted VNet
4843

@@ -58,7 +53,7 @@ To enable VNet Encryption with AMLFS:
5853
5954
## Enforcement Mode
6055

61-
Azure currently supports only the `AllowUnencrypted` enforcement mode:
56+
Azure currently supports only the [`AllowUnencrypted`](/azure/virtual-network/virtual-network-encryption-overview#limitations) enforcement mode:
6257

6358
- Unencrypted traffic is still allowed, even when VNet Encryption is enabled.
6459
- The stricter `DropUnencrypted` mode isn't generally available and requires special feature registration.
@@ -74,7 +69,7 @@ To confirm that traffic between AMLFS and client VMs is encrypted:
7469

7570
1. **Run Diagnostic Reports**
7671
- Use Azure Monitor or custom scripts to validate encrypted traffic paths.
77-
- Check VM metrics and logs for encryption status indicators.
72+
- Check VM metrics and logs for [encryption status](/azure/network-watcher/vnet-flow-logs-overview?tabs=Americas#log-format) indicators.
7873

7974
1. **Check VM Capabilities**
8075
Use the following command to verify if a VM supports VNet Encryption:

0 commit comments

Comments
 (0)