Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/api-management/validate-jwt-policy.md

@@ -121,6 +121,7 @@ The `validate-jwt` policy enforces existence and validity of a supported JSON we
     	* If used in the policy, the key must be provided inline within the policy in the Base64-encoded form.
     * **Asymmetric** - The following encryption algorithms are supported: PS256, RS256, RS512, ES256. 
     	* If used in the policy, the key may be provided either via an OpenID configuration endpoint, or by providing the ID of an uploaded certificate (in PFX format) that contains the public key, or the modulus-exponent pair of the public key.
+* If the API Management instance is injected or integrated in a virtual network, any OpenID configuration endpoint URLs configured in the policy must be reachable by the gateway.
 * To configure the policy with one or more OpenID configuration endpoints for use with a self-hosted gateway, the OpenID configuration endpoints URLs must also be reachable by the cloud gateway.
 * You can use access restriction policies in different scopes for different purposes. For example, you can secure the whole API with Microsoft Entra authentication by applying the `validate-jwt` policy on the API level, or you can apply it on the API operation level and use `claims` for more granular control.
 * When using a custom header (`header-name`), the configured required scheme (`require-scheme`) will be ignored. To use a required scheme, JWTs must be provided in the `Authorization` header.

articles/azure-functions/extension-bundles.md

@@ -2,7 +2,7 @@
 title: Azure Functions Extension Bundles
 description: Learn how to use extension bundles to make the correct set of Azure Functions trigger and binding extensions available in your non-.NET function code.
 ms.topic: concept-article
-ms.date: 07/25/2025
+ms.date: 08/06/2025
 
 #Customer intent: I want to understand how to correctly install extension bundles so that the functionality implemented in the extensions is available to my functions in my preferred development language.
 ---
@@ -25,18 +25,20 @@ You define an extension bundle reference in the `host.json` project file by addi
 
 [!INCLUDE [functions-extension-bundles-json](../../includes/functions-extension-bundles-json.md)]
 
