Update azure-data-lake-storage-backup-support-matrix.md

Author: Daya-Patil

articles/backup/azure-data-lake-storage-backup-support-matrix.md

@@ -63,7 +63,12 @@ Azure Data Lake Storage protection has the following supported and unsupported s
 - Archive tier for vault is currently not supported.
 - Azure Data Lake Storage accounts support both Blob and Data File System (DFS) APIs. The system captures operations through Change Feed and uses directory snapshots to ensure consistent recovery.
 - Vaulted Backup doesn’t support cross-container data moves because backup policies are container-specific. If you move data between containers, the replication consistency breaks.
-- When expiry is set on blobs via SetBlobExpiry API or PutBlob/PutBlock options. Once expired, expired blobs remain in restore points, creating inconsistencies in future restore points. Recommendation is to not use blob expiry.
+- When blob expiry is configured—either during creation using PutBlob or PutBlockList, or later via the SetBlobExpiry API — the following behaviors apply for storage accounts with Vaulted Backup enabled:
+  - Existing Blobs with Expiry Date: These blobs will continue to exhibit the current behavior: once expired, they remain in existing restore points, which can lead to inconsistencies in future restore points.
+  - Future Expiry Settings: Any attempt to set expiry using SetBlobExpiry will fail for storage accounts configured with Vaulted Backup. This restriction ensures restore point integrity going forward.
+- When Vaulted Backup is enabled:
+  - Soft Delete: Objects can still be soft-deleted as expected.
+  - Undelete: Restore from soft-deleted state is not supported while Vaulted Backup is active. Undelete will only work if Vaulted Backup is disabled first. Re-enabling Vaulted Backup after disabling will trigger a full backup.
 - Storage accounts upgraded from FNS to HNS are not supported for backup.
 - SFTP-enabled & NFS accounts are not supported for backup. Backup jobs may stall if SFTP-uploaded blobs encountered.
 - $web container cannot be restored as $web on the target. Use the renameTo option and restore it with a different container name.