Skip to content

Commit 6bb8b15

Browse files
author
AbhishekMallick-MS
committed
Backup vault data encryption updates
1 parent d2dde52 commit 6bb8b15

File tree

1 file changed

+37
-1
lines changed

1 file changed

+37
-1
lines changed

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

Lines changed: 37 additions & 1 deletion
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: 06/24/2024
5+
ms.date: 10/18/2024
66
ms.custom: references_regions, devx-track-azurepowershell-azurecli
77
ms.service: azure-backup
88
author: AbhishekMallick-MS
@@ -19,12 +19,16 @@ To allow encryption, you must grant the Backup vault the permissions to access t
1919

2020
## Support matrix
2121

22+
This section provides the supported scenarios for data encryption in a Backup vault.
23+
2224
### Supported regions
2325

2426
CMKs for Backup vaults are currently available in all Azure public regions.
2527

2628
### Key Vault and managed HSM key requirements
2729

30+
Before you enable encryption on a Backup vault, review the following requirements:
31+
2832
- Encryption settings use Azure Key Vault or a managed hardware security module (HSM) key, along with the details of the Backup vault's managed identity.
2933

3034
- The Backup vault's managed identity needs to have:
@@ -39,8 +43,18 @@ CMKs for Backup vaults are currently available in all Azure public regions.
3943

4044
- 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.
4145

46+
### Known limitation
47+
48+
If you delete the key vault/MHSM key used for encryption settings, the delete Backup Vault operation will fail.
49+
50+
>[!Note]
51+
>- Before performing the delete vault operation on a vault with encryption settings enabled, ensure that the encryption settings details, such as the managed identity, are attached to the vault and have the necessary permissions to access the key vault/MHSM key.
52+
>- Also, ensure that the key vault/MHSM key (if used) exists. If the key is deleted, you can recover it from the soft deleted state. Learn about the [troubleshooting steps](#troubleshoot-operation-errors-for-encryption-settings).
53+
4254
## Considerations
4355

56+
Before you enable encryption on a Backup vault, review the following considerations:
57+
4458
- After you enable encryption by using CMKs for a Backup vault, you can't revert to using PMKs (the default). You can change the encryption keys or the managed identity to meet requirements.
4559

4660
- A CMK is applied on the Azure Backup storage vault and vault-archive tiers. It isn't applicable for the operational tier.
@@ -57,6 +71,10 @@ CMKs for Backup vaults are currently available in all Azure public regions.
5771

5872
If the key or key vault that you're using is deleted or access is revoked and can't be restored, you'll lose access to the data stored in the Backup vault. Also, ensure that you have appropriate permissions to provide and update managed identity, Backup vault, and key vault details.
5973

74+
- Vaults that use user-assigned managed identities for CMK encryption don't support the use of private endpoints for Azure Backup.
75+
76+
- Key vaults that limit access to specific networks are currently not supported with User-assigned managed identities for CMK encryption.
77+
6078
## Enable encryption by using customer-managed keys at vault creation
6179

6280
When you create a Backup vault, you can enable encryption on backups by using CMKs. [Learn how to create a Backup vault](create-manage-backup-vault.md#create-a-backup-vault).
@@ -67,6 +85,8 @@ When you create a Backup vault, you can enable encryption on backups by using CM
6785

6886
To enable the encryption, follow these steps:
6987

88+
1. In the [Azure portal](https://portal.azure.com/), go to the **Backup vault**.
89+
7090
1. On the **Vault Properties** tab, select **Add Identity**.
7191

7292
:::image type="content" source="./media/encryption-at-rest-with-cmk-for-backup-vault/backup-vault-properties.png" alt-text="Screenshot that shows Backup vault properties." lightbox="./media/encryption-at-rest-with-cmk-for-backup-vault/backup-vault-properties.png":::
@@ -453,6 +473,12 @@ Before you configure backup protection, confirm that you successfully:
453473

454474
The process to configure and perform backups to a Backup vault that's encrypted via CMKs is the same as the process to configure and perform backups to a vault that uses PMKs. There are no changes to the experience.
455475

476+
## Private Endpoint support
477+
478+
You can use Azure Key Vault with Private Endpoint using System-Assigned Managed Identity of the vault.
479+
480+
If the public network access of the Azure Key Vault is disabled, the access restrictions will prevent you to use Azure portal from outside the private endpoint enabled network machine to Select Key Vault and Key on the **Encryption Settings** blade. However, you can use the **Key Vault key URI** to provide Key Vault key details in **Encryption Settings**.
481+
456482
## Troubleshoot operation errors for encryption settings
457483

458484
This section lists the various troubleshooting scenarios that you might encounter for Backup vault encryption.
@@ -497,7 +523,17 @@ This section lists the various troubleshooting scenarios that you might encounte
497523

498524
**Recommended action**: Check the Key Vault access policies and grant permissions accordingly.
499525

526+
### Vault deletion failure
527+
528+
**Error code**: `CloudServiceRetryableError`
529+
530+
**Cause**: If there is an issue with your Backup Vault Encryption Settings (such as you have removed Key Vault/MHSM permissions from the managed identity of the Encryption Settings, disabled system-assigned identity, detached/deleted the managed identity from the Backup vault used for encryption settings, or the key vault/MHSM key is deleted), then vault deletion would fail.
531+
532+
**Recommended action**: To address this issue:
500533

534+
- Ensure that the managed identity being used for Encryption Settings still has the permissions to access the key vault/MHSM. Restore them before you proceed for deletion of the vault.
535+
- [Reattach/enable the managed identity and assign the required Key Vault/MHSM permissions](#enable-a-managed-identity-for-your-backup-vault).
536+
- If the key vault key is deleted, then the vault deletion is not currently supported. However, to recover the delete key from the **Soft Deleted** state, ensure that you have the required permissions to the managed identity on the key vault/MHSM, and then retry the **Delete Backup vault** operation.
501537

502538
## Validate error codes
503539

0 commit comments

Comments
 (0)