Skip to content

Commit ef32f18

Browse files
Merge pull request #300146 from AbhishekMallick01/May-21-2025-ADLS
ADLS backup - Supported scenario updates
2 parents b575e35 + ce1875b commit ef32f18

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Support matrix for Azure Data Lake Storage Vaulted Backup (preview)
33
description: Learn about the regional availability, supported scenarios, and limitations for vaulted backups of Azure Data Lake Storage (preview).
44
ms.topic: reference
5-
ms.date: 05/19/2025
5+
ms.date: 05/21/2025
66
ms.custom: references_regions, engagement-fy24
77
ms.service: azure-backup
88
author: jyothisuri
@@ -42,9 +42,9 @@ Azure Data Lake Storage protection (preview) has the following supported and uns
4242

4343
- Any new containers that get created after backup configuration for the storage account aren't backed up automatically. To enable the backup operation for the new containers, modify the protection of the storage account.
4444
- The storage accounts to be backed up must contain a *minimum of one container*. If the storage account doesn't contain any containers or if no containers are selected, an error might appear when you configure backup.
45-
- Object Replication fails to register changes when a storage account or container is deleted and recreated with the same name between two consecutive backups, causing recovery points to retain older blobs and versions. Similarly, when you rename the parent path of blobs created via async copy, those blobs are excluded from recovery points.
45+
- Object Replication fails to register changes when a storage account or container is deleted and recreated with the same name between two consecutive backups, causing recovery points to retain older blobs and versions.
46+
- Blobs are excluded from recovery points if you rename their parent path after creating them via async copy.
4647
- Backup vaults with User-Assigned Managed Identity (UAMI) aren't compatible with Azure Blob Vaulted backups. Only System-Assigned Managed Identity (SAMI) works, because the vault needs to access the storage account where the blobs are stored. The vault uses its system-assigned managed identity for this access.
47-
- Enabling backups isn't supported for the blob container that are configured with native replication using data factory.
4848
- You can protect the storage account with the vault in another subscription but in the same region as storage account.
4949
- Archive tier for vault is currently not supported.
5050

0 commit comments

Comments
 (0)