Skip to content

Commit f6d0730

Browse files
committed
managed certificates
1 parent 2eedd7c commit f6d0730

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

articles/cdn/classic-cdn-retirement-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: halkazwini
88
ms.author: halkazwini
99
ms.service: azure-cdn
1010
ms.topic: faq
11-
ms.date: 02/28/2026
11+
ms.date: 03/31/2026
1212
ms.custom: ai-usage
1313
# Customer intent: As a cloud service user, I want to transition from Azure CDN Standard (classic) to Azure Front Door Standard or Premium, so that I can take advantage of improved features, enhanced security, and maintain support before the retirement of the legacy service on September 30, 2027.
1414
---
@@ -22,7 +22,7 @@ In our ongoing efforts to provide the best product experience and streamline our
2222
> [!IMPORTANT]
2323
> - 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](https://azure.microsoft.com/updates?id=498522)
2424
> - Starting August 15, 2025, Azure CDN from Microsoft (classic) will no longer support Managed certificates. To avoid service disruption, either [switch to Bring Your Own Certificate (BYOC)](/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate) or migrate to [AFD Standard and Premium](/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) by this date. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026. [Learn more](https://azure.microsoft.com/updates?id=498522)
25-
> - If you migrate to AFD Standard and Premium after your managed certificates have already expired, then after migration the certificates will change to "Pending Revalidation" state or start to rotate after 1-2 days. Alternatively, rotate the AFD Standard and Premium managed certificates by refreshing the validation token using either **[Powershell](https://learn.microsoft.com/powershell/module/az.cdn/update-azfrontdoorcdncustomdomainvalidationtoken)** or **[CLI](https://learn.microsoft.com/cli/azure/afd/custom-domain#az-afd-custom-domain-regenerate-validation-token)**. After adding the new TXT record token to your DNS zone, the custom domain will be revalidated and a new certificate will be deployed.
25+
> - If you migrate to Azure Front Door Standard or Premium after your managed certificates have already expired, then after migration, the certificates will change to *Pending Revalidation* state or start to rotate after 1-2 days. Alternatively, rotate the Front Door Standard and Premium managed certificates by refreshing the validation token using either **[Powershell](/powershell/module/az.cdn/update-azfrontdoorcdncustomdomainvalidationtoken)** or **[CLI](/cli/azure/afd/custom-domain#az-afd-custom-domain-regenerate-validation-token)**. After adding the new TXT record token to your DNS zone, the custom domain will be revalidated and a new certificate will be deployed.
2626
2727
## Frequently asked questions
2828

articles/frontdoor/classic-retirement-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: halkazwini
55
ms.author: halkazwini
66
ms.service: azure-frontdoor
77
ms.topic: faq
8-
ms.date: 03/27/2024
8+
ms.date: 03/31/2026
99
ms.custom: ai-usage
1010
---
1111

@@ -20,7 +20,7 @@ In our ongoing efforts to provide the best product experience and streamline our
2020
> [!IMPORTANT]
2121
> - Starting August 15, 2025, Azure Front Door (classic) will no longer support new domain onboarding. Migrate to **[AFD Standard and Premium](/azure/frontdoor/tier-migration)** to create new domains or profiles and avoid service disruption. **[Learn more](https://azure.microsoft.com/updates?id=498522)**
2222
> - Starting August 15, 2025, Azure Front Door (classic) will no longer support Managed certificates. To avoid service disruption, either **[switch to Bring Your Own Certificate (BYOC)](/azure/frontdoor/front-door-custom-domain-https?tabs=powershell)** or migrate to **[AFD Standard and Premium](/azure/frontdoor/tier-migration)** by August 15, 2025. Existing managed certificates will be auto renewed before August 15, 2025, and remain valid until April 14, 2026.  **[Learn more](https://azure.microsoft.com/updates?id=498522)**
23-
> - If you migrate to AFD Standard and Premium after your managed certificates have already expired, then after migration the certificates will change to "Pending Revalidation" state or start to rotate after 1-2 days. Alternatively, rotate the AFD Standard and Premium managed certificates by refreshing the validation token using either **[Powershell](https://learn.microsoft.com/powershell/module/az.cdn/update-azfrontdoorcdncustomdomainvalidationtoken)** or **[CLI](https://learn.microsoft.com/cli/azure/afd/custom-domain#az-afd-custom-domain-regenerate-validation-token)**. After adding the new TXT record token to your DNS zone, the custom domain will be revalidated and a new certificate will be deployed.
23+
> - If you migrate to Azure Front Door Standard or Premium after your managed certificates have already expired, then after migration, the certificates will change to *Pending Revalidation* state or start to rotate after 1-2 days. Alternatively, rotate the Front Door Standard and Premium managed certificates by refreshing the validation token using either **[Powershell](/powershell/module/az.cdn/update-azfrontdoorcdncustomdomainvalidationtoken)** or **[CLI](/cli/azure/afd/custom-domain#az-afd-custom-domain-regenerate-validation-token)**. After adding the new TXT record token to your DNS zone, the custom domain will be revalidated and a new certificate will be deployed.
2424
2525

2626
## Frequently asked questions

0 commit comments

Comments
 (0)