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
@@ -19,12 +19,16 @@ To allow encryption, you must grant the Backup vault the permissions to access t
19
19
20
20
## Support matrix
21
21
22
+
This section provides the supported scenarios for data encryption in a Backup vault.
23
+
22
24
### Supported regions
23
25
24
26
CMKs for Backup vaults are currently available in all Azure public regions.
25
27
26
28
### Key Vault and managed HSM key requirements
27
29
30
+
Before you enable encryption on a Backup vault, review the following requirements:
31
+
28
32
- 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.
29
33
30
34
- 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.
39
43
40
44
- 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.
41
45
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
+
42
54
## Considerations
43
55
56
+
Before you enable encryption on a Backup vault, review the following considerations:
57
+
44
58
- 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.
45
59
46
60
- 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.
57
71
58
72
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.
59
73
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
+
60
78
## Enable encryption by using customer-managed keys at vault creation
61
79
62
80
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
67
85
68
86
To enable the encryption, follow these steps:
69
87
88
+
1. In the [Azure portal](https://portal.azure.com/), go to the **Backup vault**.
89
+
70
90
1. On the **Vault Properties** tab, select **Add Identity**.
71
91
72
92
:::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:
453
473
454
474
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.
455
475
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
+
456
482
## Troubleshoot operation errors for encryption settings
457
483
458
484
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
497
523
498
524
**Recommended action**: Check the Key Vault access policies and grant permissions accordingly.
499
525
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:
500
533
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.
0 commit comments