Merge pull request #269377 from duongau/afdclassicretirement

v-dirichards · web-flow · commit a63553921051 · 2024-03-27T16:33:11.000-05:00
Front Door (classic) - Add retirement notice to all classic articles
diff --git a/articles/frontdoor/classic-overview.md b/articles/frontdoor/classic-overview.md
@@ -12,6 +12,8 @@ ms.author: duau
 
 # What is Azure 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 create fast, secure, and widely scalable web applications. With Front Door (classic), you can transform your global consumer and enterprise applications into robust, high-performing personalized modern applications with contents that reach a global audience through Azure.
 
 :::image type="content" source="./media/front-door-overview/front-door-visual-diagram.png" alt-text="Diagram of Azure Front Door (classic) routing user traffic to endpoints.":::
diff --git a/articles/frontdoor/front-door-caching.md b/articles/frontdoor/front-door-caching.md
@@ -12,6 +12,8 @@ zone_pivot_groups: front-door-tiers
 
 # Caching with Azure Front Door
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Azure Front Door is a modern content delivery network (CDN), with dynamic site acceleration and load balancing capabilities. When caching is configured on your route, the edge site that receives each request checks its cache for a valid response. Caching helps to reduce the amount of traffic sent to your origin server. If no cached response is available, the request is forwarded to the origin.
 
 Each Front Door edge site manages its own cache, and requests might get served by different edge sites. As a result, you might still see some traffic reach your origin, even if you served cached responses.
diff --git a/articles/frontdoor/front-door-custom-domain-https.md b/articles/frontdoor/front-door-custom-domain-https.md
@@ -13,6 +13,8 @@ ms.author: duau
 
 # Configure HTTPS on a Front Door (classic) custom domain
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 This article shows how to enable the HTTPS protocol for a custom domain that's associated with your Front Door (classic) under the frontend hosts section. By using the HTTPS protocol on your custom domain (for example, `https://www.contoso.com`), you ensure that your sensitive data is delivered securely via TLS/SSL encryption when it's sent across the internet. When your web browser is connected to a web site using HTTPS, it validates the web site's security certificate and verifies if issued by a legitimate certificate authority. This process provides security and protects your web applications from malicious attacks.
 
 Azure Front Door supports HTTPS on a Front Door default hostname, by default. For example, if you create a Front Door (such as `https://contoso.azurefd.net`), HTTPS is automatically enabled for requests made to `https://contoso.azurefd.net`. However, once you onboard the custom domain 'www.contoso.com' you need to additionally enable HTTPS for this frontend host.
diff --git a/articles/frontdoor/front-door-custom-domain.md b/articles/frontdoor/front-door-custom-domain.md
@@ -12,6 +12,8 @@ ms.author: duau
 
 # Add a custom domain to Azure Front Door
 
