AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

Microsoft 365 remained degraded as of 08:35 UTC on Nov. 13, after an Exchange Online outage began the previous day. Microsoft said a patch had stabilized some servers and was being expanded region by region, but it had not identified the root cause or said when service would be restored.

Microsoft said it was expanding a patch region by region on Friday morning after an Exchange Online outage disrupted mailbox access and related Microsoft 365 services since Thursday, Nov. 12. As of 08:35 UTC on Nov. 13, Microsoft’s status page still listed the incident as “Service degradation,” with no root cause announced.

The incident, tracked as EX1550543, began at 16:17 UTC Thursday, according to a copy of Microsoft’s service health notice cited by Cloud Admin Hub. Microsoft’s first public status post, at 17:54 UTC, said it was investigating reports of users unable to access Exchange Online mailboxes through multiple connection methods in the Americas. At 18:07 UTC, it said the issue might affect Microsoft 365 connectivity in any region.

Buying for a business?Offer from Amazon

Get business pricing on tech for your team

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

Microsoft initially described elevated load across multiple regions. It later said the load was not caused by increased traffic but by servers becoming unexpectedly unavailable, according to its status updates. The company paused deployments, shifted traffic, restarted servers and changed how it checked server health. It subsequently said a core process on affected servers was becoming overwhelmed, and warned that servers brought back online could become unresponsive again once they received 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 for EX1550543, it said servers were stable where the patch had been applied and that it had begun expanding it systematically, starting with regions in or entering peak business hours. Microsoft had not said the outage was over by 08:35 UTC.

At a glance
updateWhen: Ongoing as of 08:35 UTC, November 13, 2…
The developmentMicrosoft is expanding a patch for an ongoing Exchange Online outage that has disrupted access to Microsoft 365 services since Nov. 12.
Card graphic: what fails and what still works in the Microsoft 365 outage. Highlighted: the common thread is anything that needs Exchange Online; features that do not depend on it remain functional, Microsoft says. Affected: mail in Outlook on the web, desktop, mobile and REST, with delivery possibly delayed; Teams calendar, invites, meeting edits and new Live or Virtual events; Copilot Chat may not load or reach mail, calendar and files; Defender XDR portal pages, Safe Links, quarantine releases and Purview; also Graph mail and calendar calls, Planner, To Do, Intune and some admin pages. Largely working: Teams calls, meetings, group chats and channel messages; opening files stored directly in SharePoint Online
What the outage hits, according to Microsoft. Source: Microsoft, status.cloud.microsoft, post MO1550821, update of 07:29 UTC, November 13, 2026 (selection). Graphic: Thorsten Meyer AI.

How the Disruption Reaches Beyond Email

The outage affects more than people opening mail. Microsoft’s service notices describe problems with Outlook on the web, desktop and mobile, as well as REST connections to Exchange Online. Services that depend on Exchange Online can also be affected, including Teams calendars and meeting scheduling, parts of SharePoint Online, Microsoft 365 Copilot, the Microsoft Defender XDR portal, Purview and Planner.

That reach can interrupt scheduling, collaboration and security workflows across organizations. OpenAI and Anthropic also reported errors with their Microsoft 365 connectors, according to their status pages. Workhorse Group said it moved its third-quarter earnings call from Nov. 12 to Nov. 16 because of the outage, illustrating how disruptions to workplace services can affect scheduled business activity.

Reports from Downdetector offer a rough indication of user complaints, not a count of people affected. Reuters, in a report published by The Korea Times, said the site recorded more than 130,000 U.S. Outlook problem reports at the peak around 1 p.m. ET Thursday. Business Standard reported complaints in 74 countries, citing Downdetector. Those figures do not establish how many users lost access or how long each person was affected.

Products Worth Considering

Jackery Explorer 1500 v2 Portable Power Station with 200W Solar Panel

Jackery Explorer 1500 v2 Portable Power Station with 200W Solar Panel

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

