Skip to content
  • Microsoft 365
  • Outages
  • Business continuity
  • Automation

The Microsoft 365 outage of 12 November 2026: what happened, and what small teams should change

Outlook, Teams, SharePoint and Copilot went down worldwide for more than a day. Microsoft blamed a network capacity upgrade, not an attack. Here is what happened, and six changes that stop the next outage from stopping your business.

Founder, KarachiSol

6 min read

On Thursday 12 November, Outlook stopped loading for people all over the world. Teams followed, then SharePoint, Copilot and the admin tools IT teams would normally use to see what was going on. For many offices in Pakistan the problems started on Thursday night, and when people sat down to work on Friday, it was still going on.

Microsoft says the outage was not a cyberattack. It was a problem inside its own network. The details matter less than the lesson: if every part of your working day runs through one provider, you go down with it. Here is what happened, and what we think small teams should change before the next one.

What happened

Reports of Outlook problems began on the afternoon of Thursday 12 November, US Eastern time. According to Al Jazeera, Downdetector had reports from 74 countries and territories within about an hour.

In a status update that night, Microsoft listed these services as possibly affected (ABC7):

  • Exchange Online (Outlook email)
  • Microsoft Teams
  • SharePoint Online
  • Microsoft 365 Copilot
  • Microsoft Defender XDR and Defender for Office 365
  • Microsoft Intune
  • Microsoft Planner and To Do

TechCrunch reported that some people also lost access to their cloud Windows PCs. By Friday, Doug Madory of the network monitoring company Kentik saw traffic coming back to Microsoft’s services after about 18 hours. On Saturday 14 November, Microsoft said it had fixed the underlying issue and restored service to the customers and regions still affected (CNBC).

What Microsoft says caused it

Microsoft’s explanation changed as it learned more:

  • On Thursday it described a large number of servers becoming “unexpectedly unavailable”, which put extra load on the rest.
  • Its status update that night said “a process on the affected servers responsible for establishing secure connections becomes overwhelmed”.
  • On Friday it pointed to “an issue during an earlier network capacity upgrade” and apologised: “We are deeply sorry for the disruption this incident has caused our customers and partners.”

Microsoft also said it found no sign of malicious activity, and that the incident was “not related to cyber or AI / agents”. At the time of writing it has not published a full post-incident review. We will update this post when it does.

What small teams should change

You can’t stop Microsoft, Google or anyone else from having an outage. You can decide how much of your day stops when they do. These are the things we would set up this week.

1. Agree on a backup channel now

When Outlook and Teams are both down, people need to know where to go without asking, because asking means using the tool that is down. Pick one other place, a WhatsApp group or a Slack workspace, and keep a phone list for clients you can’t afford to go quiet on. Write it down somewhere that isn’t in OneDrive.

2. Know where to check status

Your admin can see Microsoft’s own updates in the Microsoft 365 admin center under Health → Service health. Microsoft also posts on its @MSFT365Status account on X. Checking those first saves an hour of restarting laptops and resetting passwords for a problem that isn’t yours.

3. Keep important work available offline

The Outlook desktop app keeps a local copy of mail you have already received, so you can still read and search it during an outage. In OneDrive, right-click the folders your team can’t work without and choose Always keep on this device. Files that only live in the browser are the first thing you lose.

4. Don’t send customer emails from staff mailboxes

If your website or online store sends order confirmations, invoices or password resets through a Microsoft 365 mailbox, those stopped too. Use a dedicated transactional email service for anything your systems send, and keep Microsoft 365 for people. One outage then can’t stop both your team and your checkout.

The good news for normal email: most mail servers keep retrying for several days when the receiving side is down. That is why messages from Thursday started arriving once service came back. Delayed, not lost, in most cases.

5. Give your automations and AI tools a fallback

Copilot went down with everything else. That is the part of this outage we think about most, because we build AI agents and automations for clients. An AI workflow is only as available as the cloud it runs on. Every automation we build should:

  • notice when a service it depends on is failing, and tell a person instead of failing silently,
  • queue work and retry later, so nothing is lost while a provider is down,
  • have a manual way to do the job, written down, for the day it can’t run.

6. Make your own changes easy to undo

By Microsoft’s account, the cause was a change to its own network. The same thing happens at every size: most outages start with a change, not an attack. For your website, app or internal tools, ship changes in small steps, try them on part of your traffic first where you can, and make sure you can roll back in minutes.

What we took away

Microsoft 365 is still a good choice for most businesses, and this outage doesn’t change that. But “the cloud is always up” was never true. The teams that had a slow Friday instead of a lost one were the ones that had a second channel, files on their own machines, and systems that waited and retried instead of breaking.

If you want help mapping what your business depends on, or building automations that keep working when a provider doesn’t, get in touch.

Questions

What caused the Microsoft 365 outage on 12 November 2026?
Microsoft said the disruption came from an issue during an earlier network capacity upgrade, which left many servers unavailable and overwhelmed a process that handles secure connections. It has not yet published a full post-incident review.
Was the Microsoft outage a cyberattack?
No. Microsoft said it found no sign of malicious activity and that the incident was not related to cyber or AI agents.
Which Microsoft services were affected?
Microsoft listed Exchange Online (Outlook), Teams, SharePoint Online, Microsoft 365 Copilot, Defender XDR, Defender for Office 365, Intune, Planner and To Do as possibly affected.
How long did the Microsoft 365 outage last?
Problems began on Thursday 12 November. Kentik saw traffic returning after about 18 hours, and Microsoft said on Saturday 14 November that service had been restored to the remaining affected customers.
Were emails lost during the outage?
In most cases, no. Sending mail servers usually keep retrying for several days when the receiving side is down, so most delayed messages arrived once service came back.

Written by

Ubaid Hussain

Founder, KarachiSol

Ubaid founded KarachiSol and builds its apps. He has spent more than six years building web products, from Wix and Shopify apps to business dashboards.