NewsStocksMicrosoft 365 Outage Disrupts Outlook, Copilot, and AI Connectors for ChatGPT and Claude

Microsoft 365 Outage Disrupts Outlook, Copilot, and AI Connectors for ChatGPT and Claude

Author: Cryptopolitan·

Key Takeaways

  • •Microsoft's service-health dashboard was still reporting degradation at 2:14 a.m. UTC on November 13, roughly 13 hours after Outlook connection complaints began on November 12.
  • •The disruption stemmed from servers failing automated health checks and an overloaded core process rather than a traffic surge, and Microsoft had not confirmed what triggered the failures.
  • •Services depending on Exchange Online were hit unevenly: Teams chats and online meetings kept working while meeting scheduling failed, and Copilot Chat, Microsoft Graph, Safe Links verification, Defender, Intune, Purview, Planner, and To Do were among the affected tools.
  • •ChatGPT and Claude experienced errors through their Microsoft 365 connectors, but neither OpenAI nor Anthropic reported outages of their core AI models.
  • •Microsoft redirected Outlook connections, restarted unresponsive servers, and suspended deployments and configuration changes, yet some servers relapsed when traffic resumed and no permanent fix had been announced.
Microsoft 365 Outage Disrupts Outlook, Copilot, and AI Connectors for ChatGPT and Claude

Microsoft 365 users were still contending with service disruptions early Friday. At 2:14 a.m. UTC on November 13, Microsoft's service-health dashboard continued to report degradation for business and consumer products, with updates also posted through the company's @MSFT365Status account on X. The problems were not limited to Outlook: Microsoft 365 Copilot and the Microsoft connectors used in platforms such as ChatGPT and Claude were affected as well.

Complaints began shortly before 1 p.m. ET on Thursday, November 12, when Outlook users started reporting lost connections. Later updates from Microsoft indicated that many of the affected services depended on Exchange Online, the cloud service that stores and routes email and calendar data for Microsoft 365. That dependency explains the uneven pattern of symptoms: Teams chats and online meetings kept working, but meeting scheduling did not function properly at all. Files saved in SharePoint remained available.

The disruption also reached other Microsoft tools that rely on email and calendar data. Copilot Chat could fail to load or respond, and requests through Microsoft Graph — the interface applications use to reach Microsoft 365 mail, calendar, and file data — could time out. Microsoft additionally warned about delayed emails and failures in Safe Links verification, the feature that checks web addresses in messages.

The list of affected services was extensive: Defender, Intune, Purview, Planner, To Do, administrative tools, and some Power BI exports, along with certain Education features, Universal Print functions, and Windows 365 Cloud PCs.

Why ChatGPT and Claude flashed errors

ChatGPT and Claude were drawn into the incident through their Microsoft 365 connectors — the integrations that let the assistants pull email, calendar, and search data from a connected Microsoft 365 account. Anthropic reported that most email, calendar, and search requests sent through Claude's Microsoft 365 connector were unsuccessful, and that Claude for Outlook was affected as well. OpenAI reported problems with new Microsoft connections and connector tools in ChatGPT.

Neither Anthropic nor OpenAI reported an outage of its core AI models. The failures involved access to Microsoft 365 services, not the models themselves. Microsoft 365 Copilot faced a different problem: according to Microsoft's service bulletin, Copilot Chat itself could fail to load or respond.

What Microsoft said went wrong

Microsoft's updates showed that the strain came from lost server capacity rather than a surge in traffic. Some servers failed automated health checks — the routine probes that decide whether a machine is fit to receive traffic — and dropped out of service, leaving the remaining machines to handle more requests.

Engineers found that a core process had become overloaded, causing affected servers to be unresponsive. They also suspected a problem with the component handling automated health checks, but had not confirmed what triggered the failure.

Emergency fixes, not a permanent cure

Microsoft temporarily suspended deployments and configuration changes while investigating the disruption. Engineers redirected Outlook connections away from affected infrastructure in the United States and redistributed traffic across Microsoft's global network. They also restarted unresponsive servers and tested a different health-check method to bring them back online, according to Microsoft's updates.

Some servers returned to service, only to become unresponsive again when traffic resumed. At 2:14 a.m. UTC on November 13, the service-health dashboard still reported service degradation. Microsoft was adding infrastructure capacity as regions came back online and monitoring the results. The company had not confirmed full restoration or announced a permanent fix. With some servers relapsing when traffic resumed, whether the added capacity would hold under normal use was the question Microsoft's monitoring was meant to answer.

Why one vendor's bad day matters

A disruption at one cloud provider can affect businesses worldwide. Synergy Research put third-quarter cloud infrastructure spending at $168 billion, up 55% from a year earlier. AWS held 26% of the market, Microsoft 19%, and Google 16% — a combined 61%.

Cloud investment is also accelerating. Gartner expects AI infrastructure spending to reach $2.4 trillion in 2027, accounting for 59% of global AI spending.

The financial risks are substantial. Uptime Institute found that 57% of surveyed operators' latest major outages cost over $100,000, and one in five exceeded $1 million. Third-party providers also accounted for roughly two-thirds of publicly reported outages over nine years.

Switching cloud providers is not always easy. The UK's competition watchdog flagged barriers and recommended examining Microsoft and AWS for strategic market status. Multicloud networking could help businesses reduce their dependence on a single provider — Cryptopolitan previously reported on a service connecting AWS and Google Cloud through private networks. Such connections may improve resilience, but they cannot restore an application that still depends on Microsoft 365.