Skip to content

Commit d6650f1

Browse files
committed
Updating info.
1 parent 816adc9 commit d6650f1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
- Snapshots created from disks that are encrypted with server-side encryption and customer-managed keys must be encrypted with the same customer-managed keys.
1616
- Most resources related to your customer-managed keys (disk encryption sets, VMs, disks, and snapshots) must be in the same subscription and region.
1717
- 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 Azure Active Directory tenants](../articles/virtual-machines/disks-cross-tenant-customer-managed-keys.md).
18-
- Disks and images encrypted with customer-managed keys can only move to another resource group if the VM they are attached to is in a deallocated state.
18+
- Disks encrypted with customer-managed keys can only move to another resource group if the VM they are attached to is in a deallocated state.
1919
- Disks, snapshots, and images encrypted with customer-managed keys cannot be moved between subscriptions.
2020
- Managed disks currently or previously encrypted using Azure Disk Encryption cannot be encrypted using customer-managed keys.
2121
- Can only create up to 5000 disk encryption sets per region per subscription.

0 commit comments

Comments
 (0)