Skip to content

Microsoft 365 Outage: What Happened to Outlook, Teams and Copilot

Person using a laptop to check email
Photo: Pexels

Microsoft 365 services, including Outlook, Teams and Copilot, were disrupted around the world on Thursday, November 12, 2026. Microsoft said the cause was a server problem, not an attack. Here is the timeline and what is still unknown.

Rows of servers in a data center
Server racks in a data center corridor
Laptops on a desk in an office
Photos: Pexels (free to use)

What happened

  • Start. Microsoft said the incident began Thursday at 1:26 p.m. Eastern. Reuters put the disruption at about 10 hours.
  • Services hit. Customers could have trouble connecting to Exchange Online (email), Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, according to a Microsoft advisory cited by BleepingComputer.
  • Cause given. Microsoft said “a number of servers” became unexpectedly unavailable, which strained the remaining infrastructure. Later it said a core process on affected servers became overwhelmed, causing a loss of capacity.
  • Not an attack. Microsoft said there was no indication of malicious or cyber activity.
  • The fix. Microsoft said it paused deployments, redistributed traffic and restarted affected servers.

Who was affected

Downdetector, which counts user reports, showed more than 130,000 Outlook problem reports in the US at the peak, according to Reuters. The US House of Representatives said its users were affected. Australia’s spy agency and federal police were among affected organisations, and Australia’s cyber security minister, Tony Burke, said Microsoft believed it was not a cyberattack. OpenAI and Anthropic said their Microsoft 365 connectors were affected, and truck maker Workhorse Group delayed an earnings report from November 12 to November 16, citing the outage.

Recovery

By the morning of November 13, Microsoft reported gradual recovery and extended its email timeout window to 48 hours to help delayed messages get through. By midday, email queues were “significantly reduced” and approaching normal levels, BleepingComputer reported. Microsoft executive Charles Lamanna said teams are reviewing what happened.

What we don’t know

  • The root cause of the server failures has not been disclosed.
  • An earlier, separate Teams incident that morning has not been linked to this one by Microsoft.
  • Full restoration had not been confirmed, and some intermittent issues were still possible.
  • We could not confirm how many countries were affected. Reports say “globally.”

Sources

BleepingComputer (November 12–13, 2026, updated) and Reuters via Khaleej Times (November 13, 2026). Microsoft’s own status page did not show incident details when we checked. Photos are stock images for illustration, not pictures of these events.