Merge pull request #309353 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-11 12:00 UTC

Author: learn-build-service-prod[bot]

articles/backup/backup-azure-files-faq.yml

@@ -112,7 +112,11 @@ sections:
           Will the retention policy delete a recovery point selected for restore  before the restore operation completes?
         answer: |
           No. Azure Backup takes a lease on the recovery point during restore, ensuring it isn't deleted before completion.
-
+          
+      - question: |
+          What are the permissions used by Azure Backup during backup and restore operation?
+        answer: |
+          Azure Backup uses key-based access for backup and restore operations. Ensure that you [enable keys access](../storage/common/shared-key-authorization-prevent.md?tabs=portal) on both source and target storage accounts, even if using identity-based access is configured.
 
   - name: Manage backup
     questions:

articles/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md

@@ -2,7 +2,7 @@
 title: Troubleshoot Azure Backup failures caused by agent or extension issues
 description: Symptoms, causes, and resolutions of Azure Backup failures related to agent, extension, and disks.
 ms.topic: troubleshooting
-ms.date: 04/15/2025
+ms.date: 11/12/2025
 ms.service: azure-backup
 ms.custom: engagement-fy24
 ms.reviewer: sooryar
@@ -168,8 +168,8 @@ After you register and schedule a VM for the Azure Backup service, Backup initia
   **C:\Packages\Plugins\Microsoft.Azure.RecoveryServices.VMSnapshot\\<extension version\>\iaasvmprovider.dll** <br>   To resolve this issue, check if the module is compatible with x86 (32-bit)/x64 (64-bit) version of _regsvr32.exe_, and then follow these steps:
 
   1. In the affected VM, go to **Control panel** -> **Program and features**.
-  1. Uninstall **Visual C++ Redistributable x64** for **Visual Studio 2013**.
-  1. Reinstall **Visual C++ Redistributable** for **Visual Studio 2013** in the VM. To install, follow these steps:
+  1. Uninstall **Visual C++ Redistributable (x64)** for **Visual Studio 2015**.
+  1. Reinstall **Visual C++ Redistributable (x64)** for **Visual Studio 2015** in the VM. To install, follow these steps:
      1. Go to the folder: **C:\Packages\Plugins\Microsoft.Azure.RecoveryServices.VMSnapshot\\<LatestVersion\>**
      1. Search and run the **vcredist2013_x64** file to install.
   1. Retry the backup operation.

articles/backup/backup-azure-vms-troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot backup errors with Azure VMs
 description: In this article, learn how to troubleshoot errors encountered with backup and restore of Azure virtual machines.
 ms.reviewer: srinathv
 ms.topic: troubleshooting
-ms.date: 08/13/2025
+ms.date: 11/12/2025
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -346,12 +346,12 @@ Error code: ExtensionSnapshotFailedNoSecureNetwork <br/> Error message: The snap
 * Identify all versions of the .NET Framework present in your system. They're present under the hierarchy of registry key **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft**.
 * For each .NET Framework present in the registry key, add the following key: <br> **SchUseStrongCrypto"=dword:00000001**. </ol>
 
-### ExtensionVCRedistInstallationFailure - The snapshot operation failed because of failure to install Visual C++ Redistributable for Visual Studio 2012
+### ExtensionVCRedistInstallationFailure - The snapshot operation failed because of failure to install Visual C++ Redistributable for Visual Studio 2015
 
-Error code: ExtensionVCRedistInstallationFailure <br/> Error message: The snapshot operation failed because of failure to install Visual C++ Redistributable for Visual Studio 2012.
+Error code: ExtensionVCRedistInstallationFailure <br/> Error message: The snapshot operation failed because of failure to install Visual C++ Redistributable for Visual Studio 2015.
 
 * Navigate to `C:\Packages\Plugins\Microsoft.Azure.RecoveryServices.VMSnapshot\agentVersion` and install vcredist2013_x64.<br/>Make sure that the registry key value that allows the service installation is set to the correct value. That is, set the **Start** value in **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Msiserver** to **3** and not **4**. <br><br>If you still have issues with installation, restart the installation service by running **MSIEXEC /UNREGISTER** followed by **MSIEXEC /REGISTER** from an elevated command prompt.
