What To Know About The Microsoft 365 Outage As Day Two Begins
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: What To Know About The Microsoft 365 Outage As Day Two Begins on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

Microsoft 365 remained in a service-degradation state at 08:35 UTC on Nov. 13, after an Exchange Online outage disrupted email and connected services since the prior day. Microsoft reported improved server stability after applying a patch to part of its infrastructure and said it was expanding the patch region by region; the root cause remains unknown.

Microsoft 365’s outage was still ongoing at 08:35 UTC Friday, as Microsoft expanded a patch intended to stabilize Exchange Online servers after email and connected services were disrupted across regions beginning Thursday. Microsoft’s status page continued to list a service degradation; the company said the patch had produced positive stability results on part of its infrastructure, but it has not identified the root cause.

In an update at 08:06 UTC on Nov. 13, recorded under Exchange Online incident EX1550543, Microsoft said servers were stable where the patch had been applied and that it was expanding deployment systematically, region by region. The company said it was starting with regions in, or entering, peak business hours. An earlier status update at 07:29 UTC said it was seeing positive server-stability results after applying an upstream authentication and routing configuration component patch to part of its infrastructure.

The disruption began Thursday, Nov. 12. Microsoft’s public status account first reported at 17:54 UTC that it was investigating reports of users unable to access Exchange Online mailboxes through multiple connection methods in the Americas. Microsoft later said the issue might affect Microsoft 365 connectivity in any region. The service health record, as reproduced by Cloud Admin Hub, lists the incident start as 16:17 UTC.

Microsoft has described several steps in its response: redistributing traffic, pausing deployments, restarting affected servers, and changing how server health is checked. It initially cited elevated load across multiple regions, then clarified that the load was not caused by increased traffic but by servers becoming unexpectedly unavailable. The company later said a core process on affected servers was becoming overwhelmed. Overnight, it reported that servers returning to service could become unresponsive again once they received traffic.

At a glance
updateWhen: Ongoing; status reported at 08:35 UTC o…
The developmentMicrosoft is expanding an infrastructure patch after reporting improved server stability, but its Microsoft 365 outage was still active Friday morning.

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

  1. 17:54Nov 12Mailbox access fails in the Americas
  2. 18:07“May affect” users “in any region”
  3. 18:35“Elevated load across multiple regions”
  4. 19:12All deployments paused, traffic moved, servers restarted
  5. 19:31Not more traffic: servers “unexpectedly unavailable”, the rest carry the load
  6. 21:00New health-check method: some servers back in service
  7. 23:59Returned servers “can become unresponsive again”
  8. 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

Cause: not named yet. Microsoft says it is “not aware of any malicious activity” and promises a Post-Incident Report.

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

Email Failures Spread Across Workflows

The disruption reaches beyond inbox access because Exchange Online supports multiple Microsoft 365 features. The source report says users have faced problems with Outlook on the web, desktop and mobile, as well as REST connections. Related impacts have included Teams calendars and meeting scheduling, parts of SharePoint Online, Microsoft 365 Copilot, the Microsoft Defender XDR portal, Purview and Planner.

That breadth can affect routine business operations, from arranging meetings to accessing shared files and security tools. The reported effects also reached services that connect to Microsoft 365: 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 operational consequences, though they do not establish how many organizations or users were affected.

The scale of public complaints should be read carefully. Reuters, in a report published by The Korea Times, cited more than 130,000 U.S. Downdetector reports of Outlook problems near the reported peak around 1 p.m. Eastern on Thursday. Business Standard, citing Downdetector, reported complaints from 74 countries. Downdetector counts user reports, not verified affected people, so those figures indicate reported problems rather than a confirmed total of people without service.

Ninja Foodi 7-Qt MegaZone FlexBasket Air Fryer, 6-in-1, Black, DZ071

Ninja Foodi 7-Qt MegaZone FlexBasket Air Fryer, 6-in-1, Black, DZ071

As an affiliate, we earn on qualifying purchases.

How the Outage Developed Overnight

