A widespread Azure outage on Wednesday, October 29, 2025, caused major service disruptions across Microsoft and third-party platforms. The incident began around 12 p.m. ET (16:00 UTC) and was traced to an “inadvertent configuration change” within Azure Front Door, Microsoft’s global traffic routing network. The outage impacted thousands of users worldwide, affecting productivity, gaming, and retail operations.
Microsoft engineers initiated recovery protocols within hours, restoring partial access and rerouting traffic to stabilize services.
Microsoft Azure experienced a global outage on October 29, 2025, beginning at 12 p.m. ET, due to a configuration error in Azure Front Door, its cloud traffic routing system. The disruption affected Microsoft 365, Teams, Outlook, Xbox Live, Minecraft, and services for Alaska Airlines, Starbucks, Costco, and Kroger. Microsoft responded by rolling back to a stable configuration and rerouting traffic, initiating recovery within hours.
Timeline and Affected Services
- Start Time: 12 p.m. ET (16:00 UTC)
- Root Cause: Misconfigured Azure Front Door setting
- Impacted Services:
- Microsoft 365, Teams, Outlook
- Xbox Live, Minecraft
- Third-party services: Alaska Airlines, Starbucks, Costco, Kroger
- Recovery Actions:
- Rollback to last known good configuration
- Traffic rerouting to unaffected infrastructure
- Azure portal access restored within hours
Microsoft acknowledged the issue on its status page and began mitigation immediately.
Quotes and Reactions
From Microsoft’s official status update:
“We identified an inadvertent configuration change to Azure Front Door as the root cause and initiated rollback procedures.”
Cloud analyst Dana Raines told TechWire:
“This incident underscores the importance of configuration governance in global cloud networks.”
Users on X reacted quickly:
“Teams down, Outlook down, Xbox down — Azure outage hit everything.” “Starbucks app not working. Azure’s having a rough day.”
Business Continuity and User Experience
The outage disrupted operations for enterprises and consumers alike. Retailers relying on Azure infrastructure faced transaction delays, while productivity tools like Teams and Outlook were inaccessible for hours. Gaming platforms saw login failures and matchmaking issues.
The event highlights the need for robust disaster recovery plans and multi-region failover strategies in cloud-dependent environments.
What’s Next: Monitoring and Preventive Measures
- Ongoing Recovery: Full restoration expected within 24 hours
- Monitoring Tools:
- Azure Service Health dashboard
- @AzureSupport on X
- User Actions:
- Activate BC/DR plans if needed
- Use CLI or PowerShell for manual operations
- Avoid rushed failovers to prevent data loss
- Review architecture for redundancy improvements
Microsoft is expected to release a post-incident report detailing root cause analysis and future safeguards.
