Signals/13 Nov 2026

Worth watchingAI Security· By Toswo Research

Microsoft Outlook, Teams and Copilot outage on 12 November

Microsoft says a large number of servers failed health checks on 12 November, taking down Outlook, Teams, Copilot, Intune and Defender services. It has given no timeline for full restoration.

In plain words

Microsoft's cloud services broke on 12 November. Email in Outlook, Teams, Copilot and several admin and security tools stopped working for businesses and consumers. Microsoft says some of its servers failed health checks and became unavailable, and it has not said when everything will be back. If you depend on Microsoft for mail or security alerts, expect delays, use a backup way to reach people, and do not assume messages were lost.

What happened

The Register reports that the incident began around 18:00 UTC on November 12. Exchange Online, Teams, Copilot 365 and Defender for Office 365 became unavailable. Admins also lost access to Intune and the Microsoft 365 Apps Admin Center, the tools they would normally use to diagnose the problem.

TechCrunch says Microsoft first described the problem as affecting the U.S. and the Americas, then "any region". It also reports that SharePoint, OneDrive, Office for the web and Defender XDR were affected. TechCrunch reports Microsoft attributed the incident to "a large number of servers being unexpectedly unavailable"⁠1 without explaining why.

On X, Microsoft said servers were failing automated health checks. Its early investigation indicated the failed checks may originate from a specific component responsible for processing server health. Around 22:00 UTC Microsoft said it had validated an alternative health check method that let a subset of servers return to service. The status page later said a core process on affected servers was becoming overwhelmed, and that actions so far had "not provided the anticipated relief"⁠2.

The Register's update at 00:35 UTC on November 13 says some servers were brought back and initially remained healthy, but could become unresponsive again once they began receiving traffic. Microsoft said it was analysing diagnostic data to find what triggers this. It was also testing recovery by isolating part of the infrastructure, restarting components and reintroducing traffic.

What is confirmed and what is not

Confirmed by Microsoft's own statements, as reported: a wide outage across many services, servers failing health checks, partial recovery that did not hold under traffic, and no restoration timeline.

Only claimed or tentative: the suspected health-processing component, and the possible role of recent configuration updates. The Register notes that Microsoft says it found no changes that might have sparked the incident, while its status page says it is assessing whether reverting a small number of recent configuration updates could help. The two statements are in tension.

Unknown: the root cause, the number of affected customers, whether any mail was lost or only delayed, and when service will be fully restored. Neither report says the outage involved an attack, and neither suggests one.

Analysis

Email and admin access fail together

The most direct consequence is that organisations lost their mail and the tools to manage the response at the same time. The Register reports that admins could not reach Intune or the Apps Admin Center, and TechCrunch says Microsoft's updates were meant to appear in an admin center that was unreachable. Microsoft fell back on X posts. Mechanism: when identity, mail, management and status reporting share one provider, one fault removes both the service and the usual window onto it. How sure are we: the sources show the loss of admin tools directly. How far each organisation suffered depends on its setup, which the reports do not describe.

Security monitoring gaps

Both outlets list Defender products among the affected services: Defender XDR per TechCrunch, Defender for Office 365 per The Register. If detection and alerting ran through those tools, security teams may have had reduced visibility during the outage. The reports do not say how long coverage was reduced or whether any threat went unseen. Security teams should read this as a prompt to check their own logs for the window, not as evidence of harm. An attacker could in principle exploit a period of weak monitoring, but nothing in the sources says that happened.

Dependence on a single cloud provider

Copilot was also down, so AI features built on the same infrastructure failed alongside ordinary mail. This matters for companies that have wired AI assistants into daily work: the assistant is only as available as the platform beneath it. TechCrunch notes the previous major incident in September, a days-long Microsoft 365 outage blamed on a "core authentication configuration" issue. The two incidents have different stated causes, so the sources do not show a common fault. They do show two serious outages in a short span, which is a fact customers can weigh in continuity planning. See also our earlier look at the ConnectWise breach and AI agents in Microsoft 365 tenants, which concerns a different failure in the same environment.

Testing the causal links

The story rests on Microsoft's own account, relayed by two outlets. The link between failed health checks and the outage is asserted by Microsoft, and the sources do not show independent confirmation. The explanation also shifted: "a large number of servers being unexpectedly unavailable", then health-check failures, then a core process being overwhelmed. These can be one chain, with the process overload causing failed checks and lost capacity, but the sources do not establish that. A sceptical engineer would ask why servers that came back healthy became unresponsive once traffic returned. Microsoft itself says it is analysing exactly that. The worrying reading, which is TOSWO Research's and not a source finding, is that a feedback loop exists: returning traffic overloads recovering servers, which fail again. If so, recovery would need careful staged reintroduction of load, which matches the approach Microsoft describes. Evidence that would change this reading: a root-cause report pointing to a single bad update or hardware fault.

Daily life and business

TechCrunch says both business and consumer users could not reach inboxes, and consumers could not reach OneDrive or Office for the web. People who rely on email to receive password resets, bills or work instructions may have missed time-sensitive messages. The Register reports that friends and family of its writers said their working days were severely disrupted. Whether messages sent during the outage are delayed or dropped is not stated in either report. Senders normally retry delivery for some time, which is general mail behaviour and not a finding here.

What would settle it

Microsoft's post-incident review would settle the cause, including whether a configuration change played a part, and whether the process overload was a trigger or a symptom. The service health history in the admin center and the status page would show the timeline and the final restoration time. Microsoft's reply to TechCrunch's request for comment, which TechCrunch says it would seek, would add detail. The strongest reason this reading could be wrong is that the reports capture only the first hours. A later account could show the outage was shorter, narrower or differently caused than these early reports suggest.

What can be done

For individuals: do not resend critical messages repeatedly, keep a second channel such as phone or another mail provider for urgent matters, and check official Microsoft status posts rather than third-party claims.

For organisations: confirm how you would reach staff if Microsoft mail and Teams are down, keep admin and emergency contacts outside the platform, and review security logs for the outage window once access returns. The Day Zero plan covers what to do when AI-related services fail, and our live risk monitor tracks continuing incidents. For Microsoft, the sources suggest a case for status communication that does not depend on a portal that may be down, though the company has used X as a fallback.

Questions readers ask

Is the Microsoft outlook outage caused by a hack?

Neither TechCrunch nor The Register reports an attack. Microsoft says servers failed automated health checks and became unavailable, and that it found no changes that might have sparked it. The cause is still under investigation.

Which Microsoft services were affected?

The reports name Outlook, Exchange Online, Teams, SharePoint, Copilot, OneDrive, Office for the web, Defender XDR, Defender for Office 365, Intune and the Microsoft 365 Apps Admin Center.

When will Microsoft services be restored?

Microsoft has not given a timeline for full restoration. It says some servers came back but could become unresponsive again once traffic returned, and it is still analysing why.

Is our email lost?

The reports do not say whether messages were lost or only delayed. They say email was not flowing for many customers.

Quoted from

  1. Microsoft’s Outlook email hit by new outage, TechCrunch, 2026-11-12
  2. Microsoft struggling to fix massive cloud outage that's taken down email and Intune, The Register, 2026-11-12

Written by Toswo Research. This is not investment, legal or medical advice. To report an error, see corrections.

Cite this signal

Toswo Signals, "Microsoft Outlook, Teams and Copilot outage on 12 November", https://www.toswo.com/signals/microsoft-outlook-teams-and-copilot-outage-on-12-november, published 2026-11-13, retrieved 2026-11-22.