🔍 Read the full analysis: Why Is The Microsoft 365 Outage Continuing Into Day Two? on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Microsoft 365 remained degraded at 08:35 UTC on Nov. 13, with Exchange Online disruptions affecting Outlook and connected services. Microsoft says a patch has improved server stability in part of its infrastructure and is being rolled out region by region, but the cause remains unknown.
Microsoft 365 remained degraded at 08:35 UTC on Friday, Nov. 13, as Microsoft expanded a patch intended to stabilize servers supporting Exchange Online. The continuing disruption has affected access to Outlook mailboxes and connected services; Microsoft has not identified the root cause. For response guidance, see how to respond while services are disrupted.
In an 08:06 UTC update to incident EX1550543, Microsoft said servers were stable where the patch had been applied and that it was expanding the change region by region. The company said it was starting with regions in, or entering, peak business hours. Its status page continued to list the incident as a service degradation, so the update did not indicate that service had been restored globally.
The disruption began Thursday, Nov. 12. Microsoft’s first public notice, at 17:54 UTC, said users in the Americas were having trouble accessing Exchange Online mailboxes through multiple connection methods. At 18:07 UTC, Microsoft said the issue could affect Microsoft 365 connectivity in any region. The incident record cited by Cloud Admin Hub gives a start time of 16:17 UTC.
Microsoft’s troubleshooting updates described a sequence of server and capacity problems. The company first cited elevated load across multiple regions, then said that load was not caused by increased traffic but by servers unexpectedly becoming unavailable. It paused deployments, redirected traffic, restarted servers and changed its server health-check method. Microsoft later reported that returned servers could become unresponsive again under traffic, and that a core process was becoming overwhelmed. Its Friday morning update described the affected process as responsible for establishing secure connections.
Microsoft 365 outage · Nov 12–13, 2026 · times UTC
Down, rerouted, restarted, down again
How Microsoft described the outage, step by step, in its own status posts.
Server pool (schematic)
servingcarrying extra loadunavailablerestart
What Microsoft said
- 17:54Nov 12Mailbox access fails in the Americas
- 18:07“May affect” users “in any region”
- 18:35“Elevated load across multiple regions”
- 19:12All deployments paused, traffic moved, servers restarted
- 19:31Not more traffic: servers “unexpectedly unavailable”, the rest carry the load
- 21:00New health-check method: some servers back in service
- 23:59Returned servers “can become unresponsive again”
- 08:06Nov 13Patch stable where applied, now expanding region by region; still degraded
Hit
Exchange Online mail in Outlook, Teams calendars, SharePoint features, Microsoft 365 Copilot, Defender XDR portal, Purview and more
AI connectors
OpenAI and Anthropic reported errors in their Microsoft 365 connectors
Earnings call moved
Workhorse Group: from Nov 12 to Nov 16, citing the Microsoft outage
Sources: Microsoft 365 Status on X (Nov 12, 17:54–21:00 UTC); Microsoft service health EX1550543 (Nov 12, 23:59 UTC; Nov 13, 08:06 UTC) and status.cloud.microsoft MO1550821 (Nov 13, 07:29 UTC); Anthropic and OpenAI status pages; Workhorse Group press release, Nov 12, 2026. Server pool is a schematic, not real server counts.
Graphic: Powered by Thorsten Meyer AI
Disruptions Beyond Outlook
The outage matters because Exchange Online supports more than email. According to the supplied incident reporting, problems have also affected Teams calendars and meeting scheduling, parts of SharePoint Online, Microsoft 365 Copilot, the Microsoft Defender XDR portal, Purview and Planner. Users and organizations relying on those services may face interruptions to communication, scheduling and other work, though the extent can vary by service and region.
The effects have also reached third-party services and business plans. OpenAI and Anthropic reported errors with their Microsoft 365 connectors, according to the source material. Workhorse Group moved its third-quarter earnings call from Nov. 12 to Nov. 16 because of the outage. These examples show how a disruption to a cloud platform can affect tools and activities that depend on its services, not just Microsoft’s own mail interface.
Reports from outage trackers offer a measure of public complaints, not a count of affected customers. Reuters, in a report published by The Korea Times, said Downdetector recorded more than 130,000 U.S. Outlook problem reports at the peak around 1 p.m. ET Thursday. Business Standard, citing Downdetector, reported complaints from 74 countries. Those figures should not be read as verified counts of people who lost access.
Products Worth Considering

