Skip to content

Commit 6f3395d

Browse files
committed
refresh updates
1 parent 2ed0964 commit 6f3395d

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/azure-vmware/configure-customer-managed-keys.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Configure CMK encryption at rest in Azure VMware Solution
33
description: Learn how to encrypt data in Azure VMware Solution with customer-managed keys by using Azure Key Vault.
44
ms.topic: how-to
55
ms.custom: devx-track-azurecli, engagement-fy23
6-
ms.date: 4/12/2024
6+
ms.date: 2/09/2026
77
# 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.
88
---
99

@@ -19,7 +19,7 @@ When you manage your own encryption keys, you can:
1919
- Centrally manage the lifecycle of CMKs.
2020
- Revoke Azure access to the KEK.
2121

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:
2323

2424
- **RSA**: 2048, 3072, 4096
2525
- **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
204204

205205
### Restore key vault permission
206206

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).
208208

209209
### Fix an expired key
210210

0 commit comments

Comments
 (0)