
Microsoft 365 outage spreads from Outlook to Teams, Copilot and more worldwide
Cloud dependencies turn one mailbox failure into disrupted workplace operations worldwide.
Overview
users worldwide lost access to email, meetings, files and AI tools on November 12. The problem began with connections in the Americas and then spread to other regions. Microsoft tracked the first issue as and the wider outage as . Outlook users could not open mailboxes, sign in or connect. Some Teams chats and other features still worked. recorded nearly 130,000 Outlook reports, including almost 20,000 reports per minute at the peak. Microsoft said some servers went down unexpectedly, overloading the remaining shared systems, not a surge in customer traffic. It restored service by restarting and repairing systems. Reports fell as services returned across regions.
Timeline
The outage exposed the reach of shared Microsoft 365 service infrastructure
The incident affected and multiple other Microsoft 365 services, including and related applications, after unexpected server unavailability strained remaining infrastructure.
Microsoft restored Microsoft 365 connectivity after the server-related disruption
The incident moved from widespread service failure toward recovery as Microsoft returned infrastructure to service and reduced the load on remaining capacity. Outlook, Teams, SharePoint Online, Copilot, , and other connected workloads had been affected during the disruption, with recovery varying by product and tenant.
Outlook and Microsoft 365 reports began falling as recovery efforts took effect
Public outage reports declined from their peak, although substantial numbers of users continued reporting problems later in the afternoon. The fall in complaints indicated improving availability but did not by itself establish that every or workload had fully recovered.
Microsoft directed administrators to incident records and its public status page
Microsoft told customers to follow and in the Microsoft 365 admin center. It also pointed users to the public status page when the admin center was unavailable, giving organizations an alternate source for service-health updates during the disruption.
Microsoft began restoring capacity by restarting and repairing affected infrastructure
Microsoft said it was working to return unavailable servers to service and was restarting or repairing affected portions of the infrastructure. The mitigation targeted the capacity shortage that had increased load on the remaining systems.
Microsoft said unavailable servers were straining the remaining infrastructure
Microsoft said the elevated load was not caused by an increase in customer traffic. Instead, a number of servers had become unexpectedly unavailable, placing additional pressure on the infrastructure that remained in service and contributing to connectivity errors across regions.
The outage affected Microsoft 365 services unevenly across users and regions
Reports and Microsoft updates indicated that the incident primarily affected while also causing connection problems across other Microsoft 365 services, rather than producing an identical failure for every user.
Downdetector recorded a peak of almost 20,000 Microsoft 365 reports per minute
The rapid increase in reports made the outage visible well beyond individual tenant support channels. The surge reflected a concentrated failure affecting a widely used workplace platform, while report totals varied by product and time as services degraded unevenly.
Downdetector reports approached 130,000 for Outlook during the outage peak
recorded nearly 130,000 user reports involving Outlook shortly after 1 p.m. Eastern time. Microsoft 365 reports exceeded 47,000, while Teams and Copilot also generated thousands of reports. These figures measured user-submitted complaints, not confirmed affected customers.
Microsoft added Copilot, Defender XDR, and other connected services to the impact list
The affected-workload list expanded to include and , along with services such as Planner, To Do, , and Defender for Office 365. The expansion showed how shared identity, data, and front-end dependencies could transmit an Exchange connectivity failure into AI, security, and collaboration products.
Microsoft identified Teams and SharePoint Online among the affected workloads
Microsoft said the incident could affect Microsoft and in addition to Exchange Online. Symptoms differed by workload, with some users encountering connection or authentication failures while other features remained available.
Microsoft said the connectivity problems had spread across regions
Microsoft expanded its warning from an initial regional problem to connectivity issues affecting users across multiple regions. The change indicated that the incident had become a global availability problem rather than an isolated Exchange Online fault.
Outlook and Exchange Online users reported widespread access and connectivity failures
Microsoft said the incident primarily affected , with users reporting problems connecting to across desktop, web, and mobile apps, along with broader Microsoft 365 connection timeouts.
Microsoft opened a broader Microsoft 365 incident as connectivity failures expanded
Microsoft logged the wider disruption under and described a service degradation affecting multiple . The incident record connected the broader symptoms to the Exchange Online failure while Microsoft continued investigating.
Users began losing access to Exchange Online mailboxes and Outlook
Microsoft began tracking intermittent connectivity failures under . Users reported mailbox access errors, connection timeouts, and problems opening Outlook or sending and receiving messages. The initial reports emerged in the Americas before the full geographic scope was clear.