Blob backup updates

Author: AbhishekMallick01

articles/backup/blob-backup-configure-manage.md

@@ -121,7 +121,7 @@ To configure backup for storage accounts, follow these steps:
 
       - **Role assignment not done**: This indicates that you (the user) have permissions to assign the **Storage account backup contributor** role and the other required roles for the storage account to the vault.
 
-        Select the roles, and then select **Assign missing roles** on the toolbar to automatically assign the required role to the Backup vault, and trigger an auto-revalidation.
+        Select the roles, and then select **Assign missing roles** on the toolbar to automatically assign the required role to the Backup vault, and trigger an autorevalidation.
 
         The role propagation may take some time (up to 10 minutes) causing the revalidation to fail. In this scenario, you need to wait for a few minutes and select **Revalidate** to retry validation.
 
@@ -195,7 +195,7 @@ To start configuring backup:
 
     If validation displays errors (for two of the storage accounts), you haven't assigned the **Storage account backup contributor** role for these [storage accounts](#grant-permissions-to-the-backup-vault-on-storage-accounts). Also, you can assign the required role here, based on your current permissions. The error message can help you understand if you have the required permissions, and take the appropriate action:
 
-    - **Role assignment not done:** This error (as shown for the item _blobbackupdemo3_ in the figure above) indicates that you (the user) have permissions to assign the **Storage account backup contributor** role and the other required roles for the storage account to the vault. Select the roles, and select **Assign missing roles** on the toolbar. This will automatically assign the required role to the backup vault, and also trigger an auto-revalidation.<br><br>At times, role propagation may take a  while (up to 10 minutes) causing the revalidation to fail. In such scenario, please wait for a few minutes and select the ‘Revalidate’ button retry validation.
+    - **Role assignment not done:** This error (as shown for the item _blobbackupdemo3_ in the figure above) indicates that you (the user) have permissions to assign the **Storage account backup contributor** role and the other required roles for the storage account to the vault. Select the roles, and select **Assign missing roles** on the toolbar. This will automatically assign the required role to the Backup vault, and also trigger an autorevalidation.<br><br>At times, role propagation may take a  while (up to 10 minutes) causing the revalidation to fail. In such scenario, please wait for a few minutes and select the ‘Revalidate’ button retry validation.
 
     - **Insufficient permissions for role assignment:** This error (as shown for the item _blobbackupdemo4_ in the figure above)  indicates that the vault doesn’t have the required role to configure backup, and you (the user) don’t have enough permissions to assign the required role. To make the role assignment easier, Backup allows you to download the role assignment template, which you can share with users with permissions to assign roles for storage accounts. To do this, select such storage accounts, and select **Download role assignment template** to download the template.<br><br>Once the roles are assigned, you can share it with the appropriate users. On successful assignment of the role, select **Revalidate** to validate permissions again, and then configure backup.
         >[!NOTE]
@@ -252,7 +252,8 @@ You can configure backup for blobs in a storage account directly from the ‘Dat
 
 # [Vaulted backup](#tab/vaulted-backup)
 
-In storage accounts (for which you've configured vaulted backups), the object replication rules get created under the **Object replication** item in the left pane.
+- In storage accounts (for which you've configured vaulted backups), the object replication rules get created under the **Object replication** item in the left pane.
+- Object replication requires versioning and change-feed capabilities. So, Azure Backup service enables these features on the source storage account.
 
 # [Operational backup](#tab/operational-backup)
 
@@ -311,7 +312,7 @@ To stop backup for a storage account, follow these steps:
 
     ![Stop operational backup](./media/blob-backup-configure-manage/stop-operational-backup.png)
 
-After stopping backup, you may disable other storage data protection capabilities (that are enabled for configuring backup) from the data protection pane of the storage account.
+After stopping backup, you may disable other storage data protection capabilities (enabled for configuring backups) from the data protection pane of the storage account.
 
 
 ## Next steps

articles/backup/blob-backup-overview.md

@@ -2,7 +2,7 @@
 title: Overview of Azure Blobs backup
 description: Learn about Azure Blobs backup.
 ms.topic: conceptual
-ms.date: 02/15/2023
+ms.date: 03/10/2023
 ms.service: backup
 author: jyothisuri
 ms.author: jsuri
@@ -61,7 +61,7 @@ To allow Backup to enable these properties on the storage accounts to be protect
 
 ### Protection using vaulted backup (in preview)
 
-Vaulted backup is configured at the storage account level. However, you can exclude containers that don't need backup. If your storage account has *>100* containers, you need to mandatorily exclude containers to reduce the count to *100* or below. For vaulted backups, the schedule and retention are managed via backup policy. You can set the frequency as *daily* or *weekly*, and specify when the backup recovery points need to be created. You can also configure different retention values for backups taken every day, week, month, or year. The retention rules are evaluated in a pre-determined order of priority. The *yearly* rule has the priority compared to *monthly* and *weekly* rule. Default retention settings are applied if other rules don't qualify.
+Vaulted backup is configured at the storage account level. However, you can exclude containers that don't need backup. If your storage account has *>100* containers, you need to mandatorily exclude containers to reduce the count to *100* or below. For vaulted backups, the schedule and retention are managed via backup policy. You can set the frequency as *daily* or *weekly*, and specify when the backup recovery points need to be created. You can also configure different retention values for backups taken every day, week, month, or year. The retention rules are evaluated in a predetermined order of priority. The *yearly* rule has the priority compared to *monthly* and *weekly* rule. Default retention settings are applied if other rules don't qualify.
 
 In storage accounts (for which vaulted backups are configured), the object replication rules get created under the *object replication* item on the *TOC* blade of the source storage account.
 
@@ -91,7 +91,7 @@ You won't incur any management charges or instance fee when using operational ba
 
 ### Vaulted backup (preview)
 
-Vaulted backup currently doesn't incur any charges with preview release.
+You won't incur backup storage charges or instance fees during the preview. However, you'll incur the source side cost, [associated with Object replication](/storage/blobs/object-replication-overview#billing), on the backed-up source account.
 
 ## Next steps