Microsoft 365 outage takes Outlook, Teams and Copilot offline worldwide

A team on Microsoft 365 could not work for most of Thursday afternoon. Outlook was down. Teams calls failed. Copilot stopped answering. BleepingComputer cites Microsoft's own status posts. The outage began at 1:26 pm Eastern on 12 November 2026. Two hours later only limited recovery had arrived.

The services affected are long. BleepingComputer names Outlook, Microsoft Teams and Copilot. It also names Exchange Online, SharePoint Online, OneDrive, Azure, Microsoft Defender XDR and the Microsoft Store. The outlet writes that the problem first looked like it only hit the Americas. Microsoft later told users in any region that they could be affected.

What Microsoft said about the cause

BleepingComputer quotes Microsoft's statement that the cause was "a number of servers being unexpectedly unavailable" rather than high traffic. That failure, Microsoft said, put a heavier load on the servers that stayed up. The company paused deployments and moved traffic between regions. It also restarted the failed servers. It said it was checking whether a configuration change should be rolled back. The outlet reports "limited recovery" after some of those servers returned to service. Full recovery would arrive gradually as client apps reconnected.

A separate Teams problem had already hit users that morning. BleepingComputer writes that it ran from 9:45 to 10:53 am Eastern. Microsoft attributed it to resource contention. The outlet says Microsoft has not confirmed whether the two events are connected.

Map your Microsoft 365 dependencies before the next outage

A team whose product depends on Microsoft's cloud lost three core tools at once. Email stops, calls stop, and the AI assistant everyone leans on stops too. The useful exercise in the hours after an event like this one is not to pick a different vendor. It is to list every path in your product that calls Microsoft 365. Then say in one line what each path does when that call fails.

The same list is useful whichever host you use. A Copilot feature inside your app is a dependency. So is a Teams notification your agents post into. So is a SharePoint document your retrieval pipeline reads. Each one will one day have a quiet six hours. Write a short plan for that hour before the event. The on-call engineer reads it in the first minute. That plan is cheaper than the plan you write while the alerts are firing.

Microsoft has not disclosed a user count for this outage. The outlet does not state one either. BleepingComputer's article is the primary source until Microsoft posts a longer postmortem on the status page.

Source

Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide, BleepingComputer.