Skip to content

Commit 69c7648

Browse files
Merge pull request #268222 from AbhishekMallick-MS/Mar-6-2024-CMKBV
CMK for Backup vault - Region updates
2 parents 062503f + 75e25c2 commit 69c7648

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/backup/encryption-at-rest-with-cmk-for-backup-vault.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Encrypt backup data in a Backup vault by using customer-managed keys
33
description: Learn how to use Azure Backup to encrypt your backup data by using customer-managed keys (CMKs) in a Backup vault.
44
ms.topic: how-to
5-
ms.date: 11/20/2023
5+
ms.date: 03/06/2024
66
ms.custom: references_regions, devx-track-azurepowershell-azurecli
77
ms.service: backup
88
author: AbhishekMallick-MS
@@ -23,7 +23,7 @@ Support for CMK configuration for a Backup vault is in preview.
2323

2424
### Supported regions
2525

26-
CMKs for Backup vaults are currently available in the following regions: West Central US, Switzerland North, Australia East, North Europe, South Central US.
26+
CMKs for Backup vaults are currently available in all Azure public regions.
2727

2828
### Key Vault and managed HSM key requirements
2929

@@ -33,13 +33,13 @@ CMKs for Backup vaults are currently available in the following regions: West Ce
3333

3434
- A built-in [Crypto Service Encryption User role](/azure/role-based-access-control/built-in-roles#key-vault-crypto-service-encryption-user) assigned, if your key vault is using a role-based access control (RBAC) configuration that's based on identity and access management (IAM).
3535
- **Get**, **Wrap**, and **Unwrap** permissions if your key vault is using a configuration that's based on access policies.
36-
- **Get**, **Wrap**, and **Unwrap** permissions granted via local RBAC on the key if you're using a managed HSM. [Learn more](/azure/key-vault/managed-hsm/overview).
36+
- **Get**, **Wrap**, and **Unwrap** permissions granted via local RBAC on the key if you're using a managed HSM. [Learn more](../key-vault/managed-hsm/overview.md).
3737

3838
- Ensure that you have a valid, enabled Key Vault key. Don't use an expired or disabled key, because it can't be used for encryption at rest and will lead to failures of backup and restore operations. The Key Vault term also indicates a managed HSM if you didn't note it earlier.
3939

4040
- Key Vault must have soft delete and purge protection enabled.
4141

42-
- Encryption settings support Azure Key Vault RSA and RSA-HSM keys only of sizes 2,048, 3,072, and 4,096. [Learn more about keys](/azure/key-vault/keys/about-keys). Before you consider Key Vault regions for encryption settings, see [Key Vault disaster recovery scenarios](/azure/key-vault/general/disaster-recovery-guidance) for regional failover support.
42+
- Encryption settings support Azure Key Vault RSA and RSA-HSM keys only of sizes 2,048, 3,072, and 4,096. [Learn more about keys](../key-vault/keys/about-keys.md). Before you consider Key Vault regions for encryption settings, see [Key Vault disaster recovery scenarios](../key-vault/general/disaster-recovery-guidance.md) for regional failover support.
4343

4444
### Known limitations
4545

0 commit comments

Comments
 (0)