-* Check the event log to verify if you're noticing access related issues. For example: *Product: Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005 -- Error 1401.Could not create key: Software\Classes.  System error 5.  Verify that you have sufficient access to that key, or contact your support personnel.* <br><br> Ensure the administrator or user account has sufficient permissions to update the registry key **HKEY_LOCAL_MACHINE\SOFTWARE\Classes**. Provide sufficient permissions and restart the Windows Azure Guest Agent.<br><br> <li> If you have antivirus products in place, ensure they have the right exclusion rules to allow the installation.
+* Check the event log to verify if you're noticing access related issues. For example: *Product: Microsoft Visual C++ 2015 x64 Minimum Runtime - 12.0.21005 -- Error 1401.Could not create key: Software\Classes.  System error 5.  Verify that you have sufficient access to that key, or contact your support personnel.* <br><br> Ensure the administrator or user account has sufficient permissions to update the registry key **HKEY_LOCAL_MACHINE\SOFTWARE\Classes**. Provide sufficient permissions and restart the Windows Azure Guest Agent.<br><br> <li> If you have antivirus products in place, ensure they have the right exclusion rules to allow the installation.
 
 ### UserErrorRequestDisallowedByPolicy - An invalid policy is configured on the VM which is preventing Snapshot operation
 

articles/backup/backup-reports-email.md

@@ -2,7 +2,7 @@
 title: Email Azure Backup Reports
 description: Create automated tasks to receive periodic reports via email
 ms.topic: how-to
-ms.date: 12/12/2024
+ms.date: 12/10/2025
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -20,15 +20,17 @@ Using the **Email Report** feature available in Backup Reports, you can create a
 
 To configure email tasks via Backup Reports, perform the following steps:
 
-1.	Go to **Business Continuity Center** > **Backup Reports** and click on the **Email Report** tab.
-2.	Create a task by specifying the following information:
+1.	Go to **Resiliency** > **Monitoring + Reporting** > **Reports**.
+1. On the **Reports** pane, select **Backup Reports (consolidated)**.
+1. On the **Backup Reports (consolidated)** pane, select the **Email Report** tab.
+1.	Create a task by specifying the following information:
     * **Task Details** - The name of the logic app to be created, and the subscription, resource group, and location in which it should be created. Note that the logic app can query data across multiple subscriptions, resource groups, and locations (as selected in the Report Filters section), but is created in the context of a single subscription, resource group and location.
     * **Data To Export** - The tab which you wish to export. You can either create a single task app per tab, or email all tabs using a single task, by selecting the **All Tabs** option.
     * **Email options**: The email frequency, recipient email ID(s), and the email subject.
 
     :::image type="content" source="./media/backup-azure-configure-backup-reports/email-tab.png" alt-text="Screenshot shows the Email tab." lightbox="./media/backup-azure-configure-backup-reports/email-tab.png":::
 
