Merge pull request #314579 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-10 17:00 UTC

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

.openpublishing.redirection.json

@@ -1,5 +1,140 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/healthcare-apis/iot/concepts-machine-learning.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-machine-learning",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/concepts-power-bi.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-power-bi",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/concepts-teams.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-teams",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/configure-metrics.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/configure-metrics",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-arm-template.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-arm-template",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-bicep-powershell-cli",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-choose-method.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-choose-method",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-json-powershell-cli.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-json-powershell-cli",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/deploy-manual-portal.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-manual-portal",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/device-messages-through-iot-hub.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/device-messages-through-iot-hub",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/frequently-asked-questions.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/frequently-asked-questions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/get-started.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/get-started",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/git-projects.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/git-projects",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-enable-diagnostic-settings",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-calculatedcontent-templates.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-calculatedcontent-templates",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-custom-functions.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-custom-functions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-mapping-debugger.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-mapping-debugger",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/index.yml",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/index",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-device-data-processing-stages.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-device-data-processing-stages",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-device-mapping.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-device-mapping",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-fhir-destination-mapping",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview-of-samples.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-samples",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/overview.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/troubleshoot-errors-deployment.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/troubleshoot-errors-deployment",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/iot/troubleshoot-errors-logs.md",
+      "redirect_url": "/previous-versions/azure/healthcare-apis/iot/troubleshoot-errors-logs",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/sentinel/datalake/sentinel-mcp-chatgpt-connector.md",
       "redirect_url": "/azure/sentinel/datalake/sentinel-mcp-chatgpt-claude-connector",

articles/app-service/app-service-key-vault-references.md

@@ -90,6 +90,9 @@ After you grant permissions to the user-assigned identity, follow these steps:
 
 This setting applies to all Key Vault references for the app.
 
+> [!TIP]
+> If you want to revert your app to use the system-assigned identity, set the value to `SystemAssigned` instead of the Resource ID.
+
 ## <a name = "rotation"></a> Understand rotation
 
 If the secret version isn't specified in the reference, the app uses the latest version that exists in the key vault. When newer versions become available, such as with rotation, the app is automatically updated and begins using the latest version within 24 hours.

articles/app-service/configure-authentication-provider-openid-connect.md

@@ -32,7 +32,7 @@ When you register your app, you need to collect a *client ID* and a *client secr
 > - The client secret value is an important security credential. Don't share this secret with anyone or distribute it within a client application.
 > - Your app must provide the client secret if you want users to acquire access tokens using the interactive authorization code flow. If you don't want to acquire access tokens, you don't need to use a secret.
 
