Merge pull request #308793 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-26 18:00 UTC

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

articles/api-management/tutorials/link-api-center.md

@@ -30,7 +30,7 @@ In this tutorial, you:
 
 Before you start, make sure you meet the following requirements.
 
-- An Azure account with an active subscription is required. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account).
+- An Azure account with an active subscription is required. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 - An existing API Management service in the subscription where you want to manage APIs
 - Contributor (or Owner) permissions on the API Management resource and permission to create resources in a resource group
 

articles/app-service/environment/app-service-app-service-environment-custom-settings.md

@@ -5,7 +5,7 @@ author: seligj95
 
 ms.assetid: 1d1d85f3-6cc6-4d57-ae1a-5b37c642d812
 ms.topic: tutorial
-ms.date: 08/20/2025
+ms.date: 11/26/2025
 ms.author: jordanselig
 ms.custom: mvc, devx-track-arm-template
 ms.service: azure-app-service
@@ -89,6 +89,9 @@ You can also disable TLS 1.0 and TLS 1.1 using the Azure portal by going to the
 
 App Service Environment supports changing the cipher suite from the default. The default set of ciphers is the same set that is used in the multitenant App Service. Changing the cipher suite is only possible with App Service Environment, the single-tenant offering, not the multitenant offering, because changing it affects the entire App Service deployment. There are two cipher suites that are required for an App Service Environment: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. Additionally, you should include the following cipher suites, which are required for TLS 1.3: TLS_AES_256_GCM_SHA384 and TLS_AES_128_GCM_SHA256.
 
+> [!IMPORTANT]
+> The `FrontEndSSLCipherSuiteOrder` App Service Environment cluster setting isn't compatible with the app-level `minTlsCipherSuite` setting. If you configure the cipher suite order at the App Service Environment level using `FrontEndSSLCipherSuiteOrder`, don't also configure the minimum TLS cipher suite at the individual app level. You must use one or the other, not both. Configuring both settings can cause SSL errors and rejected requests.
+
 To configure your App Service Environment to use just the ciphers that it requires, modify the **clusterSettings** as shown in the following sample. **Ensure that the TLS 1.3 ciphers are included at the beginning of the list**.
 
 ```json

articles/application-gateway/tcp-tls-proxy-overview.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 11/17/2025
+ms.date: 11/26/2025
 ms.author: mbender
 # Customer intent: As a network architect, I want to implement TCP/TLS proxy capabilities on an application gateway, so that I can efficiently manage both HTTP and non-HTTP workloads while ensuring secure connections to backend servers.
 ---
@@ -63,7 +63,6 @@ Process flow:
 - A WAF v2 SKU gateway allows the creation of TLS or TCP listeners and backends to support HTTP and non-HTTP traffic through the same resource. However, it does not inspect traffic on TLS and TCP listeners for exploits and vulnerabilities. 
 - The default [draining timeout](configuration-http-settings.md#connection-draining) value for backend servers is 30 seconds. At present, a user-defined draining value is not supported.
 - A configuration update (PUT) on Application Gateway ends the active connections after the default draining timeout period.
-- Client IP preservation is currently not supported.
 - Application Gateway Ingress Controller (AGIC) is not supported and works only with L7 proxy through HTTP(S) listeners.
 
 ## Next steps

articles/azure-maps/migrate-bing-maps-overview.md

@@ -165,7 +165,7 @@ Developers can get migration support through the [Azure Maps Q&A] or through one
 [Authentication with Azure Maps]: azure-maps-authentication.md
 [Authentication best practices]: authentication-best-practices.md
 [Autosuggest]: /bingmaps/rest-services/autosuggest
-[Azure Licensing]: https://azure.microsoft.com/pricing/purchase-options/azure-account
+[Azure Licensing]: https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn
 [Azure Maps account]: how-to-manage-account-keys.md#create-a-new-account
 [Azure Maps blog]: https://aka.ms/AzureMapsTechBlog
 [Azure Maps code samples]: https://samples.azuremaps.com/

articles/backup/backup-azure-monitor-alerts-notification.md

@@ -2,7 +2,7 @@
 title: Configure and manage Azure Monitor based alert notifications for Azure Backup
 description: Learn how to configure Azure Monitor alert notifications.
 ms.topic: how-to
-ms.date: 12/30/2024
+ms.date: 11/26/2025
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -18,7 +18,7 @@ This article describes how to configure and manage Azure Monitor based alert not
 
 To configure notifications for Azure Monitor alerts, create an [alert processing rule](/azure/azure-monitor/alerts/alerts-action-rules). To create an alert processing rule (earlier called *action rule*) to send email notifications to a given email address, follow these steps. Also, follow these steps to route these alerts to other notification channels, such as ITSM, webhook, logic app, and so on.
 
-1. In the [Azure portal](https://portal.azure.com/), go to **Business Continuity Center** > **Monitoring + Reporting** > **Alerts** to create or view alert processing rules. [Learn more](/azure/azure-monitor/alerts/alerts-processing-rules?tabs=portal&branch=main#configure-an-alert-processing-rule).
+1. In the [Azure portal](https://portal.azure.com/), go to **Resiliency** > **Monitoring + Reporting** > **Alerts** to create or view alert processing rules. [Learn more](/azure/azure-monitor/alerts/alerts-processing-rules?tabs=portal&branch=main#configure-an-alert-processing-rule).
 
 1. Send alerts to the notification channel of your choice using action groups as part of the alert processing rules. Learn [how to create action groups](/azure/azure-monitor/alerts/action-groups#create-an-action-group-in-the-azure-portal).
 
@@ -33,10 +33,10 @@ Learn more [about suppression of notifications during planned maintenance
 
 To create a suppression alert processing rule, follow these steps:
 
-1. Go to **Business Continuity Center** > **Monitoring + Reporting** > **Alerts**.
+1. Go to **Resiliency** > **Monitoring + Reporting** > **Alerts**.
 1. Select **Manage alerts** > **Manage alert processing rules**.
 
-   :::image type="content" source="./media/move-to-azure-monitor-alerts/alert-processing-rule-blade-inline.png" alt-text="Screenshot showing alert processing rules blade in portal." lightbox="./media/move-to-azure-monitor-alerts/alert-processing-rule-blade-expanded.png":::
+   :::image type="content" source="./media/move-to-azure-monitor-alerts/alert-processing-rule-blade.png" alt-text="Screenshot showing alert processing rules blade in portal." lightbox="./media/move-to-azure-monitor-alerts/alert-processing-rule-blade.png":::
 
 1. Select **Create**.