Follow us on Google News
A global Microsoft 365 outage disrupted Outlook, Teams and other services for over 11 hours, affecting users and AI tools.
Microsoft experienced a prolonged service disruption on Friday, November 13, affecting thousands of users across its Microsoft 365 ecosystem. The outage interrupted access to Outlook, Teams, Copilot and several other applications, while also affecting Microsoft 365 connectors used by artificial intelligence companies OpenAI and Anthropic.
The company attributed the disruption to server-related failures and said its technical teams were working to restore services. Recovery was gradual, with some systems continuing to experience difficulties even after corrective measures were introduced.
How Widespread Was the Microsoft Outage?
The disruption continued for more than 11 hours, affecting users who depend on Microsoft’s cloud-based communication and productivity services. Outlook was among the most visibly affected applications, with users reporting difficulties accessing email and related functions.
According to outage-tracking platform Downdetector, reports concerning Outlook peaked at approximately 1.30 am on Friday, reaching 1,38,058 complaints. By 4.30 am, the number had declined to around 34,490, indicating that problems were continuing despite a reduction in reported incidents.
The outage also affected Microsoft 365 connectors used by OpenAI and Anthropic, disrupting connections and certain functions of their AI tools. Services dependent on Exchange Online and Microsoft’s email infrastructure experienced interruptions, although features operating independently of those systems remained functional.
https://the420.in/fcrf-certified-chief-ai-officer-second-cohort-november-2026/
What Caused the Server Failures?
Microsoft said its investigation identified a process responsible for establishing secure connections on affected servers as a significant factor behind the outage. The process became overwhelmed, preventing servers from processing incoming requests and affecting service availability.
The company clarified that the disruption was not caused by an overall increase in network traffic. Instead, fewer servers were available to handle existing demand, placing additional pressure on the remaining infrastructure.
Microsoft was also examining a recent network configuration change that coincided with the beginning of the disruption. Engineers began reversing the change to determine whether it had contributed to the failures.
What Steps Did Microsoft Take to Restore Services?
Microsoft introduced several corrective measures, including increasing virtual machine capacity to distribute workloads and reduce pressure on affected systems. Engineers also worked to restore machines that had entered faulty states by synchronising recent network changes.
However, some machines failed to synchronise as expected, slowing the recovery process. The company also prepared configuration adjustments, testing them on selected servers before wider deployment alongside infrastructure restarts.
Temporary traffic restrictions were introduced in certain locations to reduce server loads. Microsoft monitored the affected systems under reduced demand before gradually restoring additional connections. The company issued more than 15 updates through X, detailing its recovery efforts and continuing technical assessments.
What Was the Impact on Businesses and AI Services?
The disruption affected cloud-based services used for workplace communication, email management and AI integrations. Problems involving Exchange Online also affected applications relying on Microsoft’s underlying email infrastructure.
For AI platforms using Microsoft 365 connectors, the outage interrupted access to connected services and affected certain tool functions. The incident demonstrated how technical failures within a major cloud infrastructure provider can disrupt applications operated by other technology companies.
Microsoft said it would continue monitoring the effectiveness of its corrective measures and introduce further adjustments where necessary. Although services were gradually recovering as users reconnected, the company continued working to stabilise affected servers and restore normal operations across its Microsoft 365 environment.
