A widespread Microsoft 365 outage disrupted Outlook, Teams and other workplace services on Thursday, November 12, leaving thousands of users unable to access email and collaboration tools. The disruption began in the United States and extended to users in other regions as Microsoft worked to restore affected infrastructure.
Outlook drew more than 130,000 problem reports on Downdetector shortly after 1 p.m. Eastern time. Microsoft 365 and Teams also recorded thousands of complaints. The interruption continued for hours, affecting businesses and individuals who rely on Microsoft’s cloud services for daily operations.
Microsoft 365 Outage Affects Outlook and Teams
Outlook users reported difficulty opening inboxes, sending messages and receiving email. Others experienced connectivity failures across Microsoft 365 applications. The problems also affected Teams, although Microsoft said it had resolved an earlier Teams disruption in North America.
According to Downdetector’s Outlook outage tracker, reports surged during the afternoon before gradually declining. The service collects reports from users and other sources, so its figures do not represent a confirmed count of affected customers.
The disruption extended beyond email. Other affected services included SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, according to Microsoft’s incident updates. The breadth of the outage made it difficult for organizations using several Microsoft services together.
Microsoft Identifies Problems With Cloud Infrastructure
Microsoft initially linked the connectivity errors to elevated infrastructure load across multiple regions. Further investigation found that numerous servers had unexpectedly become unavailable. That shifted more traffic to the remaining infrastructure and increased pressure on systems still operating.
The company paused deployments and configuration changes while engineers investigated possible contributing factors. It also redistributed connection traffic across its global infrastructure and restarted affected servers to restore capacity.
Microsoft later reported that an alternative health-check method had helped some servers return to service. Engineers began applying the approach more broadly while developing an automated recovery process to detect and restart unresponsive machines.
The company continued publishing technical information through its Microsoft 365 service health page and administrative incident notices. At the time of the initial reports, it had not established a firm timeline for complete recovery.
Outage Also Disrupts AI Service Connections
The service interruption reached applications outside Microsoft’s own productivity suite. OpenAI reported problems with Microsoft connectors that could prevent users from establishing new connections or using connected tools as expected.
Anthropic also identified an upstream provider issue affecting its Microsoft 365 connector. These integrations allow AI applications to access authorized information from services such as email and workplace document systems.
The connector disruptions showed how an outage in a major cloud platform can affect applications that depend on its authentication, data access and communication services. Even when another application remains available, some integrated features may stop working until the underlying service recovers.
Recovery Continues After Hours of Disruption
By approximately 6 p.m. Eastern time Thursday, Microsoft had observed limited recovery as users gradually reconnected. Reuters reported that Outlook problem reports had fallen to roughly 34,500, compared with a peak of about 138,000 earlier in the day.
Lower complaint totals did not mean every affected service had recovered. Microsoft was still returning servers to operation and monitoring whether its recovery measures would keep them responsive under renewed traffic.
The disruption also continued to affect business operations on Friday. Companies in banking, finance and shipping turned to alternative communication methods as problems with email and collaboration tools persisted. Microsoft subsequently reported signs of stabilization after applying broader recovery measures.
The incident illustrates the operational risks of relying heavily on interconnected cloud services. Organizations may need backup communication channels and procedures that remain available when their primary email and collaboration platforms experience prolonged interruptions.
Users experiencing continuing problems can check Microsoft’s official service health information for updates. Business administrators can also review incident notices EX1550543 and MO1550821 in the Microsoft 365 admin center for details relevant to their environments. Confirm complete restoration through official service updates rather than relying on outage-report totals alone.
