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

Author: gitName

.openpublishing.publish.config.json

@@ -632,6 +632,12 @@
             "branch": "main",
             "branch_mapping": {}
         },
+        {
+            "path_to_root": "app-service-agentic-langgraph-foundry-python",
+            "url": "https://github.com/Azure-Samples/app-service-agentic-langgraph-foundry-python",
+            "branch": "main",
+            "branch_mapping": {}
+        },
         {
             "path_to_root": "app-service-agentic-semantic-kernel-java",
             "url": "https://github.com/Azure-Samples/app-service-agentic-semantic-kernel-java",

.openpublishing.redirection.json

@@ -7152,7 +7152,17 @@
     {
       "source_path": "articles/reliability/migrate-storage.md",
       "redirect_url": "/azure/storage/common/redundancy-migration",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/reliability/reliability-operator-nexus.md",
+      "redirect_url": "/azure/reliability/overview-reliability-guidance",
+      "redirect_document_id": false
     }
+
+
+
+    
   ]
 }
 

articles/active-directory-b2c/service-limits.md

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 07/29/2025
+ms.date: 08/19/2025
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
 
@@ -169,14 +169,20 @@ The following table lists the administrative configuration limits in the Azure A
 |Number of sign-out URLs per application        |1          |
 |String Limit per Attribute      |250 Chars          |
 |Number of B2C tenants per subscription      |20         |
