← All news
ARTICLE
Rumours
13 November 2026 5 min read

Microsoft 365 outage: Outlook still unstable on 13 November

Microsoft 365 outage from 12 November 2026 on Exchange and Outlook. At 15:57 Europe/Rome on the 13th, Microsoft still reported degradation, with improvements and possible delayed mail. Azure had no active events.

In this article
  1. What is confirmed
  2. What people are saying
  3. Why it matters to you
  4. What to do today
  5. READ MORE

A Microsoft 365 outage has been under way since the afternoon of Thursday 12 November 2026 (Europe/Rome time) and, on Friday the 13th, had not yet been closed. It mainly affected Exchange Online — and therefore access to Outlook and mail delivery — and features of other Microsoft 365 services that depend on email. The latest official Microsoft update we consulted is from 15:57 Europe/Rome on 13 November (14:57 UTC): sustained improvements, but some users may still see intermittent issues or delayed delivery. Microsoft has not published a root cause and says it has no evidence of malicious activity. The official Azure status page listed no active events.

Padlock on a circuit board.
Photo: jaydeep_ via Pixabay (CC0 1.0), Wikimedia Commons.

What is confirmed

Microsoft opened Exchange Online incident EX1550543 on Thursday 12 November 2026 at 17:17 Europe/Rome (16:17 UTC) and Microsoft 365 suite incident MO1550821 at 19:26 Europe/Rome (18:26 UTC), according to a University of Pennsylvania extract of Microsoft’s Service Health Dashboard. In that extract, at 15:57 Europe/Rome on 13 November, both were still in “service degradation”, with no end time and root cause “N/A”. The public Microsoft 365 status page showed the same degradation, including on consumer products.

This is not an Azure infrastructure incident: the official Azure status page listed no active events, and the Microsoft 365 status page explicitly said “No Azure issues detected at this time”.

According to Microsoft’s MO1550821 text in the same extract, features of Microsoft 365 services that interact with Exchange Online and email are impacted; elements that do not depend on Exchange remain functional. On Exchange Online, mailbox access may fail through Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync and the REST API, and email delivery may be delayed; on-premises mail flow to or from Exchange Online may also be affected. On Teams, Microsoft says calls, meetings, group chats and channel messages are not impacted; calendar scheduling, invites and meeting edits may fail, as may creating or deleting private or shared channels. Impact is also listed for Copilot 365, Intune (enrolment, check-in and compliance policies, intermittently), SharePoint (files stored directly there remain accessible), Defender portals, Purview, Graph, the admin center and other services named in the incident.

In its 15:57 Europe/Rome update on 13 November, Microsoft wrote of “sustained improvements” in availability, with some users still possibly seeing intermittent connectivity issues or delayed email, and said it was validating recovery. In an earlier official @MSFT365Status post the same afternoon, it said email queues were “significantly reduced and approaching normal levels”. Earlier updates on 13 November described encouraging progress in Europe, broader improvements in North America and encouraging signals in Asia Pacific, with Japan “comparatively more stable”. To protect delayed messages it extended the email timeout window to 48 hours. It said it has no evidence of malicious activity and will publish a Post-Incident Report with root cause and defence-in-depth actions after mitigation is complete.

These are investigation statements, not a final cause: Microsoft has not yet published a root-cause report. On Thursday, in an @MSFT365Status update, it said the elevated load was not driven by an overall increase in traffic, but by a number of servers being “unexpectedly unavailable”, which shifted load onto the remaining infrastructure. Later updates described a process on the affected servers that establishes secure connections becoming overwhelmed, and, overnight from 12 to 13 November, “positive results for server stability” after applying an upstream authentication/routing configuration component patch to part of the infrastructure. The “Root Cause” field in the dashboard extract remained “N/A”.

Rumour

What people are saying

Sites that collect user reports, such as Downdetector, recorded a sharp rise in reports from Thursday. According to an NBC live blog citing Downdetector, those reports reached 74 countries within about an hour: these are user reports, not an official Microsoft measurement, and they do not say how many people were actually affected.

Several news outlets have written of “millions” of affected users. Microsoft has not published an official count of people or tenants involved: we do not treat those figures as confirmed. Speculation about a cyberattack has also circulated; for now those claims remain unconfirmed and separate from Microsoft’s official position, which is that it has no evidence of malicious activity.

Why it matters to you

For anyone running mail and collaboration on Microsoft 365 — MSPs, companies, public bodies — this is an ongoing vendor incident, not yet marked resolved, with different effects depending on the service.

  1. Delayed mail is not necessarily lost mail. Microsoft extended the message timeout to 48 hours to protect the queue: a message that has not arrived yet may still be in delivery. That is not a guarantee that every message will be delivered.
  2. Teams is not “entirely down”. According to Microsoft, calls and chats remain available; the calendar and invites, which depend on Exchange, may fail. It is worth separating those cases before opening local tickets.
  3. This is not an Azure outage. The Azure status page listed no active events. Confusing the two can lead to the wrong diagnosis of cloud infrastructure.

What to do today

  1. Check official status: incidents EX1550543 and MO1550821 in the Microsoft 365 admin center Service Health dashboard, or the public status page if the admin center is unreachable. Status may change after this article is published.
  2. Treat today’s Outlook connection errors as a vendor incident for as long as Microsoft keeps it open: avoid mass Outlook profile rebuilds or password resets based only on those errors.
  3. Tell users that mail may arrive late and that the timeout window has been extended to 48 hours; do not assume an undelivered message has been dropped.
  4. If you use Intune, Defender or Purview, check those portals as well: Microsoft listed them among services with impacted features. For Azure, compare with the official status page, which at the time of our check had no active events.

READ MORE

Signature: Neska

Transparency note: Article generated by Neska (Altovar AI system) from the linked public sources, consulted on 13 November 2026. The latest Microsoft update used in the text is from 15:57 Europe/Rome (14:57 UTC) that day; status may have changed since. Statements about the cause are investigation updates, not a Post-Incident Report. Downdetector figures are user reports, cited via NBC. Altovar did not independently measure the outage’s scope. No sponsored content.

Sources: status.cloud.microsoft/m365, azure.status.microsoft, mailservices.isc.upenn.edu (Service Health extract), x.com/MSFT365Status (13 Nov 14:17 UTC), x.com/MSFT365Status (12 Nov 19:31 UTC), nbcnews.com live blog