All articles

NewsNovember 12, 20265 min read

Microsoft 365: global outage hits Outlook, Teams and Copilot

Servers going offline knocked out Exchange Online, Teams, Copilot and Defender XDR worldwide. Timeline, known causes, phishing risks and what to do now.

Cloud icon on a dark blue digital background

On Thursday 12 November 2026 Microsoft 365 suffered a widespread outage: for hours many users could not use Exchange Online and Outlook email and, as a result, the Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR features that depend on it. What began as a mailbox connectivity problem in the Americas was later extended by Microsoft to users in any region. All sources agree on one point: Microsoft reported no sign of malicious activity or a cyberattack.

Timeline (CET)

  • 15:45–16:53: an earlier Teams incident (TM1550488), limited to North and South America, delays or blocks message sending and conversation handling. Microsoft attributes it to resource contention in its infrastructure and declares it resolved; it has not said whether it is related to what followed.
  • Shortly before 19:00: Microsoft reports problems reaching Exchange Online mailboxes through multiple connection methods in the Americas (incident EX1550543).
  • 19:26: official start of the broader incident MO1550821 in the Microsoft 365 admin center.
  • 20:07: according to Downdetector data reported by Reuters (cited by Security Affairs), more than 97,000 reports for Outlook, over 38,000 for Microsoft 365 and about 4,500 for Teams.
  • Night of 12–13 November: Microsoft first reports limited recovery, then improvement after restarting servers, without confirming full restoration.
  • 13 November: the latest update quoted by Infosecurity Magazine mentions early signs of stabilisation, with capacity not yet back to normal levels.

Computing (España) reports spikes in at least 74 countries and territories, a rise in Spain overnight and on Friday morning, and slowdowns at public offices in Japan, the United States, Canada, Australia and New Zealand: it is the only source for these figures.

Affected services

In advisory MO1550821 Microsoft lists Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR. Computer Weekly, citing the status portal, adds the Microsoft 365 Admin Center, Microsoft 365 apps, Microsoft Fabric, Defender and Intune. According to Microsoft, quoted by SecurityWeek, features that do not interact with Exchange Online remain functional: in Teams, for example, core functionality works, but calendar, invitations and meeting scheduling do not.

Other effects reported by the sources:

  • problems for Google Workspace users who read their mail with Outlook desktop or mobile clients (SecurityWeek);
  • OpenAI and Anthropic Microsoft 365 connectors failing, because the underlying services were unavailable (Reuters via Security Affairs, Computing);
  • in Intune, device enrolment, check-in and compliance policies impaired (Computer Weekly).

The cause, according to Microsoft

The explanation changed over the day. Microsoft first pointed to elevated load across multiple regions, then clarified that traffic had not increased: a number of servers had become unavailable and the rest of the infrastructure had to carry the whole load. Later updates mentioned servers failing automated health checks, elevated processor usage and a process becoming overwhelmed so that servers stopped handling requests; according to SecurityWeek, it is the process that establishes secure connections.

Announced countermeasures: all deployments paused, connection traffic redistributed across the worldwide infrastructure, traffic moved off affected systems, servers restarted, a workaround tested to bypass the component that processes health checks, and a rollback of a recent network configuration change that coincided with the start of the disruption (SecurityWeek; BleepingComputer refers to “a small number” of configuration updates).

The sources differ on how certain this is: Computing (España) presents the saturation linked to the configuration change as the confirmed origin, while SecurityWeek writes that Microsoft had not yet confirmed the root cause. SecurityWeek also notes that the outage came two days after November’s Patch Tuesday, which fixed the already exploited Outlook flaw CVE-2026-124194; Microsoft has not linked the two.

Why it is a security issue

Infosecurity Magazine and Computer Weekly report consistent warnings from analysts and from Australia’s National Cyber Security Coordinator:

  • Microsoft-themed phishing: people clearing a day’s email backlog are inclined to trust fake “security updates” or requests to re-verify their account. According to Check Point, cited by Infosecurity Magazine, Microsoft was the most impersonated brand in phishing in Q3 2026, with 33% of attempts;
  • fake IT support calls, including faked voices or video: locked-out employees are waiting for exactly that call;
  • reduced visibility: with Defender XDR and Outlook-delivered alerts unavailable, a suspicious sign-in or a new mail forwarding rule can go unnoticed.

Impact for European and Italian organisations

In continental Europe the outage started in the late afternoon and continued through the night, hitting evening shifts, on-call teams and anyone working with offices or customers in the Americas hardest. For NIS2 entities it is a concrete case of supplier dependency: the directive requires business continuity and supply chain risk management, and a communication channel independent of corporate email belongs in those plans. Healthcare organisations that rely on email and Teams for clinical communications or shift handovers should check that fallback procedures are known to staff.

What to do now

  1. Follow incidents EX1550543 and MO1550821 in the Microsoft 365 admin center, not messages or links received by email or on social media.
  2. Warn employees: IT and Microsoft do not ask for passwords or MFA codes by phone or via links; any “update” must be verified on a channel you already know.
  3. Avoid making things worse: according to Computer Weekly, Microsoft suggests that users already signed in should not sign out, clear app data or reinstall; for Power Apps and Field Service, the web version may get around the problem.
  4. Treat the outage window as an incident: review sign-ins, mailbox rules (forwarding above all), account changes and endpoint activity from the hours without visibility, collecting evidence directly from the machines rather than only from the platform that was down.
  5. Once Intune is back, check that device enrolment and compliance checks have resumed.
  6. Expect delays in email and message delivery and recheck queues once service is restored.

How ARXDOME helps

ARX Sentry collects logs and events directly from computers, servers and firewalls through its probes and shows them in the SOC pages, including the identity views: sign-ins, bursts of attempts, privileged access, night-time access and account changes. With ARX Trace, analysts launch collections and searches across multiple machines and reconstruct, with evidence taken from the endpoints, what happened during the hours when Microsoft 365 tools were unavailable.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles