Merge pull request #281512 from MicrosoftDocs/release-blob-backup

release-blob-backup - 07/24 - 10:00 PM PST/10:30 AM IST

Author: Saisang

articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md

@@ -75,7 +75,8 @@ The following is the request body to configure backup for all blobs within a sto
   }
 }
 ```
-To configure backup with vaulted backup (preview) enabled, refer the below request body.
+
+To configure backup with vaulted backup enabled, refer the below request body.
 
 ```json
 {backupInstanceDataSourceType is Microsoft.Storage/storageAccounts/blobServices
@@ -153,7 +154,8 @@ The [request body](#prepare-the-request-to-configure-blob-backup) that you prepa
   }
 }
 ```
-#### Example request body for vaulted backup (preview)
+
+#### Example request body for vaulted backup
 
 ```json
 {

articles/backup/backup-azure-dataprotection-use-rest-api-create-update-blob-policy.md

@@ -94,7 +94,7 @@ The policy says:
 }
 ```
 
-To configure a backup policy with the vaulted backup (preview), use the following JSON script:
+To configure a backup policy with the vaulted backup, use the following JSON script:
 
 ```json
 {

articles/backup/backup-azure-dataprotection-use-rest-api-restore-blobs.md

@@ -25,7 +25,7 @@ To illustrate the restoration steps in this article, we'll refer to blobs in a s
 
 ## Prepare for Azure Blobs restore
 
-You can now do the restore operation for *operational backup* and *vaulted backup (preview)* for Azure Blobs.
+You can now do the restore operation for *operational backup* and *vaulted backup* for Azure Blobs.
 
 **Choose a backup tier**:
 
@@ -201,7 +201,7 @@ The key points to remember in this scenario are:
 }
 ```
 
-# [Vaulted backup (preview)](#tab/vaulted-backup)
+# [Vaulted backup](#tab/vaulted-backup)
 
 [!INCLUDE [blob-vaulted-backup-restore-restapi.md](../../includes/blob-vaulted-backup-restore-restapi.md)]
 

articles/backup/backup-blobs-storage-account-arm-template.md

@@ -8,7 +8,7 @@ author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
 
-# Quickstart: Back up a storage account with Blob data using an ARM template (preview)
+# Quickstart: Back up a storage account with Blob data using an ARM template
 
 This quickstart describes how to back up a storage account with Azure Blob data with a vaulted backup policy using an ARM template.
 

articles/backup/backup-blobs-storage-account-bicep.md

@@ -8,7 +8,7 @@ author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
 
-# Quickstart: Back up a storage account with Blob data using Azure Backup via a Bicep template (preview)
+# Quickstart: Back up a storage account with Blob data using Azure Backup via a Bicep template
 
 This quickstart describes how to back up a storage account with Azure Blob data with a vaulted backup policy using a Bicep template.
 

articles/backup/backup-blobs-storage-account-cli.md

@@ -60,7 +60,7 @@ After creating a vault, let's create a Backup policy to protect Azure Blobs in a
 
 ## Create a backup policy
 
-You can create a backup policy for *operational backup* and *vaulted backup (preview)* for Azure Blobs using Azure CLI.
+You can create a backup policy for *operational backup* and *vaulted backup* for Azure Blobs using Azure CLI.
 
 **Choose a backup tier**:
 
@@ -170,7 +170,7 @@ az dataprotection backup-policy create -g testBkpVaultRG --vault-name TestBkpVau
   }
 ```
 
-# [Vaulted backup (preview)](#tab/vaulted-backup)
+# [Vaulted backup](#tab/vaulted-backup)
 
 [!INCLUDE [blob-backup-create-policy-cli.md](../../includes/blob-backup-create-policy-cli.md)]
 

articles/backup/backup-blobs-storage-account-ps.md

