Skip to content

Commit 3b26ef9

Browse files
Merge pull request #267595 from roygara/clarifyUpdate
Clarifying PV2 / Ultra Restriction with CMK
2 parents 191443f + 0d11bdc commit 3b26ef9

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,17 @@
44
author: roygara
55
ms.service: azure-disk-storage
66
ms.topic: include
7-
ms.date: 02/22/2023
7+
ms.date: 02/28/2024
88
ms.author: rogarana
99
ms.custom: include file
1010
---
1111
- If this feature is enabled for a disk with incremental snapshots, it can't be disabled on that disk or its snapshots.
1212
To work around this, copy all the data to an entirely different managed disk that isn't using customer-managed keys. You can do that with either the [Azure CLI](../articles/virtual-machines/linux/disks-upload-vhd-to-managed-disk-cli.md#copy-a-managed-disk) or the [Azure PowerShell module](../articles/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell.md#copy-a-managed-disk).
1313
- Only [software and HSM RSA keys](../articles/key-vault/keys/about-keys.md) of sizes 2,048-bit, 3,072-bit and 4,096-bit are supported, no other keys or sizes.
1414
- [HSM](../articles/key-vault/keys/hsm-protected-keys.md) keys require the **premium** tier of Azure Key vaults.
15-
- For Ultra Disks and Premium SSD v2 disks only: Snapshots created from disks that are encrypted with server-side encryption and customer-managed keys must be encrypted with the same customer-managed keys.
15+
- For Ultra Disks and Premium SSD v2 disks only:
16+
- Snapshots created from disks that are encrypted with server-side encryption and customer-managed keys must be encrypted with the same customer-managed keys.
17+
- User-assigned managed identities aren't supported for Ultra Disks and Premium SSD v2 disks encrypted with customer-managed keys.
1618
- Most resources related to your customer-managed keys (disk encryption sets, VMs, disks, and snapshots) must be in the same subscription and region.
1719
- 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).
1820
- 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)