🔍 Read the full analysis: How Microsoft 365 Users Can Adapt To The Ongoing Outage on ThorstenMeyerAI.com
TL;DR
Microsoft 365 remained in service degradation as of 08:35 UTC on Nov. 13, after an Exchange Online disruption began the previous 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; users should not assume access has been restored. The company has not identified a root cause.
Microsoft 365 remained disrupted as of 08:35 UTC on Friday, Nov. 13, with Microsoft still listing service degradation after Exchange Online problems began the previous day. In an update at 08:06 UTC, Microsoft said servers were stable where it had applied a patch and that it was expanding the fix region by region; the company has not named the outage’s root cause.
The incident, tracked as EX1550543, is affecting access to Exchange Online mailboxes through Outlook on the web, desktop and mobile apps, as well as REST connections, according to the source report and Microsoft’s service updates. Services that depend on Exchange Online have also been affected, including Teams calendars and meeting scheduling, some SharePoint Online functions, Microsoft 365 Copilot, the Microsoft Defender XDR portal, Purview and Planner. The extent of impact can vary by service and user.
Microsoft’s updates described servers becoming unavailable and remaining infrastructure carrying the resulting load. The company said restarts and other early steps did not provide the expected relief: servers that returned to service could become unresponsive again when they received traffic. At 07:29 UTC on Friday, Microsoft reported positive server-stability results after applying an upstream authentication and routing configuration patch to part of its infrastructure. The 08:06 UTC update said the patch was being expanded systematically, beginning with regions in or entering peak business hours.
Users who still have access to a service should save important work and use available alternatives for urgent communication, while checking Microsoft’s service-health updates before treating the incident as resolved. Organizations can follow their existing continuity procedures, such as contacting colleagues through an approved backup channel or using already-authorized copies of critical schedules and documents. These are practical precautions, not confirmation that any particular workaround will function; Microsoft has not announced a universal workaround or restoration time.
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
Disruption Beyond Outlook Email
The impact reaches beyond inbox access because several workplace tools rely on Exchange Online for connected functions. A mailbox outage can interfere with calendar visibility, meeting coordination and workflows that draw on Microsoft 365 data, even if some applications remain reachable. That makes the incident a practical concern for organizations coordinating work across regions and time zones.
The disruption has also had effects outside Microsoft’s own services. The source report says OpenAI and Anthropic reported errors in their Microsoft 365 connectors. It also reports that Workhorse Group moved its third-quarter earnings call from Nov. 12 to Nov. 16 because of the outage. These examples show possible knock-on effects, but they do not establish how many organizations or users have been affected overall.
Reported outage figures should be read carefully. Reuters, as published by The Korea Times, reported more than 130,000 Downdetector reports about Outlook problems in the United States at the peak, around 1 p.m. ET Thursday. Business Standard reported users in 74 countries citing Downdetector. Those are reports of problems, not verified counts of people unable to work, and the underlying comparison basis is not a measure of total affected users.
Popular right now

Dyson Airwrap i.d. Multi-Styler with Bluetooth Connectivity

Vitamix Nano Personal Blender with SmoothiePilot Technology, Black

KitchenAid Classic Series 4.5-Quart Tilt-Head Stand Mixer, Onyx Black
As an affiliate, we earn on qualifying purchases.
How the Exchange Incident Developed
Microsoft’s first public notice appeared at 17:54 UTC on Nov. 12, saying it was investigating reports of users unable to access Exchange Online mailboxes through multiple connection methods in the Americas. A service-health copy cited by the source report gives the incident start as 16:17 UTC. At 18:07 UTC, Microsoft said the issue could affect Microsoft 365 connectivity in any region.
Microsoft’s explanations evolved as it investigated. It first described elevated load across multiple regions, then said the load was not caused by increased traffic but by servers unexpectedly becoming unavailable. The company paused deployments, redistributed traffic and restarted servers. It later said a core process was becoming overwhelmed and that a process involved in establishing secure connections was causing servers to stop processing requests.
Microsoft also said it had begun reverting a recent network configuration change that correlated with the start of the impact, but it has not said that change was the cause. A separate Teams incident, TM1550488, was declared resolved at 17:09 UTC Thursday. The source report says Microsoft has not stated whether that incident is related to EX1550543.
„Servers are stable where the patch was applied.“
— Microsoft, service-health update at 08:06 UTC on Nov. 13
Root Cause and Recovery Remain Open
Microsoft has not identified or disclosed a root cause, and the reported link between a recent network configuration change and the incident remains a correlation, not a confirmed explanation. The company said it was not aware of malicious activity. It has promised a Post-Incident Report after the problem is mitigated, but that report was not yet available as of 08:35 UTC.
It is also unclear how quickly the patch will reach all affected regions, when every impacted service will return to normal, or whether users will see intermittent failures during recovery. Microsoft’s status page still listed service degradation at the stated check time. There is no confirmed restoration estimate in the source material.
Reports from Downdetector and examples of affected organizations indicate the breadth of complaints, but they do not establish the precise number of people or businesses affected. The status and function of individual Microsoft 365 features may differ, so users should check their organization’s Microsoft service-health information rather than infer that all services are either down or recovered.
Watch for Regional Recovery Updates
Microsoft said it was expanding the patch systematically, prioritizing regions in or entering peak business hours. Users and administrators should monitor the Microsoft 365 status page and their tenant’s service-health notices for changes to incident EX1550543, including confirmation that the patch has reached their region and that affected services are recovering.
Until Microsoft reports mitigation, organizations can keep essential communication on approved backup channels, avoid relying on an Outlook or calendar view that may be stale, and follow internal procedures for urgent meetings and work. They should verify that a message, invitation or update has actually been sent or received rather than assuming a retry succeeded. These steps may reduce disruption, but they cannot restore Microsoft-hosted services.
Microsoft has said it will publish a Post-Incident Report after mitigation. That report should provide further information about the cause and response, though no publication time was given. For now, the confirmed development is limited: Microsoft reports stability where the patch is applied and is extending it, while the service remains listed as degraded.
Key Questions
Is the Microsoft 365 outage over?
No. As of 08:35 UTC on Nov. 13, Microsoft still listed service degradation. It had reported stable servers in patched areas and was expanding the patch, but had not announced full recovery.
Which services are affected?
The reported issue centers on Exchange Online mailbox access through Outlook and REST connections. The source report also describes effects on connected functions such as Teams calendars and meeting scheduling, parts of SharePoint Online, Copilot, Defender XDR, Purview and Planner. Impact may differ across users and services.
What can users do while service is disrupted?
Check Microsoft’s service-health notices, use organization-approved backup communication channels for urgent matters, and follow internal continuity procedures. Save important work where possible and verify that messages or meeting changes have gone through; no universal workaround has been confirmed.
What caused the outage?
Microsoft has not disclosed a confirmed root cause. It described unexpected server unavailability and an overwhelmed process affecting secure connections, and said a recent network configuration change correlated with the start of the incident. Correlation does not establish that the change caused the outage.
When will Microsoft 365 be fully restored?
Microsoft had not provided a confirmed restoration time in the available updates. It said it was expanding the patch region by region and plans to publish a Post-Incident Report after mitigation.
Source: ThorstenMeyerAI.com