Merge pull request #298270 from MicrosoftDocs/main

4/15/2025 AM Publish

Author: Taojunshen

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/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/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

articles/azure-resource-manager/bicep/parameters.md

@@ -150,7 +150,7 @@ param storageAccountName string
 
 When you hover your cursor over **storageAccountName** in Visual Studio Code, you see the formatted text:
 
-:::image type="content" source="./media/parameters/vscode-bicep-extension-description-decorator-markdown.png" alt-text="Use Markdown-formatted text in VSCode":::
+:::image type="content" source="./media/parameters/vscode-bicep-extension-description-decorator-markdown.png" alt-text="Use Markdown-formatted text in VS Code":::
 
 Make sure the text follows proper Markdown formatting; otherwise, it might not display correctly when rendered.
 

articles/azure-resource-manager/management/tag-mission-critical-workload.md

@@ -1,40 +1,35 @@
 ---
-title: Mission critical workload labeling
-description: Understand how to label mission critical workloads in Azure for Microsoft workload assessments
+title: Label mission-critical workloads 
+description: Learn how to label mission-critical workloads in Azure to assess Microsoft workloads.
 ms.topic: conceptual
-ms.date: 03/20/2025
+ms.date: 04/14/2025
 ---
-# Mission critical workload labeling
 
-Azure provides a robust, scalable cloud platform with various tools and services to help you manage and optimize your resources. This document outlines how to tag resources in an Azure tenant for identifying mission-critical workloads and determining potential resiliency improvements. Tagging your resources streamlines the onboarding of your workload definition for Microsoft assessments, providing a more concisely targeted review.
+# Label mission-critical workloads
 
-## Understanding Azure tags
+Azure provides a robust, scalable cloud platform with various tools and services to help you manage and optimize your resources. This document outlines how to tag resources in an Azure tenant to identify mission-critical workloads and determine potential resiliency improvements. Tagging your resources streamlines how your workload definitions are onboarded for Microsoft assessments, providing a more concisely targeted review.
 
-For an introduction to tagging of Azure resources and to learn about requirements and limitations refer to the following article.
+## Understand Azure tags
 
-[Use tags to organize your Azure resources and management hierarchy - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources)
+For an introduction about tagging Azure resources and to learn about requirements and limitations, refer to [Use tags to organize your Azure resources and management hierarchy](/azure/azure-resource-manager/management/tag-resources).
 
-## Why identify mission critical workloads?
+## Why identify mission-critical workloads?
 
-Identifying mission critical related resources brings numerous benefits including resource management, cost management and optimization, security, automation and workload optimization. By tagging these resources, you can group them as part of a mission critical workload. These tags help in accurately identifying and managing these essential workloads. You can read more about tagging usage here [Resource naming and tagging decision guide - Cloud Adoption Framework | Microsoft Learn](/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming-and-tagging-decision-guide).
+The term _workload_ refers to a collection of application resources that support a common business goal or the execution of a common business process with multiple services, such as APIs and data stores, that work together to deliver specific end-to-end functionality.
 
-This article aligns with workload optimization, where tagging can help inform of opportunities to improve resiliency and further enhance your Service Level Objectives.
+Mission-critical workload resources are often spread across multiple resource groups and subscriptions. Regardless of the resource location, each resource within a mission-critical workload should be included in the workload definition and tagged appropriately.
 
-*This documentation supports a Microsoft assessment of your environment using the tagging approach described. Your Microsoft contact reviews this tagging approach with you at the beginning of the assessment. If you don't have an engagement with Microsoft, you can still follow the guidance to realize the benefits outlined earlier.*
+Identifying related mission-critical resources has benefits that include resource management, cost management and optimization, security, automation, and workload optimization. By tagging resources, you to group them into a mission-critical workload where tags accurately identify and manage these essential workloads.
 
-The term workload refers to a collection of application resources that support a common business goal or the execution of a common business process, with multiple services, such as APIs and data stores, working together to deliver specific end-to-end functionality.
+In a scenario where a mission-critical workload depends on a service that's shared across multiple workloads, such as an Azure ExpressRoute gateway or an Azure Firewall, the shared resources should also be included in the workload definition and tagged appropriately. See the examples in the following section for how to tag values on shared services.
 
