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/backup/backup-azure-enhanced-soft-delete-configure-manage.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@ ms.date: 05/26/2025
6
6
ms.service: azure-backup
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-mallicka
9
+
ms.custom: references_regions
9
10
# Customer intent: As a backup administrator, I want to configure soft delete for my recovery services vault or backup vault, so that I can protect my backup data from accidental deletion and ensure its recoverability over a specified retention period.
10
11
---
11
12
@@ -252,18 +253,19 @@ Follow these steps:
252
253
253
254
---
254
255
255
-
## Manage Customer-Managed Keys (CMKs) After Undeletion:
256
+
## Manage customer-managed keys (CMKs) after undeletion
256
257
257
258
To ensure CMKs are enabled after undeleting the vault, follow these steps:
258
259
259
260
1. To reapply CMK settings, perform one of the following actions to activate CMK:
260
261
261
-
1. Choose a different key and apply CMK settings and then revert back to the original CMK key.
262
+
- Choose a different key and apply CMK settings and then revert back to the original CMK key.
263
+
264
+
- Choose a different managed identity than the identity used for CMK encryption before vault undeletion and reapply CMK settings.
262
265
263
-
1. Choose a different managed identity than the identity used for CMK encryption before vault undeletion and reapply CMK settings.
264
266
These actions will reactivate CMK on the vault after it is undeleted.
265
267
266
-
## Resume Backup for a Soft-Deleted Backup Item
268
+
## Resume backup for a soft-deleted backup item
267
269
268
270
To resume backup for a soft-deleted backup item, follow these steps:
# Customer intent: As a data administrator, I want to utilize soft delete features in Azure Backup, so that I can ensure the recoverability of deleted backup data for up to 180 days and protect against accidental or malicious deletions.
10
10
---
11
11
@@ -143,16 +143,16 @@ The following table outlines the behavior of the **_Delete Protected Item_** act
|**Azure Portal**| Backup items move to a soft-deleted state. | Backup items move to a soft-deleted state. |
146
+
|**Azure portal**| Backup items move to a soft-deleted state. | Backup items move to a soft-deleted state. |
147
147
|**PowerShell**| Backup items move to a soft-deleted state. | For PowerShell modules version **7.5.0** or later, backup items in Recovery Services vault move to a soft-deleted state. For earlier versions, backup items are deleted immediately.<br>Backup vault actions are independent of the module version. |
148
148
|**CLI**| Backup items move to a soft-deleted state. | For Azure CLI version **2.75.0** or later, backup items in Recovery Services vault move to a soft-deleted state. For earlier versions, backup items are deleted immediately.<br>Backup vault actions are independent of the module version. |
149
149
|**REST API**| Backup items move to a soft-deleted state. | In Recovery Services vault, for API versions **2024-09-30-preview** or later, backup items move to a soft-deleted state. In Backup vault, for API versions **2025-09-01** or later, backup items move to a soft-deleted state.<br>For earlier API versions, backup items are deleted immediately. |
|**Azure Portal**| Soft deletion of the vault is allowed when the vault is either empty or contains only soft-deleted backup items or containers. |
167
+
|**Azure portal**| Soft deletion of the vault is allowed when the vault is either empty or contains only soft-deleted backup items or containers. |
168
168
|**PowerShell**| For PowerShell module versions **7.5.0** or later, soft deletion of the Recovery Services vault is allowed when it is either empty or contains only soft-deleted backup items or containers. For earlier versions, vault deletion is allowed only when the vault is completely empty.<br>Backup vault actions are independent of the module version. |
169
169
|**CLI**| For Azure CLI versions **2.75.0** or later, soft deletion of the Recovery Services vault is allowed when the vault is either empty or contains only soft-deleted backup items or containers. For earlier versions, vault deletion is allowed only when the vault is completely empty.<br>Backup vault actions are independent of the module version. |
170
170
|**REST API**| In Recovery Services vault, for API versions **2024-09-30-preview** or later, soft deletion of the vault is allowed when the vault is either empty or contains only soft-deleted backup items or containers. In Backup vault, for API versions **2025-09-01** or later, soft deletion of the vault is allowed when the vault is either empty or contains only soft-deleted backup items or containers.<br>For earlier API versions, vault deletion is allowed only when the vault is completely empty. |
@@ -187,17 +187,17 @@ The following table describes the behavior of the **_Disable Soft Delete_** acti
187
187
188
188
|**Client**|**Behavior**|
189
189
|-------------|--------------|
190
-
|**Azure Portal**| Not allowed. |
190
+
|**Azure portal**| Not allowed. |
191
191
|**PowerShell**| Not allowed for PowerShell module versions **7.5.0** or later in Recovery Services vault. Allowed for earlier versions.<br>Backup vault actions are independent of the module version. |
192
192
|**CLI**| Not allowed for Azure CLI versions **2.75.0** or later in Recovery Services vault. Allowed for earlier versions.<br>Backup vault actions are independent of the module version. |
193
193
|**REST API**| Not allowed for API versions **2024-09-30-preview** or later in Recovery Services vault. Not allowed for API versions **2025-09-01** or later in Backup vault.<br>Allowed for earlier API versions. |
0 commit comments