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

Author: v-thepet

articles/api-center/includes/api-center-service-limits.md

@@ -14,6 +14,7 @@ ms.custom: Include file
 
 | Resource | Free plan<sup>1</sup> | Standard plan<sup>2</sup> |
 | ---------------------------------------------------------------------- | -------------------------- |-------------|
+| Maximum number of APIs | 200 |  10,000 |
 | Maximum number of versions per API | 5 | 100 |
 | Maximum number of definitions per version | 5  | 5 |
 | Maximum number of deployments per API | 10 | 10 |

articles/app-service/configure-authentication-provider-aad.md

@@ -3,7 +3,7 @@ title: Configure Microsoft Entra Authentication
 description: Learn how to configure Microsoft Entra authentication as an identity provider for your App Service or Azure Functions app.
 ms.assetid: 6ec6a46c-bce4-47aa-b8a3-e133baef22eb
 ms.topic: how-to
-ms.date: 01/28/2025
+ms.date: 03/28/2025
 ms.custom: fasttrack-edit, AppServiceIdentity
 author: cephalin
 ms.author: cephalin

articles/app-service/configure-custom-container.md

@@ -226,9 +226,9 @@ Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WE
 
 You can use the */home* directory in your custom container file system to persist files across restarts and share them across instances. The */home* directory is provided to enable your custom container to access persistent storage. Saving data within */home* contributes to the [storage space quota](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-app-service-limits) included with your App Service Plan.
 
-When persistent storage is disabled, writes to the *C:\home* directory aren't persisted across app restarts or across multiple instances. When persistent storage is enabled, all writes to the *\home* directory persist. All instances of a scaled-out app can access them. Any existing files already present on the persistent storage when the container starts overwrite any contents in the *\home* directory of the container.
+When persistent storage is disabled, writes to the */home* directory aren't persisted across app restarts or across multiple instances. When persistent storage is enabled, all writes to the */home* directory persist. All instances of a scaled-out app can access them. Any existing files already present on the persistent storage when the container starts overwrite any contents in the */home* directory of the container.
 
