Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into afd-wildcard

Author: halkazwini

articles/application-gateway/migrate-v1-v2.md

@@ -66,6 +66,11 @@ This article focuses on the configuration stage of migration. Migration of clien
 
 The configuration migration focuses on setting up the new V2 gateway with the settings from your existing V1 environment. Two Azure PowerShell scripts facilitate the migration of configurations (Standard or Web Application Firewall) from V1 to V2 gateways. These scripts help streamline the transition process by automating key deployment and configuration tasks.
 
+> [!NOTE]
+>If the existing Application Gateway V1 deployment is configured with a private-only frontend, you must [register the `EnableApplicationGatewayNetworkIsolation` feature in the subscription](../application-gateway/application-gateway-private-deployment.md#onboard-to-the-feature) for private deployment before running the migration script even though the feature is in GA. This step is required to avoid deployment failures.
+
+>Private Application Gateway deployments must have subnet delegation configured to `Microsoft.Network/applicationGateways`. Use the [steps to set up subnet delegation](/azure/virtual-network/manage-subnet-delegation?tabs=manage-subnet-delegation-portal).
+
 ## Enhanced cloning script (recommended)
 
 The enhanced cloning script is the recommended option. It offers an improved migration experience by:

articles/automation/automation-hrw-run-runbooks.md

@@ -16,10 +16,7 @@ author: RochakSingh-blr
 
 > [!IMPORTANT]
 > - Starting 1st April 2025, all jobs running on agent-based Hybrid Worker will be stopped. 
-> - Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) has retired on **31 August 2024** and is no longer supported. Follow the guidelines on how to [migrate from an existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md).
-
-> [!NOTE]
-> Azure Automation Run As Account has retired on September 30, 2023 and is replaced with Managed Identities. Follow the guidelines on [how to start migrating your runbooks to use managed identities](automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity.md#sample-scripts).
+> - Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) has retired on **31 August 2024** and is no longer supported. Follow the guidelines on how to [migrate from an existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md)
 
 
 Runbooks that run on a [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md) typically manage resources on the local computer or against resources in the local environment where the worker is deployed. Runbooks in Azure Automation typically manage resources in the Azure cloud. Even though they are used differently, runbooks that run in Azure Automation and runbooks that run on a Hybrid Runbook Worker are identical in structure.
@@ -96,7 +93,7 @@ If the *Python* executable file is at the default location *C:\Python27\python.e
 
 > [!NOTE]
 >- PowerShell 7.4 and Python 3.10 runbooks are supported on extension-based Linux Hybrid Workers only. Ensure the Linux Hybrid worker extension version is 1.1.23 or above.
->- PowerShell 5.1, PowerShell 7.1 (preview), Python 2.7, Python 3.8 runbooks are supported on both extension-based and agent-based Linux Hybrid Runbook Workers. For agent-based workers, ensure the Linux Hybrid Runbook worker version is 1.7.5.0 or above.
+>- PowerShell 7.1 (preview), Python 2.7, Python 3.8 runbooks are supported on both extension-based and agent-based Linux Hybrid Runbook Workers. For agent-based workers, ensure the Linux Hybrid Runbook worker version is 1.7.5.0 or above.
 >- PowerShell 7.2 runbook is supported on extension-based Linux Hybrid Workers only. Ensure the Linux Hybrid worker extension version is 1.1.11 or above.
 
 #### Extension-based Hybrid Workers

articles/azure-netapp-files/azure-netapp-files-cost-model.md

