You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/configure-customer-managed-keys.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Configure CMK encryption at rest in Azure VMware Solution
3
3
description: Learn how to encrypt data in Azure VMware Solution with customer-managed keys by using Azure Key Vault.
4
4
ms.topic: how-to
5
5
ms.custom: devx-track-azurecli, engagement-fy23
6
-
ms.date: 4/12/2024
6
+
ms.date: 2/09/2026
7
7
# Customer intent: As a cloud administrator, I want to configure customer-managed key encryption for my Azure VMware Solution, so that I can securely manage the encryption keys and control access to sensitive data at rest.
8
8
---
9
9
@@ -19,7 +19,7 @@ When you manage your own encryption keys, you can:
19
19
- Centrally manage the lifecycle of CMKs.
20
20
- Revoke Azure access to the KEK.
21
21
22
-
The CMKs feature supports the following key types and their key sizes:
22
+
The CMK feature supports the following key types and their key sizes:
23
23
24
24
-**RSA**: 2048, 3072, 4096
25
25
-**RSA-HSM**: 2048, 3072, 4096
@@ -204,7 +204,7 @@ If you accidentally delete your key in the key vault, the private cloud can't pe
204
204
205
205
### Restore key vault permission
206
206
207
-
If you have a private cloud that has lost access to the CMK, check if Managed System Identity (MSI) requires permissions in the key vault. The error notification returned from Azure might not correctly indicate MSI requiring permissions in the key vault as the root cause. Remember, the required permissions are `get`, `wrapKey`, and `unwrapKey`. See step 4 in [Prerequisites](#prerequisites).
207
+
If you have a private cloud that lost access to the CMK, check if Managed System Identity (MSI) requires permissions in the key vault. The error notification returned from Azure might not correctly indicate MSI requiring permissions in the key vault as the root cause. Remember, the required permissions are `get`, `wrapKey`, and `unwrapKey`. See step 4 in [Prerequisites](#prerequisites).
0 commit comments