You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/frontdoor/front-door-faq.yml
+18-18Lines changed: 18 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ metadata:
6
6
ms.author: halkazwini
7
7
ms.service: azure-frontdoor
8
8
ms.topic: faq
9
-
ms.date: 02/24/2026
9
+
ms.date: 04/07/2026
10
10
title: Azure Front Door frequently asked questions (FAQ)
11
11
summary : |
12
12
This article provides answers to the most frequently asked questions about Azure Front Door features and functionality. If you don't see the answer to your question, you can contact us through the following channels (in escalating order):
@@ -306,9 +306,9 @@ sections:
306
306
questions:
307
307
308
308
- question: |
309
-
What is happening with DigiCert’s CNAME Delegation DCV workflow?
309
+
What is happening with DigiCert's CNAME Delegation DCV workflow?
310
310
answer: |
311
-
Effective15 August 2025, DigiCert has transitioned to a new open-source software (OSS) domain control validation (DCV) platform designed to enhance transparency and accountability in domain validation processes. DigiCert will no longer support the legacy CNAME Delegation DCV workflow for domain control validation in the specified Azure services. [Learn more](https://learn.microsoft.com/en-us/azure/security/fundamentals/managed-tls-changes)
311
+
Effective August 15, 2025, DigiCert transitioned to a new open-source software (OSS) domain control validation (DCV) platform designed to enhance transparency and accountability in domain validation processes. DigiCert will no longer support the legacy CNAME Delegation DCV workflow for domain control validation in the specified Azure services. [Learn more](https://learn.microsoft.com/en-us/azure/security/fundamentals/managed-tls-changes)
312
312
313
313
- question: |
314
314
Which Azure Front Door SKUs are affected by this change?
@@ -319,43 +319,43 @@ sections:
319
319
- Azure CDN from Microsoft (classic)
320
320
321
321
- question: |
322
-
What’s the current status?
322
+
What's the current status?
323
323
answer: |
324
324
Azure Front Door (classic) and Azure CDN from Microsoft (classic):
325
-
- From 15 August 2025, no longer support for new domain onboarding,new profile creation, or Azure-managed certificates.
326
-
- From 14 April 2026, existing managed certificates will be retired.
325
+
- Effective August 15, 2025, no longer support for new domain onboarding,new profile creation, or Azure-managed certificates.
326
+
- Effective April 14, 2026, existing managed certificates will be retired.
327
327
328
328
- question: |
329
329
What actions should I take to avoid service disruption?
330
330
answer: |
331
-
Microsoft will automatically migrate eligible profiles on a "best effort" basis toAzure Front Door Standard/Premium between 10–14 April 2026, unless you notify us otherwise. Classic and Azure Front Door Standard/Premium SKUs are charged differently. Please refer to the [pricing page](https://azure.microsoft.com/en-us/pricing/details/frontdoor/?msockid=06fc59dfa84d6e0612124fafa9586f44) for details.
331
+
Microsoft will automatically migrate eligible profiles on a "best effort" basis toAzure Front Door Standard/Premium between April 10, 2026 and April 14, 2026, unless you notify us otherwise. Classic and Azure Front Door Standard/Premium SKUs are charged differently. Please refer to the [pricing page](https://azure.microsoft.com/en-us/pricing/details/frontdoor/?msockid=06fc59dfa84d6e0612124fafa9586f44) for details.
332
332
333
-
If you plan to migrate to Azure Front Door Standard/Premium or switch to BYOC yourself, please notify Microsoft by 9 April 2026 by setting the required feature flag, see instructions below.
333
+
If you plan to migrate to Azure Front Door Standard/Premium or switch to BYOC yourself, please notify Microsoft by April 9, 2026 by setting the required feature flag, see instructions below.
334
334
335
335
You can check the auto-migration eligibility by following [the migration steps](https://learn.microsoft.com/en-us/azure/frontdoor/migrate-tier). If step 1 Validate compatibility succeeds, your profile is eligible. If you proceed with auto‑migration, monitor your email for final migration confirmation and status updates.
336
336
337
-
**Required action**
337
+
**Required action**
338
338
339
339
Azure CDN from Microsoft (classic)
340
340
341
-
Before 9 April 2026:
341
+
Before April 9, 2026:
342
342
- [Migrate to Azure Front Door Standard or Premium](https://learn.microsoft.com/en-us/azure/cdn/migrate-tier?toc=%2Fazure%2Ffrontdoor%2Ftoc.json) or [move to Bring Your Own Certificate (BYOC)](https://learn.microsoft.com/en-us/azure/cdn/cdn-custom-ssl?toc=%2Fazure%2Ffrontdoor%2Ftoc.json&tabs=option-1-default-enable-https-with-a-cdn-managed-certificate).
343
-
- If you plan to migrate to Azure Front Door or move to BYOC yourself before 14 April 2026 or want to opt out of auto migration and willing to risk disruption to the HTTPS traffic, you will need to set a Feature Flag by following [instruction provided](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/preview-features?tabs=azure-portal), and selecting the Feature Flag "Microsoft.Cdn/DoNotAutoMigrateClassicManagedCertificatesProfiles") before 9 April 2026. Doing so will prevent Microsoft from migrating your eligible classic managed certificate profiles to Azure Front Door.
343
+
- If you plan to migrate to Azure Front Door or move to BYOC yourself before April 14, 2026 or want to opt out of auto migration and willing to risk disruption to the HTTPS traffic, you will need to set a Feature Flag by following [instruction provided](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/preview-features?tabs=azure-portal), and selecting the Feature Flag "Microsoft.Cdn/DoNotAutoMigrateClassicManagedCertificatesProfiles") before April 9, 2026. Doing so will prevent Microsoft from migrating your eligible classic managed certificate profiles to Azure Front Door.
344
344
345
-
Between 10 April 2026 and 14 April 2026:
346
-
- Customers who have not set the said Feature Flag before 9 April 2026, their profiles will be migrated to Azure Front Door Standard or Premium SKU on a "best effort" basis and should watch for an email related to their migration status.
347
-
- Customers who have set the said Feature Flag but are still consuming services with classic SKUs will have until 14 April 2026 to complete migration or move to BYOC.
345
+
Between April 10, 2026 and April 14, 2026:
346
+
- Customers who didn't set the said Feature Flag before April 9, 2026, their profiles will be migrated to Azure Front Door Standard or Premium SKU on a "best effort" basis and should watch for an email related to their migration status.
347
+
- Customers who set the said Feature Flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC.
348
348
349
349
Azure Front Door (classic)
350
350
351
-
Before 9 April 2026:
351
+
Before April 9, 2026:
352
352
- [Migrate to Azure Front Door Standard or Premium](https://learn.microsoft.com/en-us/azure/frontdoor/tier-migration) or [move to Bring Your Own Certificate (BYOC)](https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https?tabs=powershell).
353
353
354
-
- If you plan to migrate to Azure Front Door or transition to Bring Your Own Certificate (BYOC) before 14 April 2026, or if you choose to opt out of auto migration and accept the risk of HTTPS traffic disruption, you will need to set a feature flag by following the [instruction provided](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/preview-features?tabs=azure-portal), and selecting the Feature Flag "Microsoft.Cdn/DoNotAutoMigrateClassicManagedCertificatesProfiles" before 9 April 2026. Doing so will prevent Microsoft from migrating your eligible classic managed certificate profiles to Azure Front Door.
354
+
- If you plan to migrate to Azure Front Door or transition to Bring Your Own Certificate (BYOC) before April 14, 2026, or if you choose to opt out of auto migration and accept the risk of HTTPS traffic disruption, you will need to set a feature flag by following the [instruction provided](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/preview-features?tabs=azure-portal), and selecting the Feature Flag "Microsoft.Cdn/DoNotAutoMigrateClassicManagedCertificatesProfiles" before April 9, 2026. Doing so will prevent Microsoft from migrating your eligible classic managed certificate profiles to Azure Front Door.
355
355
356
-
Between 10 April 2026 and 14 April 2026:
356
+
Between April 10, 2026 and April 14, 2026:
357
357
358
-
- For customers who do not set the feature flag by 9 April 2026, Microsoft will migrate their profiles to Azure Front Door Standard or Premium SKU on a "best effort" basis. Customers are advised to monitor their email for updates on migration status. Customers who have set the said Feature Flag but are still consuming services with classic SKUs will have until 14 April 2026 to complete migration or move to BYOC.
358
+
- For customers who do not set the feature flag by April 9, 2026, Microsoft will migrate their profiles to Azure Front Door Standard or Premium SKU on a "best effort" basis. Customers are advised to monitor their email for updates on migration status. Customers who have set the said Feature Flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC.
0 commit comments