Skip to content

Commit bc45053

Browse files
Merge pull request #191895 from roygara/subKeyClarity
Clarity on key vault use.
2 parents 097a24d + b13772d commit bc45053

File tree

2 files changed

+4
-3
lines changed

2 files changed

+4
-3
lines changed

includes/virtual-machines-disks-encryption-create-key-vault-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717
When creating the Key Vault, you must enable purge protection. Purge protection ensures that a deleted key cannot be permanently deleted until the retention period lapses. These settings protect you from losing data due to accidental deletion. These settings are mandatory when using a Key Vault for encrypting managed disks.
1818

1919
> [!IMPORTANT]
20-
> Do not camel case the region, if you do so you may experience problems when assigning additional disks to the resource in the Azure portal.
20+
> Don't camel case the region, if you do so, you may experience problems when assigning additional disks to the resource in the Azure portal.
2121
2222
```azurecli
2323
subscriptionId=yourSubscriptionID

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,16 @@
55
author: roygara
66
ms.service: virtual-machines
77
ms.topic: include
8-
ms.date: 08/24/2020
8+
ms.date: 03/16/2022
99
ms.author: rogarana
1010
ms.custom: include file
1111
---
1212
- 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.
1313
- [HSM](../articles/key-vault/keys/hsm-protected-keys.md) keys require the **premium** tier of Azure Key vaults.
1414
- Disks created from custom images that are encrypted using server-side encryption and customer-managed keys must be encrypted using the same customer-managed keys and must be in the same subscription.
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.
16-
- All resources related to your customer-managed keys (Azure Key Vaults, disk encryption sets, VMs, disks, and snapshots) must be in the same subscription and region.
16+
- Most resources related to your customer-managed keys (disk encryption sets, VMs, disks, and snapshots) must be in the same subscription and region.
17+
- Azure Key Vaults may be used from a different subscription but must be in the same region and tenant as your disk encryption set.
1718
- Disks, snapshots, and images encrypted with customer-managed keys cannot move to another resource group and subscription.
1819
- Managed disks currently or previously encrypted using Azure Disk Encryption cannot be encrypted using customer-managed keys.
1920
- Can only create up to 1000 disk encryption sets per region per subscription.

0 commit comments

Comments
 (0)