@@ -108,7 +108,7 @@ blobBkpPolicy       Microsoft.DataProtection/backupVaults/backupPolicies
 
 $blobBkpPol = Get-AzDataProtectionBackupPolicy -ResourceGroupName "testBkpVaultRG" -VaultName $TestBkpVault.Name -Name "blobBkpPolicy"
 ```
-# [Vaulted Backup (preview)](#tab/vaulted-backup)
+# [Vaulted Backup](#tab/vaulted-backup)
 
 [!INCLUDE [blob-vaulted-backup-create-policy-ps.md](../../includes/blob-vaulted-backup-create-policy-ps.md)]
 
@@ -138,7 +138,7 @@ blobrg-PSTestSA-3df6ac08-9496-4839-8fb5-8b78e594f166 Microsoft.DataProtection/ba
 > [!IMPORTANT]
 > Once a storage account is configured for blobs backup, a few capabilities are affected, such as change feed and delete lock. [Learn more](blob-backup-configure-manage.md#effects-on-backed-up-storage-accounts).
 
-# [Vaulted Backup (preview)](#tab/vaulted-backup)
+# [Vaulted Backup](#tab/vaulted-backup)
 
 [!INCLUDE [blob-vaulted-backup-prepare-request-ps.md](../../includes/blob-vaulted-backup-prepare-request-ps.md)]
 

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

@@ -16,9 +16,9 @@ Azure Backup allows you to configure operational and vaulted backups to protect
 
 # [Operational backup](#tab/operational-backup)
 
-- Operational backup of blobs is a local backup solution that maintains data for a specified duration in the source storage account itself. This solution doesn't maintain an additional copy of data in the vault. This solution allows you to retain your data for restore for up to 360 days. Long retention durations may, however, lead to longer time taken during the restore operation.
-- The solution can be used to perform restores to the source storage account only and may result in data being overwritten.
-- If you delete a container from the storage account by calling the *Delete Container operation*, that container can't be restored with a restore operation. Rather than deleting an entire container, delete individual blobs if you may want to restore them later. Also, Microsoft recommends enabling soft delete for containers, in addition to operational backup, to protect against accidental deletion of containers.
+- Operational backup of blobs is a local backup solution that maintains data for a specified duration in the source storage account itself. This solution doesn't maintain an additional copy of data in the vault. This solution allows you to retain your data for restore for up to 360 days. Long retention durations can, however, lead to longer time taken during the restore operation.
+- The solution can be used to perform restores to the source storage account only and can result in data being overwritten.
+- If you delete a container from the storage account by calling the *Delete Container operation*, that container can't be restored with a restore operation. Rather than deleting an entire container, delete individual blobs if you want to restore them later. Also, Microsoft recommends enabling soft delete for containers, in addition to operational backup, to protect against accidental deletion of containers.
 - Ensure that the **Microsoft.DataProtection** provider is registered for your subscription.
 
 For more information about the supported scenarios, limitations, and availability, see the [support matrix](blob-backup-support-matrix.md).
@@ -53,12 +53,12 @@ To assign the required role for storage accounts that you need to protect, follo
 >[!NOTE]
 >You can also assign the roles to the vault at the Subscription or Resource Group levels according to your convenience.
 
-1. In the storage account that needs to be protected, go to the **Access Control (IAM)** tab on the left navigation pane.
+1. In the storage account that needs to be protected, go to the **Access Control (IAM)** tab on the left navigation blade.
 1. Select **Add role assignments** to assign the required role.
 
     ![Add role assignments](./media/blob-backup-configure-manage/add-role-assignments.png)
 
-1. In the Add role assignment pane:
+1. In the Add role assignment blade:
 
     1. Under **Role**, choose **Storage Account Backup Contributor**.
     1. Under **Assign access to**, choose **User, group or service principal**.
@@ -70,107 +70,17 @@ To assign the required role for storage accounts that you need to protect, follo
         >[!NOTE]
         >The role assignment might take up to 30 minutes to take effect.
 
-## Create a backup policy
 
-A backup policy defines the schedule and frequency of the recovery points creation, and its retention duration in the Backup vault. You can use a single backup policy for your vaulted backup, operational backup, or both. You can use the same backup policy to configure backup for multiple storage accounts to a vault.
+[!INCLUDE [blob-backup-azure-portal-create-policy.md](../../includes/blob-backup-azure-portal-create-policy.md)]
 
-To create a backup policy, follow these steps:
 
-1. Go to **Backup center**, and then select **+ Policy**. This takes you to the create policy experience.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/add-policy-inline.png" alt-text="Screenshot shows how to initiate adding backup policy for vaulted blob backup." lightbox="./media/blob-backup-configure-manage/add-policy-expanded.png":::
-
-2. Select the *data source type* as **Azure Blobs (Azure Storage)**, and then select **Continue**.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/datasource-type-selection-for-vaulted-blob-backup.png" alt-text="Screenshot shows how to select datasource type for vaulted blob backup.":::
-
-3. On the **Basics** tab, enter a name for the policy and select the vault you want this policy to be associated with.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/add-vaulted-backup-policy-name.png" alt-text="Screenshot shows how to add vaulted blob backup policy name.":::
-
-   You can view the details of the selected vault in this tab, and then select **continue**.
- 
-4. On the **Schedule + retention** tab, enter the *backup details* of the data store, schedule, and retention for these data stores, as applicable.
-
-   1. To use the backup policy for vaulted backups, operational backups, or both, select the corresponding checkboxes.
-   1. For each data store you selected, add or edit the schedule and retention settings:
-      - **Vaulted backups**: Choose the frequency of backups between *daily* and *weekly*, specify the schedule when the backup recovery points need to be created, and then edit the default retention rule (selecting **Edit**) or add new rules to specify the retention of recovery points using a *grandparent-parent-child* notation.
-      - **Operational backups**: These are continuous and don't require a schedule. Edit the default rule for operational backups to specify the required retention.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/define-vaulted-backup-schedule-and-retention-inline.png" alt-text="Screenshot shows how to configure vaulted blob backup schedule and retention." lightbox="./media/blob-backup-configure-manage/define-vaulted-backup-schedule-and-retention-expanded.png":::
-
-5. Go to **Review and create**.
-6. Once the review is complete, select **Create**.
-
-## Configure backups
-
-You can configure backup for one or more storage accounts in an Azure region if you want them to back up to the same vault using a single backup policy.
-
-To configure backup for storage accounts, follow these steps:
-
-1. Go to **Backup center** > **Overview**, and then select **+ Backup**.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/start-vaulted-backup.png" alt-text="Screenshot shows how to initiate vaulted blob backup.":::
-
-2. On the **Initiate: Configure Backup** tab, choose **Azure Blobs (Azure Storage)** as the **Datasource type**.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/choose-datasource-for-vaulted-backup.png" alt-text="Screenshot shows how to initiate configuring vaulted blob backup.":::
-
-3. On the **Basics** tab, specify **Azure Blobs (Azure Storage)** as the **Datasource type**, and then select the *Backup vault* that you want to associate with your storage accounts.
-
-   You can view details of the selected vault on this tab, and then select **Next**.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/select-datasource-type-for-vaulted-backup.png" alt-text="Screenshot shows how to select datasource type to initiate vaulted blob backup.":::
- 
-4. Select the *backup policy* that you want to use for retention.
-
-   You can view the details of the selected policy. You can also create a new backup policy, if needed. Once done, select **Next**.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/select-policy-for-vaulted-backup.png" alt-text="Screenshot shows how to select policy for vaulted blob backup.":::
-
-5. On the **Datasources** tab, select the *storage accounts* you want to back up.
-
-   :::image type="content" source="./media/blob-backup-configure-manage/select-storage-account-for-vaulted-backup.png" alt-text="Screenshot shows how to select storage account for vaulted blob backup." lightbox="./media/blob-backup-configure-manage/select-storage-account-for-vaulted-backup.png":::
-
-   You can select multiple storage accounts in the region to back up using the selected policy. Search or filter the storage accounts, if required.
-  
-   If you've chosen the vaulted backup policy in step 4, you can also select specific containers to backup. Click "Change" under the "Selected containers" column. In     the context blade, choose "browse containers to backup" and unselect the ones you don't want to backup.
-
-6. When you select the storage accounts and containers to protect, Azure Backup performs the following validations to ensure all prerequisites are met. The **Backup readiness** column shows if the Backup vault has enough permissions to configure backups for each storage account.
-
-   1. Validates that the Backup vault has the required permissions to configure backup (the vault has the **Storage account backup contributor** role on all the selected storage accounts. If validation shows errors, then the selected storage accounts don't have **Storage account backup contributor** role. You can assign the required role, based on your current permissions. The error message helps you understand if you have the required permissions, and take the appropriate action:
-
-      - **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 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.
-
-      - **Insufficient permissions for role assignment**: This indicates that the vault doesn't have the required role to configure backups, and you (the user) don't have enough permissions to assign the required role. To make the role assignment easier, Azure 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 the storage accounts, and then select **Download role assignment template** to download the template. Once the role assignments are complete, select **Revalidate** to validate the permissions again, and then configure backup.
-
-        :::image type="content" source="./media/blob-backup-configure-manage/vaulted-backup-role-assignment-success.png" alt-text="Screenshot shows that the role assignment is successful.":::
-
-        >[!Note]
-        >The template contains details for selected storage accounts only. So, if there are multiple users that need to assign roles for different storage accounts, you can select and download different templates accordingly.
-
-    1. In case of vaulted backups, validates that the number of containers to be backed up is less than *100*. By default, all containers are selected; however, you can exclude containers that shouldn't be backed up. If your storage account has *>100* containers, you must exclude containers to reduce the count to *100 or below*.
-
-      >[!Note]
-      >In case of vaulted backups, the storage accounts to be backed up must contain at least *1 container*. If the selected storage account doesn't contain any containers or if no containers are selected, you may get an error while configuring backups.
-
-7. Once validation succeeds, open the **Review and configure** tab.
-
-8. Review the details on the **Review + configure** tab and select **Next** to initiate the *configure backup* operation.
-
-You'll receive notifications about the status of configuring protection and its completion.
+[!INCLUDE [blob-backup-azure-portal-configure-backup.md](../../includes/blob-backup-azure-portal-configure-backup.md)]
 
 ### Using Data protection settings of the storage account to configure backup
 
 You can configure backup for blobs in a storage account directly from the ‘Data Protection’ settings of the storage account. 
 
-1. Go to the storage account for which you want to configure backup for blobs, and then go to **Data Protection** in left pane (under **Data management**).
+1. Go to the storage account for which you want to configure backup for blobs, and then go to **Data Protection** in left blade (under **Data management**).
 
 1. In the available data protection options, the first one allows you to enable operational backup using Azure Backup.
 
@@ -188,7 +98,7 @@ You can configure backup for blobs in a storage account directly from the ‘Dat
         ![Enable operational backup with Azure Backup](./media/blob-backup-configure-manage/enable-operational-backup-with-azure-backup.png)
 
 
-        1. On selecting **Manage identity**, brings you to the Identity pane of the storage account. 
+        1. On selecting **Manage identity**, brings you to the Identity blade of the storage account. 
 
         1. Select **Add role assignment** to initiate the role assignment.
 
@@ -208,13 +118,13 @@ You can configure backup for blobs in a storage account directly from the ‘Dat
 
             ![Finish role assignment](./media/blob-backup-configure-manage/finish-role-assignment.png)
 
-        1. Select the cancel icon (**x**) on the top right corner to return to the **Data protection** pane of the storage account.<br><br>Once back, continue configuring backup.
+        1. Select the cancel icon (**x**) on the top right corner to return to the **Data protection** blade of the storage account.<br><br>Once back, continue configuring backup.
 
 ## Effects on backed-up storage accounts
 
 # [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 blade.
 - 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)
@@ -242,7 +152,7 @@ Once backup is configured, changes taking place on block blobs in the storage ac
 
 ## Manage backups
 
-You can use Backup Center as your single pane of glass for managing all your backups. Regarding backup for Azure Blobs, you can use Backup Center to do the following:
+You can use Backup Center as your single blade of glass for managing all your backups. Regarding backup for Azure Blobs, you can use Backup Center to do the following:
 
 - As we've seen above, you can use it for creating Backup vaults and policies. You can also view all vaults and policies under the selected subscriptions.
 - Backup Center gives you an easy way to monitor the state of protection of protected storage accounts as well as storage accounts for which backup isn't currently configured.
@@ -274,7 +184,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 (enabled for configuring backups) from the data protection pane of the storage account.
+After stopping backup, you can disable other storage data protection capabilities (enabled for configuring backups) from the data protection blade of the storage account.
 
 
 ## Next steps