On Thursday, November 12, 2026, Microsoft 365 failed in the middle of the workday. Outlook, Teams, SharePoint, Copilot and Defender XDR stopped connecting for organizations across the Americas and then in other regions. Microsoft is tracking it as incident EX1550543, with a related multi-service entry MO1550821. Updated Friday, November 13, 8:30 a.m. ET: The outage is in its second day and Microsoft has not declared it resolved. Overnight, servers it had restored stopped responding again once traffic returned. Early Friday it said servers were stable where a fix had been applied and that it was extending that fix region by region. It has not named a root cause and has committed to a Post-Incident Report once recovery is complete.
This page covers what happened, what to do while it is still down, how Microsoft's service credit actually works, and the decisions to make before the next one. If your organization runs on Microsoft 365, most of this applies to you whether or not your users noticed today.
What happened, in Microsoft's own words
Around 12:39 p.m. ET: reports of Outlook failures begin to spike.
12:54 p.m. ET: Microsoft says it is investigating problems accessing Exchange Online mailboxes through multiple connection methods in the Americas, and soon after confirms the issue may affect Microsoft 365 connectivity in any region.
Early afternoon: Microsoft says part of its infrastructure is under elevated load across multiple regions, and begins redistributing connection traffic across its worldwide infrastructure.
Mid afternoon: Microsoft says the load is not caused by more traffic. A large number of servers became unexpectedly unavailable, pushing their load onto the rest. It paused all deployments and configuration changes, began restarting affected servers, and is testing a configuration change for servers failing automated health checks.
Around 4 p.m. ET: Microsoft says an alternative service health check method let a subset of servers return to service, and it begins applying that change broadly, with automated systems restarting servers that stop responding.
Early evening: Microsoft says its actions so far have not given the relief it expected. It has found that a core process on the affected servers becomes overwhelmed, causing the servers to stop responding. It reports no recent change correlated with the start of the incident.
Thursday evening: Microsoft returns a portion of the affected servers to service and shifts traffic to alternate routes where it can, describing the recovery as limited and gradual.
Around 7 p.m. ET Thursday: Microsoft says restored servers initially stay healthy but can stop responding again once they begin receiving traffic.
Overnight: Microsoft reports positive results from restarts, expands the fix, and scales up capacity to absorb the surge of reconnecting clients. It describes the overwhelmed component as a process on the affected servers that sets up secure connections.
Around 3 a.m. ET Friday: Microsoft says servers are stable where the fix has been applied and extends it region by region. Delayed inbound mail is being held for retry for up to 48 hours.
Microsoft executive Charles Lamanna has said there is no indication the outage resulted from malicious or cyber activity, and no published evidence links it to an attack. Treat it as a service failure, not as a sign that your own tenant was compromised.
By 2 p.m. ET, Downdetector had logged more than 97,000 Outlook reports. Affected connection methods include Outlook on the web, desktop Outlook (MAPI), mobile mail (Exchange ActiveSync) and the REST API, so switching apps does not help.



