Merge pull request #308492 from MicrosoftDocs/main

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

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

articles/app-service/overview-agent-identity.md

@@ -374,6 +374,8 @@ items:
           href: tutorial-auth-aad.md
         - name: App to app to another Azure service as user
           href: tutorial-connect-app-app-graph-javascript.md
+    - name: Connect by using agent identity
+      href: overview-agent-identity.md
 - name: Scaling and performance
   items:
     - name: Scale up server capacity

articles/app-service/toc.yml

@@ -100,7 +100,7 @@ Use the following steps to help diagnose a test not finishing:
 1. [Download and analyze the test logs](#download-apache-jmeter-or-locust-worker-logs-for-your-load-test) to identify issues in the JMeter test script.
 1. [Download the test results](./how-to-export-test-results.md) to identify issues with individual requests.
 
-You can also view AI-based error insights for your test run after a test run completes. The insights generated contain the cause of error and more actionable recommendations. Refer to [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839)
+You can also view AI-based error insights for your test run after a test run completes. The insights generated contain the cause of error and more actionable recommendations. This feature is tunred on by default and can be turned off in the error blade settings. Refer to [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839).
 
 > [!NOTE]
 > By agreeing to use AI-based error insights, you agree that the log files for your test run will be used by AI to generate recommendations. 

articles/app-testing/load-testing/how-to-diagnose-failing-load-test.md

@@ -136,6 +136,8 @@
       href: functions-identity-based-connections-tutorial-2.md
     - name: Access Azure SQL with managed identity
       href: functions-identity-access-azure-sql-with-managed-identity.md
+    - name: Access MCP server with agent identity
+      href: ../app-service/overview-agent-identity.md?toc=/azure/azure-functions/toc.json
   - name: Low-latency Blob trigger using Event Grid
     displayName: storage, ngrok, local
     href: functions-event-grid-blob-trigger.md

articles/azure-functions/TOC.yml

@@ -217,6 +217,7 @@ This section provides references for High Performance Computing (HPC) solutions.
 * [Benefits of using Azure NetApp Files for electronic design automation](solutions-benefits-azure-netapp-files-electronic-design-automation.md)
 * [Azure CycleCloud: EDA HPC Lab with Azure NetApp Files](https://github.com/Azure/cyclecloud-hands-on-labs/blob/master/EDA/README.md)
 * [Benchmark EDA workloads on Azure Intel Emerald Rapids (EMR) VMs](https://techcommunity.microsoft.com/blog/azurehighperformancecomputingblog/benchmark-eda-workloads-on-azure-intel-emerald-rapids-emr-vms/4334619)
+* [Accelerating HPC and EDA with Powerful Azure NetApp Files Enhancements](https://techcommunity.microsoft.com/blog/azurearchitectureblog/accelerating-hpc-and-eda-with-powerful-azure-netapp-files-enhancements/4469739)
 
 ### Analytics
 

articles/azure-netapp-files/azure-netapp-files-solution-architectures.md

@@ -17,54 +17,7 @@ Azure NetApp Files backup expands the data protection capabilities of Azure NetA
 
 ## Supported regions 
 
-Azure NetApp Files backup is supported for the following regions:   
-
-* Australia Central
-* Australia Central 2
-* Australia East
-* Australia Southeast
-* Brazil South
-* Brazil Southeast 
-* Canada Central
-* Canada East
-* Central India
-* Central US
-* East Asia
-* East US
-* East US 2
-* France Central
-* Germany North
-* Germany West Central
-* Israel Central
-* Italy North 
-* Japan East
-* Japan West
-* Korea Central
-* Korea South
-* North Central US
-* North Europe
-* Norway East
-* Norway West
-* Qatar Central
-* South Africa North
-* South Central US
-* South India
-* Southeast Asia
-* Spain Central
-* Sweden Central
-* Switzerland North
-* Switzerland West 
-* UAE Central
-* UAE North
-* UK South
-* UK West
-* US Gov Arizona
-* US Gov Texas
-* US Gov Virginia
-* West Europe
-* West US
-* West US 2
-* West US 3
+Azure NetApp Files backup is available in all Azure NetApp Files-enabled regions.
 
 ## Backup vault 
 

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

@@ -34,56 +34,10 @@ By default (unless cool access retrieval policy is configured otherwise), data b
 
 Metadata is never cooled and always remains in the hot tier. Tiering doesn't affect the activities of metadata-intensive workloads like high file-count environments like chip design, version control systems, and home directories.
 
+
 ## Supported regions 
 
-Azure NetApp Files storage with cool access is supported for the following regions:
-
-* Australia Central
-* Australia Central 2
-* Australia East 
-* Australia Southeast
-* Brazil South 
-* Brazil Southeast
-* Canada Central 
-* Canada East
-* Central India 
-* Central US
-* East Asia  
-* East US
-* East US 2   
-* France Central
-* Germany North 
-* Germany West Central
-* Israel Central
-* Italy North 
-* Japan East
-* Japan West 
-* Korea Central
-* Korea South 
-* North Central US 
-* North Europe  
-* Norway East
-* Norway West
-* Qatar Central
-* South Africa North
-* South Central US
-* South India
-* Southeast Asia
-* Spain Central
-* Switzerland North 
-* Switzerland West 
-* Sweden Central
-* UAE Central
-* UAE North 
-* UK South
-* UK West
-* US Gov Arizona
-* US Gov Texas
-* US Gov Virginia 
-* West Europe
-* West US
-* West US 2
-* West US 3
+Azure NetApp Files storage with cool access is available in all Azure NetApp Files-enabled regions.
 
 ## Metrics 
 

articles/azure-netapp-files/cool-access-introduction.md

@@ -81,7 +81,7 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
     The "remote path" values are the host, server, and volume names of your on-premises storage. 
 
     ```rest
-    PUT: https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-name>/providers/Microsoft.NetApp/netAppAccounts/<account-name>/capacityPools/<capacity-pool-name>/volumes/Migvolfinal?api-version=2025-06-01
+    PUT: https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-name>/providers/Microsoft.NetApp/netAppAccounts/<account-name>/capacityPools/<capacity-pool-name>/volumes/Migvolfinal?api-version=2025-07-01
     Body: {
        "type":"Microsoft.NetApp/netAppAccounts/capacityPools/volumes",
        "location":"<LOCATION>",
@@ -140,7 +140,7 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
     >Every node in your ONTAP system needs an IC LIF. Each IC LIF needs to be listed here. 
 
     ```rest
-        PUT https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-name>/providers/Microsoft.NetApp/netAppAccounts/<account-name>/capacityPools/<capacity-pool-name>/volumes/<volume-names>/peerExternalCluster?api-version=2025-06-01
+        PUT https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-name>/providers/Microsoft.NetApp/netAppAccounts/<account-name>/capacityPools/<capacity-pool-name>/volumes/<volume-names>/peerExternalCluster?api-version=2025-07-01
     
         Body: {
            "PeerAddresses":[
@@ -156,7 +156,7 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
 1. In your ONTAP or Cloud Volumes ONTAP system, accept the cluster peer request from Azure NetApp Files by sending a GET request using Azure-AsyncOperation ID.
 
     ```rest
-    POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/providers/Microsoft.NetApp/locations/<location>/operationResults/<Azure-AsyncOperation>?api-version=2025-06-01...
+    POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/providers/Microsoft.NetApp/locations/<location>/operationResults/<Azure-AsyncOperation>?api-version=2025-07-01...
     ```
     
     >[!NOTE]
@@ -187,13 +187,13 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
 1. Issue an `authorizeExternalReplication` API request for your migration volumes. Repeat this request for each migration volume. 
 
     ```rest
-    POST: https://<region>.management.azure.com/subscriptions/<subscription>/resourceGroups/<resource-group>/providers/Microsoft.NetApp/netAppAccounts/<account-name>/capacityPools/<capacity-pool-name>/volumes/<volume-names>/authorizeExternalReplication?api-version=2025-06-01
+    POST: https://<region>.management.azure.com/subscriptions/<subscription>/resourceGroups/<resource-group>/providers/Microsoft.NetApp/netAppAccounts/<account-name>/capacityPools/<capacity-pool-name>/volumes/<volume-names>/authorizeExternalReplication?api-version=2025-07-01
     ```
 
 1. Accept the storage virtual machine (SVM) peer request from Azure NetApp Files by sending a GET request using the Azure-AsyncOperation ID in step 4. 
 
     ```rest
-    GET https://<region>.management.azure.com/subscriptions/<subscription-ID>/providers/Microsoft.NetApp/locations/<location>/operationResults/<>?api-version=2025-06-01&...
+    GET https://<region>.management.azure.com/subscriptions/<subscription-ID>/providers/Microsoft.NetApp/locations/<location>/operationResults/<>?api-version=2025-07-01&...
     ```
 
     The response looks like: 
@@ -220,13 +220,13 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
 1. If there were changes to the data after the baseline transfer, send a "Perform Replication Transfer" request to capture any incremental data written after the baseline transfer was completed. Repeat this operation for _each_ migration volume. 
 
     ```rest
-        POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-names>/providers/Microsoft.NetApp/netAppAccounts/<account-name>>/capacityPools/<capacity-pool>/volumes/<volumes>/performReplicationTransfer?api-version=2024-06-01 
+        POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-names>/providers/Microsoft.NetApp/netAppAccounts/<account-name>>/capacityPools/<capacity-pool>/volumes/<volumes>/performReplicationTransfer?api-version=2025-07-01 
     ```
 
 1. Break the replication relationship. [To break replication in the portal, navigate to each volume's **Replication** menu then select **Break peering**.](cross-region-replication-manage-disaster-recovery.md) You can alternately submit an API request: 
 
     ```rest
-    POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group>/providers/Microsoft.NetApp/netAppAccounts/<NetApp-account>/capacityPools/<capacity-pool-name>>/volumes/<volumes>/breakReplication?api-version=2025-06-01
+    POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group>/providers/Microsoft.NetApp/netAppAccounts/<NetApp-account>/capacityPools/<capacity-pool-name>>/volumes/<volumes>/breakReplication?api-version=2025-07-01
     ```
 
     >[!NOTE]
@@ -235,7 +235,7 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
 1. Delete the migration replication relationship. If the deleted replication is the last migration associated with your subscription, the associated cluster peer and intercluster LIFs are deleted. 
 
     ```rest
-    POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-name>/providers/Microsoft.NetApp/netAppAccounts/<NetApp-account>/capacityPools/<capacity-pool>/volumes/<volume-names>/finalizeExternalReplication?api-version=2025-06-01
+    POST https://<region>.management.azure.com/subscriptions/<subscription-ID>/resourceGroups/<resource-group-name>/providers/Microsoft.NetApp/netAppAccounts/<NetApp-account>/capacityPools/<capacity-pool>/volumes/<volume-names>/finalizeExternalReplication?api-version=2025-07-01
     ```
 
     Finalizing replication removes all the peering information on Azure NetApp Files. Manually confirm that all replication data is removed on the ONTAP cluster. If any peering information remains, run the `cluster peer delete` command. 

articles/azure-netapp-files/migrate-volumes.md

@@ -381,7 +381,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
     Backup further extends Azure NetApp Files' built-in snapshot technology; when snapshots are vaulted to a Backup vault only changed data blocks relative to previously vaulted snapshots are copied and stored, in an efficient format. Vaulted snapshots however are still represented in full and can be restored to a new volume individually and directly, eliminating the need for an iterative full-incremental recovery process.   
 
     This feature is now generally available in all [supported regions](backup-introduction.md#supported-regions). 
-
+    
 ## April 2024 
 
 * [Application volume group for Oracle](application-volume-group-oracle-introduction.md) (preview)