Merge pull request #303089 from Daya-Patil/main

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

Author: v-ccolin

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

@@ -21,6 +21,10 @@ This article summarizes the regional availability, supported scenarios, and limi
 
 Vaulted backups of Azure Data Lake Storage are available in the following regions: France South, India West, West Central US, East Asia, India Central.
 
+>[!Note]
+>- This feature is currently in limited preview and is available in specific regions only. See the [supported regions](azure-data-lake-storage-backup-support-matrix.md#supported-regions).
+>- To enroll in this preview feature, fill [this form](https://forms.office.com/r/sixidTkYb4)  and write to [[email protected]](mailto:[email protected]).
+
 ## Supported storage accounts
 
 The following table lists the supported storage account details:
@@ -47,7 +51,8 @@ Azure Data Lake Storage protection (preview) has the following supported and uns
 - 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. 
 - 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.
 - 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.
-- Blobs are excluded from recovery points if you rename their parent path after creating them via async copy.
+- Blobs are excluded from recovery points if you rename any folder in their parent path when async copy in progress.
+- The backup operation isn't supported for blobs created using async copy. 
 - 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.
 - You can protect the storage account with the vault in another subscription but in the same region as storage account.
 - Archive tier for vault is currently not supported.

articles/backup/azure-data-lake-storage-configure-backup.md

@@ -1,8 +1,8 @@
 ---
-title: Configure Vaulted Backup for Azure Data Lake Storage using Azure Portal (preview)
+title: Configure Vaulted Backup for Azure Data Lake Storage using Azure portal (preview)
 description: Learn how to configure vaulted backup for Azure Data Lake Storage (preview) using Azure portal.
 ms.topic: how-to
-ms.date: 04/16/2025
+ms.date: 07/23/2025
 author: AbhishekMallick-MS
 ms.author: v-mallicka
 # Customer intent: As a cloud administrator, I want to configure vaulted backup for Azure Data Lake Storage, so that I can ensure data protection and recovery capabilities are in place for my storage accounts.
@@ -20,7 +20,9 @@ Before you configure backup for Azure Data Lake Storage, ensure the following pr
 - The target account mustn't have containers with the  names same as the containers in a recovery point; otherwise, the restore operation fails.
 
 >[!Note]
->Vaulted backup restores are only possible to a different storage account.
+>- This feature is currently in limited preview and is available in specific regions only. See the [supported regions](azure-data-lake-storage-backup-support-matrix.md#supported-regions).
+>- To enroll in this preview feature, fill [this form](https://forms.office.com/r/sixidTkYb4)  and write to [[email protected]](mailto:[email protected]).
+>- Vaulted backup restores are only possible to a different storage account.
 
 For more information about the supported scenarios, limitations, and availability, see the [support matrix](azure-data-lake-storage-backup-support-matrix.md).
 
@@ -107,12 +109,12 @@ To configure backup, follow these steps:
 
    | Error | Cause | Recommended action |
    | --- | --- | --- |
-   | **Role assignment not done** | The **Storage account backup contributor** role and the other required roles for the storage account to the vault are not assigned. | Select the roles, and then select **Assign missing roles** to automatically assign the required role to the Backup vault and trigger an auto revalidation. <br><br> If the role propagation takes more than **10 minutes**, then the validation might fail. In this scenario, you need to wait for a few minutes and select Revalidate to retry validation. <br><br> You need to assign the following types of permissions for various operations: <br><br> - **Resource-level** permissions: For backing up a single account within a resource group. <br> - **Resource group** or **Subscription-level** permissions: For backing up multiple accounts within a resource group. <br> - **Higher-level** permissions: For reducing the number of role assignments needed. <br><br> Note that the maximum count of role assignments supported at the subscription level is **4,000**. Learn more [about Azure Role-Based Access Control Limits](/azure/role-based-access-control/troubleshoot-limits). |
+   | **Role assignment not done** | The **Storage account backup contributor** role and the other required roles for the storage account to the vault aren't assigned. | Select the roles, and then select **Assign missing roles** to automatically assign the required role to the Backup vault and trigger an auto revalidation. <br><br> If the role propagation takes more than **10 minutes**, then the validation might fail. In this scenario, you need to wait for a few minutes and select Revalidate to retry validation. <br><br> You need to assign the following types of permissions for various operations: <br><br> - **Resource-level** permissions: For backing up a single account within a resource group. <br> - **Resource group** or **Subscription-level** permissions: For backing up multiple accounts within a resource group. <br> - **Higher-level** permissions: For reducing the number of role assignments needed. <br><br> The maximum count of role assignments supported at the subscription level is **4,000**. Learn more [about Azure Role-Based Access Control Limits](/azure/role-based-access-control/troubleshoot-limits). |
    | **Insufficient permissions for role assignment** | The vault doesn't have the required role to configure backups, and you don't have enough permissions to assign the required role. | Download the role assignment template, and then share with users with permissions to assign roles for storage accounts. |
 
 1. Review the configuration details, and then select **Configure Backup**.
 
-You can track the progress of the backup configuration under **Backup instances**. After the configuration of backup is complete, Azure Backup triggers the backup operation as per the backup policy schedule to create the recovery points. Backup may take a minimum of 30–40 minutes, as backups rely on snapshots, which are taken every 15 minutes and require two snapshots to detect changes before triggering the backup.
+You can track the progress of the backup configuration under **Backup instances**. After the configuration of backup is complete, Azure Backup triggers the backup operation as per the backup policy schedule to create the recovery points. Backup might take a minimum of 30–40 minutes, as backups rely on snapshots, which are taken in every 15 minutes and require two snapshots to detect changes before triggering the backup.
 
 ## Next steps