Skip to content

Commit d27f78d

Browse files
Apply suggestions from PR review
1 parent 2885f49 commit d27f78d

2 files changed

Lines changed: 15 additions & 13 deletions

File tree

articles/backup/backup-azure-enhanced-soft-delete-configure-manage.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ ms.date: 05/26/2025
66
ms.service: azure-backup
77
author: AbhishekMallick-MS
88
ms.author: v-mallicka
9+
ms.custom: references_regions
910
# 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.
1011
---
1112

@@ -252,18 +253,19 @@ Follow these steps:
252253

253254
---
254255

255-
## Manage Customer-Managed Keys (CMKs) After Undeletion:
256+
## Manage customer-managed keys (CMKs) after undeletion
256257

257258
To ensure CMKs are enabled after undeleting the vault, follow these steps:
258259

259260
1. To reapply CMK settings, perform one of the following actions to activate CMK:
260261

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.
262265

263-
1. Choose a different managed identity than the identity used for CMK encryption before vault undeletion and reapply CMK settings.
264266
These actions will reactivate CMK on the vault after it is undeleted.
265267

266-
## Resume Backup for a Soft-Deleted Backup Item
268+
## Resume backup for a soft-deleted backup item
267269

268270
To resume backup for a soft-deleted backup item, follow these steps:
269271

articles/backup/secure-by-default.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.topic: overview
55
ms.date: 11/10/2025
66
author: AbhishekMallick-MS
77
ms.author: v-mallicka
8-
ms.custom: engagement-fy24, ignite-2024
8+
ms.custom: engagement-fy24, ignite-2024, references_regions
99
# 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.
1010
---
1111

@@ -143,16 +143,16 @@ The following table outlines the behavior of the **_Delete Protected Item_** act
143143

144144
| **Client** | **Soft Delete – Enabled / Always On** | **Soft Delete – Disabled** |
145145
|-------------|----------------------------------------|-----------------------------|
146-
| **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. |
147147
| **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. |
148148
| **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. |
149149
| **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. |
150150

151-
# [General Availability](#tab/general-availability)
151+
# [General availability](#tab/general-availability)
152152

153153
| **Clients** | **Soft Delete – Enabled/AlwaysOn/Disabled.** |
154154
|------------------------------------------------|---------------------------------------------------------|
155-
| **Azure Portal / Powershell / CLI / REST API** | Backup items go into soft deleted state for **all** modules/API versions |
155+
| **Azure portal / PowerShell / CLI / REST API** | Backup items go into soft deleted state for **all** modules/API versions |
156156

157157
---
158158

@@ -164,13 +164,13 @@ The following table outlines the behavior of the ***Delete Vault*** action acros
164164

165165
| **Client** | **Soft Delete – Disabled / Enabled / Always On** |
166166
|-------------|--------------------------------------------------|
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. |
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. |
168168
| **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. |
169169
| **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. |
170170
| **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. |
171171

172172

173-
# [General Availability](#tab/general-availability)
173+
# [General availability](#tab/general-availability)
174174

175175
| **Clients** | **Soft Delete – Disabled/Enabled/AlwaysOn** |
176176
|---------------------------------------|--------------------------------------------------------|
@@ -187,17 +187,17 @@ The following table describes the behavior of the **_Disable Soft Delete_** acti
187187

188188
| **Client** | **Behavior** |
189189
|-------------|--------------|
190-
| **Azure Portal** | Not allowed. |
190+
| **Azure portal** | Not allowed. |
191191
| **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. |
192192
| **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. |
193193
| **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. |
194194

195195

196-
# [General Availability](#tab/general-availability)
196+
# [General availability](#tab/general-availability)
197197

198198
| **Clients** | **Behavior** |
199199
|------------------------------------------------|------------------------------------------------------------------|
200-
| **Azure Portal / Powershell / CLI / REST API** | Disable soft delete is **not allowed** for any module/API versions |
200+
| **Azure portal / PowerShell / CLI / REST API** | Disable soft delete is **not allowed** for any module/API versions |
201201

202202
---
203203

0 commit comments

Comments
 (0)