@@ -21,7 +21,7 @@ For cost model specific to cross-region replication, see [Cost model for cross-r
 
 Azure NetApp Files is billed on provisioned storage capacity, which is allocated by creating capacity pools. Capacity pools are billed monthly based on a set cost per allocated GiB per hour. Capacity pool allocation is measured hourly.  
 
-Capacity pools must be at least 1 TiB and can be increased or decreased in 1-TiB intervals. Capacity pools contain volumes that range in size from a minimum of 50 GiB to a maximum of 100 TiB for regular volumes and up to 1 PiB for [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes). Volumes are assigned quotas that are subtracted from the capacity pool’s provisioned size. For an active volume, capacity consumption against the quota is based on logical (effective) capacity, being active filesystem data or snapshot data. See [How Azure NetApp Files snapshots work](snapshots-introduction.md) for details. 
+Capacity pools must be at least 1 TiB and can be increased or decreased in 1-TiB intervals. Capacity pools contain volumes that range in size from a minimum of 50 GiB to a maximum of 100 TiB for regular volumes and up to 1 PiB for [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes). Volumes are assigned quotas that are subtracted from the capacity pool’s provisioned size. For an active volume, capacity consumption against the quota is based on logical (effective) capacity, being active filesystem data or snapshot data. See [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md) for details. 
 
 ### Pricing examples
 

articles/azure-netapp-files/backup-introduction.md

@@ -13,7 +13,7 @@ ms.custom: references_regions
 
 # Understand Azure NetApp Files backup
 
-Azure NetApp Files backup expands the data protection capabilities of Azure NetApp Files by providing fully managed backup solution for long-term recovery, archive, and compliance. Backups created by the service are stored in Azure storage, independent of volume snapshots that are available for near-term recovery or cloning. Backups taken by the service can be restored to new Azure NetApp Files volumes within the region. Azure NetApp Files backup supports both policy-based (scheduled) backups and manual (on-demand) backups. For more information, see [How Azure NetApp Files snapshots work](snapshots-introduction.md).
+Azure NetApp Files backup expands the data protection capabilities of Azure NetApp Files by providing fully managed backup solution for long-term recovery, archive, and compliance. Backups created by the service are stored in Azure storage, independent of volume snapshots that are available for near-term recovery or cloning. Backups taken by the service can be restored to new Azure NetApp Files volumes within the region. Azure NetApp Files backup supports both policy-based (scheduled) backups and manual (on-demand) backups. For more information, see [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md).
 
 ## Supported regions 
 
@@ -60,4 +60,4 @@ If you choose to restore a backup of, for example, 600 GiB to a new volume, you'
 * [Delete backups of a volume](backup-delete.md)
 * [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
 * [Azure NetApp Files backup FAQs](faq-backup.md)
-* [How Azure NetApp Files snapshots work](snapshots-introduction.md)
+* [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md)

articles/azure-netapp-files/backup-requirements-considerations.md

@@ -68,4 +68,4 @@ You need to be aware of several requirements and considerations before using Azu
 * [Delete backups of a volume](backup-delete.md)
 * [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
 * [Azure NetApp Files backup FAQs](faq-backup.md)
-* [How Azure NetApp Files snapshots work](snapshots-introduction.md)
+* [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md)

articles/azure-netapp-files/backup-restore-new-volume.md

@@ -99,4 +99,4 @@ Ensure you choose the workflow for the correct service level.
 * [Delete backups of a volume](backup-delete.md)
 * [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
 * [Azure NetApp Files backup FAQs](faq-backup.md)
-* [How Azure NetApp Files snapshots work](snapshots-introduction.md)
+* [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md)

articles/azure-netapp-files/create-short-term-clone.md

@@ -70,5 +70,5 @@ By default, short-term clones convert to regular volumes after 32 days.
 
 ## Next steps
 
-* [How Azure NetApp Files snapshots work](snapshots-introduction.md)
+* [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md)
 * [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)

articles/azure-netapp-files/data-protection-disaster-recovery-options.md

@@ -28,7 +28,7 @@ The foundation of data protection solutions including volume restores and clones
 - Restore a snapshot to new volume (clone) in seconds to test or develop with current data  
 - Application-consistent snapshots with [AzAcSnap integration](azacsnap-introduction.md) and third party backup tools 
 
-To learn more, see [How Azure NetApp Files Snapshots work](snapshots-introduction.md) and [Ways to restore data from snapshots](snapshots-introduction.md#ways-to-restore-data-from-snapshots). To create a Snapshot policy, see [Manage Snapshot policies in Azure NetApp Files](snapshots-manage-policy.md). 
+To learn more, see [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md) and [Ways to restore data from snapshots](snapshots-introduction.md#ways-to-restore-data-from-snapshots). To create a Snapshot policy, see [Manage Snapshot policies in Azure NetApp Files](snapshots-manage-policy.md). 
 
 ## Backups
 
@@ -93,7 +93,7 @@ Fast data recovery (whole volume) | Revert volume from snapshot | Revert volume
 
 ## Next steps
 
-* [How Azure NetApp Files snapshots work](snapshots-introduction.md)
+* [Understand Azure NetApp Files snapshot-based data protection](snapshots-introduction.md)
 * [Understand Azure NetApp Files backup](backup-introduction.md)
 * [Understand Azure NetApp Files replication](replication.md)
 * [Reliability in Azure NetApp Files](/azure/reliability/reliability-netapp-files)

articles/azure-netapp-files/elastic-zone-redundant-concept.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 02/04/2026
+ms.date: 03/26/2026
 ms.author: anfdocs
 ms.custom: references-regions 
 ---
@@ -49,7 +49,7 @@ Elastic zone-redundant storage offers several key benefits for resiliency, opera
 | Operational simplicity | Azure manages replication and failover automatically, eliminating the need for duplicate volumes or cross‑zone replication. High availability becomes a one‑click setup, simplifying operations and reducing configuration risk.|
 | Extensive feature support | Elastic zone-redundant storage volumes support a growing set of Azure NetApp Files features, including NFSv3, NFSv4.1, and SMB, along with capabilities including snapshots, backups, customer‑managed keys, and Active Directory integration, delivering enhanced resiliency as feature coverage continues to expand. |
 | Cost-effective high availability | Azure NetApp Files Elastic zone-redundant storage delivers multi‑availability zone redundancy more cost‑effectively than duplicate standby volumes by using all provisioned capacity with no idle replicas. You pay for a single resilient volume, improving utilization, lowering TCO, and avoiding the added egress and administrative costs of external replication solutions. |
-| Metadata performance | Beyond consistent throughput, Azure NetApp Files Elastic zone-redundant storage redefines performance for metadata-heavy workloads. This is critical for SAP shared files and similar environments where metadata operations drive application responsiveness. The shared QoS architecture dynamically allocates IOPS across volumes to maintain low-latency, metadata-intensive operations consistently, even across multiple availability zones. |
+| Metadata performance | Beyond consistent throughput, Azure NetApp Files Elastic zone-redundant storage redefines performance for metadata-heavy workloads. This is critical for environments where high rates of metadata operations directly influence application responsiveness. The shared QoS architecture dynamically allocates IOPS across volumes to sustain low-latency, metadata intensive operations consistently, even across multiple availability zones. |
 
 ## Supported regions
 
@@ -106,4 +106,4 @@ For more detailed information, see [Azure NetApp Files REST API](/rest/api/netap
 - [Storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md)
 - [Create a NetApp Elastic account](elastic-account.md)
 - [Set up an Elastic capacity pool](elastic-capacity-pool-task.md)
-- [Azure NetApp Files resource limits](azure-netapp-files-resource-limits.md)
+- [Azure NetApp Files resource limits](azure-netapp-files-resource-limits.md)

articles/azure-netapp-files/includes/region-pairs.md

@@ -69,8 +69,15 @@ Azure NetApp Files volume replication is supported between various [Azure region
 | North America | West US 2 | West US 3 |
 | Sweden/Europe | Sweden Central | North Europe |
 | Sweden/Europe | Sweden Central | West Europe |
+| UAE/Sweden*   | UAE North  | Sweden Central |
 | UK/Europe | UK South | North Europe |
 | US Government | US Gov Arizona | US Gov Virginia |
 
+*Billing
 > [!NOTE]
-> There can be a discrepancy in the size and number of snapshots between the source and the destination. This discrepancy is expected. Snapshot policies and replication schedules influence the number of snapshots. Snapshot policies and replication schedules, combined with the amount of data that changes between snapshots, influence the size of snapshots. For more information, see [How Azure NetApp Files snapshots work](../snapshots-introduction.md).
+> During the initial rollout, your Azure bill may temporarily show cross-region replication charges for an alternative region pair while the final billing SKUs are being implemented. **There is no overbilling** - the cost shown is the same rate that will apply for **UAE Central to Sweden Central** replication.
+
+<br/><br/>
+
+> [!NOTE]
+> There can be a discrepancy in the size and number of snapshots between the source and the destination. This discrepancy is expected. Snapshot policies and replication schedules influence the number of snapshots. Snapshot policies and replication schedules, combined with the amount of data that changes between snapshots, influence the size of snapshots. For more information, see [Understand Azure NetApp Files snapshot-based data protection](../snapshots-introduction.md).