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

Author: halkazwini

articles/api-center/includes/install-apic-extension.md

@@ -1,17 +1,17 @@
 ---
 title: Include file
-description: Include file
+description: Notes about 'apic-extension' Azure CLI extension installation.
 services: api-center
-
+author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 05/23/2024
-
+ms.date: 02/20/2026
+ms.author: danlep
 ms.custom: Include file
 ---
 
 > [!NOTE]
-> `az apic` commands require the `apic-extension` Azure CLI extension. If you haven't used `az apic` commands, the extension can be installed dynamically when you run your first `az apic` command, or you can install the extension manually. Learn more about [Azure CLI extensions](/cli/azure/azure-cli-extensions-overview).
+> The `az apic` commands require the `apic-extension` Azure CLI extension. The extension can be installed dynamically when you run your first `az apic` command, or you can install the extension manually. For more information, see [Manage Azure CLI Extensions: Install, Update, and Remove](/cli/azure/azure-cli-extensions-overview).
 >
-> See the [release notes](https://github.com/Azure/azure-cli-extensions/blob/main/src/apic-extension/HISTORY.rst) for the latest changes and updates in the `apic-extension`. Certain features may require a preview or specific version of the extension.
+> For the latest changes and updates in the `apic-extension`, see the [release notes](https://github.com/Azure/azure-cli-extensions/blob/main/src/apic-extension/HISTORY.rst). Certain features might require a preview or specific version of the extension.

articles/api-center/media/register-apis-github-actions/api-registered-api-center.png

@@ -4,7 +4,7 @@ description: This how-to article walks you through configuring routing on a regi
 author: seligj95
 ms.author: jordanselig
 ms.topic: how-to
-ms.date: 11/24/2025
+ms.date: 02/25/2026
 ms.service: azure-app-service
 ---
 
@@ -20,7 +20,7 @@ Your app is already integrated using the regional virtual network integration fe
 
 Application routing defines what traffic is routed from your app and into the virtual network. You can configure routing at two levels:
 
-- **All traffic routing** (`outboundVnetRouting.allTraffic`): Routes all outbound traffic from your app through the virtual network integration, including application traffic and configuration traffic (such as container image pulls, content share access, and backup operations).
+- **All traffic routing** (`outboundVnetRouting.allTraffic`): Routes all outbound traffic from your app through the virtual network integration, including application traffic and configuration traffic (such as container image pulls, content share access, backup operations, and managed identity token acquisition).
 - **Application traffic only** (`outboundVnetRouting.applicationTraffic`): Routes only application-generated traffic through the virtual network integration, while configuration traffic continues to use the public route by default (unless individually configured in the configuration routing section).
 
 We recommend that you use the `outboundVnetRouting.allTraffic` property to enable routing of all traffic. Using this property allows you to audit the behavior with [a built-in policy](https://www.azadvertizer.net/azpolicyadvertizer/a691eacb-474d-47e4-b287-b4813ca44222.html). 
@@ -114,6 +114,14 @@ az resource update --resource-group <group-name> --name <app-name> --resource-ty
 > [!NOTE]
 > For backwards compatibility, the legacy `vnetBackupRestoreEnabled` property is still supported.
 
+### Managed identity
+
+Routing managed identity token acquisition traffic over virtual network integration can be configured using the Azure CLI. When enabled, requests to acquire Microsoft Entra tokens for managed identities are routed through the virtual network integration.
+
+```azurecli-interactive
+az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.outboundVnetRouting.managedIdentityTraffic=true
+```
+
 ## Next steps
 
 - [Enable virtual network integration](./configure-vnet-integration-enable.md)

articles/api-center/media/register-apis-github-actions/repository-secrets-github-small.png

@@ -3,7 +3,7 @@ title: Integrate your app with an Azure virtual network
 description: Integrate your app in Azure App Service with Azure virtual networks.
 author: seligj95
 ms.topic: conceptual
-ms.date: 09/03/2025
+ms.date: 02/25/2026
 ms.update-cycle: 1095-days
 ms.author: jordanselig
 ms.custom:
@@ -92,7 +92,7 @@ For each App Service plan instance, you need:
 For 10 instances:
 5 x 10 = 50 IP addresses per App Service plan
 
-Since you have 1 App Service plan, 1 x 50 = 50 IP addresses.
+Since you have 1 App Service plan, 1 x 50 = 50 IP addresses
 
 You are in addition limited by the number of cores available in the worker tier used. Each core adds three networking units. The worker itself uses one unit and each virtual network connection uses one unit. The remaining units can be used for apps.
 
@@ -151,6 +151,10 @@ When using custom containers, you can pull the container over the virtual networ
 
 App Service has built-in backup/restore, but if you want to back up to your own storage account, you can use the custom backup/restore feature. If you want to route the traffic to the storage account through the virtual network integration, you must configure the route setting. Database backup isn't supported over the virtual network integration.
 
+#### Managed identity
+
+By default, managed identity token acquisition traffic goes over the public route. You can route this traffic through the virtual network integration so that token requests to Microsoft Entra ID are sent through the virtual network. Learn [how to configure managed identity routing](./configure-vnet-integration-routing.md#managed-identity).
+
 #### App settings using Key Vault references
 
 App settings using Key Vault references attempt to get secrets over the public route. If the Key Vault is blocking public traffic and the app is using virtual network integration, an attempt is made to get the secrets through the virtual network integration.

articles/api-center/media/register-apis-github-actions/repository-secrets-github.png

@@ -1,12 +1,13 @@
 ---
-title: Internet peering - FAQ
+title: Internet Peering - FAQ
 description: This article provides answers to some of the frequently asked questions asked about Internet peering.
 services: internet-peering
 author: halkazwini
 ms.author: halkazwini
 ms.service: internet-peering
 ms.topic: faq
-ms.date: 10/23/2024
+ms.date: 02/25/2026
+
 # Customer intent: As a network engineer, I want to understand the differences between Internet peering options and their configurations, so that I can effectively manage my organization’s connectivity and optimize performance when integrating with Microsoft services.
 ---
 

articles/api-center/media/register-apis-github-actions/workflow-action.png

@@ -1,15 +1,14 @@
 ---
-title: Create or modify an Exchange peering with Route Server - Azure portal
+title: Create or Modify an Exchange Peering with Route Server - Azure Portal
 titleSuffix: Internet Peering
 description: Create or modify an Exchange peering with Route Server using the Azure portal.
-ms.author: halkazwini
 author: halkazwini
+ms.author: halkazwini
 ms.service: internet-peering
 ms.topic: how-to
-ms.date: 03/03/2025
+ms.date: 02/25/2026
 ms.custom: sfi-image-nochange
 
-#CustomerIntent: As an administrator, I want to learn how to create or modify an an Exchange peering with Route Server using the Azure portal so I can manage my Exchange peerings.
 # Customer intent: As a network administrator, I want to create or modify an Exchange peering with Route Server using the Azure portal, so that I can efficiently manage my network configurations and ensure optimal connectivity.
 ---