Microsoft’s updates show a changing account of the technical problem, rather than a confirmed root cause. On Thursday evening, it said infrastructure was experiencing elevated load and that it was shifting connection traffic. It then said unexpectedly unavailable servers were straining the remaining infrastructure, and that failed automated health checks might be involved. Microsoft tested an alternative health-check method that returned some servers to service, but later said those actions had not provided the expected relief.

At 01:06 UTC Friday, Microsoft said a process responsible for establishing secure connections was becoming overwhelmed and 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 impact. At 02:54 UTC, it reported that a change it had applied was not taking as expected. The later patch updates mark a shift toward stabilizing affected infrastructure, but do not establish why the outage began.

A separate Teams incident, tracked as TM1550488, was declared fully resolved at 17:09 UTC Thursday. BleepingComputer noted that Microsoft had not said whether that incident was connected to the Exchange Online outage. The two should not be treated as the same event without further confirmation.

“Servers are stable where a patch was applied, and Microsoft is expanding the patch region by region.”

— Microsoft, in its 08:06 UTC service-health update for EX1550543

Root Cause and Recovery Remain Unknown

Microsoft has not named a root cause, and its updates have not established whether the recent network configuration change caused the outage. The company said the change correlated with the start of the impact, but correlation alone does not confirm causation. It also said it was not aware of malicious activity; that is the company’s current assessment, not a published account of a completed investigation.

The status page still listed service degradation at 08:35 UTC, and Microsoft had not said that all affected regions or features were working normally. It is also unclear how quickly the patch will reach each region, whether servers will remain stable after returning to traffic, and how many users or organizations have been affected. Microsoft said it would publish a Post-Incident Report once the problem is mitigated.

Regional Patch Rollout Continues

Microsoft said it would continue expanding the patch systematically, prioritizing regions that are in or entering peak business hours. Users and organizations should treat the service as still degraded until Microsoft updates its status; the reported stability in patched areas is not confirmation of a full recovery. Further updates to incident EX1550543 should clarify whether stability holds as more servers receive traffic and the deployment reaches additional regions.

After mitigation, Microsoft has promised a Post-Incident Report. That report is expected to provide more detail on the cause, the sequence of failures and the measures taken, though its release timing has not been specified in the available updates.

Key Questions

Is the Microsoft 365 outage over?

No. At 08:35 UTC on Nov. 13, Microsoft’s status page still listed service degradation. The company reported stability where its patch had been applied and was expanding it region by region.

Which Microsoft 365 services have been affected?

The central issue is access to Exchange Online mailboxes through Outlook on the web, desktop and mobile, and REST connections. Reported knock-on effects include Teams calendars and scheduling, parts of SharePoint Online, Copilot, Defender XDR, Purview and Planner.

What caused the outage?

Microsoft has not confirmed the root cause. It has described unexpectedly unavailable servers, an overwhelmed process involved in secure connections, and a network configuration change that correlated with the start of the impact. Those details do not yet establish a definitive cause.

Was the outage caused by a cyberattack?

Microsoft said it had no indication of malicious activity as of its 04:10 UTC update. The company has not published its final incident findings.

When will Microsoft publish a full explanation?

Microsoft said it would issue a Post-Incident Report after the problem is mitigated. It has not specified when that report will be published.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

The Bottleneck Moved: Inside Anthropic’s Expansion of Project Glasswing

Anthropic extends Project Glasswing to over 150 organizations, shifting focus from finding to fixing security vulnerabilities in critical software systems.

Every Benchmark Launched 2023-2024 Has Fallen — The METR / SWE-Bench / CORE-Bench / MLE-Bench / PostTrainBench Sequence

Every major AI research benchmark launched in 2023-2024 has been saturated or is nearing saturation, signaling rapid progress in AI capabilities.

Signal: The Agent Bottleneck Moved — It’s Not the Models Anymore, It’s the Plumbing

New insights reveal the bottleneck in enterprise AI agents has shifted from models to integration and plumbing, favoring small operators owning entire stacks.

Telecom Operators Gain Faster Access To The Smart Home Security Market Through Egardia’s New Wholesale Platform

Telecom operators now access the smart home security market more quickly through Egardia’s new wholesale platform, enhancing their service offerings.