Major outages and post-mortemsBackground
Azure Front Door outage on October 29, 2025 hits Microsoft 365 and Entra sign-ins
From 15:41 UTC on October 29 to 00:05 UTC on October 30, 2025 (11:41 a.m. to 8:05 p.m. EDT), Azure Front Door, Microsoft’s global front-end network, had connectivity problems across regions. Microsoft’s incident record lists Microsoft 365, Microsoft Entra ID and the Azure Portal among affected services and traces it to incompatible configuration metadata that exposed a latent bug. Remote workers on Teams and Outlook could not fix this from home. Published October 6, 2026.
- Event date
- Published here
- Updated
- Source
- Azure status history
Background itemThis happened 342 days before we published it (more than 90). It is here as context for the guides it links, not as breaking news. Check the source for anything that has changed since.
What changed
On October 29, 2025, Azure Front Door, the global network Microsoft uses to route traffic to many of its services, had connectivity problems across multiple regions. Microsoft’s incident record lists Microsoft 365, Microsoft Entra ID (the sign-in system most companies use for Microsoft accounts), the Azure Portal, Azure SQL Database, Dynamics 365, Power Platform and others among the affected services.
Microsoft’s post-incident review traces the cause to configuration data. In its words: “A specific sequence of customer configuration changes, performed across two different control plane build versions, resulted in incompatible customer configuration metadata being generated.” That metadata exposed a latent bug in the part of the system that handles traffic, and nodes crashed.
When
- Start: 15:41 UTC on October 29, 2025 (11:41 a.m. EDT).
- End: 00:05 UTC on October 30 (8:05 p.m. EDT on October 29).
- That is a little over eight hours, covering most of the US work day.
Who is affected and what it means for you
If your job runs on Microsoft 365, this outage could show up as Teams failing to join a meeting, Outlook not syncing, or a sign-in prompt that never finishes. Because Entra ID was affected, other company apps that use a Microsoft login could fail too, including some VPN and remote-desktop logins.
From your desk, that looks a lot like a connection problem. It wasn’t. A Starlink line, a cable line and a phone hotspot all reached the same failing front door. A backup internet line wouldn’t have helped, and neither would restarting the router.
What does help is recognizing the pattern fast: several Microsoft services failing at once while other sites load normally points to Microsoft, not to your dish.
What you can do now
- Check the Microsoft 365 service status (or ask your IT team, who can see the admin center) before troubleshooting your connection.
- Confirm your link in the Starlink app. No outages and normal latency mean the problem is elsewhere.
- Have a non-Microsoft fallback for urgent contact during long outages, such as a phone number or a team chat that runs elsewhere, if your employer allows it.
- Our video calls guide covers the call problems that are on your side, and our troubleshooting page helps tell them apart.
What stays the same
- Starlink was not involved.
- Teams’ network requirements are unchanged. Microsoft’s network test still expects latency under 100 ms, jitter under 30 ms and loss under 1%.
What we don’t know yet
- Microsoft’s review doesn’t give a count of affected users.
- The incident record we read does not show when the review was first published, so we date this item by the event.
- We have no logged data from October 2025.
This item is background: it happened more than 90 days before we published this page.
Source
Related guides on this site
Correction log
No corrections since publication. Spotted an error? See corrections for how to tell us; changes are logged here with the date.