-You also need the provider's OIDC metadata. This metadata is often exposed in a [configuration metadata document](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig) that you can get at the path formed by appending `/.well-known/openid-configuration` to the provider's issuer URL.
+You also need the provider's OIDC metadata. This metadata is often exposed in a [configuration metadata document](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig) that you can get at the path formed by appending `/.well-known/openid-configuration` to the provider's issuer URL. The metadata includes `mtls_endpoint_aliases` as part of [Mutual-TLS Client Authentication](https://datatracker.ietf.org/doc/html/rfc8705).
 
 If you can't access a configuration metadata document, get the following values separately:
 

articles/app-service/reference-app-settings.md

@@ -306,7 +306,7 @@ APACHE_RUN_GROUP | RUN sed -i 's!User ${APACHE_RUN_GROUP}!Group www-data!g' /etc
 > | `WORDPRESS_ADMIN_EMAIL` | Deployment only | Not applicable | Not applicable | WordPress admin email. |
 > | `WORDPRESS_ADMIN_PASSWORD` | Deployment only | Not applicable | Not applicable | WordPress admin password. This setting is only for deployment purposes. Modifying this value has no effect on the WordPress installation. To change the WordPress admin password, see [Reset your password](https://wordpress.org/support/article/resetting-your-password/#to-change-your-password). |
 > | `WORDPRESS_ADMIN_USER` | Deployment only | Not applicable | Not applicable|WordPress admin username. |
-> | `WORDPRESS_ADMIN_LOCALE_CODE` | Deployment only | Not applicable | Not applicable | Database username used to connect to WordPress. |
+> | `WORDPRESS_LOCALE_CODE` | Deployment only | `en_US` | Not applicable | WordPress localization code for site language. |
 
 ## Domain and DNS
 

articles/app-service/scenario-ai-model-context-protocol-server.md

@@ -38,6 +38,8 @@ Consider implementing your App Service app as an MCP server when you want to:
 - **Improve developer productivity**: Reduce context switching by bringing your app's functionality into the IDE
 - **Leverage existing infrastructure**: Use your deployed App Service apps as agent tools without separate deployments
 
+If you're evaluating where to host an MCP server in Azure, compare App Service with other options in [Choose an Azure service for hosting MCP servers](/azure/container-apps/mcp-choosing-azure-service) before selecting your deployment target.
+
 MCP is particularly valuable for line-of-business applications, internal tools, and developer-focused services where making functionality easily accessible to AI agents can dramatically improve productivity.
 
 ## How MCP works with App Service

articles/app-service/toc.yml

@@ -23,6 +23,8 @@ items:
     href: scenario-ai-openapi-tool.md
   - name: Model Context Protocol servers
     href: scenario-ai-model-context-protocol-server.md
+  - name: MCP hosting options
+    href: /azure/container-apps/mcp-choosing-azure-service?toc=/azure/app-service/toc.json&bc=/azure/app-service/breadcrumb/toc.json
   - name: Local small language models
     href: scenario-ai-local-small-language-model.md
   - name: Secure AI applications

articles/application-gateway/overview-v2.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: overview
-ms.date: 12/09/2025
+ms.date: 4/10/2026
 ms.author: mbender
 ms.custom: references_regions, devx-track-azurepowershell
 # Customer intent: As a cloud architect, I want to understand the features and enhancements of Azure Application Gateway v2, so that I can effectively plan migration from v1 and utilize its capabilities for improved application performance and reliability.
@@ -22,7 +22,7 @@ Application Gateway v2 is the latest version of Application Gateway. It provides
 
 The v2 SKU includes the following enhancements:
 
-- **TCP/TLS proxy**: Azure Application Gateway now also supports Layer 4 (TCP protocol) and TLS (Transport Layer Security) proxying. This feature is currently in public preview. For more information, see [Application Gateway TCP/TLS proxy overview](tcp-tls-proxy-overview.md).
+- **TCP/TLS proxy**: Azure Application Gateway now also supports Layer 4 (TCP protocol) and TLS (Transport Layer Security) proxying. For more information, see [Application Gateway TCP/TLS proxy overview](tcp-tls-proxy-overview.md).
 - **Autoscaling**: Application Gateway or WAF deployments under the autoscaling SKU can scale out or in based on changing traffic load patterns. Autoscaling also removes the requirement to choose a deployment size or instance count during provisioning. This SKU offers true elasticity. In the Standard_v2 and WAF_v2 SKU, Application Gateway can operate both in fixed capacity (autoscaling disabled) and in autoscaling enabled mode. Fixed capacity mode is useful for scenarios with consistent and predictable workloads. Autoscaling mode is beneficial in applications that see variance in application traffic.
 - **Zone redundancy**: Application Gateway or WAF deployments span multiple Availability Zones by default, removing the need to provision separate Application Gateway instances in each zone with a Traffic Manager. Application Gateway instances are deployed (by default) in a minimum of two availability zones, which makes it more resilient to zone failure. The backend pool for applications can be similarly distributed across availability zones.
 
@@ -53,7 +53,7 @@ The following table displays a comparison between Basic and Standard_v2.
 |     :---:                | :---                                     |     :---:      |     :---:         |
 | Reliability              | SLA                                      | 99.9           | 99.95             |
 | Functionality - basic    | HTTP/HTTP2/HTTPS<br>WebSocket<br>Public/Private IP<br>Cookie Affinity<br>Path-based affinity<br>Wildcard<br>Multisite<br>KeyVault<br>Zone<br>Header rewrite | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713; | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;|
-| Functionality - advanced | AKS (via AGIC)<br>URL rewrite<br>mTLS<br>Private Link<br>Private-only (preview)<br>TCP/TLS Proxy (preview) |  | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713; |
+| Functionality - advanced | AKS (via AGIC)<br>URL rewrite<br>mTLS<br>Private Link<br>Private-only<br>TCP/TLS Proxy |  | &#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713;<br>&#x2713; |
 | Scale                    | Max. connections per second<br>Number of listeners<br>Number of backend pools<br>Number of backend servers per pool<br>Number of rules | 200<sup>1</sup><br>5<br>5<br>5<br>5  | 62500<sup>1</sup><br>100<br>100<br>1200<br>400 |
 | Capacity Unit            | Connections per second per compute unit<br>Throughput<br>Persistent new connections  | 10<br>2.22 Mbps<br>2500 | 50<br>2.22 Mbps<br>2500 |