Skip to content

Commit 65097cf

Browse files
committed
Learn Editor: Update front-door-custom-domain-https.md
1 parent 4a2c81f commit 65097cf

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@ ms.custom:
1717
**Applies to:** :heavy_check_mark: Front Door (classic)
1818

1919
[!INCLUDE [Azure Front Door (classic) retirement notice](../../includes/front-door-classic-retirement.md)]
20-
2120
> [!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")**
21+
> - Starting August 15, 2025, Azure Front Door (classic) will no longer support new domain onboarding or profile creation. Migrate to [AFD Standard and Premium](/azure/frontdoor/tier-migration) to create new domains or profiles and avoid service disruption. [Learn more](/azure/frontdoor/tier-migration)
22+
> - Switch from Azure-managed certificates on existing domains to Bring Your Own Certificate (BYOC) or migrate to [AFD Standard and Premium](/azure/frontdoor/tier-migration) 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%22https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https?tabs=powershell%22)**
23+
2424
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.
2525

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

0 commit comments

Comments
 (0)