Skip to content

Commit 67938eb

Browse files
Merge pull request #283738 from b-ahibbard/2xencrypt-usgov
remove us gov caveat for 2x encryption
2 parents 5446588 + c05dcd5 commit 67938eb

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/azure-netapp-files/double-encryption-at-rest.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,6 @@ If you are using this feature for the first time, you need to create a double-en
2323

2424
When you create a volume in a double-encryption capacity pool, the default key management (the **Encryption key source** field) is `Microsoft Managed Key`, and the other choice is `Customer Managed Key`. Using customer-managed keys requires additional preparation of an Azure Key Vault and other details. For more information about using volume encryption with customer managed keys, see [Configure customer-managed keys for Azure NetApp Files volume encryption](configure-customer-managed-keys.md).
2525

26-
>[!IMPORTANT]
27-
>Double encryption in US Gov regions is only supported with platform-managed keys, not customer-managed keys.
28-
2926
:::image type="content" source="./media/double-encryption-at-rest/double-encryption-create-volume.png" alt-text="Screenshot of the Create Volume page in a double-encryption capacity pool." lightbox="./media/double-encryption-at-rest/double-encryption-create-volume.png":::
3027

3128
## Supported regions

0 commit comments

Comments
 (0)