Merge pull request #303500 from jainsabal/docs-editor/front-door-custom-domain-1753794658

Update front-door-custom-domain.md

Author: JamesJBarnett

articles/cdn/cdn-create-endpoint-how-to.md

@@ -18,8 +18,8 @@ ROBOTS: NOINDEX
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
 > [!IMPORTANT]
-> Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#"https://ms.portal.azure.com/#") to create new domains or profiles and avoid service disruption. [Learn more](https://ms.portal.azure.com/verifyLink?href=https%3A%2F%2Faka.ms%2Fcdn%2Fmigration&id=Microsoft_Azure_Cdn"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2faka.ms%2fcdn%2fmigration&id=microsoft_azure_cdn")
-> Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#%22https://ms.portal.azure.com/#%22) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
+> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) to create new domains or profiles and avoid service disruption. [Learn more](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json)
+> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate) 
 
 This article describes all the settings for creating an [Azure Content Delivery Network](cdn-overview.md) endpoint in an existing content delivery network profile. After you've created a profile and an endpoint, you can start delivering content to your customers. For a quickstart on creating a profile and endpoint, see [Quickstart: Create an Azure Content Delivery Network profile and endpoint](cdn-create-new-endpoint.md).
 
@@ -79,11 +79,12 @@ Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
 
    ![Screenshot of Content Delivery Network endpoint.](./media/cdn-create-new-endpoint/cdn-endpoint-success.png)
 
-      It may take up to 10 minutes for the endpoint registration to propagate and become available for use.
-
-      If you attempt to use the content delivery network domain name before the endpoint configuration has propagated to the point of presence (POP) servers, you might receive an HTTP 404 response status. If it has been several hours since you created your endpoint and you're still receiving a 404 response status, see [Troubleshooting Azure Content Delivery Network endpoints that return a 404 status code](cdn-troubleshoot-endpoint.md).
-
-## Clean up resources
+      ```
+     It may take up to 10 minutes for the endpoint registration to propagate and become available for use.
+   
+   
+     If you attempt to use the content delivery network domain name before the endpoint configuration has propagated to the point of presence (POP) servers, you might receive an HTTP 404 response status. If it has been several hours since you created your endpoint and you're still receiving a 404 response status, see [Troubleshooting Azure Content Delivery Network endpoints that return a 404 status code](cdn-troubleshoot-endpoint.md).
+   ```## Clean up resources
 
 To delete an endpoint when it's no longer needed, select it and then select **Delete**.
 

articles/cdn/cdn-custom-ssl.md

@@ -18,8 +18,8 @@ ROBOTS: NOINDEX
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
 > [!IMPORTANT]
-> Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#"https://ms.portal.azure.com/#") to create new domains or profiles and avoid service disruption. [Learn more](https://ms.portal.azure.com/verifyLink?href=https%3A%2F%2Faka.ms%2Fcdn%2Fmigration&id=Microsoft_Azure_Cdn"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2faka.ms%2fcdn%2fmigration&id=microsoft_azure_cdn")
-> Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#%22https://ms.portal.azure.com/#%22) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
+> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) to create new domains or profiles and avoid service disruption. [Learn more](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json)
+> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
 
 This tutorial shows how to enable the HTTPS protocol for a custom domain associated with an Azure CDN endpoint.
 

articles/cdn/cdn-manage-powershell.md

@@ -17,11 +17,9 @@ ms.custom: devx-track-azurepowershell
 
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
-
-
 > [!IMPORTANT]
-> Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#"https://ms.portal.azure.com/#") to create new domains or profiles and avoid service disruption. [Learn more](https://ms.portal.azure.com/verifyLink?href=https%3A%2F%2Faka.ms%2Fcdn%2Fmigration&id=Microsoft_Azure_Cdn"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2faka.ms%2fcdn%2fmigration&id=microsoft_azure_cdn")
-> Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#"https://ms.portal.azure.com/#") by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
+> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) to create new domains or profiles and avoid service disruption. [Learn more](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json)
+> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
 
 PowerShell provides one of the most flexible methods to manage your Azure Content Delivery Network profiles and endpoints. You can use PowerShell interactively or by writing scripts to automate management tasks. This tutorial demonstrates several of the most common tasks you can accomplish with PowerShell to manage your Azure Content Delivery Network profiles and endpoints.
 

articles/cdn/cdn-map-content-to-custom-domain.md

@@ -18,10 +18,9 @@ ms.custom: mvc, devx-track-azurepowershell
 # Tutorial: Add a custom domain to your endpoint
 
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
-
 > [!IMPORTANT]
-> Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#"https://ms.portal.azure.com/#") to create new domains or profiles and avoid service disruption. [Learn more](https://ms.portal.azure.com/verifyLink?href=https%3A%2F%2Faka.ms%2Fcdn%2Fmigration&id=Microsoft_Azure_Cdn"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2faka.ms%2fcdn%2fmigration&id=microsoft_azure_cdn")
-> Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#%22https://ms.portal.azure.com/#%22) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
+> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) to create new domains or profiles and avoid service disruption. [Learn more](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json)
+> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
 
 This tutorial shows how to add a custom domain to an Azure Content Delivery Network endpoint.
 

articles/cdn/cdn-overview.md

