Skip to content

Commit dfbf0ac

Browse files
Merge pull request #303494 from jainsabal/docs-editor/front-door-custom-domain-1753785722
Update front-door-custom-domain.md
2 parents e712fac + 8ee6a64 commit dfbf0ac

File tree

5 files changed

+16
-0
lines changed

5 files changed

+16
-0
lines changed

articles/frontdoor/classic-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ ms.date: 11/15/2024
1616

1717
[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
1818

19+
> [!IMPORTANT]
20+
> Starting August 15, 2025, 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"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%2Flearn.microsoft.com%2Fazure%2Ffrontdoor%2Fmigrate-tier%3FWT.mc_id%3DPortal-Microsoft_Azure_Frontdoor&id=Microsoft_Azure_Frontdoor%22https://ms.portal.azure.com/verifylink?href=https%3a%2f%2flearn.microsoft.com%2fazure%2ffrontdoor%2fmigrate-tier%3fwt.mc_id%3dportal-microsoft_azure_frontdoor&id=microsoft_azure_frontdoor%22"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2flearn.microsoft.com%2fazure%2ffrontdoor%2fmigrate-tier%3fwt.mc_id%3dportal-microsoft_azure_frontdoor&id=microsoft_azure_frontdoor%22https://ms.portal.azure.com/verifylink?href=https%3a%2f%2flearn.microsoft.com%2fazure%2ffrontdoor%2fmigrate-tier%3fwt.mc_id%3dportal-microsoft_azure_frontdoor&id=microsoft_azure_frontdoor%22")**
21+
> 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"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/frontdoor/front-door-custom-domain-https?tabs=powershell"https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https?tabs=powershell")**
22+
1923
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.
2024

2125
:::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.":::

articles/frontdoor/front-door-custom-domain-https.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ ms.custom:
1818

1919
[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
2020

21+
> [!IMPORTANT]
22+
> Starting August 15, 2025, 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"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%2Flearn.microsoft.com%2Fazure%2Ffrontdoor%2Fmigrate-tier%3FWT.mc_id%3DPortal-Microsoft_Azure_Frontdoor&id=Microsoft_Azure_Frontdoor%22https://ms.portal.azure.com/verifylink?href=https%3a%2f%2flearn.microsoft.com%2fazure%2ffrontdoor%2fmigrate-tier%3fwt.mc_id%3dportal-microsoft_azure_frontdoor&id=microsoft_azure_frontdoor%22"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2flearn.microsoft.com%2fazure%2ffrontdoor%2fmigrate-tier%3fwt.mc_id%3dportal-microsoft_azure_frontdoor&id=microsoft_azure_frontdoor%22https://ms.portal.azure.com/verifylink?href=https%3a%2f%2flearn.microsoft.com%2fazure%2ffrontdoor%2fmigrate-tier%3fwt.mc_id%3dportal-microsoft_azure_frontdoor&id=microsoft_azure_frontdoor%22")**
23+
> 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"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/frontdoor/front-door-custom-domain-https?tabs=powershell"https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https?tabs=powershell")**
24+
2125
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.
2226

2327
Azure Front Door supports HTTPS by default on its default hostname (for example, `https://contoso.azurefd.net`). However, you need to enable HTTPS separately for custom domains like `www.contoso.com`.

articles/frontdoor/front-door-custom-domain.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ ms.date: 08/12/2024
1616

1717
[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
1818

19+
> [!IMPORTANT]
20+
> Starting August 15, 2025, 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/#"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%2Flearn.microsoft.com%2Fazure%2Ffrontdoor%2Fmigrate-tier%3FWT.mc_id%3DPortal-Microsoft_Azure_Frontdoor&id=Microsoft_Azure_Frontdoor"https://ms.portal.azure.com/verifylink?href=https%3a%2f%2flearn.microsoft.com%2fazure%2ffrontdoor%2fmigrate-tier%3fwt.mc_id%3dportal-microsoft_azure_frontdoor&id=microsoft_azure_frontdoor")
21+
> 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/frontdoor/front-door-custom-domain-https?tabs=powershell)
22+
1923
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.
2024

2125
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`.

articles/frontdoor/front-door-tutorial-rules-engine.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ ms.custom: devx-track-azurecli
1616

1717
**Applies to:** :heavy_check_mark: Front Door (classic)
1818

19+
1920
This tutorial shows how to create a Rules engine configuration and your first rule in both Azure portal and CLI.
2021

2122
In this tutorial, you learn how to:

articles/frontdoor/scripts/custom-domain.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ ms.custom: devx-track-azurecli
1414

1515
**Applies to:** :heavy_check_mark: Front Door (classic)
1616

17+
[!INCLUDE [Azure Front Door (classic) retirement notice](../../../includes/front-door-classic-retirement.md)]
18+
19+
1720
[!INCLUDE [Azure Front Door (classic) retirement notice](../../../includes/front-door-classic-retirement.md)]
1821
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.
1922

0 commit comments

Comments
 (0)