add applies to

halkazwini · halkazwini · commit d5eff13da52a · 2025-05-12T17:21:14.000-05:00
diff --git a/articles/frontdoor/classic-overview.md b/articles/frontdoor/classic-overview.md
@@ -12,6 +12,8 @@ ms.date: 11/15/2024
 
 # What is Azure Front Door (classic)?
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 
 Azure Front Door (classic) is a global, scalable entry-point that uses the Microsoft global edge network to deliver fast, secure, and highly scalable web applications. It enables you to transform your global consumer and enterprise applications into robust, high-performing, and personalized modern applications that reach a global audience through Azure.
diff --git a/articles/frontdoor/classic-retirement-faq.md b/articles/frontdoor/classic-retirement-faq.md
@@ -11,6 +11,8 @@ ms.custom: ai-usage
 
 # Azure Front Door (classic) retirement FAQ
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 Azure Front Door introduced two new tiers named Standard and Premium on March 29, 2022. These tiers offer improvements over the current product offerings of Azure Front Door (Classic), incorporating capabilities such as Azure Private Link integration, Bot management, advanced Web Application Firewall (WAF) enhancements with DRS 2.1, anomaly scoring-based detection and bot management, out-of-the-box reports and enhanced diagnostic logs, a simplified pricing model, and much more.
 
 In our ongoing efforts to provide the best product experience and streamline our portfolio of products and tiers, we're announcing the retirement of the Azure Front Door (Classic) tier. This retirement will affect the public cloud and the Azure Government regions of Arizona and Texas, effective March 31, 2027. We'll communicate retirement plan of Azure Front Door classic in Azure Government regions US DoD Central and US DoD East in a future announcement. We strongly recommend all users of Azure Front Door (classic) to transition to Azure Front Door Standard and Premium.  
diff --git a/articles/frontdoor/front-door-custom-domain-https.md b/articles/frontdoor/front-door-custom-domain-https.md
@@ -12,6 +12,8 @@ ms.date: 11/15/2024
 
 # Configure HTTPS on an Azure Front Door (classic) custom domain
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 
 This article explains how to enable HTTPS for a custom domain associated with your Front Door (classic). Using HTTPS on your custom domain (for example, `https://www.contoso.com`) ensures secure data transmission via TLS/SSL encryption. When a web browser connects to a website using HTTPS, it validates the website's security certificate and verifies its legitimacy, providing security and protecting your web applications from malicious attacks.
diff --git a/articles/frontdoor/front-door-custom-domain.md b/articles/frontdoor/front-door-custom-domain.md
@@ -12,6 +12,8 @@ ms.date: 08/12/2024
 
 # Add a custom domain to Azure Front Door
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 
 This article shows how to add a custom domain to your Front Door. When you use Azure Front Door for application delivery, a custom domain is necessary if you want your own domain name to be visible in your end-user request. Having a visible domain name can be convenient for your customers and useful for branding purposes.
diff --git a/articles/frontdoor/front-door-security-headers.md b/articles/frontdoor/front-door-security-headers.md
@@ -13,6 +13,8 @@ ms.date: 04/10/2025
 
 # Tutorial: Add security headers with rules engine
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 
 This tutorial demonstrates how to implement security headers to prevent browser-based vulnerabilities such as HTTP Strict-Transport-Security (HSTS), X-XSS-Protection, Content-Security-Policy, and X-Frame-Options. Security attributes can also be defined with cookies.
diff --git a/articles/frontdoor/front-door-tutorial-rules-engine.md b/articles/frontdoor/front-door-tutorial-rules-engine.md
@@ -14,6 +14,8 @@ ms.custom: devx-track-azurecli
 
 # Tutorial: Configure your rules engine
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 This tutorial shows how to create a Rules engine configuration and your first rule in both Azure portal and CLI.
 
 In this tutorial, you learn how to:
diff --git a/articles/frontdoor/front-door-waf.md b/articles/frontdoor/front-door-waf.md
@@ -11,6 +11,8 @@ ms.custom: devx-track-azurecli
 
 # Tutorial: Quickly scale and protect a web application using Azure Front Door and Azure Web Application Firewall (WAF)
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 
 Web applications often experience traffic surges and malicious attacks, such as denial-of-service attacks. Azure Front Door with Azure WAF can help scale your application and protect it from such threats. This tutorial guides you through configuring Azure Front Door with Azure WAF for any web app, whether it runs inside or outside of Azure.
diff --git a/articles/frontdoor/scripts/custom-domain.md b/articles/frontdoor/scripts/custom-domain.md
@@ -12,6 +12,8 @@ ms.custom: devx-track-azurecli
 
 # Azure Front Door: Deploy custom domain
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../../includes/front-door-classic-retirement.md)]
 This Azure CLI script example demonstrates how to deploy a custom domain name and TLS certificate on an Azure Front Door front-end. The script automates the provisioning of Azure Front Door with a custom domain name (hosted by Azure DNS) and a TLS certificate.
 
diff --git a/articles/frontdoor/tier-mapping.md b/articles/frontdoor/tier-mapping.md
@@ -10,6 +10,8 @@ ms.date: 11/18/2024
 
 # Settings mapped between Azure Front Door (classic) and Standard/Premium tier
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 When migrating from Azure Front Door (classic) to Azure Front Door Standard or Premium, some configurations are changed or relocated for a better management experience. This article explains how routing rules, cache duration, rules engine configuration, WAF policy, and custom domains are mapped in the new Azure Front Door tier.
 
diff --git a/articles/frontdoor/tier-migration.md b/articles/frontdoor/tier-migration.md
@@ -10,6 +10,8 @@ ms.date: 03/04/2024
 
 # About Azure Front Door (classic) to Standard/Premium tier migration
 
+**Applies to:** :heavy_check_mark: Front Door (classic)
+
 [!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
 
 Azure Front Door Standard and Premium tier were released in March 2022 as the next generation content delivery network service. The newer tiers combine the capabilities of Azure Front Door (classic), Microsoft CDN (classic), and Web Application Firewall (WAF). With features such as Private Link integration, enhanced rules engine and advanced diagnostics you have the ability to secure and accelerate your web applications to bring a better experience to your customers.