-The only exception is the *\home\LogFiles* directory. This directory stores the container and application logs. This folder always persists upon app restarts if [application logging is enabled](troubleshoot-diagnostic-logs.md#enable-application-logging-linuxcontainer) with the **File System** option, whether or not persistent storage is enabled. In other words, enabling or disabling the persistent storage doesn't affect the application logging behavior.
+The only exception is the */home/LogFiles* directory. This directory stores the container and application logs. This folder always persists upon app restarts if [application logging is enabled](troubleshoot-diagnostic-logs.md#enable-application-logging-linuxcontainer) with the **File System** option, whether or not persistent storage is enabled. In other words, enabling or disabling the persistent storage doesn't affect the application logging behavior.
 
 We recommend that you write data to */home* or a [mounted Azure storage path](configure-connect-to-azure-storage.md?tabs=portal&pivots=container-linux). Data written outside these paths isn't persistent during restarts. The data is saved to platform-managed host disk space separate from the App Service Plans file storage quota.
 

articles/app-service/deploy-authentication-types.md

@@ -2,7 +2,7 @@
 title: Authentication Types by Deployment Methods
 description: Learn the available types of authentication with Azure App Service when you're deploying application code.
 ms.topic: concept-article
-ms.date: 01/24/2025
+ms.date: 03/28/2025
 author: cephalin
 ms.author: cephalin
 #customer intent: As an app developer, I want to understand the authentication options available for different deployment methods in Azure App Service.

articles/app-service/deploy-staging-slots.md

@@ -3,7 +3,7 @@ title: Set Up Staging Environments
 description: Learn how to deploy apps to a nonproduction slot and automatically swap into production. Increase the reliability and eliminate app downtime from deployments.
 ms.assetid: e224fc4f-800d-469a-8d6a-72bcde612450
 ms.topic: how-to
-ms.date: 01/24/2025
+ms.date: 03/28/2025
 author: cephalin
 ms.author: cephalin
 ms.custom: fasttrack-edit, devx-track-azurepowershell, devx-track-azurecli, ai-video-demo

articles/app-service/includes/regionalization-note.md

@@ -12,4 +12,4 @@ ms.subservice: web-apps
 > [!NOTE]
 > Starting June 1, 2024, newly created App Service apps can generate a unique default host name that uses the naming convention `<app-name>-<random-hash>.<region>.azurewebsites.net`. For example: `myapp-ds27dh7271aah175.westus-01.azurewebsites.net`. Existing app names remain unchanged.
 >
-> For more information, see the [blog post about creating a web app with a unique default host name](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/public-preview-creating-web-app-with-a-unique-default-hostname/ba-p/4156353).
+> For more information, see the [blog post about creating a web app with a unique default host name](https://techcommunity.microsoft.com/blog/appsonazureblog/secure-unique-default-hostnames-ga-on-app-service-web-apps-and-public-preview-on/4303571).

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

@@ -2,7 +2,7 @@
 title: Environment Variables and App Settings Reference
 description: This article describes the commonly used environment variables in Azure App Service, and which ones can be modified with app settings.
 ms.topic: conceptual
-ms.date: 03/19/2025
+ms.date: 03/28/2025
 author: cephalin
 ms.author: cephalin
 ---

articles/application-gateway/configuration-http-settings.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 03/19/2025
+ms.date: 04/14/2025
 ms.author: greglin
 ---
 
@@ -34,9 +34,7 @@ The default affinity cookie name is *ApplicationGatewayAffinity* and you can cha
 
 ## Connection draining
 
-Connection draining helps you gracefully remove backend pool members during planned service updates. It applies to backend instances that are 
-- explicitly removed from the backend pool, or
-- reported as unhealthy by the health probes.
+Connection draining helps you gracefully remove backend pool members during planned service updates. It applies to backend instances that are explicitly removed from the backend pool.
 
 You can apply this setting to all backend pool members by enabling Connection Draining in the Backend Setting. It ensures that all deregistering instances in a backend pool don't receive any new requests/connections while maintaining the existing connections until the configured timeout value. This process is also true for WebSocket connections.
 

articles/application-gateway/features.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 03/24/2023
+ms.date: 04/14/2025
 ms.author: greglin
 ---
 
@@ -104,15 +104,11 @@ For more information, see [WebSocket support](application-gateway-websocket.md)
 
 ## Connection draining
 
-Connection draining helps you achieve graceful removal of backend pool members during planned service updates or problems with backend health. This setting is enabled via the [Backend Setting](configuration-http-settings.md) and is applied to all backend pool members during rule creation. Once enabled, the application gateway ensures all deregistering instances of a backend pool don't receive any new requests while allowing existing requests to complete within a configured time limit. It applies to cases where backend instances are:
-- explicitly removed from the backend pool after a configuration change by a user, or
-- reported as unhealthy by the health probes
-
-The only exception is when requests continue to be proxied to the deregistering instances because of gateway-managed session affinity. 
+Connection draining helps you achieve graceful removal of backend pool members during planned service updates or problems with backend health. This setting is enabled via the [Backend Setting](configuration-http-settings.md) and is applied to all backend pool members during rule creation. Once enabled, the application gateway ensures all deregistering instances of a backend pool don't receive any new requests while allowing existing requests to complete within a configured time limit. It applies to cases where backend instances are explicitly removed from the backend pool after a configuration change by a user.
 
 The connection draining is honored for WebSocket connections as well. Connection draining is invoked for every single update to the gateway. To prevent connection loss to existing members of the backend pool, make sure to enable connection draining.
 
-For information on time limits, see [Backend Settings configuration](configuration-http-settings.md#connection-draining).
+For more details, see [Backend Settings configuration](configuration-http-settings.md#connection-draining).
 
 ## Custom error pages
 

articles/azure-cache-for-redis/index.yml

@@ -10,7 +10,7 @@ metadata:
     - ignite-2024
 
 
-  ms.date: 03/11/2025
+  ms.date: 04/14/2025
   appliesto:
     - ✅ Azure Cache for Redis
 
@@ -76,10 +76,10 @@ landingContent:
       - linkListType: overview
         links:
           - text: What is Azure Managed Redis?
-            url: ../redis/overview.md
+            url: /azure/redis/overview
           - text: What's new?
-            url: ../redis/whats-new.md
+            url: /azure/redis/whats-new
           - text: Azure Managed Redis architecture
-            url: ../redis/architecture.md
+            url: /azure/redis/architecture
           - text: Moving to Azure Managed Redis from Azure Cache for Redis
-            url: ../redis/migrate/migrate-overview.md
+            url: /azure/redis/migrate/migrate-overview