+[!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.
 
 After you create a Front Door profile, the default frontend host is a subdomain of `azurefd.net`. This name is included in the URL for delivering Front Door content to your backend by default. For example, `https://contoso-frontend.azurefd.net`. For your convenience, Azure Front Door provides the option to associate a custom domain to the endpoint. With this capability, you can deliver your content with your URL instead of the Front Door default domain name such as, `https://www.contoso.com/photo.png`. 
diff --git a/articles/frontdoor/front-door-diagnostics.md b/articles/frontdoor/front-door-diagnostics.md
@@ -170,6 +170,8 @@ To enable and store your diagnostic logs, see [Configure Azure Front Door logs](
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 When using Azure Front Door (classic), you can monitor resources in the following ways:
 
 - **Metrics**. Azure Front Door currently has eight metrics to view performance counters.
diff --git a/articles/frontdoor/front-door-how-to-onboard-apex-domain.md b/articles/frontdoor/front-door-how-to-onboard-apex-domain.md
@@ -14,6 +14,8 @@ zone_pivot_groups: front-door-tiers
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Azure Front Door uses CNAME records to validate domain ownership for the onboarding of custom domains. Azure Front Door doesn't expose the frontend IP address associated with your Front Door profile. So you can't map your apex domain to an IP address if your intent is to onboard it to Azure Front Door.
 
 The DNS protocol prevents the assignment of CNAME records at the zone apex. For example, if your domain is `contoso.com`; you can create CNAME records for `somelabel.contoso.com`; but you can't create CNAME for `contoso.com` itself. This restriction presents a problem for application owners who have load-balanced applications behind Azure Front Door. Since using a Front Door profile requires creation of a CNAME record, it isn't possible to point at the Front Door profile from the zone apex.
diff --git a/articles/frontdoor/front-door-how-to-redirect-https.md b/articles/frontdoor/front-door-how-to-redirect-https.md
@@ -12,6 +12,8 @@ ms.author: duau
 
 # Configure HTTP to HTTPS redirection using the Azure portal
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 This article shows you how to redirect traffic from HTTP to HTTPS for an Azure Front Door (classic) profile using the Azure portal. This configuration is useful if you want to redirect traffic from HTTP to HTTPS for your domain.
 
 ## Prerequisites
diff --git a/articles/frontdoor/front-door-route-matching.md b/articles/frontdoor/front-door-route-matching.md
@@ -24,6 +24,8 @@ A *route* in Azure Front Door defines how traffic gets handled when the incoming
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 When a request arrives Azure Front Door (classic) edge, one of the first things that Front Door does is determine how to route the matching request to a backend resource and then take a defined action in the routing configuration. The following document explains how Front Door determines which route configuration to use when processing a request.
 
 ::: zone-end
diff --git a/articles/frontdoor/front-door-routing-architecture.md b/articles/frontdoor/front-door-routing-architecture.md
@@ -25,6 +25,8 @@ The following diagram illustrates the routing architecture:
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 ![Diagram that shows the Front Door routing architecture, including each step and decision point.](media/front-door-routing-architecture/routing-process-classic.png)
 
 ::: zone-end
diff --git a/articles/frontdoor/front-door-routing-limits.md b/articles/frontdoor/front-door-routing-limits.md
@@ -12,6 +12,8 @@ ms.author: jodowns
 
 # Front Door routing limits
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Each Front Door profile has a *composite route limit*.
 
 Your Front Door profile's composite route metric is derived from the number of routes, and the front end domains, protocols, and paths associated with that route.
diff --git a/articles/frontdoor/front-door-rules-engine-actions.md b/articles/frontdoor/front-door-rules-engine-actions.md
@@ -396,6 +396,8 @@ In this example, we rewrite all requests to the path `/redirection`, and don't p
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 In Azure Front Door (classic), a [Rules engine](front-door-rules-engine.md) can consist up to 25 rules containing matching conditions and associated actions. This article provides a detailed description of each action you can define in a rule.
 
 An action defines the behavior that gets applied to the request type that matches the condition or set of match conditions. In the Rules engine configuration, a rule can have up to 10 matching conditions and 5 actions. You can only have one *Override Routing Configuration* action in a single rule.
diff --git a/articles/frontdoor/front-door-rules-engine.md b/articles/frontdoor/front-door-rules-engine.md
@@ -75,6 +75,8 @@ For information about quota limits, refer to [Front Door limits, quotas and cons
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 A Rules engine configuration allows you to customize how HTTP requests get handled at the Front Door edge and provides controlled behavior to your web application. Rules Engine for Azure Front Door (classic) has several key features, including:
 
 * Enforces HTTPS to ensure all your end users interact with your content over a secure connection.
diff --git a/articles/frontdoor/front-door-security-headers.md b/articles/frontdoor/front-door-security-headers.md
@@ -13,6 +13,8 @@ ms.custom: template-tutorial, engagement-fy23
 
 # Tutorial: Add Security headers with Rules Engine
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 This tutorial shows how to implement security headers to prevent browser-based vulnerabilities like HTTP Strict-Transport-Security (HSTS), X-XSS-Protection, Content-Security-Policy, or X-Frame-Options. Security-based attributes can also be defined with cookies.
 
 The following example shows you how to add a Content-Security-Policy header to all incoming requests that match the path defined in the route your Rules Engine configuration is associated with. Here, we only allow scripts from our trusted site, **https://apiphany.portal.azure-api.net** to run on our application.
diff --git a/articles/frontdoor/front-door-traffic-acceleration.md b/articles/frontdoor/front-door-traffic-acceleration.md
@@ -21,6 +21,8 @@ Front Door optimizes the traffic path from the end user to the origin server. Th
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Front Door optimizes the traffic path from the end user to the backend server. This article describes how traffic is routed from the user to Front Door and from Front Door to the backend.
 
 ::: zone-end
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.author: duau
 
 # Tutorial: Configure your rules engine
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 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-url-redirect.md b/articles/frontdoor/front-door-url-redirect.md
@@ -25,6 +25,8 @@ In Azure Front Door Standard/Premium tier, you can configure URL redirect using
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 :::image type="content" source="./media/front-door-url-redirect/front-door-url-redirect.png" alt-text="Azure Front Door URL Redirect":::
 
 ::: zone-end
diff --git a/articles/frontdoor/front-door-url-rewrite.md b/articles/frontdoor/front-door-url-rewrite.md
@@ -47,6 +47,8 @@ Preserve unmatched path allows you to append the remaining path after the source
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Azure Front Door (classic) supports URL rewrite by configuring a **Custom forwarding path** when configuring the forward routing type rule. By default, if only a forward slash (`/*`) is defined, Front Door copies the incoming URL path to the URL used in the forwarded request. The host header used in the forwarded request is as configured for the selected backend. For more information, see [Backend host header](origin.md#origin-host-header).
 
 The robust part of URL rewrite is the custom forwarding path copies any part of the incoming path that matches the wildcard path to the forwarded path.
diff --git a/articles/frontdoor/front-door-waf.md b/articles/frontdoor/front-door-waf.md
@@ -12,6 +12,8 @@ ms.author: duau
 
 # Tutorial: Quickly scale and protect a web application by using Azure Front Door and Azure Web Application Firewall (WAF)
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Many web applications experience a rapid increase of traffic over time. These web applications are also experiencing a surge in malicious traffic, including denial-of-service attacks. There's an effective way to both scale out your application for traffic surges and protect yourself from attacks: configure Azure Front Door with Azure WAF as an acceleration, caching, and security layer in front of your web app. This article provides guidance on how to get Azure Front Door with Azure WAF configured for any web app that runs inside or outside of Azure. 
 
 We're using the Azure CLI to configure the WAF in this tutorial. You can accomplish the same thing by using the Azure portal, Azure PowerShell, Azure Resource Manager, or the Azure REST APIs. 
diff --git a/articles/frontdoor/front-door-wildcard-domain.md b/articles/frontdoor/front-door-wildcard-domain.md
@@ -13,6 +13,8 @@ zone_pivot_groups: front-door-tiers
 
 # Wildcard domains in Azure Front Door
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Wildcard domains allow Azure Front Door to receive traffic for any subdomain of a top-level domain. An example wildcard domain is `*.contoso.com`.
 
 By using wildcard domains, you can simplify the configuration of your Azure Front Door profile. You don't need to modify the configuration to add or specify each subdomain separately. For example, you can define the routing for `customer1.contoso.com`, `customer2.contoso.com`, and `customerN.contoso.com` by using the same route and adding the wildcard domain `*.contoso.com`.
diff --git a/articles/frontdoor/health-probes.md b/articles/frontdoor/health-probes.md
@@ -12,6 +12,8 @@ ms.author: duau
 
 # Health probes
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 > [!NOTE]
 > An *origin* and an *origin group* in this article refers to the backend and backend pool of an Azure Front Door (classic) configuration.
 >
diff --git a/articles/frontdoor/migrate-tier-powershell.md b/articles/frontdoor/migrate-tier-powershell.md
@@ -12,6 +12,8 @@ ms.author: duau
 
 # Migrate Azure Front Door (classic) to Standard/Premium tier with Azure PowerShell
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Azure Front Door Standard and Premium tier bring the latest cloud delivery network features to Azure. With enhanced security features and an all-in-one service, your application content is secured and closer to your end users using the Microsoft global network. This article guides you through the migration process to move your Azure Front Door (classic) profile to either a Standard or Premium tier profile with Azure PowerShell.
 
 ## Prerequisites
diff --git a/articles/frontdoor/migrate-tier.md b/articles/frontdoor/migrate-tier.md
@@ -11,6 +11,8 @@ ms.author: duau
 
 # Migrate Azure Front Door (classic) to Standard/Premium tier
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Azure Front Door Standard and Premium tier bring the latest cloud delivery network features to Azure. With enhanced security features and an all-in-one service, your application content is secured and closer to your end users using the Microsoft global network. This article will guide you through the migration process to move your Azure Front Door (classic) profile to either a Standard or Premium tier profile.
 
 ## Prerequisites
diff --git a/articles/frontdoor/origin.md b/articles/frontdoor/origin.md
@@ -15,6 +15,8 @@ zone_pivot_groups: front-door-tiers
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 > [!NOTE]
 > *Origin* and *origin group* in this article refers to the backend and backend pool of the Azure Front Door (classic) configuration.
 >
diff --git a/articles/frontdoor/quickstart-create-front-door-bicep.md b/articles/frontdoor/quickstart-create-front-door-bicep.md
@@ -13,6 +13,8 @@ ms.custom: subject-armqs, mode-arm, devx-track-bicep
 
 # Quickstart: Create a Front Door using Bicep
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 This quickstart describes how to use Bicep to create a Front Door to set up high availability for a web endpoint.
 
 [!INCLUDE [About Bicep](../../includes/resource-manager-quickstart-bicep-introduction.md)]
diff --git a/articles/frontdoor/quickstart-create-front-door-cli.md b/articles/frontdoor/quickstart-create-front-door-cli.md
@@ -15,6 +15,10 @@ ms.devlang: azurecli
 
 # Quickstart: Create a Front Door for a highly available global web application using Azure CLI
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Get started with Azure Front Door by using Azure CLI to create a highly available and high-performance global web application.
 
 The Front Door directs web traffic to specific resources in a backend pool. You defined the frontend domain, add resources to a backend pool, and create a routing rule. This article uses a simple configuration of one backend pool with a web app resource and a single routing rule using default path matching "/*".
diff --git a/articles/frontdoor/quickstart-create-front-door-powershell.md b/articles/frontdoor/quickstart-create-front-door-powershell.md
@@ -14,6 +14,8 @@ ms.custom: devx-track-azurepowershell, mode-api
 
 # Quickstart: Create a Front Door for a highly available global web application using Azure PowerShell
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Get started with Azure Front Door by using Azure PowerShell to create a highly available and high-performance global web application.
 
 The Front Door directs web traffic to specific resources in a backend pool. You defined the frontend domain, add resources to a backend pool, and create a routing rule. This article uses a simple configuration of one backend pool with two web app resources and a single routing rule using default path matching "/*".
diff --git a/articles/frontdoor/quickstart-create-front-door-template.md b/articles/frontdoor/quickstart-create-front-door-template.md
@@ -13,6 +13,8 @@ ms.custom: subject-armqs, mode-arm, devx-track-arm-template
 
 # Quickstart: Create a Front Door using an ARM template
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 This quickstart describes how to use an Azure Resource Manager template (ARM Template) to create a Front Door to set up high availability for a web endpoint.
 
 [!INCLUDE [About Azure Resource Manager](../../includes/resource-manager-quickstart-introduction.md)]
diff --git a/articles/frontdoor/quickstart-create-front-door-terraform.md b/articles/frontdoor/quickstart-create-front-door-terraform.md
@@ -15,6 +15,8 @@ ai-usage: ai-assisted
 
 # Quickstart: Create an Azure Front Door (classic) using Terraform
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 This quickstart describes how to use Terraform to create a Front Door (classic) profile to set up high availability for a web endpoint.
 
 In this article, you learn how to:
diff --git a/articles/frontdoor/quickstart-create-front-door.md b/articles/frontdoor/quickstart-create-front-door.md
@@ -14,6 +14,8 @@ ms.custom: template-tutorial, mode-ui, engagement-fy23
 
 # Quickstart: Create a Front Door for a highly available global web application
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 This quickstart shows you how to use the Azure portal to set up high availability for a web application with Azure Front Door. You create a Front Door configuration that distributes traffic across two instances of a web application running in different Azure regions. The configuration uses equal weighted and same priority backends, which means that Azure Front Door directs traffic to the closest available site that hosts the application. Azure Front Door also monitors the health of the web application and performs automatic failover to the next nearest site if the closest site is down.
 
 :::image type="content" source="media/quickstart-create-front-door/environment-diagram.png" alt-text="Diagram of Front Door deployment environment using the Azure portal." border="false":::
diff --git a/articles/frontdoor/routing-methods.md b/articles/frontdoor/routing-methods.md
@@ -12,6 +12,8 @@ ms.author: duau
 
 # Traffic routing methods to origin
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 Azure Front Door supports four different traffic routing methods to determine how your HTTP/HTTPS traffic is distributed between different origins. When user requests reach the Front Door edge locations, the configured routing method gets applied to ensure requests are forwarded to the best backend resource.
 
 > [!NOTE]
diff --git a/articles/frontdoor/rules-match-conditions.md b/articles/frontdoor/rules-match-conditions.md
@@ -20,6 +20,8 @@ In Azure Front Door [Rule sets](front-door-rules-engine.md), a rule consists of
 
 ::: zone pivot="front-door-classic"
 
+[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
+
 In Azure Front Door (classic) [Rules engines](front-door-rules-engine.md), a rule consists of none or some match conditions and an action. This article provides detailed descriptions of match conditions you can use in Azure Front Door (classic) Rules engines.
 
 ::: zone-end
diff --git a/articles/frontdoor/scripts/custom-domain.md b/articles/frontdoor/scripts/custom-domain.md
diff --git a/articles/frontdoor/tier-mapping.md b/articles/frontdoor/tier-mapping.md
diff --git a/articles/frontdoor/tier-migration.md b/articles/frontdoor/tier-migration.md
diff --git a/includes/front-door-classic-retirement.md b/includes/front-door-classic-retirement.md
