Skip to content

Commit 06582b1

Browse files
committed
Updating limitation.
1 parent f68bdfc commit 06582b1

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

includes/virtual-machines-managed-disks-customer-managed-keys-restrictions.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
author: roygara
55
ms.service: azure-disk-storage
66
ms.topic: include
7-
ms.date: 02/28/2024
7+
ms.date: 06/04/2024
88
ms.author: rogarana
99
ms.custom: include file
1010
---
@@ -15,6 +15,7 @@
1515
- For Ultra Disks and Premium SSD v2 disks only:
1616
- Snapshots created from disks that are encrypted with server-side encryption and customer-managed keys must be encrypted with the same customer-managed keys.
1717
- User-assigned managed identities aren't supported for Ultra Disks and Premium SSD v2 disks encrypted with customer-managed keys.
18+
- Not currently supported in Azure Government or Azure China.
1819
- Most resources related to your customer-managed keys (disk encryption sets, VMs, disks, and snapshots) must be in the same subscription and region.
1920
- Azure Key Vaults may be used from a different subscription but must be in the same region as your disk encryption set. As a preview, you can use Azure Key Vaults from [different Microsoft Entra tenants](../articles/virtual-machines/disks-cross-tenant-customer-managed-keys.md).
2021
- Disks encrypted with customer-managed keys can only move to another resource group if the VM they are attached to is deallocated.

0 commit comments

Comments
 (0)