-3.	After you click **Submit** and **Confirm**, the logic app will get created. The deployed logic app uses the [Consumption plan](../../articles/logic-apps/single-tenant-overview-compare.md#logic-app-workflow-types-and-environments) pricing. The logic app and the associated API connections are created with the tag **UsedByBackupReports: true** for easy discoverability. You'll need to perform a one-time authorization step for the logic app to run successfully, as described in the section below.
+1.	After you select **Submit** and **Confirm**, the logic app will get created. The deployed logic app uses the [Consumption plan](../../articles/logic-apps/single-tenant-overview-compare.md#logic-app-workflow-types-and-environments) pricing. The logic app and the associated API connections are created with the tag **UsedByBackupReports: true** for easy discoverability. You'll need to perform a one-time authorization step for the logic app to run successfully, as described in the section below.
 
 > [!NOTE]
 > Support for Backup vault workloads (Azure Database for PostgreSQL Server, Azure Blobs, Azure Disks) is added to the logic app templates in April 2023. So, if you've deployed these logic apps on an earlier date, you'll have to redeploy these using the above steps if you want to see data for Backup vault workloads in your email reports.
@@ -44,7 +46,7 @@ To perform the authorization, follow the steps below:
 
     :::image type="content" source="./media/backup-azure-configure-backup-reports/logic-apps.png" alt-text="Screenshot shows the Logic Apps." lightbox="./media/backup-azure-configure-backup-reports/logic-apps.png":::
 
-3.	Click on the **API connections** menu item.
+3.	Select the **API connections** menu item.
 
     :::image type="content" source="./media/backup-azure-configure-backup-reports/api-connections.png" alt-text="Screenshot shows the API Connections." lightbox="./media/backup-azure-configure-backup-reports/api-connections.png":::
 
@@ -62,7 +64,7 @@ To perform the authorization, follow the steps below:
 
 * All the charts and graphs shown in the portal are available as inline content in the email. [Learn more](configure-reports.md) about the information shown in Backup Reports.
 * The grids shown in the portal are available as *.csv attachments in the email.
-* The data shown in the email uses all the report-level filters selected by the user in the report, at the time of creating the email task.
+* The data shown in the email uses the report-level filters selected by the user in the report, at the time of creating the email task.
 * Tab-level filters such as **Backup Instance Name**, **Policy Name** and so on, aren't applied. The only exception to this is the **Retention Optimizations** grid in the **Optimize** tab, where the filters for **Daily**, **Weekly**, **Monthly** and **Yearly** RP retention are applied.
 * The time range and aggregation type (for charts) are based on the user’s time range selection in the reports. For example, if the time range selection is last 60 days (translating to weekly aggregation type), and email frequency is daily, the recipient will receive an email every day with charts spanning data taken over the last 60-day period, with data aggregated at a weekly level.
 
@@ -74,7 +76,7 @@ If you aren't receiving emails as expected even after successful deployment of t
 
 * This issue could be occurring because the Outlook API connector isn't authorized. To authorize the connection, follow the authorization steps provided above.
 
-* This issue could also be occurring if you've specified an incorrect email recipient while creating the logic app. To verify that the email recipient has been specified correctly, you can go to the logic app in the Azure portal, open the Logic App designer and select email step to see whether the correct email IDs are being used.
+* This issue could also be occurring if you've specified an incorrect email recipient while creating the logic app. To verify that the email recipient has been specified correctly, you can go to the logic app in the Azure portal, open the Logic App designer, and select email step to see whether the correct email IDs are being used.
 
 ### Scenario 2: Receiving an error email that says that the logic app failed to execute to completion
 
@@ -86,7 +88,7 @@ To troubleshoot this issue:
 
 ### Scenario 3: Error in authorizing Microsoft 365 API connection
 
-When attempting to authorize the Microsoft 365 API connection, you might see an error of the form _Test connection failed. Error 'REST API is not yet supported for this mailbox. This error can occur for sandbox (test) accounts or for accounts that are on a dedicated (on-premises) mail server._ 
+When attempting to authorize the Microsoft 365 API connection, you might see an error of the form _Test connection failed. Error 'REST API isn't yet supported for this mailbox. This error can occur for sandbox (test) accounts or for accounts that are on a dedicated (on-premises) mail server._ 
 
 This error can occur if the mailbox is on a dedicated Microsoft Exchange Server and isn't a valid Office 365 mailbox. [Learn more](/connectors/office365/#common-errors)
 
@@ -114,19 +116,19 @@ To update the authentication type for the Office 365 connection via the Azure po
 
    Learn about [how to authorize the Azure Monitor Logs connection](#authorize-connections-to-azure-monitor-logs-and-office-365).
 
-1. Once deployed, go to the logic app in the Azure portal and click **Logic app designer** from the menu.
+1. Once deployed, go to the logic app in the Azure portal and select **Logic app designer** from the menu.
 
-   :::image type="content" source="./media/backup-azure-configure-backup-reports/logic-app-designer-inline.png" alt-text="Screenshot showing to click Logic app designer." lightbox="./media/backup-azure-configure-backup-reports/logic-app-designer-expanded.png":::
+   :::image type="content" source="./media/backup-azure-configure-backup-reports/logic-app-designer-inline.png" alt-text="Screenshot shows the selection of Logic app designer." lightbox="./media/backup-azure-configure-backup-reports/logic-app-designer-expanded.png":::
 
 1. Locate the places where the Office 365 action is used.
 
    You'll find two Office 365 actions used, both at the bottom of the flow.
 
    :::image type="content" source="./media/backup-azure-configure-backup-reports/office-365-change-connection.png" alt-text="Screenshot showing Office 365 change connection.":::
 
-1. Click **Change connection** and click the *information icon*.
+1. Select **Change connection** and select the *information icon*.
 
-   :::image type="content" source="./media/backup-azure-configure-backup-reports/email-information-icon.png" alt-text="Screenshot showing to click information icon.":::
+   :::image type="content" source="./media/backup-azure-configure-backup-reports/email-information-icon.png" alt-text="Screenshot shows how to select information icon.":::
 
 1. A popup opens where you can select the authentication type for GCC High.
 
@@ -136,11 +138,11 @@ Once you select the correct authentication type in all the places where the Offi
 
 You can also directly update the ARM template, which is used for deploying the logic app, to ensure that the GCC High endpoint is used for authorization. Follow these steps:
 
-1. Go to the **Email Report** tab, provide the required inputs, and then click **Submit**.
+1. Go to the **Email Report** tab, provide the required inputs, and then select **Submit**.
 
    :::image type="content" source="./media/backup-azure-configure-backup-reports/view-template-inline.png" alt-text="View email template." lightbox="./media/backup-azure-configure-backup-reports/view-template-expanded.png":::
 
-1. Click **View template**.
+1. Select **View template**.
 
    This opens up the ARM template json which you can download and edit.
 

articles/backup/blob-backup-faq.yml

@@ -0,0 +1,45 @@
+### YamlMime:FAQ
+metadata:
+    title: Frequently Asked Questions About Azure Blob Backup
+    description: 'Learn how to answer common questions about Azure Blob Backup.'
+    ms.topic: faq
+    ms.service: azure-backup
+    ms.date: 12/11/2025
+    author: AbhishekMallick-MS
+    ms.author: v-mallicka
+    ms.reviewer: v-mallicka
+    ms.custom: engagement-fy24
+
+title: Frequently asked questions about Azure Blob Backup
+summary: This article answers frequently asked questions about Azure Blob Backup. For more information on the Azure Blob backup region availability, supported scenarios, and limitations, see the [support matrix](blob-backup-support-matrix.md).
+
+sections:
+  - name: Backup
+    questions:
+      - question: |
+          Why does Azure Backup require to keep all versions for Blob backups?
+        answer: |
+          Azure Backup doesn’t manage blob versioning because it’s a storage account feature. When you enable vaulted backup, Azure Backup uses the Object Replication Service (ORS) to replicate blobs, including all versions, to the Backup Vault. The Backup Vault applies retention policies, such as 42 days, at the backup layer and not at the source storage account. Azure Backup doesn't change versioning settings in the storage account, as there might be independent compliance or operational requirements for retaining versions.
+
+      - question: |
+          Does Backup vault reconcile or delete older blob versions in the source account?
+        answer: |
+          No, the Backup vault doesn't delete or reconcile blob versions in the source storage account. The retention policy applies only to restore points stored in the vault. For blob version cleanup in the source account, manage it separately using Lifecycle Management (LCM) policies or manual configuration.
+
+      - question: |
+          Can I align blob versioning retention with my backup policy, such as 42 days?
+        answer: |
+          Yes, you can configure blob version retention in the storage account, but it works independently of the backup policy.  
+
+          - For operational backup, set version retention to backup retention plus seven days. For example, if backup retention is 30 days, set version retention to 37 days.
+
+          - For vaulted backup only, reduce version retention after the first successful backup. We recommend you to keep versions for at least seven days after backup completion, or longer for large accounts with frequent changes.
+
+          - If you use both operational and vaulted backup, apply the higher of the two retention requirements.
+
+additionalContent: |
+  ## Related content
+
+  - [Create a backup policy for Azure Blob using REST API](backup-azure-dataprotection-use-rest-api-create-update-blob-policy.md).
+  - [Back up Azure Blob using REST API](backup-azure-dataprotection-use-rest-api-backup-blobs.md).
+  - [Restore Azure Blob using REST API](backup-azure-dataprotection-use-rest-api-restore-blobs.md).

articles/backup/blob-backup-support-matrix.md

@@ -78,6 +78,7 @@ Operational backup of blobs uses blob point-in-time restore, blob versioning, so
 - Enabling backups isn't supported for the blob container that are configured with native replication using data factory.
 - The protection of  a container that is part of any object replication isn't supported, either as a source or destination. Attempting to back up such a container will result in backup failure.
 - Containers with **legal hold** enabled aren't supported.
+- If your storage account is large or contains huge number of versions, the first backup can take multiple days to complete. 
 
 
 ---

articles/backup/media/backup-azure-configure-backup-reports/email-tab.png

@@ -20,6 +20,7 @@ You can restore an entire File Share or specific files on the share. You can res
 
 >[!NOTE]
 >- Azure Files restore is only supported within the same subscription when using PowerShell or CLI.
+>- Cross Region Restore is not supported using PowerShell or CLI.
 >- Azure Backup now supports restoring multiple files or folders to the original or alternate Location using PowerShell. Refer to [this section](#restore-multiple-files-or-folders-to-original-or-alternate-location) of the document to learn how.
 
 ## Fetch recovery points