Microsoft (Nasdaq: MSFT) returned some servers to service Thursday after a failure in Exchange Online cut off Outlook and other Microsoft 365 tools for hours, but it had not declared the outage over or named a cause.
The outage began around 11:17 a.m. ET, when users in the Americas lost access to Exchange Online mailboxes. Microsoft later said users in any region could be affected, and it listed Teams, SharePoint, Copilot and Defender XDR among the services hit. Outlook outage reports on Downdetector topped 130,000 in the early afternoon and still stood near 31,000 at 8 p.m. ET.
Microsoft's outage reports on November 12 reached 74 countries and territories in about an hour on Downdetector.
— Downdetector (@downdetector) November 12, 2026
Microsoft says its Exchange Online incident began at 16:17 UTC. Reports to Downdetector about Outlook began climbing at about 17:25 UTC, 12:25 in New York. By 18:25,… pic.twitter.com/7FQ4dDsfbm
Microsoft first blamed elevated load, then said traffic had not increased, and servers were unexpectedly unavailable, straining the rest of its infrastructure. It froze all deployments and configuration changes to check whether a recent change caused the problem, and by 2:43 p.m. ET it said affected servers were failing automated health checks.
We’re seeing positive results with our efforts to restart affected infrastructure and recover server availability in an isolated manner. We’re actively monitoring the performance of these portions of infrastructure to verify stability, which we suspect will support improved…
— Microsoft 365 Status (@MSFT365Status) November 13, 2026
Around 4 p.m. ET, Microsoft said a replacement health check brought some affected servers back online and began applying it more broadly. It warned that restored servers might stop responding again once traffic returned, and engineers are considering undoing a handful of recent setting changes to speed recovery.
Microsoft has yet to explain what went wrong and has not suggested a cyberattack.