-<!---## Supported extension bundles
+## Supported extension bundles
 
 This table lists all `Microsoft.Azure.Functions.ExtensionBundle` bundle versions and the current [support state](#support-policy):
 
-| Bundle version | Version in host.json | Support state | End-of-support date |
-| --- | --- | --- | --- |
-| [4.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[4.0.0, 5.0.0)` | Active | Not yet determined  |
-| [3.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v3/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[3.3.0, 4.0.0)` | Deprecated | May 30, 2026 |
-| [2.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v2/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[2.*, 3.0.0)` | Deprecated | May 30, 2026 |
-| [1.x](https://github.com/Azure/azure-functions-extension-bundles/blob/v1.x/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[1.*, 2.0.0)` | Deprecated | May 30, 2026 |
+| Bundle version | Version in host.json | Support state<sup>*</sup> | 
+| --- | --- | --- | 
+| [4.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[4.0.0, 5.0.0)` | Active | 
+| [3.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v3/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[3.3.0, 4.0.0)` | Deprecated | 
+| [2.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v2/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[2.*, 3.0.0)` | Deprecated | 
+| [1.x](https://github.com/Azure/azure-functions-extension-bundles/blob/v1.x/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[1.*, 2.0.0)` | Deprecated |
 
-The default extension bundles are defined via version ranges. To see the `extensions.json` definition file that generates the current bundle version for a major extension, select the link in the table.-->
+<sup>*</sup> Deprecated bundle versions can use deprecated binding extension versions. For optimal supportability and reliability, you should [upgrade to bundle version 4.x](#upgrade-extension-bundles). 
+
+The default extension bundles are defined via version ranges. To see the `extensions.json` definition file that generates the current bundle version for a major extension, select the link in the table.
 
 ## Considerations for extension bundles
 
@@ -50,7 +52,17 @@ Keep these considerations in mind when you work with extension bundles:
 
 It's important to keep your bundle version up-to-date so that your apps can continue to be eligible for new features, security patches, and performance optimizations. 
 
-To upgrade your app to the most recent bundle, edit the host.json file in the root of your app project. Replace the value of `extensionBundle.version` with the most recent supported extension bundles version.
+To upgrade your app to the most recent bundle, edit the host.json file in the root of your app project. Set the value of `extensionBundle.version` to `[4.x,5.0.0)`, which should look like this in your host.json file:
+
+```json
+{
+    "version": "2.0",
+    "extensionBundle": {
+        "id": "Microsoft.Azure.Functions.ExtensionBundle",
+        "version": "[4.0.0, 5.0.0)"
+    }
+}
+```
 
 Keep these considerations in mind when upgrading the extension bundle version used by your app:
 

articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json

@@ -44,6 +44,36 @@
             "source_path_from_root": "/articles/azure-netapp-files/access-smb-volume-from-windows-client.md",
             "redirect_url": "/azure/azure-netapp-files/mount-volumes-vms-smb",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-netapp-files/use-availability-zones.md",
+            "redirect_url": "/azure/reliability/reliability-netapp-files",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-netapp-files/cross-zone-replication-introduction.md",
+            "redirect_url": "/azure/azure-netapp-files/replication",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-netapp-files/cross-zone-region-replication.md",
+            "redirect_url": "/azure/azure-netapp-files/replication",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-netapp-files/cross-region-replication-introduction.md",
+            "redirect_url": "/azure/azure-netapp-files/replication",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root":"/articles/azure-netapp-files/cross-region-replication-requirements-considerations.md",
+            "redirect_url": "/azure/azure-netapp-files/replication-requirements",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root":"/articles/azure-netapp-files/cross-zone-replication-requirements-considerations.md",
+            "redirect_url": "/azure/azure-netapp-files/replication-requirements",
+            "redirect_document_id": false
         }
     ]
 }

articles/azure-netapp-files/TOC.yml

@@ -177,6 +177,8 @@
           href: application-volume-group-oracle-considerations.md
   - name: Data protection and resiliency
     items:
+    - name: Reliability in Azure NetApp Files 
+      href: ../reliability/reliability-netapp-files.md?toc=azure/azure-netapp-files/toc.json&bc=/azure/azure-netapp-files/breadcrumb/toc.yml
     - name: Understand data protection and disaster recovery options
       href: data-protection-disaster-recovery-options.md
     - name: How Azure NetApp Files snapshots work
@@ -187,22 +189,12 @@
         href: backup-introduction.md  
       - name: Requirements and considerations for Azure NetApp Files backup
         href: backup-requirements-considerations.md
-    - name: Disaster recovery with cross-region replication
+    - name: Replication 
       items: 
-      - name: Understand cross-region replication
-        href: cross-region-replication-introduction.md
-      - name: Requirements and considerations for cross-region replication
-        href: cross-region-replication-requirements-considerations.md
-    - name: High availability and resiliency with availability zones and cross-zone replication
-      items: 
-      - name: Use availability zones for high availability 
-        href: use-availability-zones.md
-      - name: Understand cross-zone replication 
-        href: cross-zone-replication-introduction.md
-      - name: Requirements and considerations for cross-zone replication 
-        href: cross-zone-replication-requirements-considerations.md
-    - name: Understand cross-zone-region replication 
-      href: cross-zone-region-replication.md
+      - name: Replication in Azure NetApp Files 
+        href: replication.md
+      - name: Replication requirements and considerations
+        href: replication-requirements.md
     - name: Azure Application Consistent Snapshot (AzAcSnap) tool
       items: 
       - name: What is AzAcSnap?

articles/azure-netapp-files/application-volume-group-considerations.md

@@ -17,7 +17,7 @@ This article describes the requirements and considerations you need to be aware
 
 * You need to use the [manual QoS capacity pool](manage-manual-qos-capacity-pool.md) functionality.  
 * Application volume group supports Basic and Standard network features. To use features including availability zone volume placement, use [Standard network features](azure-netapp-files-network-topologies.md).
-* Application volume group supports [availability zone volume placement](use-availability-zones.md) as the default and recommended method for placement. Using availability zone volume placement mitigates the need for AVset pinning and eliminates the need for proximity placement groups. With support for availability zone volume placement, you only need to select the same availability zone as the database servers. Using availability zone volume placement aligns with the Microsoft recommendation on how to deploy SAP HANA infrastructures to achieve best performance with high-availability, maximum flexibility, and simplified deployment. 
+* Application volume group supports [availability zone volume placement](replication.md#availability-zones) as the default and recommended method for placement. Using availability zone volume placement mitigates the need for AVset pinning and eliminates the need for proximity placement groups. With support for availability zone volume placement, you only need to select the same availability zone as the database servers. Using availability zone volume placement aligns with the Microsoft recommendation on how to deploy SAP HANA infrastructures to achieve best performance with high-availability, maximum flexibility, and simplified deployment. 
     * If regions don't support availability zones, you can select a regional deployment or choose proximity placement groups (PPG).
 
     When you create a PPG, you must anchor it to your SAP HANA compute resources. Application volume group for SAP HANA needs this setup to search for an Azure NetApp Files resource that is close to the SAP HANA servers. For more information, see [Best practices about PPGs](#best-practices-about-proximity-placement) and [Create a PPG using the Azure portal](/azure/virtual-machines/windows/proximity-placement-groups-portal).

articles/azure-netapp-files/application-volume-group-disaster-recovery.md

@@ -17,7 +17,7 @@ This article describes using an application volume group to add volumes for an S
 
 ## CRR between source and destination HANA servers
 
-The Azure NetApp Files [cross-region replication](cross-region-replication-introduction.md) functionality enables you to replicate volumes between [supported cross-region replication pairs](cross-region-replication-introduction.md#supported-region-pairs). This functionality allows you to [replicate a volume](cross-region-replication-create-peering.md) from a source region to a volume on the destination region for disaster recovery (DR). 
+The Azure NetApp Files [cross-region replication](replication.md) functionality enables you to replicate volumes between [supported cross-region replication pairs](replication.md#supported-region-pairs). This functionality allows you to [replicate a volume](cross-region-replication-create-peering.md) from a source region to a volume on the destination region for disaster recovery (DR). 
 
 Instead of using HANA System Replication (HSR), you can use cross-region replication to protect a database without needing a HANA database server that runs all the time. You need to create replication destination volumes in a region supported for cross-region replication. Application volume group for SAP HANA ensures that the destination volumes are created with the correct volume type that meets all SAP HANA specific requirements.
 
@@ -80,7 +80,7 @@ The following example adds volumes to an SAP HANA system. The system serves as a
     * **Multiple-host**:  
         Select this option if you're adding additional hosts to a multiple-hosts HANA system.
     * **Disaster recover destination**:  
-        Select this option to create volumes for a HANA system as a DR site using [cross-region replication](cross-region-replication-introduction.md).  
+        Select this option to create volumes for a HANA system as a DR site using [cross-region replication](replication.md).  
 
         Selecting **Disaster recover destination** triggers the naming convention for the volume group name to include `"-DR-"` to indicate a disaster-recovery setup. 
 

articles/azure-netapp-files/application-volume-group-introduction.md

@@ -24,7 +24,7 @@ Application volume group for SAP HANA is supported for all regions where Azure N
 * Supporting SAP HANA configurations for both single and multiple host setups, including: 
     * Volumes for a single or primary SAP HANA database
     * Volumes for an SAP HANA System Replication (HSR) secondary system
-    * Volumes for a disaster recovery (DR) scenario using [cross-region replication](cross-region-replication-introduction.md)
+    * Volumes for a disaster recovery (DR) scenario using [cross-region replication](replication.md)
 
 * Creating the following volumes: 
     * SAP HANA data volumes (one for each database host)
@@ -41,7 +41,7 @@ Application volume group for SAP HANA is supported for all regions where Azure N
 
 Application volume group for SAP HANA helps you simplify the deployment process and increase the storage performance for SAP HANA workloads. Some of the new features are as follows:
 
-* [Availability zone volume placement](use-availability-zones.md)
+* [Availability zone volume placement](replication.md#availability-zones)
 
     Designating the same availability zone for the volumes ensures that virtual machines and Azure NetApp Files volumes reside in the same availability zone and meet the latency requirements for SAP HANA. Availability zone volume placement simplifies the deployment process, avoiding the manual AvSet pinning process and eliminating the requirement for availability sets. To learn more about the differences between availability zone volume placement and proximity placement groups, see [Requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md#best-practices-about-proximity-placement).
 

articles/azure-netapp-files/application-volume-group-oracle-introduction.md

@@ -46,15 +46,15 @@ Application volume group for Oracle helps you simplify the deployment process an
 * Creation of separate storage endpoints (with different IP addresses) for data and log volumes.   
     This deployment method provides better performance and throughput for the Oracle database.
 * Customer-managed keys support increased security and compliance. 
-* [Cross-zone](cross-zone-replication-introduction.md) and [cross-region](cross-region-replication-introduction.md) replication provide efficient storage-based data replication without load on compute infrastructure and a layer of protection for disaster recovery. This feature currently is in preview and only supported with the [REST API](configure-application-volume-oracle-api.md#replication). 
+* [Cross-zone and cross-region replication](replication.md) provide efficient storage-based data replication without load on compute infrastructure and a layer of protection for disaster recovery. This feature currently is in preview and only supported with the [REST API](configure-application-volume-oracle-api.md#replication). 
 
 ## Application volume group layout
 
 Application volume group for Oracle deploys multiple volumes based on your input and on resource availability in the selected region and zone, subject to the following rules:
 
 [!INCLUDE [AVG bullet points](includes/application-volume-group-layout.md)]
 
-High availability deployments will include volumes in two availability zones or regions. Application volume group for Oracle allows you to deploy production volumes in the primary zone and data protection volumes in an alternate zone or region. You can use Data Guard to replicate redo log and data volumes, or you can choose to offload data volume replication load from the application server by using Azure NetApp Files [cross-zone](cross-zone-replication-introduction.md) or [cross-region replication](cross-region-replication-introduction.md) for the data volumes. Use application-based data replication with Data Guard to synchronously replicate the redo logs so the database can be rolled forward after a failover.
+High availability deployments will include volumes in two availability zones or regions. Application volume group for Oracle allows you to deploy production volumes in the primary zone and data protection volumes in an alternate zone or region. You can use Data Guard to replicate redo log and data volumes, or you can choose to offload data volume replication load from the application server by using Azure NetApp Files [cross-zone or cross-region replication](replication.md) for the data volumes. Use application-based data replication with Data Guard to synchronously replicate the redo logs so the database can be rolled forward after a failover.
 
 :::image type="content" source="./media/application-volume-group-oracle-introduction/oracle-dual-zone-layout.png" alt-text="Diagram of dual-zone volume layout." lightbox="./media/application-volume-group-oracle-introduction/oracle-dual-zone-layout.png":::
 

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

@@ -13,7 +13,7 @@ ms.author: anfdocs
 
 Understanding the cost model for Azure NetApp Files helps you manage your expenses from the service. 
 
-For cost model specific to cross-region replication, see [Cost model for cross-region replication](cross-region-replication-introduction.md#cost-model-for-cross-region-replication).
+For cost model specific to cross-region replication, see [Cost model for cross-region replication](replication.md#cost-model-for-cross-region-replication).
 
 ## Calculation of capacity consumption
 
@@ -100,7 +100,7 @@ The following diagram illustrates the concepts.
 * [Azure NetApp Files pricing page](https://azure.microsoft.com/pricing/details/storage/netapp/)
 * [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md)
 * [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)
-* [Cost model for cross-region replication](cross-region-replication-introduction.md#cost-model-for-cross-region-replication)
+* [Cost model for cross-region replication](replication.md#cost-model-for-cross-region-replication)
 * [Understand volume quota](volume-quota-introduction.md)
 * [Monitor the capacity of a volume](monitor-volume-capacity.md)
 * [Resize the capacity pool or a volume](azure-netapp-files-resize-capacity-pools-or-volumes.md)