Update azure-data-lake-storage-configure-backup.md

Author: AbhishekMallick-MS

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

@@ -1,5 +1,5 @@
 ---
-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: 07/23/2025
@@ -109,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