The Library

Microsoft 365 Outage: Outlook, Teams, SharePoint, Copilot and Defender XDR Disrupted November 12 to 13, What Is Confirmed and What to Do This Week

A major Microsoft 365 outage began November 12, 2026 and ran into November 13, with reported disruption to Outlook, Teams, SharePoint Online, Copilot and Defender XDR. Here is what is confirmed, what is not known, and how to plan for the next one.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

Microsoft 365 Outage: Outlook, Teams, SharePoint, Copilot and Defender XDR Disrupted November 12 to 13, What Is Confirmed and What to Do This Week
On this page 8 sections

A major Microsoft 365 outage began on November 12, 2026 and continued into November 13. Reports say it disrupted Outlook, Teams, SharePoint Online, Copilot and Microsoft Defender XDR. If your business runs its email, chat, files and security monitoring on Microsoft 365, one failure could stop several parts of your working day at the same time.

Below you will find what is confirmed, what is still not known, and a short list of things to set up this week so the next outage costs you less time.

What happened in the Microsoft 365 outage

Cyberpress and Cybersecurity News both reported a major Microsoft 365 outage that disrupted access to cloud services starting November 12. Cybersecurity News reported that the disruption continued into November 13, 2026.

The reported impact covered:

  • Outlook (email)
  • Microsoft Teams
  • SharePoint Online
  • Copilot
  • Microsoft Defender XDR

Cybersecurity News quoted Microsoft's public updates, which described the recovery work. One update said that the status of the changes applied to improve serviceability had been monitored.

One caution about sourcing: we have not seen a Microsoft post-incident report. The facts in this post come from two security news sites that reported on Microsoft's public updates. Treat the details as reported, not final.

Was the Microsoft 365 outage a cyberattack?

Nothing in the reports points to an attack. According to Cybersecurity News, Microsoft's public updates describe infrastructure failures and recovery work, not malicious activity.

Based on what has been published, you have no reason to treat this as a break-in to your own Microsoft 365 account. It was reported as a service failure on Microsoft's side. If you see something that does look like a security problem in your own systems, deal with it on its own terms. Don't assume it was caused by the outage.

Microsoft 365 outage: what is confirmed and what is not

Point Status
Outage began November 12, 2026 Reported by Cyberpress and Cybersecurity News
Disruption continued into November 13, 2026 Reported by Cybersecurity News
Outlook, Teams, SharePoint Online, Copilot and Defender XDR affected Reported by Cyberpress
Cause described as infrastructure failure Microsoft's public updates, as reported by Cybersecurity News
Evidence of a cyberattack None reported
How many users or businesses were affected Not known
Which countries or regions were hit Not stated in the sources we verified
The exact time every service was fully back Not known
A detailed root cause from Microsoft Not published in the sources we verified

Anything in the "not known" rows is a gap, and we have not filled it in. If Microsoft publishes more, those rows may change.

Is Microsoft 365 down right now?

The sources we checked don't say when every service was fully restored. If your staff still have problems with Outlook or Teams, check Microsoft's own status updates before you change anything in your settings. Try one thing first: open the same service on a phone using cellular data, off your office network. If it fails there as well, the problem is probably not in your building. If it works there, look at your own network, devices or accounts.

Why a Microsoft 365 outage matters for a company network

Most businesses on Microsoft 365 don't use only one part of it. Email, internal chat, shared files, the AI assistant and often the security console all come from the same provider. That is convenient on a normal day. On a day like November 12, it means those tools can all go down at once.

The security console is the part to look at hardest. Microsoft Defender XDR was among the services reported as affected. If your IT team or provider relies on it to watch for threats, an outage like this could leave them unable to see what is happening while it lasts. Decide ahead of time who watches for problems, and how, if that console stops responding.

This is a planning issue, not a reason to panic. A cloud subscription means someone else runs the systems, and you rely on their uptime. Our post on who you call when your systems go down covers the people side of that. If you are weighing which systems to keep under your own control, see our self-hosting and infrastructure page.

What to do this week: Microsoft 365 outage checklist

None of these steps depend on a Microsoft setting or update. They are continuity steps, so you can still work the next time a cloud service stops.

Task How to check it is done
Confirm Outlook, Teams and SharePoint work for every user Ask each team lead to confirm sign-in, sending mail and opening shared files
Ask staff what went missing on November 12 and 13 Have people resend or follow up on anything important they sent or expected during the outage
Pick a backup channel that does not run on Microsoft 365 A phone list or a group text everyone has already joined
Keep key contact numbers offline A printed or phone-saved list of staff, key customers, suppliers and your IT contact
Name who watches security if Defender XDR is unreachable One named person, plus what they check instead
Keep offline copies of the few documents you cannot work without Price lists, open orders, procedures, stored somewhere you can open without signing in
Decide who declares an outage and who tells customers One name, written down, with a short message ready to send
Test the plan Run a drill once a quarter where everyone uses the backup channel

Microsoft 365 outage questions people are asking

Is Outlook down today?

Reports say Outlook was disrupted from November 12 into November 13, 2026. The sources we verified don't give a time for full recovery. If you still have trouble, check Microsoft's status updates and test from a phone on cellular data.

Why was Teams down?

Teams was one of several services caught in the same outage. According to reports, Microsoft's public updates describe infrastructure failures and recovery work. No more detailed cause has been published in the sources we checked.

Was the Microsoft 365 outage a hack?

No evidence of a cyberattack has been reported. Microsoft's updates, as reported, describe an infrastructure failure, not malicious activity.

Was any data lost in the Microsoft 365 outage?

This is not known. The reports don't mention data loss either way. Ask your staff to check that anything important they sent during the outage actually arrived.

How long did the Microsoft 365 outage last?

It began November 12, 2026 and continued into November 13, according to reports. The exact end time is not known from the sources we verified.

Was Copilot affected by the outage?

Yes. Copilot is listed among the affected services, along with Outlook, Teams, SharePoint Online and Microsoft Defender XDR.

Should we move off Microsoft 365 after this?

One outage is not a reason to move on its own. It is a reason to have a backup channel, offline contacts and a named person in charge for the next one.

The bigger lesson

When one provider runs your email, chat, files, AI assistant and security console, its bad day becomes your bad day. You can't stop a cloud outage. What you can control is how long your team sits idle when one happens. A written backup plan, tested once a quarter, turns a lost day into a short inconvenience.

For help planning for outages and locking down the systems you run, see security hardening or get a quote.

Get security alerts like this by email, along with our free checklist, at security alerts.

Sources: Cybersecurity News; Cyberpress.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

Security alerts by email

Hear about the next one first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.

Want a result like this?

Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.

Get a Tech Quote

Security alerts by email

The next security hole is already out there. Hear about it from us first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.