Dynamics 365 Business Central and Azure Front Door issue.
On October 29, 2025, an 8.5-hour outage of Azure Front Door caused widespread disruption to Dynamics 365 Business Central and other Azure services. A faulty configuration deployment with inadequate validation checks cascaded across the global edge network, causing node failures, increased latencies, and connection errors until Microsoft rolled back to the last known good configuration.
post Stefano Demiliani
"The issue was not a Dynamics 365 Business Central-related issue, but the cause of this unreliability was a different service: Azure Front Door."
Key points
- Azure Front Door is Microsoft’s global content delivery and load balancing service that handles routing, caching, and security for cloud services like Business Central
- The outage started October 29 at 15:45 UTC and lasted 8.5 hours, caused by a software defect in configuration validation that allowed an erroneous configuration to bypass safety checks
- The invalid configuration caused cascading failures across AFD nodes worldwide, resulting in timeouts, connection errors, and imbalanced traffic distribution
- Microsoft resolved the issue by immediately blocking further configuration changes, rolling back to the last known good configuration, and gradually rebalancing traffic
- Post-incident improvements include enhanced validation controls, better automated rollback mechanisms, and strengthened monitoring capabilities
Quotes
- “The issue was not a Dynamics 365 Business Central-related issue, but the cause of this unreliability was a different service: Azure Front Door.” (Clarifies that Business Central outages may result from underlying Azure infrastructure problems, not the application itself)
Context
- Features: multi-region backend pools, health probes, path-based routing, geo-filtering, geo-routing, content caching, automatic failover
Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.