@@ -19,8 +19,8 @@ ROBOTS: NOINDEX
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
 > [!IMPORTANT]
-> Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#"https://ms.portal.azure.com/#") to create new domains or profiles and avoid service disruption. [Learn more](https://ms.portal.azure.com/verifyLink?href=https%3A%2F%2Faka.ms%2Fcdn%2Fmigration&id=Microsoft_Azure_Cdn"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2faka.ms%2fcdn%2fmigration&id=microsoft_azure_cdn")
-> Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#%22https://ms.portal.azure.com/#%22) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
+> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) to create new domains or profiles and avoid service disruption. [Learn more](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json)
+> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
 
 A content delivery network is a distributed network of servers that can efficiently deliver web content to users. A content delivery network store cached content on edge servers in point of presence (POP) locations that are close to end users, to minimize latency.
 

articles/cdn/cdn-standard-rules-engine.md

@@ -14,6 +14,9 @@ ROBOTS: NOINDEX
 # Set up the Standard rules engine for Azure Content Delivery Network
 
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
+> [!IMPORTANT]
+> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) to create new domains or profiles and avoid service disruption. [Learn more](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json)
+> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
 
 This article describes how to set up and use the Standard rules engine for Azure Content Delivery Network.
 
@@ -35,35 +38,34 @@ You can use the Standard rules engine for Azure Content Delivery Network to cust
     The **Rules Engine** pane opens and displays the list of available global rules.
 
     [![Screenshot of Azure Content Delivery Network new rules page.](./media/cdn-standard-rules-engine/cdn-new-rule.png)](./media/cdn-standard-rules-engine/cdn-new-rule.png#lightbox)
-
+   
    > [!IMPORTANT]
    > The order in which multiple rules are listed affects how rules are handled. The actions that are specified in a rule might be overwritten by a subsequent rule.
-   >
 
 1. Select **Add rule** and enter a rule name. Rule names must begin with a letter and can contain only numbers and letters.
 
 1. To identify the type of requests the rule applies to, create a match condition:
-    1. Select **Add condition**, and then select the **Request protocol** match condition.
-    1. For **Operator**, select **Equals**.
-    1. For **Value**, select **HTTP**.
-
+   1. Select **Add condition**, and then select the **Request protocol** match condition.
+   1. For **Operator**, select **Equals**.
+   1. For **Value**, select **HTTP**.
+      
    [![Screenshot of Azure Content Delivery Network rule match condition.](./media/cdn-standard-rules-engine/cdn-match-condition.png)](./media/cdn-standard-rules-engine/cdn-match-condition.png#lightbox)
-
-   > [!NOTE]
-   > You can select from multiple match conditions in the **Add condition** dropdown list. For a detailed list of match conditions, see [Match conditions in the Standard rules engine](cdn-standard-rules-engine-match-conditions.md).
-
-1. Select the action to apply to the requests that satisfy the match condition:
+ 
+> [!NOTE]
+> You can select from multiple match conditions in the **Add condition** dropdown list. For a detailed list of match conditions, see [Match conditions in the Standard rules engine](cdn-standard-rules-engine-match-conditions.md).
+> 
+6. Select the action to apply to the requests that satisfy the match condition:
    1. Select **Add action**, and then select **URL redirect**.
    1. For **Type**, select **Found (302)**.
    1. For **Protocol**, select **HTTPS**.
    1. Leave all other fields blank to use incoming values.
 
    [![Screenshot of Azure Content Delivery Network rule action.](./media/cdn-standard-rules-engine/cdn-action.png)](./media/cdn-standard-rules-engine/cdn-action.png#lightbox)
+   
+ > [!NOTE]
+ > You can select from multiple actions in the **Add action** dropdown list. For a detailed list of actions, see [Actions in the Standard rules engine](cdn-standard-rules-engine-actions.md).
 
-   > [!NOTE]
-   > You can select from multiple actions in the **Add action** dropdown list. For a detailed list of actions, see [Actions in the Standard rules engine](cdn-standard-rules-engine-actions.md).
-
-6. Select **Save** to save the new rule. The rule is now available to use.
+7. Select **Save** to save the new rule. The rule is now available to use.
 
    > [!IMPORTANT]
    > Rule changes might take up to 15 minutes to propagate through Azure Content Delivery Network.

articles/cdn/cdn-storage-custom-domain-https.md

@@ -17,8 +17,8 @@ ms.custom: mvc
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
 > [!IMPORTANT]
-> Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#"https://ms.portal.azure.com/#") to create new domains or profiles and avoid service disruption. [Learn more](https://ms.portal.azure.com/verifyLink?href=https%3A%2F%2Faka.ms%2Fcdn%2Fmigration&id=Microsoft_Azure_Cdn"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2faka.ms%2fcdn%2fmigration&id=microsoft_azure_cdn")
-> Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#%22https://ms.portal.azure.com/#%22) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
+> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) to create new domains or profiles and avoid service disruption. [Learn more](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json)
+> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by August 15, 2025 to avoid service disruption. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate)
 
 After you've integrated your Azure Storage account with Azure Content Delivery Network, you can add a custom domain and enable HTTPS on that domain for your custom blob storage endpoint.