Skip to content

Commit 6f93cd8

Browse files
Update articles/backup/secure-by-default.md
Co-authored-by: Abhishek Mallick <[email protected]>
1 parent aa1b4d0 commit 6f93cd8

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/backup/secure-by-default.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ The key benefits of soft delete are:
5555
- **Soft delete and re-registration of backup containers**: You can unregister the backup containers (which you can soft delete) if you've deleted all backup items in the container. You can then register such soft deleted containers to other vaults. This is applicable for applicable workloads only, including SQL in Azure VM backup, SAP HANA in Azure VM backup and backup of on-premises servers.
5656

5757
>[!Note]
58-
> To unregister hybrid backups(using MARS, DPM, or MABS), you need not disable soft delete. Backup data will move to soft deleted state and will be deleted permanently after soft delete retention period expires.
58+
> To unregister hybrid backups(using MARS, DPM, or MABS), you need not disable soft delete. Backup data moves to soft deleted state and is deleted permanently after soft delete retention period expires.
5959
6060
- **Soft delete across workloads**: Soft delete applies to all vaulted datasources alike and is supported for Recovery Services vaults and Backup vaults. Soft delete also applies to operational backups of disks and VM backup snapshots used for instant restores. However, unlike vaulted backups, these snapshots can be directly accessed and deleted before the soft delete period expires. Soft delete is currently not supported for operational backup for Blobs and Azure Files.
6161

0 commit comments

Comments
 (0)