🔍 Read the full analysis: Microsoft 365 Outage: A Timeline Of Updates And Practical Advice 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, after an Exchange Online outage began the previous day. Microsoft reported improved stability on patched servers and is expanding the patch region by region, but has not disclosed the root cause or said when service will be restored.
Microsoft said it is expanding a patch region by region after a Microsoft 365 outage disrupted Exchange Online and related services, but its status page still listed service degradation at 08:35 UTC on November 13. In its latest update, at 08:06 UTC, Microsoft reported stable servers where the patch had been applied; it has not identified the root cause or provided a restoration time.
The incident, tracked as EX1550543, began at 16:17 UTC on Thursday, November 12, according to a copy of Microsoft’s service-health post carried by Cloud Admin Hub. Microsoft first publicly reported it at 17:54 UTC, saying users in the Americas were having trouble accessing Exchange Online mailboxes through multiple connection methods. At 18:07 UTC, it warned the issue could affect Microsoft 365 connectivity in any region.
The main reported impact was difficulty reaching Exchange Online mail through Outlook on the web, desktop and mobile apps, as well as through REST connections. Services dependent on Exchange Online were also affected, including Teams calendars and meeting scheduling, and parts of SharePoint Online, Microsoft 365 Copilot, the Microsoft Defender XDR portal, Purview and Planner. OpenAI and Anthropic separately reported errors with their Microsoft 365 connectors, according to the source report.
Microsoft’s explanation evolved during its response. It first described 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 checks. Later, it said a core process on affected servers was becoming overwhelmed and that returned servers could become unresponsive again after receiving traffic.
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
Outage Reaches Beyond Email
The disruption affected more than inbox access because several workplace tools rely on Exchange Online for functions such as calendars, scheduling and connected services. For organizations using Microsoft 365 across communications and daily operations, unreliable mail and meeting tools can interrupt coordination even when other parts of the suite remain available.
The effects also extended to outside organizations. Workhorse Group moved its third-quarter earnings call from November 12 to November 16 because of the outage, according to the source report. That example shows how a cloud service incident can affect scheduled business activity beyond Microsoft’s own applications. However, the available material does not establish the total number of affected customers or the full extent of disruption.
Reports on Downdetector offer an indication of user complaints, not a count of people who lost service. Reuters, in a report published by The Korea Times, said the site recorded more than 130,000 U.S. Outlook problem reports near 1 p.m. ET Thursday. Business Standard, citing Downdetector, reported complaints from 74 countries. Those figures should not be read as verified totals of affected users.
Products Worth Considering
Amazon Kindle Paperwhite (12th Generation, 2024), 16GB, 7-Inch Display, Raspberry
Samsung Odyssey G3 G30D 27-Inch FHD Gaming Monitor
LG UltraGear 32-Inch QHD 180Hz Curved Gaming Monitor
As an affiliate, we earn on qualifying purchases.
How Microsoft Traced the Failure
Microsoft’s updates describe a sequence of troubleshooting steps rather than a confirmed diagnosis. On Thursday evening, the company said it was redistributing traffic and restarting affected servers. It later reported that a specific component responsible for processing server health might be involved in failed automated checks. A revised health-check method allowed some servers to return to service, but Microsoft said the steps had not delivered the expected relief.
At 01:06 UTC Friday, Microsoft said a process responsible for establishing secure connections was becoming overwhelmed, causing servers to stop processing requests. It also said it had begun reverting a recent network configuration change that correlated with the start of the incident. At 02:54 UTC, the company reported that a change it had applied was not working as expected. At 07:29 UTC, it reported positive server-stability results after patching an upstream authentication and routing configuration component on part of its infrastructure.
A separate Teams incident, tracked as TM1550488, was declared fully resolved by Microsoft at 17:09 UTC Thursday. BleepingComputer reported that Microsoft had not said whether that incident was related to EX1550543. The source report also cites CNBC’s account that email and other tools were unavailable through much of the Asian business day and into the early European hours.
“The elevated load isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable.”
— Microsoft, in its 19:31 UTC update on November 12
Root Cause and Recovery Remain Unknown
Microsoft has not named a root cause, and it has not said how long the regional patch rollout will take or when all affected services will return to normal. The company described a connection between a recent network configuration change and the incident’s start, but that does not establish that the change caused the outage. It also said a change it tried was not taking as expected.
Microsoft said at 04:10 UTC Friday that there was no indication of malicious activity. That is the company’s assessment, not a public disclosure of a completed investigation. The available updates also do not give a verified count of affected users, the complete list of impacted service functions, or confirmation that the separate Teams incident was related. Microsoft said it would publish a Post-Incident Report after mitigation.
Watch for Regional Recovery Updates
Microsoft’s next stated step is to continue expanding the patch region by region, prioritizing areas in or entering peak business hours. Customers should check Microsoft’s service-health page and the EX1550543 record for current status rather than assume that stable patched servers mean the whole service has recovered.
For people still affected, practical steps include trying another available connection method or device, checking whether colleagues in a different region report the same issue, and using an approved alternative communication channel for urgent work. Repeatedly restarting devices or changing account settings is unlikely to resolve a server-side outage. Organizations should follow their own continuity procedures and avoid treating user-report totals as an official measure of impact.
Microsoft has not announced a restoration deadline. The next significant indicators are whether the patch continues to stabilize additional regions, whether Microsoft changes the incident status, and what the promised Post-Incident Report says about the cause and corrective measures.
Key Questions
Is the Microsoft 365 outage over?
No. Microsoft’s status page still listed service degradation at 08:35 UTC on November 13. The company reported stability on patched servers but was still expanding the patch.
Which services were affected?
The main disruption involved Exchange Online mailbox access through Outlook and REST connections. Microsoft also identified potential effects on connected services and functions, including Teams calendars and scheduling, parts of SharePoint Online, Copilot, Defender XDR, Purview and Planner.
What caused the outage?
Microsoft has not confirmed a root cause. Its updates described unavailable servers, an overwhelmed process involved in secure connections, and a recent network configuration change that correlated with the incident’s start.
What can users do while service is degraded?
Check Microsoft’s service-health updates, use an approved alternative channel for time-sensitive work and follow your organization’s continuity procedures. The company has not provided a restoration deadline, and local device changes may not resolve a server-side disruption.
Source: ThorstenMeyerAI.com
