Merge pull request #299716 from halkazwini/afd-appliesto2

Add "Applies to" checkmarks #1

Author: prmerger-automator[bot]

articles/frontdoor/apex-domain.md

@@ -10,6 +10,8 @@ ms.date: 03/31/2024
 
 # Apex domains in Azure Front Door
 
+**Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
+
 Apex domains, also called *root domains*, or *naked domains*, are at the root of a Domain Name System (DNS) zone and don't contain subdomains. For example, `contoso.com` is an apex domain.
 
 Azure Front Door supports apex domains, but requires special considerations. This article describes how apex domains work in Azure Front Door.

articles/frontdoor/domain.md

@@ -10,6 +10,8 @@ ms.author: jodowns
 
 # Domains in Azure Front Door
 
+**Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
+
 A *domain* represents a custom domain name that Azure Front Door uses to receive your application's traffic. Azure Front Door supports adding three types of domain names:
 
 - **Subdomains** are the most common type of custom domain name. An example subdomain is `myapplication.contoso.com`.

articles/frontdoor/endpoint.md

@@ -14,6 +14,8 @@ In Azure Front Door, an *endpoint* is a logical grouping of one or more routes a
 
 ## How many endpoints should I create?
 
+**Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
+
 A Front Door profile can contain multiple endpoints, but in many cases, a single endpoint might suffice.
 
 Consider the following factors when planning your endpoints:

articles/frontdoor/manager.md

@@ -10,6 +10,8 @@ ms.date: 11/13/2024
 
 # What is Azure Front Door Manager?
 
+**Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
+
 Azure Front Door Manager in Azure Front Door Standard and Premium provides an overview of the endpoints configured for your Azure Front Door profile. With Front Door Manager, you can manage your collection of endpoints, configure routing rules, domains, origin groups, and apply security policies to protect your web application.
 
 :::image type="content" source="./media/manager/manager.png" alt-text="Screenshot of the Azure Front Door Manager page." lightbox="./media/manager/manager-expanded.png":::

articles/frontdoor/standard-premium/how-to-add-custom-domain.md

@@ -13,6 +13,8 @@ ms.date: 03/26/2025
 
 # Configure a custom domain on Azure Front Door by using the Azure portal
 
+**Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
+
 When using Azure Front Door for application delivery, a custom domain allows your own domain name to appear in user requests. This visibility can enhance customer convenience and support branding efforts.
 
 By default, after creating an Azure Front Door Standard/Premium profile and endpoint, the endpoint host is a subdomain of `azurefd.net`. For example, the URL might look like `https://contoso-frontend-mdjf2jfgjf82mnzx.z01.azurefd.net/activeusers.htm`.

articles/frontdoor/standard-premium/how-to-cache-purge-powershell.md

@@ -12,6 +12,8 @@ ms.custom: devx-track-azurepowershell
 
 # Cache purging in Azure Front Door with Azure PowerShell
 
+**Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
+
 Azure Front Door caches assets until their time-to-live (TTL) expires. When a client requests an asset with an expired TTL, Azure Front Door retrieves and caches a new copy of the asset.
 
 To ensure users always get the latest assets, version your assets for each update and publish them with new URLs. Azure Front Door fetches the new assets for subsequent client requests. However, you might need to purge cached content from all edge nodes to force them to retrieve updated assets, especially after making updates or correcting incorrect information.

articles/frontdoor/standard-premium/how-to-cache-purge.md

@@ -11,6 +11,8 @@ ms.date: 11/15/2024
 
 # Cache purging in Azure Front Door
 
+**Applies to:** :heavy_check_mark: Front Door Standard :heavy_check_mark: Front Door Premium
+
 Azure Front Door caches assets until their time-to-live (TTL) expires. When a client requests an asset with an expired TTL, Azure Front Door retrieves and caches a new copy of the asset to serve the request.
 
 To ensure end users always receive the latest version of your assets, it's best practice to version your assets with each update and publish them under new URLs. This way, Azure Front Door will fetch the new assets on the next client request.