Merge pull request #303497 from jainsabal/docs-editor/cdn-create-endpoint-how-to-1753787268

Update cdn-create-endpoint-how-to.md

Author: prmerger-automator[bot]

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

@@ -17,6 +17,10 @@ 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)
+
 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).
 
 ## Prerequisites
@@ -69,15 +73,15 @@ Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
     - **Azure CDN Standard from Microsoft** profiles:
        - [**General web delivery**](cdn-optimization-overview.md#general-web-delivery)
 
-10. Select **Add** to create the new endpoint.
+1. Select **Add** to create the new endpoint.
 
     After the endpoint is created, it appears in the list of endpoints for the profile.
 
-    ![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.
+   ![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).
+      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
 

articles/cdn/cdn-custom-ssl.md

@@ -17,6 +17,10 @@ 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)
+
 This tutorial shows how to enable the HTTPS protocol for a custom domain associated with an Azure CDN endpoint.
 
 The HTTPS protocol on your custom domain (for example, `https://www.contoso.com`), ensures your sensitive data is delivered securely via TLS/SSL. When your web browser is connected via HTTPS, the browser validates the web site's certificate. The browser verifies it's issued by a legitimate certificate authority. This process provides security and protects your web applications from attacks.

articles/cdn/cdn-manage-powershell.md

@@ -17,6 +17,12 @@ 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)
+
 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.
 
 ## Prerequisites

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

@@ -19,6 +19,10 @@ ms.custom: mvc, 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/#%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)
+
 This tutorial shows how to add a custom domain to an Azure Content Delivery Network endpoint.
 
 The endpoint name in your content delivery network profile is a subdomain of azureedge.net. By default when delivering content, the content delivery network profile domain gets included in the URL.

articles/cdn/cdn-overview.md

@@ -18,6 +18,10 @@ 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)
+
 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.
 
 Azure Content Delivery Network offers developers a global solution for rapidly delivering high-bandwidth content to users by caching their content at strategically placed physical nodes across the world. Azure Content Delivery Network can also accelerate dynamic content, which can't get cached, by using various network optimizations using content delivery network POPs. For example, route optimization to bypass Border Gateway Protocol (BGP).

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

@@ -16,6 +16,10 @@ 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)
+
 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.
 
 > [!NOTE]  

articles/cdn/endpoint-multiorigin.md

@@ -16,6 +16,10 @@ 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)
+
 Multi-origin support eliminates downtime and establishes global redundancy.
 
 When you choose multiple origins within an Azure CDN endpoint, the redundancy provided spreads the risk by probing the health of each origin and failing over if necessary.

articles/cdn/onboard-apex-domain.md

@@ -15,6 +15,10 @@ ms.date: 03/31/2025
 
 [!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)
+
 Azure CDN uses CNAME records to validate domain ownership for onboarding of custom domains. CDN doesn't expose the frontend IP address associated with your CDN profile. You can't map your apex domain to an IP address if your intent is to onboard it to Azure CDN.
 
 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 a CNAME for `contoso.com` itself. This restriction presents a problem for application owners who have load-balanced applications behind Azure CDN. Since using a CDN profile requires creation of a CNAME record, it isn't possible to point at the CDN profile from the zone apex.

articles/frontdoor/front-door-cdn-comparison.md

@@ -23,6 +23,10 @@ Azure Front Door and Azure CDN are both Azure services that offer global content
 
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
+> [!IMPORTANT]
+> Starting August 15, 2025, Azure CDN from Microsoft (classic) and Azure Front Door (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](https://ms.portal.azure.com/#%22https://ms.portal.azure.com/#%22) 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%22https://ms.portal.azure.com/verifylink?href=https%3a%2f%2faka.ms%2fcdn%2fmigration&id=microsoft_azure_cdn%22)
+> 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 on Azure CDN from Microsoft (classic) and Azure Front Door (classic) 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)
+
 ## Service comparison
 
 The following table provides a comparison between Azure Front Door and Azure CDN services.