LG 27GS60QC-B Ultragear 27-inch Curved Gaming Monitor (QHD, 180Hz, 1ms, 1000R)

Jackery Explorer 300 Portable Power Station, 292Wh

Samsung 27-Inch Odyssey OLED G5 QHD Gaming Monitor (G50SF)
As an affiliate, we earn on qualifying purchases.
How the Incident Developed
Microsoft’s first explanation on Thursday pointed to elevated infrastructure load. By 19:31 UTC, it said the load was not driven by a rise in traffic but by unavailable servers placing strain on the remaining infrastructure. At 20:19 UTC, the company said its investigation pointed to a component involved in processing server health checks, while noting it had not identified a recent change correlated with the incident’s start.
Later updates described limited progress and setbacks. Microsoft said an alternative health-check method allowed some affected servers to return to service, but at 22:09 UTC it said actions had not provided the expected relief and that a core process was becoming overwhelmed. At 23:59 UTC, it warned that servers could become unresponsive again after receiving traffic. At 01:06 UTC Friday, Microsoft said a process for establishing secure connections was overwhelming and that it had begun reverting a recent network configuration change it said correlated with the start of the impact.
Microsoft reported at 07:29 UTC Friday that a patch to an upstream authentication and routing configuration component had produced positive server-stability results on part of its infrastructure. A separate Teams incident, TM1550488, was marked fully resolved at 17:09 UTC Thursday, according to Microsoft. BleepingComputer reported that Microsoft had not said whether that incident was related to the ongoing Exchange Online problem.
“Servers are stable where the patch was applied.”
— Microsoft, in its 08:06 UTC service-health update for EX1550543
Root Cause Still Undetermined
Microsoft has not named the root cause of the outage. Its updates have described unavailable servers, failed health checks, an overwhelmed process, and a network configuration change that correlated with the start of the incident. Those details outline what engineers observed and tried, but do not establish why the failure began.
The company said it was not aware of malicious activity. That is a statement about its investigation at the time, not a published final finding. It has promised a Post-Incident Report after mitigation. The source material also does not establish how many users or organizations are affected, when service will return fully, or whether every connected Microsoft 365 product is experiencing the same level of impact.
Downdetector figures cited in news reports count user-submitted problem reports rather than confirmed affected people. The reports indicate the scale and spread of complaints, but cannot establish the number of customers without service.
Patch Rollout and Service Checks
Microsoft’s immediate next step is to continue expanding the patch region by region, prioritizing locations in or approaching peak business hours, while monitoring server stability. Its latest update in the source material does not give a completion time or a schedule for restoring all affected services.
Users and organizations should refer to Microsoft’s service-health notices for the status of specific services and regions. The next key developments are whether patched servers remain responsive under traffic, whether the rollout reaches the remaining infrastructure, and when Microsoft can confirm mitigation. A fuller explanation is expected in the company’s promised Post-Incident Report.
Key Questions
Is the Microsoft 365 outage over?
No. As of 08:35 UTC on Nov. 13, Microsoft’s status page still listed a service degradation. The company reported stability on servers where it had applied a patch, while expanding that patch to other regions.
Which services are affected?
The main incident concerns Exchange Online, including access to Outlook mailboxes through web, desktop, mobile and REST connections. Reports also describe effects on Teams calendars and scheduling, parts of SharePoint Online, Copilot, Defender XDR, Purview and Planner. The impact may differ across services and regions.
What caused the outage?
Microsoft has not stated a root cause. Its updates describe servers becoming unavailable, health-check failures and an overwhelmed process involved in secure connections. The company also said a network configuration change correlated with the start of the impact, but has not presented that as a final explanation.
Was the outage caused by a cyberattack?
Microsoft said it had no indication of malicious activity in a Friday update. A final incident report has not yet been issued, so that statement reflects the company’s assessment at that point in the investigation.
When will Microsoft 365 be fully restored?
Microsoft had not provided a restoration deadline in the supplied updates. It said it was expanding the patch region by region and monitoring stability; users should check Microsoft’s service-health notices for newer status information.
Source: ThorstenMeyerAI.com
