Azure outage reports surged across multiple Microsoft services on Wednesday, October 29, affecting thousands of users globally. According to outage tracking platform Downdetector, problems spiked just before noon ET, impacting Azure and Microsoft 365 functionality. Many users faced difficulties accessing cloud-based dashboards and online workspaces, forcing enterprises to delay operations relying on Azure infrastructure.
Microsoft acknowledged the widespread azure outage through its official status page, confirming that customers may experience issues accessing the Azure Portal. Engineers responded swiftly, implementing corrective actions expected to stabilize services soon. Despite this, reports continued flooding social media as IT administrators sought clarity on the cause and anticipated resolution timeframe.
Experts suggest the outage may have stemmed from a regional network disruption affecting Microsoft’s data centers handling global cloud traffic. The incident highlights the growing dependence of enterprises on centralized platforms like Azure for mission-critical workloads. Microsoft has assured users that updates will be provided as systems gradually recover and full service is restored.
Is the reported Microsoft Azure outage effecting your day?
— Downdetector (@downdetector) October 29, 2025
We've gotten over 105k outage reports globally for Azure on Downdetector. Azure also supports services like Mircosoft 365, Minecraft, Xbox, Copilot, etc.https://t.co/hm4F8dhpys pic.twitter.com/G4c1yG115U
Microsoft Confirms Configuration Error Behind Azure Front Door Outage
Starting around 16:00 UTC, Microsoft confirmed that customers and internal services using Azure Front Door (AFD) experienced latency, timeouts, and widespread errors. The company identified an inadvertent configuration change as the main cause, which triggered system instability across multiple Azure-managed platforms and services on Wednesday.
To contain the issue, Microsoft temporarily blocked all configuration changes to AFD, including customer-initiated updates. Engineers are currently rolling back the service to a stable, previously known configuration state. The company assured users that the rollback process is cautious to prevent the faulty configuration from reactivating during system recovery.
Throughout the incident, some customers struggled to access the Azure management portal. Microsoft redirected portal traffic to bypass AFD, restoring partial functionality for most users. While the core portal and extensions are operational, a few endpoints, such as Marketplace, may still face loading issues. Microsoft has not provided an exact ETA but pledged to issue updates within 30 minutes or as progress continues.