As an affiliate, we earn on qualifying purchases.

From Regional Reports to a Global Patch

Microsoft’s first public post on Thursday identified reports in the Americas. Within 13 minutes, its status account said connectivity problems might affect users in any region. The incident continued overnight: CNBC reported that email and other tools were unavailable through much of the Asian business day and into the early European hours.

A separate Teams incident, tracked as TM1550488, was declared fully resolved at 17:09 UTC Thursday, according to Microsoft. BleepingComputer reported that Microsoft had not said whether that incident was related to EX1550543. The available updates do not establish a connection between them.

Microsoft’s response evolved from traffic redistribution and server restarts to a patch after restarts proved temporary. The latest available status update described a staged regional expansion, while the overall Microsoft 365 status remained degraded at 08:35 UTC Friday.

““We’ve determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors.””

— Microsoft 365 Status account, Nov. 12, 18:35 UTC

Root Cause and Restoration Time Remain Unknown

Microsoft had not identified the root cause as of its 08:06 UTC update, and the available status information did not give a restoration estimate. The patch had produced stable results on some servers, but Microsoft was still expanding it across regions. It remained unclear how quickly that rollout would reach all affected infrastructure or whether the stability would hold as more traffic returned.

The relationship, if any, between the resolved Teams incident and EX1550543 had not been stated. Downdetector reports also cannot confirm the total number of affected users. Microsoft said it would publish a Post-Incident Report after mitigation; that report had not yet been released.

Watch for Regional Recovery Updates

Microsoft’s next stated step was to continue expanding the patch region by region, prioritizing areas at or approaching peak business hours. Users and administrators can follow the Microsoft 365 service health page for changes to EX1550543 and check whether specific services have returned to normal.

Microsoft has said it will publish a Post-Incident Report once the problem is mitigated. That report may provide a fuller account of the cause and response. Until Microsoft marks the incident resolved and services recover, the status remains ongoing; no completion time had been announced as of 08:35 UTC Friday.

Key Questions

Is the Microsoft 365 outage over?

No. As of 08:35 UTC on Nov. 13, Microsoft’s status page still listed service degradation. Its 08:06 UTC update said the patch was stable where applied and was being expanded region by region.

Which services are affected?

The reported disruption centers on Exchange Online mailbox access through Outlook on the web, desktop, mobile and REST connections. Dependent services can also be affected, including Teams calendars and meeting scheduling, parts of SharePoint Online, Copilot, Defender XDR, Purview and Planner.

What caused the outage?

Microsoft had not named a root cause. It said servers became unexpectedly unavailable and that a core process on affected servers was becoming overwhelmed. The company also said it was not aware of malicious activity.

When will service be restored?

Microsoft had not provided a restoration time as of 08:35 UTC Friday. It was expanding the patch across regions and said it would publish a Post-Incident Report after mitigation.

How large was the outage?

Downdetector recorded more than 130,000 U.S. Outlook problem reports at the peak cited by Reuters, and Business Standard reported complaints in 74 countries. These are user reports, not verified counts of affected people.

Source: Thorsten Meyer AI

You May Also Like

Creative industries. The bifurcated reality.

New evidence shows AI is causing a bifurcation in creative jobs, with top-tier augmenting and routine roles declining by up to 33%, leading to a middle-tier squeeze.

Top 5 AI-Driven Productivity Tools To Boost Your 2026 Workflow

Discover the five leading AI-powered tools set to transform workflows in 2026, enhancing efficiency for professionals across roles.

7 Best Tablet Stands and Docks for Prime Day Deals in 2026

Discover the best tablet stands and docks on Prime Day 2026, including top picks for stability, comfort, and versatility for various setups.

First Turkey-Japan defense event in Istanbul signifies closer cooperation

First Turkey-Japan defense industry event held in Istanbul signals deepening military and technological ties, with official agreements signed.