-|Total number of objects (user accounts and applications) per tenant (default limit)|1.25 million |
-|Total number of objects (user accounts and applications) per tenant (using a verified custom domain). If you want to increase this limit, please contact [Microsoft Support](find-help-open-support-ticket.md).|5.25 million |
+|Number of objects (user accounts and applications) per tenant (default limit)  <sup>2</sup>|1.25 million|
+|Number of objects (user accounts and applications) per tenant (using a verified custom domain) <sup>3</sup>. If you want to increase this limit, please contact [Microsoft Support](find-help-open-support-ticket.md).|5.25 million|
+|Number of objects per tenant for Japan Go-Local Azure AD B2C tenants (default limit) <sup>4</sup>|310K|
+|Number of objects per tenant for Japan Go-Local Azure AD B2C tenants (using a verified custom domain) <sup>5</sup>. If you want to increase this limit, please contact [Microsoft Support](find-help-open-support-ticket.md).|570K|
 |Levels of [inheritance](custom-policy-overview.md#inheritance-model) in custom policies     |10         |
 |Number of policies per Azure AD B2C tenant (user flows + custom policies)     |200          |
 |Maximum policy file size      |1024 KB          |
 |Number of API connectors per tenant     |20         |
 
-<sup>1</sup> See also [Microsoft Entra service limits and restrictions](../active-directory/enterprise-users/directory-service-limits-restrictions.md).
+- <sup>1</sup> See also [Microsoft Entra service limits and restrictions](../active-directory/enterprise-users/directory-service-limits-restrictions.md).
+- <sup>2</sup> 1M user accounts and 250K applications.
+- <sup>3</sup> 5M user accounts and 250K applications.
+- <sup>4</sup> 60K user accounts and 250K applications.
+- <sup>5</sup> 320K user accounts and 250K applications.
 
 ## Region specific service limits 
 

articles/api-management/api-management-region-availability.md

@@ -31,6 +31,7 @@ Information in the following table is updated regularly. Capacity availability i
 | Australia East | ✅ | ✅ | ✅ | ✅ |
 | Australia Southeast | ✅ | ✅ | | |
 | Brazil South | ✅ | ✅ | |  |
+| Canada Central  | ✅ | ✅ | |  |
 | Central India  | ✅ | ✅ | |  |
 | Central US  | ✅ | ✅ | |  |
 | East Asia | ✅ | ✅ | | ✅ |

articles/api-management/observability.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 02/10/2025
+ms.date: 08/26/2025
 ms.author: danlep
 ---
 
@@ -27,21 +27,20 @@ The following table summarizes all the observability capabilities supported by A
 > [!NOTE]
 > For API consumers who use the developer portal, a built-in API report is available. It only provides information about their individual API usage during the preceding 90 days. Currently, the built-in API report isn't available in the developer portal for the v2 service tiers.
 >  
-| Tool        | Useful for    | Data lag | Retention | Sampling | Data kind | Supported Deployment Model(s) |
+| Tool        | Useful for    | Data lag<sup>4</sup> | Retention | Sampling | Data kind | Supported Deployment Model(s) |
 |:------------- |:-------------|:---- |:----|:---- |:--- |:---- |
-| **[API Inspector](api-management-howto-api-inspector.md)** | Testing and debugging | Instant | Last 100 traces | Turned on per request | Request traces | Managed, Self-hosted, Azure Arc, Workspace |
+| **[Request tracing (API Inspector)](api-management-howto-api-inspector.md)** | Testing and debugging | Instant | Last 100 traces | Turned on per request | Request traces | Managed, Self-hosted, Azure Arc, Workspace |
 | **[Built-in Analytics](monitor-api-management.md#get-api-analytics-in-azure-api-management)** | Reporting and monitoring | Minutes | Lifetime | 100% | Reports and logs | Managed |
 | **[Azure Monitor Metrics](monitor-api-management-reference.md#metrics)** | Reporting and monitoring | Minutes | 90 days (upgrade to extend) | 100% | Metrics | Managed, Self-hosted<sup>2</sup>, Azure Arc |
 | **[Azure Monitor Logs](monitor-api-management-reference.md#resource-logs)** | Reporting, monitoring, and debugging | Minutes | 31 days/5GB (upgrade to extend) | 100% (adjustable) | Logs | Managed<sup>1</sup>, Self-hosted<sup>3</sup>, Azure Arc<sup>3</sup> |
 | **[Azure Application Insights](api-management-howto-app-insights.md)** | Reporting, monitoring, and debugging | Seconds | 90 days/5GB (upgrade to extend) | Custom | Logs, metrics | Managed<sup>1</sup>, Self-hosted<sup>1</sup>, Azure Arc<sup>1</sup>, Workspace<sup>1</sup> |
 | **[Logging through Azure Event Hubs](api-management-howto-log-event-hubs.md)** | Custom scenarios | Seconds | User managed | Custom | Custom | Managed<sup>1</sup>, Self-hosted<sup>1</sup>, Azure Arc<sup>1</sup> |
 | **[OpenTelemetry](how-to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md#introduction-to-opentelemetry)** | Monitoring | Minutes | User managed | 100% | Metrics | Self-hosted<sup>2</sup> |
 
-*1. Optional, depending on the configuration of feature in Azure API Management*
-
-*2. Optional, depending on the configuration of the gateway*
-
-*3. The [self-hosted gateway](self-hosted-gateway-overview.md) currently doesn't send diagnostic logs to Azure Monitor. However, it's possible to configure and persist logs locally where the self-hosted gateway is deployed. For more information, please see [configuring local metrics and logs for self-hosted gateway](how-to-configure-local-metrics-logs.md)*
+<sup>1</sup> Optional, depending on the configuration of feature in Azure API Management.<br/>
+<sup>2</sup> Optional, depending on the configuration of the gateway.<br/>
+<sup>3</sup> The [self-hosted gateway](self-hosted-gateway-overview.md) currently doesn't send diagnostic logs to Azure Monitor. However, it's possible to configure and persist logs locally where the self-hosted gateway is deployed. For more information, see [configuring local metrics and logs for self-hosted gateway](how-to-configure-local-metrics-logs.md).<br/>
+<sup>4</sup> Except for request tracing, all logging in API Management occurs asynchronously.
 
 ## Related content
 

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

@@ -3,7 +3,7 @@ title: Configure Premium V4 Tier
 description: Learn how to better performance for your web, mobile, and API app in Azure App Service by scaling to the new Premium V4 pricing tier.
 keywords: app service, azure app service, scale, scalable, app service plan, app service cost
 ms.topic: how-to
-ms.date: 07/17/2025
+ms.date: 08/22/2025
 ms.author: msangapu
 author: msangapu-msft
 ms.custom:
@@ -104,6 +104,7 @@ Premium V4 is available in the following regions:
 - East US 2
 - France Central
 - Japan East
+- Korea Central
 - North Central US
 - North Europe
 - Norway East

articles/app-service/app-service-managed-certificate-changes-july-2025.md

@@ -51,6 +51,10 @@ You can use [Azure Resource Graph (ARG)](https://portal.azure.com/?feature.custo
 ### Scenario 1: Site is not publicly accessible
 This ARG query retrieves a list of sites that either have the public network access property disabled or are configured to use client certificates. It then filters for sites that are using App Service Managed Certificates (ASMC) for their custom hostname SSL bindings. These certificates are the ones that could be affected by the upcoming changes. However, this query does not provide complete coverage, as there may be other configurations impacting public access to your app that are not included here. Ultimately, this query serves as a helpful guide for users, but a thorough review of your environment is recommended. You can copy this query, paste it into [ARG Explorer](https://portal.azure.com/?feature.customPortal=false#view/HubsExtension/ArgQueryBlade), and then click "Run query" to view the results for your environment. 
 
+> [!NOTE]
+> ARG can only retrive site property values (ie. client certificate and public network access), however it cannot retrieve any site config values (ie. IP restrictions). If you would like to retrive both site properties and site config values as well, you can refer to this [PowerShell script from GitHub](https://github.com/nimccoll/AppServiceManagedCertificates).
+> 
+
 ```kql
 // ARG Query: Identify App Service sites that commonly restrict public access and use ASMC for custom hostname SSL bindings 
 resources 
@@ -87,7 +91,6 @@ resources
 | project siteName, siteId, siteResourceGroup, publicNetworkAccess, clientCertEnabled, thumbprint, certName, certId, certResourceGroup, certExpiration, canonicalName
 ```
 
-
 ### Scenario 2: Site is an Azure Traffic Manager "nested" or "external" endpoint
 If your App Service uses custom domains routed through **Azure Traffic Manager**, you may be impacted if your profile includes **external** or **nested endpoints**. These endpoint types are not supported for certificate issuance or renewal under the new validation.
 

articles/app-service/environment/overview.md

@@ -3,7 +3,7 @@ title: App Service Environment Overview
 description: Learn about App Service Environments, which are fully isolated and single-tenant App Service deployments that provide high-scale, network-secured hosting.
 author: seligj95
 ms.topic: overview
-ms.date: 08/14/2025
+ms.date: 08/25/2025
 ms.update-cycle: 1095-days
 ms.author: jordanselig
 ms.custom:
@@ -143,7 +143,7 @@ App Service Environment v3 is available in the following regions.
 | Central India        | ✅                           | ✅                          |
 | Central US           | ✅                           | ✅                          |
 | East Asia            | ✅                           | ✅                          |
-| East US              | ✅                           | ✅                          |
+| East US              | ✅                           | ✅**                        |
 | East US 2            | ✅                           | ✅                          |
 | France Central       | ✅                           | ✅                          |
 | France South         | ✅                           |                             |

articles/app-service/getting-started.md

@@ -42,6 +42,7 @@ stacks, App Service supports all recent Java long-term support (LTS) versions. T
 several key scenarios for which you should consider adopting App Service for your Java 
 applications.
 
+
 ### Java SE on App Service
 Java SE on App Service allows you to effortlessly deploy your applications to fully 
 managed Java Virtual Machine (JVM) instances. You should consider this stack if you 
@@ -59,6 +60,10 @@ as WebLogic or WebSphere that can be easily migrated to Tomcat. You can deploy
 your web application archive (WAR) file and let App Service do the rest.
 
 ### JBoss EAP on App Service
+
+> [!NOTE]
+> JBoss EAP on App Service now supports "Bring Your Own License" (BYOL) billing, this allows customers with existing Red Hat subscriptions to apply those licenses directly to their JBoss EAP deployments on Azure App Service. [Learn more](https://aka.ms/byol-eap-jboss).
+
 You can effortlessly run any JBoss EAP version currently supported by Red Hat on this 
 App Service stack. JBoss EAP is fully compatible with the Java Enterprise Edition (EE) 
 and Jakarta EE standards. The stack can optionally support any application that requires 

articles/app-service/includes/configure-language-java-data-sources/configure-jboss-mysql.md

@@ -7,6 +7,9 @@ ms.date: 11/05/2024
 ms.author: cephalin
 ---
 
+> [!NOTE]
+> JBoss EAP on App Service now supports "Bring Your Own License" (BYOL) billing, this allows customers with existing Red Hat subscriptions to apply those licenses directly to their JBoss EAP deployments on Azure App Service. [Learn more](https://aka.ms/byol-eap-jboss).
+
 1. Put your JBoss CLI commands into a file named *jboss-cli-commands.cli*. The JBoss commands must add the module and register it as a data source. The following example shows the JBoss CLI commands for creating a MySQL data source with the JNDI name `java:jboss/datasources/mysqlDS`.
 
     ```bash