🔍 Read the full analysis: Microsoft 365 Outage: From What Broke To What To Do Now on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Microsoft 365 was still experiencing service degradation at 08:35 UTC on Nov. 13, after Exchange Online problems began the previous day. Microsoft reported improved stability on servers that received a patch and said it was expanding deployment region by region; the root cause remains unknown.
Microsoft’s Microsoft 365 outage was still ongoing at 08:35 UTC on Friday, November 13, after problems accessing Exchange Online mailboxes began the previous day. Microsoft said a patch had improved server stability on part of its infrastructure and that it was expanding the patch region by region; it had not identified or named the root cause.
The incident, tracked as EX1550543, affects access to Exchange Online through Outlook on the web, desktop and mobile apps, as well as REST connections, according to the incident information summarized by ThorstenMeyerAI.com. Services that depend on Exchange Online have also experienced disruption, including Teams calendars and meeting scheduling. The report also lists parts of SharePoint Online, Microsoft 365 Copilot, the Microsoft Defender XDR portal, Purview and Planner among affected services. The impact may vary by service and region; the available updates do not establish that every user or feature is unavailable.
Microsoft’s public updates describe a changing diagnosis. It first cited elevated load across multiple regions, then said the load was not caused by increased traffic but by servers becoming unexpectedly unavailable. The company paused deployments, shifted traffic, restarted servers and changed its server health-check method. It later reported that a core process on affected servers was becoming overwhelmed, and said servers returned to service could become unresponsive again after receiving traffic.
At 07:29 UTC Friday, Microsoft reported positive server-stability results after applying a patch to part of its infrastructure. In its 08:06 UTC update to the Exchange Online record, it said it was beginning a systematic expansion, starting with regions in or approaching peak business hours. The status page still listed the service as degraded at 08:35 UTC, so the patch had not yet meant a full resolution.
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
How Mail Disruption Spreads
The incident reaches beyond inbox access because Exchange Online supports connected Microsoft 365 functions. When mailboxes or related connections fail, users may also have trouble with calendars, meeting scheduling and tools that rely on Microsoft 365 data. That can interrupt coordination and routine work even if an individual application appears to be running.
The outage has also had reported effects outside Microsoft’s own services. ThorstenMeyerAI.com says OpenAI and Anthropic reported errors in their Microsoft 365 connectors. Workhorse Group moved its third-quarter earnings call from November 12 to November 16 because of the outage, according to the report. These examples show possible knock-on effects, but do not establish the full number of organizations or users affected.
For readers, the immediate distinction is between partial recovery and resolution. Microsoft’s update indicates that some patched servers were more stable, while the overall status remained degraded. Organizations that rely on Exchange Online should treat access and dependent features as potentially impaired until Microsoft reports recovery for their services and regions.
Products Worth Considering
Bose TV Speaker (2nd Gen) Compact Soundbar
Samsung 32-Inch Odyssey G5 QHD 180Hz Gaming Monitor
Samsung Odyssey G3 G30D 27-Inch FHD Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Regional Errors to Server Instability
The first public Microsoft 365 Status post about EX1550543 appeared at 17:54 UTC on November 12, describing reports of Exchange Online mailbox access problems through multiple connection methods in the Americas. A service-health post cited by ThorstenMeyerAI.com gives the incident start as 16:17 UTC. At 18:07 UTC, Microsoft said connectivity issues could affect users in any region.
Microsoft’s updates over the evening shifted from elevated load to server availability and health checks. It said it had not identified a recent change correlated with the start of the impact, then later reported that a process responsible for establishing secure connections was becoming overwhelmed. At 01:06 UTC Friday, Microsoft said it had begun reverting a recent network configuration change that correlated with the outage; subsequent updates said a change was not taking as expected. These statements describe investigation steps, not a confirmed root cause.
Reports cited by ThorstenMeyerAI.com indicate the disruption continued across the Asian business day and into early European hours. Downdetector figures cited in media reports included more than 130,000 U.S. Outlook problem reports at a Thursday peak and reports from 74 countries. Downdetector counts submissions, not verified affected users, so those figures measure reported complaints rather than the number of people unable to work. A separate Teams issue, TM1550488, was marked resolved at 17:09 UTC Thursday; Microsoft has not said whether it was connected to EX1550543.
“The elevated load isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable.”
— Microsoft, in its November 12 update
Root Cause and Full Recovery
The root cause remains unconfirmed. Microsoft’s updates describe unavailable servers, overwhelmed processes, health-check problems and a network configuration change being reverted, but the company has not said which issue triggered the outage or how those findings relate. It also has not published a complete account of why servers became unstable again after returning to service.
Microsoft said it was not aware of malicious activity; that is the company’s assessment, not a detailed public post-incident finding. The scope of remaining impact by region, product and customer is also not clear from the available updates. Nor has Microsoft provided a confirmed time for full restoration. Reports of high Downdetector volume should not be read as a verified count of affected users.
Microsoft’s Regional Patch Rollout
Microsoft said it would continue expanding the patch region by region, prioritizing regions that were in or entering peak business hours, and monitor server stability as patched capacity receives traffic. The next practical milestone is an update showing whether the rollout has restored access across affected regions and whether Microsoft 365’s service status changes from degradation to resolved.
Microsoft has also promised a Post-Incident Report after the problem is mitigated. That report is expected to provide more detail on the cause and response, but no publication time was given in the source material. Until Microsoft posts further status information, users and administrators should check the Microsoft 365 service-health page for current effects on their specific services; the available information does not establish a universal workaround.
Key Questions
Is the Microsoft 365 outage over?
No. As of 08:35 UTC on November 13, Microsoft’s status page still listed service degradation. The company reported improved stability on some patched servers, but had not declared the incident resolved.
Which Microsoft 365 services are affected?
The reported issue centers on Exchange Online mailbox access through Outlook on the web, desktop, mobile and REST connections. The source also lists dependent features and services, including Teams calendars and meeting scheduling, parts of SharePoint Online, Copilot, the Defender XDR portal, Purview and Planner; the effects may differ by service and region.
What caused the outage?
Microsoft has not confirmed a root cause. Its updates describe unexpectedly unavailable servers and an overwhelmed process, and mention a network configuration change being reverted. The relationship among those findings is not yet clear.
What should users do while services are degraded?
Check the Microsoft 365 service-health page for the latest status affecting your organization and services. Microsoft’s published updates describe a regional patch rollout, but the source material does not confirm a universal workaround or give a restoration time.
Was the outage caused by malicious activity?
Microsoft said it was not aware of malicious activity. That is the company’s current assessment; the root cause remains under investigation, and Microsoft said it would issue a post-incident report after mitigation.
Source: ThorstenMeyerAI.com
