Azure Frontdoor
Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) experienced latencies, timeouts, and errors.
The AFD & CDN delivery services continue to be stable and are running as expected.
Out of an abundance of caution, all service management operations (including creation, updates, deletions, and purges) to AFD via portal or APIs continue to remain temporarily suspended. We are working on a comprehensive plan to gradually reenable these in a phased approach, while ensuring the platform remains stable.
We will continue to share periodic updates as we make progress. Next Update will be by 01:00 UTC on 31 Oct 2025 or sooner.
The Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remains at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
We will notify customers once the restriction is lifted, and we will be sending periodic communication on the progress. Next Update will be by 19:00 UTC on 31 Oct 2025 or sooner as event warrant.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
We are working to provide an ETA on when we can lift the restriction and will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 01 November 2025 or sooner as events warrant.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
Our current expectation is to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 01 November 2025 or sooner as events warrant.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 02 November 2025 or sooner as events warrant.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 03:00 UTC on 03 November 2025 or sooner as events warrant.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 03:00 UTC on 03 November 2025 or sooner as events warrant.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 03 November 2025 or sooner as events warrant.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As part of completing our full investigation and safe checks, performing service management operations (create, update, delete, purge, etc.) were made temporarily unavailable.
Restrictions on service management operations have been removed for this Azure subscription ID. Please allow approximately 30–40 minutes for changes to fully propagate to edge sites. We expect all restrictions across subscriptions, including other subscriptions under your tenant, to be lifted by 05 November 2025. Updates on progress will continue via Azure Service Health. The next update will be provided by 22:00 UTC on 04 November 2025, or sooner if circumstances change.
We acknowledge that previous communication may have contained information meant for another list of customers. We apologize for the inconvenience and request you to note the following.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
The workflow to manage and rotate Bring Your Own Certificate (BYOC) certificates has been re-enabled. We will monitor the progress of working through the queue of necessary rotations. We will continue to provide regular updates on progress. Our current expectation remains to lift the restriction on 05 November 2025. The next update will be by 22:00 UTC on 04 November 2025 or sooner as events warrant.
In preparation for lifting the service management restrictions, an incorrect communication was sent indicating an early removal. Our current date for lifting all control plane restrictions remains 05 November 2025. The next update will be provided by 22:00 UTC on 04 November 2025, or sooner.
Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable.
We continue to hit our milestones toward the expectation to lift this restriction on 05 November 2025. The next update will be sent to confirm once this has happened, or sooner if events warrant.
Latest Update: As of 23:00 UTC on 5 November, 2025 restrictions on Azure Front Door (AFD) and Content Delivery Network (CDN) service management operations have been removed. You may now resume normal operations on the AFD service management plane. For enhanced safety and protection, we have extended the configuration propagation times up to 45 minutes. Additional platform enhancements which are underway are expected to optimize the propagation times further.
Previous Context: Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated by 00:05 UTC on 30 October 2025 and remain at normal operating levels. We previously notified you that, as part of completing our full investigation and safe checks, performing service management operations (create, update, delete, purge, etc.) were temporarily restricted. This notification is to confirm that those temporary restrictions no longer apply.
Next Steps: As mentioned in our Preliminary PIR we are completing an internal retrospective to understand the incident in more detail. Once this is completed, which is expected within approximately 7 days, we will publish our final Post Incident Review (PIR) - including a link to register for an Azure Incident Retrospective livestream, discussing the incident and our learnings.
Azure Front Door frequently asked questions (FAQ) | Microsoft Learn
Latest Update: As of 23:00 UTC on 5 November, 2025 restrictions on Azure Front Door (AFD) and Content Delivery Network (CDN) service management operations have been removed. You may now resume normal operations on the AFD service management plane. For enhanced safety and protection, we have extended the configuration propagation times up to 45 minutes. Additional platform enhancements which are underway are expected to optimize the propagation times further.
Previous Context: Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated by 00:05 UTC on 30 October 2025 and remain at normal operating levels. We previously notified you that, as part of completing our full investigation and safe checks, performing service management operations (create, update, delete, purge, etc.) were temporarily restricted. This notification is to confirm that those temporary restrictions no longer apply.
Next Steps: As mentioned in our Preliminary PIR we are completing an internal retrospective to understand the incident in more detail. Once this is completed, which is expected within approximately 7 days, we will publish our final Post Incident Review (PIR) - including a link to register for an Azure Incident Retrospective livestream, discussing the incident and our learnings.
Azure Front Door frequently asked questions (FAQ) | Microsoft Learn
An emergency maintenance window is opened effective immediately to ensure continued stability and security of our service. The service may be unavailable for the next two hours.
Our Maintenance services are complete. Services are working as intended.
If you have ever have an issue, you can reach out to our support team via our support portal.
Impact Statement: Starting at 06:45 UTC on 26 Jun 2023 you have been identified as a customer using Azure Front Door who may have encountered intermittent HTTP 502 errors response codes when accessing Azure Front Door CDN services.
Current Status: Based on our initial investigation, we have determined that a subset of AFD POPs became unhealthy and unable to handle the load of incoming requests, which in turn impacted Azure Front Door availability.
After a successfully simulation we are currently applying the potential mitigation workstream, by removing impacted instances from rotation while monitoring traffic allocations to remaining healthy cluster. The first set of impacted instances have been successfully removed at 15:30 UTC on 26 Jun 2023. Since the removal we have been seeing a reduction of errors and we will continue to monitor impact. We are currently working on removing the rest of the impacted instances and allocating the resources to a healthy alternative. Some customers may already begin to see signs of recovery. The next update will be provided in 60 minutes, or as events warrant.
Summary of Impact: Between 06:45 UTC and 17:15 UTC on 26 Jun 2023 you were identified as a customer using Azure Front Door who may have encountered intermittent HTTP 502 errors response codes when accessing Azure Front Door CDN services.
This issue is now mitigated, more information on mitigation will be provided shortly.
Summary of Impact: Between 06:45 UTC and 17:15 UTC on 26 Jun 2023 you were identified as a customer using Azure Front Door who may have encountered intermittent HTTP 502 errors response codes when accessing Azure Front Door CDN services.
Preliminary Root Cause: We found that a subset of AFD POPs were throwing errors and unable to process requests.
Mitigation: We moved the resources from the affected AFD POPs to healthy alternatives which returned the service to a healthy state.
Next Steps: We will continue to investigate to establish the full root cause and prevent future occurrences. Stay informed about Azure service issues by creating custom service health alerts: https://aka.ms/ash-videos for video tutorials and https://aka.ms/ash-alerts for how-to documentation.
How to stay informed about Azure service issues