Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into fxl---remove-reddison

Author: flang-msft

.openpublishing.redirection.json

@@ -990,6 +990,11 @@
       "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-configure-compute",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge.md",
+      "redirect_url": "/articles/databox-online/azure-stack-edge-gpu-kubernetes-workload-management",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/databox-online/azure-stack-edge-system-requirements.md",
       "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-system-requirements",

articles/automation/automation-runbook-types.md

@@ -26,7 +26,7 @@ The Azure Automation Process Automation feature supports several types of runboo
 To learn about the process automation environment, see [Runbook execution in Azure Automation](automation-runbook-execution.md).
 
 > [!NOTE]
-> Azure Automation will follow the support lifecycle of PowerShell and Python language versions in accordance with the timelines published by parent the products, [PowerShell](/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.3&preserve-view=true#powershell-end-of-support-dates) and [Python](https://devguide.python.org/versions/), respectively. We recommend that you use runbooks with supported language versions.
+> Azure Automation will follow the support lifecycle of PowerShell and Python language versions in accordance with the timelines published by the parent products, [PowerShell](/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.3&preserve-view=true#powershell-end-of-support-dates) and [Python](https://devguide.python.org/versions/), respectively. We recommend that you use runbooks with supported language versions.
 
 Take into account the following considerations when determining which type to use for a particular runbook:
 
@@ -43,7 +43,7 @@ The PowerShell version is determined by the **Runtime Version** specified.
 The same Azure sandbox and Hybrid Runbook Worker can execute multiple **PowerShell** runbooks targeting different runtime versions side by side.
 
 > [!NOTE]
-> - Currently, PowerShell 7.4 runtime version is supported for both Cloud and Hybrid jobs in all Public regions except Brazil Southeast and Gov clouds. 
+> - Currently, PowerShell 7.4 runtime version is supported for both Cloud and Hybrid jobs in all Public regions except Brazil Southeast and Gov clouds.
 > - At the time of runbook execution, if you select **Runtime Version** as **7.4**, PowerShell modules targeting 7.4 runtime version is used and if you select **Runtime Version** as **5.1**, PowerShell modules targeting 5.1 runtime version is used.
 
 Ensure that you select the right Runtime Version for modules.

articles/azure-netapp-files/replication.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 07/14/2025
+ms.date: 11/25/2025
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -33,7 +33,7 @@ Azure [availability zones](../reliability/availability-zones-overview.md) ar
 To learn more about availability zones in Azure NetApp Files, see [Reliability in Azure NetApp Files](../reliability/reliability-netapp-files.md).
 
 > [!IMPORTANT]
-> We don't recommend that you use availability zones with Terraform-managed volumes. If you do, you must [add the zone property to your volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes).
+> If you manage volumes with Terraform, [add the zone property to your volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes).
 
 #### Azure regions with availability zones
 

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

@@ -26,7 +26,7 @@ Vaulted backups of Azure Data Lake Storage are available in the following region
 
 | Availability type | Region |
 | --- | --- |
-| **General availability** | East Asia, France South, Southeast US, Switzerland North, Switzerland West, UAE North, UK West, West India. |
+| **General availability** | Central US, East Asia, France South, Germany West Central, Southeast US, Switzerland North, Switzerland West, UAE North, UK West, West India. |
 | **Preview** | Australia East, Central India, Central US, East US, East US 2, Germany West Central, North Central US, North Europe, South India, Southeast Asia, West Central US, West US, West US 2, West US 3. |
 
 ## Supported storage accounts
@@ -70,7 +70,7 @@ Azure Data Lake Storage protection has the following supported and unsupported s
   - Soft Delete: Objects can still be soft-deleted as expected.
   - Undelete: Restore from soft-deleted state is not supported while Vaulted Backup is active. Undelete will only work if Vaulted Backup is disabled first. Re-enabling Vaulted Backup after disabling will trigger a full backup.
 - Storage accounts upgraded from FNS to HNS are not supported for backup.
-- SFTP-enabled & NFS accounts are not supported for backup. Backup jobs may stall if SFTP-uploaded blobs encountered.
+- SFTP- and NFS-enabled accounts aren’t supported for Vaulted Backup. Backup jobs on these accounts fail or hang when processing blobs uploaded via SFTP.
 - $web container cannot be restored as $web on the target. Use the renameTo option and restore it with a different container name.
 - $root container can be restored as $root on the target only if $root does not already exist there. If it already exists, use the renameTo option and restore it with a different container name.
 

articles/backup/backup-azure-manage-windows-server.md

@@ -195,8 +195,8 @@ Use **Export jobs** to create a spreadsheet containing all Jobs menu information
 
 To export the jobs information to a spreadsheet, select **Export jobs**. The service creates a spreadsheet using the name of the vault and date, but you can change the name.
 
->[!Note]
->Azure Backup currently doesn't support exporting jobs with a filter applied, triggerring this operation fails for SQL and SAP HANA workload types. Alternatively, enable a Log Analytics workspace and [export workload-specific jobs](backup-azure-monitoring-use-azuremonitor.md#queries-specific-to-recovery-services-vault-workloads).
+> [!NOTE]
+> Azure Backup currently doesn't support exporting jobs with a filter applied. Triggering this operation fails for SQL and SAP HANA workload types. Alternatively, enable a Log Analytics workspace and [export workload-specific jobs](backup-azure-monitoring-use-azuremonitor.md#queries-specific-to-recovery-services-vault-workloads).
 
 ## Monitor Backup usage
 

articles/backup/backup-managed-disks-policy.md

@@ -1,48 +1,55 @@
 ---
 title: Audit and enforce backup for Managed Disks using Azure Policy 
-description: 'An article describing how to use Azure Policy to audit and enforce backup for all Disks created in a given scope'
+description: Learn how to use Azure Policy to audit and enforce backups for Azure Managed Disks to ensure compliance and protect business-critical data.
 ms.topic: how-to
-ms.date: 12/03/2024
+ms.date: 11/25/2025
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
 # Customer intent: As a Backup Admin, I want to configure Azure Policies to enforce backup for Managed Disks, so that I can ensure compliance and protect business-critical data across my organization's resources.
 ---
 
-# Audit and enforce backup for Managed Disks using Azure Policy 
+# Audit and enforce backup for Azure Managed Disks using Azure Policy 
 
-One of the key responsibilities of a Backup or Compliance Admin in an organization is to ensure that all business-critical machines are backed up with the appropriate retention.
+This article describes how Azure Backup uses built-in [Azure Policy](../governance/policy/overview.md) definitions to automate auditing and enforce backup configurations for Azure Managed Disks. These built-in policies ensure compliance with your organization’s retention requirements for business-critical machines.
 
-Today, Azure Backup provides various built-in policies (using [Azure Policy](../governance/policy/overview.md)) to help you automatically ensure that your Azure Managed Disks are configured for backup. Depending on how your backup teams and resources are organized, you can use any one of the below policies:
+As a Backup and Compliance admin, choose the policy that best fits your team’s structure and resource organization to automatically configure backups for Azure Managed Disks.
+
+## Azure Policy types for Azure Managed Disk backup
+
+The following table lists the various policy types that allow you to manage Azure Managed Disk instances backups automatically:
+
+| Policy type | Description |
+| --- | --- |
+| [Policy 1](#policy-1---azure-backup-should-be-enabled-for-managed-disks) | Identify Azure Managed Disks that don't have backup enabled. |
+| [Policy 2](#policy-2---configure-backup-for-azure-disks-managed-disks-with-a-given-tag-to-an-existing-backup-vault-in-the-same-region) | Configures backup for Azure Managed Disks with a given tag to an existing backup vault in the same region. |
+| [Policy 3](#policy-3---configure-backup-for-azure-disks-managed-disks-without-a-given-tag-to-an-existing-backup-vault-in-the-same-region) | Configures backup for Azure Managed Disks without a given tag to an existing backup vault in the same region. | 
 
 ## Policy 1 - Azure Backup should be enabled for Managed Disks
 
-Use an [audit-only](../governance/policy/concepts/effects.md#audit) policy to identify disks which don't have backup enabled. However, this policy doesn't automatically configure backups for these disks. It is useful when you're only looking to evaluate the overall compliance of the disks but not looking to take action immediately.
+Use an [audit-only](../governance/policy/concepts/effects.md#audit) policy to identify disks, which don't have backup enabled. However, this policy doesn't automatically configure backups for these disks. It's useful when you're only looking to evaluate the overall compliance of the disks but not looking to take action immediately.
 
 ## Policy 2 - Configure backup for Azure Disks (Managed Disks) with a given tag to an existing backup vault in the same region
 
-A central backup team of an organization can use this policy to configure backup to an existing central Backup vault in the same subscription and location as the Managed Disks being governed. You can choose to **include** Disks that contain a certain tag, in the scope of this policy.
+A central backup team of an organization can use this policy to back up Azure Managed Disks to an existing central Backup vault in the same subscription and location. You can choose to **include** Disks that contain a certain tag, in the scope of this policy.
 
 ## Policy 3 - Configure backup for Azure Disks (Managed Disks) without a given tag to an existing backup vault in the same region
 
 This policy works the same as Policy 2 above, with the only difference being that you can use this policy to **exclude** Disks that contain a certain tag, from the scope of this policy.
 
-## Supported Scenarios
-
-Before you audit and enforce backups for AKS clusters, see the following scenarios supported:
+## Supported and unsupported scenarios for Azure Managed Disk backup using Azure Policy
 
-* The built-in policy is currently supported only for Azure Managed Disks. Ensure that the Backup Vault and backup policy specified during assignment is a Disk backup policy. 
+Before you audit and enforce backups for Azure Managed Disk, review the following supported and unsupported scenarios:
 
-* The Policies 2 and 3 can be assigned to a single location and subscription at a time. To enable backup for Disks across locations and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of location and subscription.
 
-* For the Policies 1, 2 and 3, management group scope is currently unsupported.
+| Policy type | Supported | Unsupported |
+| --- | --- | --- |
+| Policy 1, 2, 3 | Supported for Azure Managed Disk only. <br><br> Ensure that the Backup vault and backup policy specified during assignment is a Disk backup policy. | Management group scope is currently unsupported. |
+|Policy 2 and 3 | Can be assigned to a single location and subscription at a time. <br><br> To enable backup for Disks across locations and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of location and subscription. The specified vault and the disks configured for backup can be under different resource groups. |       |
 
-* For the  Policies 2 and 3, the specified vault and the disks configured for backup can be under different resource groups.
+## Assign built-in Azure Policy for Azure Managed Disk backup
 
-
-## Using the built-in policies
-
-The below steps describe the end-to-end process of assigning Policy 2: **Configure backup on Managed Disks with a given tag to an existing backup vault in the same location to a given scope** . Similar instructions are applicable for the other policies. Once assigned, any new Managed Disk created in the scope is automatically configured for backup.
+This section describes the end-to-end process of assigning Policy 2: **Configure backup on Managed Disks with a given tag to an existing backup vault in the same location to a given scope** . Similar instructions apply for the other policies. Once assigned, any new Managed Disk created in the scope is automatically configured for backup.
 
 To assign Policy 2, follow these steps:
 
@@ -52,21 +59,21 @@ To assign Policy 2, follow these steps:
 
 3. Filter the list for **Category=Backup** and select the policy named *Configure backup on Managed Disks with a given tag to an existing backup vault in the same location to a given scope*.
 
-:::image type="content" source="./media/backup-managed-disks-policy/policy-dashboard-inline.png" alt-text="Screenshot showing how to filter the list by category on Policy dashboard.":::
+:::image type="content" source="./media/backup-managed-disks-policy/policy-dashboard-inline.png" alt-text="Screenshot shows how to filter the list by category on Policy dashboard.":::
 
 4. Select the name of the policy. You're then redirected to the detailed definition for this policy.
 
-:::image type="content" source="./media/backup-managed-disks-policy/policy-definition-blade.png" alt-text="Screenshot showing the Policy Definition pane.":::
+:::image type="content" source="./media/backup-managed-disks-policy/policy-definition-blade.png" alt-text="Screenshot shows the Policy Definition pane.":::
 
 5. Select the **Assign** button at the top of the pane. This redirects you to the **Assign Policy** pane.
 
 6. Under **Basics**, select the three dots next to the **Scope** field. It opens up a right context pane where you can select the subscription for the policy to be applied on. You can also optionally select a resource group, so that the policy is applied only for Disks in a particular resource group.
 
-:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-basics.png" alt-text="Screenshot showing the Policy Assignment Basics tab.":::
+:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-basics.png" alt-text="Screenshot shows the Policy Assignment Basics tab.":::
 
 7. In the **Parameters** tab, choose a location from the drop-down, and select the vault, backup policy to which the Disks in the scope must be associated, and resource group where these disk snapshots are stored. You can also choose to specify a tag name and an array of tag values. A Disk that contains any of the specified values for the given tag is included in the scope of the policy assignment.
 
-:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-parameters.png" alt-text="Screenshot showing the Policy Assignment Parameters pane.":::
+:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-parameters.png" alt-text="Screenshot shows the Policy Assignment Parameters pane.":::
 
 8. Ensure that **Effect** is set to deployIfNotExists.
 
@@ -75,8 +82,9 @@ To assign Policy 2, follow these steps:
 > [!NOTE]
 >
 > - Use [remediation](../governance/policy/how-to/remediate-resources.md) to enable policy of existing Managed Disks.
-> - It's recommended that this policy not be assigned to more than 200 Disks at a time. If the policy is assigned to more than 200 Disks, it can result in the backup being triggered a few hours later than that specified by the schedule.
+> - We recommend that you don’t assign this policy to more than 200 disks. Otherwise, backup operation delays by several hours beyond the scheduled time.
+
 
-## Next step
+## Next steps
 
 [Learn more about Azure Policy](../governance/policy/overview.md)

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

@@ -2,7 +2,7 @@
 title: Configure and manage backup for Azure Blobs using Azure Backup
 description: Learn how to configure and manage operational and vaulted backups for Azure Blobs.
 ms.topic: how-to
-ms.date: 09/26/2025
+ms.date: 11/25/2025
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -154,17 +154,17 @@ Once backup is configured, changes taking place on block blobs in the storage ac
 
 ## Manage backups
 
-You can use [Azure Business Continuity Center](../business-continuity-center/business-continuity-center-overview.md) as your single blade of glass for managing all your backups. Regarding backup for Azure Blobs, you can use Azure Business Continuity Center to do the following operations:
+You can use [Resiliency](../resiliency/resiliency-overview.md) as your single blade of glass for managing all your backups. Regarding backup for Azure Blobs, you can use Resiliency to do the following operations:
 
 - 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.
-- Azure Business Continuity Center gives you an easy way to [monitor the state of protection](../business-continuity-center/tutorial-monitor-protection-summary.md) of protected storage accounts as well as storage accounts for which [backup isn't currently configured](../business-continuity-center/quick-understand-protection-estate.md#identify-unprotected-resources).
+- Resiliency gives you an easy way to [monitor the state of protection](../resiliency/tutorial-monitor-protection-summary.md) of protected storage accounts as well as storage accounts for which [backup isn't currently configured](../resiliency/quick-understand-protection-estate.md#identify-unprotected-resources).
 - You can configure backup for any storage accounts using the **+Configure protection** button.
 - You can initiate restores using the **Restore** button and track restores using **Jobs**. For more information on performing restores, see [Restore Azure Blobs](blob-restore.md?tabs=vaulted-backup).
 - Analyze your backup usage using Backup reports.
 
     :::image type="content" source="./media/blob-backup-configure-manage/manage-azure-blob-backup.png" alt-text="Screenshot shows the Azure Business  Continuity Center console to manage the Azure Blob backups." lightbox="./media/blob-backup-configure-manage/manage-azure-blob-backup.png":::
 
-For more information, see [Overview of Azure Business Continuity Center](../business-continuity-center/business-continuity-center-overview.md).
+For more information, see [Overview of Resiliency](../resiliency/resiliency-overview.md).
 
 ## Stop protection
 
@@ -177,7 +177,7 @@ To stop backup for a storage account, follow these steps:
 
 1. Go to the backup instance for the storage account being backed up.
 
-   You can go to the backup instance from the storage account via **Storage account** > **Data protection** > **Manage backup settings**, or directly from the Business Continuity Center  via **Business Continuity Center** > **Protected Items** , and then select **Azure Backup** as a **Solution** in the filter. 
+   You can go to the backup instance from the storage account via **Storage account** > **Data protection** > **Manage backup settings**, or directly from the Resiliency  via **Resiliency** > **Protected Items** , and then select **Azure Backup** as a **Solution** in the filter. 
 
    :::image type="content" source="./media/blob-backup-configure-manage/storage-account-location.png" alt-text="Screenshot shows the Storage account location.":::