merge with main

Author: b-ahibbard

.openpublishing.publish.config.json

@@ -638,6 +638,12 @@
             "branch": "main",
             "branch_mapping": {}
         },
+        {
+            "path_to_root": "playwright-workspaces",
+            "url": "https://github.com/Azure/playwright-workspaces",
+            "branch": "main",
+            "branch_mapping": {}
+        },
         {
             "path_to_root": "playwright-testing-service",
             "url": "https://github.com/microsoft/playwright-testing-service",

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/app-service/app-service-configure-premium-v3-tier.md

@@ -128,4 +128,4 @@ New-AzAppServicePlan -ResourceGroupName <resource_group_name> `
 
 - [Scale up an app in Azure App Service](manage-scale-up.md)
 - [Get started with autoscale in Azure](/azure/azure-monitor/autoscale/autoscale-get-started)
-- [Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Run a load test to identify performance bottlenecks in a web app](../app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md)

articles/app-service/app-service-configure-premium-v4-tier.md

@@ -160,4 +160,4 @@ New-AzAppServicePlan -ResourceGroupName <resource_group_name> `
 ## Related content
 
 - [Scale up an app in Azure App Service](manage-scale-up.md)
-- [Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Run a load test to identify performance bottlenecks in a web app](../app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md)

articles/app-service/manage-scale-per-app.md

@@ -139,4 +139,4 @@ Follow these steps to configure high-density hosting for your apps:
 
 - [What are Azure App Service plans?](overview-hosting-plans.md)
 - [App Service Environment overview](environment/overview.md)
-- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md)

articles/app-service/manage-scale-up.md

@@ -87,7 +87,7 @@ For a table of service limits, quotas, and constraints, and supported features i
 
 * [Get started with autoscale in Azure](/azure/azure-monitor/autoscale/autoscale-get-started)
 * [Configure Premium V3 tier for App Service](app-service-configure-premium-tier.md)
-* [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+* [Tutorial: Run a load test to identify performance bottlenecks in a web app](../app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md)
 <!-- LINKS -->
 [vmsizes]:https://azure.microsoft.com/pricing/details/app-service/
 [SQLaccountsbilling]:https://go.microsoft.com/fwlink/?LinkId=234930

articles/app-service/overview-diagnostics.md

@@ -141,4 +141,4 @@ Post your questions or feedback at [Share your ideas](https://feedback.azure.com
 
 ## Related content
 
-- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md)

articles/app-service/overview-inbound-outbound-ips.md

@@ -4,7 +4,7 @@ description: Learn how inbound and outbound IP addresses are used in Azure App S
 author: msangapu-msft
 ms.author: msangapu
 ms.topic: article
-ms.date: 08/05/2025
+ms.date: 08/07/2025
 ms.update-cycle: 1095-days
 ms.custom:
   - UpdateFrequency3
@@ -139,6 +139,8 @@ You can configure the IP mode behavior using the `IPMode` property:
 - **IPv6**: DNS returns IPv6 address only
 - **IPv4AndIPv6**: DNS returns both IPv4 and IPv6 addresses
 
+IPMode is a DNS-only feature. Every App Service site can receive requests via both IPv4 and IPv6 endpoints—regardless of the configured IpMode. IpMode only influences how DNS resolves the endpoint, so it affects clients that rely on DNS resolution (which should be most clients), but it doesn't restrict which protocol endpoints can be reached.
+
 ### Configure IPv6 support
 
 # [Azure portal](#tab/azure-portal)

articles/app-service/troubleshoot-diagnostic-logs.md

@@ -205,4 +205,4 @@ For information about restrictions for diagnostic settings, see [Destination lim
 - [Log queries in Azure Monitor](/azure/azure-monitor/logs/log-query-overview)
 - [Azure App Service quotas and alerts](web-sites-monitor.md)
 - [Troubleshoot an app in Azure App Service by using Visual Studio](troubleshoot-dotnet-visual-studio.md)
-- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md)

articles/app-service/troubleshoot-performance-degradation.md

@@ -175,4 +175,4 @@ You can also manage your app using Azure PowerShell. For more information, see [
 ## Related content
 
 - [Troubleshooting intermittent outbound connection errors in Azure App Service](troubleshoot-intermittent-outbound-connection-errors.md)
-- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
+- [Tutorial: Run a load test to identify performance bottlenecks in a web app](../app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md)