-Mission critical workload resources are often spread across multiple resource groups and subscriptions. Regardless of the resource location, each resource within the mission critical workload should be included in the workload definition and tagged appropriately.
+This article aligns with workload optimization, and tagging can identify opportunities to improve resiliency and further enhance your Service Level Objectives.
 
-In a scenario where a mission critical workload depends on a service that is shared across multiple workloads, such as an ExpressRoute gateway or an Azure Firewall, the shared resources should also be included in the workload definition and tagged appropriately. See the example in the previous section for tag values to be used on shared services.
+*This documentation recommends the tagging approach described to support a Microsoft assessment of your environment. Your Microsoft contact reviews this tagging approach with you at the beginning of the assessment. If you don't have an engagement with Microsoft, you can still follow the guidance to realize the benefits outlined earlier.*
 
-For further insights into defining a workload, refer to the following article.
+## Mission-critical predefined tags
 
-[Azure Well-Architected Framework workloads - Microsoft Azure Well-Architected Framework | Microsoft Learn](/azure/well-architected/workloads)
-
-## Mission critical predefined tags
-
-To enable use by Microsoft in a workload assessment, the tags used for mission critical workloads must use the following tag name and adhere to the value format.
+To enable use by Microsoft in a workload assessment, the tags used for mission-critical workloads must use the following tag name and adhere to the value format:
 
 > [!Important]
 > Tag values must **NOT** contain numeric or non-English characters.
@@ -47,14 +42,14 @@ To enable use by Microsoft in a workload assessment, the tags used for mission c
 
 ### Examples
 
-#### Mission critical workload #1
+#### Mission-critical workload #1
 
 | **Workload Component** | **Tag Name** | **Tag Value** |
 |---|---|---|
 | **Workload A** | Azure.MissionCriticalWorkload | Finance-Workload |
 | **Shared Services** | Azure.MissionCriticalWorkload | SharedServices-ExpressRoute |
 
-#### Mission critical workload #2
+#### Mission-critical workload #2
 
 | **Workload Component** | **Tag Name** | **Tag Value** |
 |---|---|---|
@@ -64,11 +59,16 @@ To enable use by Microsoft in a workload assessment, the tags used for mission c
 
 ## How to apply Azure tags
 
-Tagging of mission critical workloads requires that tags be applied to each of the individual Azure resources that make up the workload. Tags can be applied to resources in the Azure portal, with Azure Policy, or via automation tools. Review the following guidance to determine the approach that works best for your organization.
+Tagging mission-critical workloads requires that tags be applied to each Azure resource that makes up a workload. Tags can be applied to resources in the Azure portal, with Azure Policy, or via automation tools. Review the following guidance to determine the approach that works best for your organization:
+
+- Azure portal: [Apply tags with Azure portal](/azure/azure-resource-manager/management/tag-resources-portal)
+- Azure Policy: [Assign policy definitions for tag compliance](/azure/azure-resource-manager/management/tag-policies)
+- Azure PowerShell: [Apply tags with Azure PowerShell](/azure/azure-resource-manager/management/tag-resources-powershell)
+- Azure CLI: [Apply tags with Azure CLI](/azure/azure-resource-manager/management/tag-resources-cli)
+- Bicep: [Apply tags with Bicep](/azure/azure-resource-manager/management/tag-resources-bicep)
+- Terraform: [Microsoft.Resources/tags](/azure/templates/microsoft.resources/tags?pivots=deployment-language-terraform)
+
+## Next steps
 
-- Azure portal: [Tag resources, resource groups, and subscriptions with Azure portal - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-portal)
-- Azure Policy: [Policy definitions for tagging resources - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-policies)
-- Azure PowerShell: [Tag resources, resource groups, and subscriptions with Azure PowerShell - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-powershell)
-- Azure CLI: [Tag resources, resource groups, and subscriptions with Azure CLI - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-cli)
-- Bicep: [Tag resources, resource groups, and subscriptions with Bicep - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-bicep)
-- Terraform: [Microsoft.Resources/tags - Bicep, ARM template & Terraform AzAPI reference | Microsoft Learn](/azure/templates/microsoft.resources/tags)
+- For more information about defining workloads, see [Azure Well-Architected Framework workloads](/azure/well-architected/workloads).
+- To learn more about using tags, see the Azure Cloud Adoption Framework [Resource naming and tagging decision guide](/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming-and-tagging-decision-guide).