On Thursday 12 November 2026, the Microsoft 365 outage took Outlook, Teams, SharePoint and Copilot offline for businesses around the world. For many it didn't stop at email. Messages queued for hours, so booking confirmations, quotes and anything else passed through Outlook simply waited, along with the shared files and the business tools connected to Microsoft 365. Microsoft didn't say every service was back until Saturday. Here's what happened, what Microsoft says caused it, whether it could happen again as AI spreads through business software, and how to make sure one supplier's bad day isn't yours.

  • 74countries and territories

    Where Downdetector received outage reports, most within an hour of the first problems in the US.

  • 430m+people

    The number Microsoft says use Microsoft 365 apps, all on the same shared platform.

  • 3days

    From the first problems on Thursday to Microsoft confirming full restoration on Saturday 14 November.

The Microsoft outage didn’t affect any of our bespoke business systems. Why bespoke? →

What happened, in Microsoft's own words

Problems began late on Thursday afternoon, UK time. Microsoft's first updates described "elevated load across multiple regions" and "a number of servers being unexpectedly unavailable", which put strain on the servers that were left. Engineers changed the way servers were health-checked, restarted the ones that had stopped responding and worked through a backlog of queued email. By Friday morning Microsoft said email queues were "approaching normal levels", and on Saturday it said it had "completed our efforts to address the underlying issue of the incident."

On Friday Microsoft gave its first explanation of the cause: "an issue during an earlier network capacity upgrade" that surfaced after a more recent network change. It apologised too: "We are deeply sorry for the disruption this incident has caused our customers and partners."

So was it an attack? On everything Microsoft has said so far, it may not have been malicious at all. Microsoft says there is "no indication" of malicious activity, and that the outage was not related to a cyberattack or to AI agents. That's Microsoft's early account, though, not the final word. Its full post-incident review hasn't been published yet, and we'll update this article when it is.

One more warning. Banks told customers to watch for scam emails and calls pretending to be about the outage. If a message asks you to "re-verify" your Microsoft account or pay to restore a service, don't click. Go to Microsoft through your usual route instead.

Who was affected

This wasn't just an inconvenience for office workers. In the UK alone, according to the Associated Press:

  • NHS services were disrupted, and doctors had trouble emailing prescriptions to pharmacies. The National Pharmacy Association warned of medication delays.
  • A trial in Manchester was halted and the jury sent home.
  • Police couldn't take online crime reports and asked people to phone about urgent matters.
  • The UK government said it was working with Microsoft and had contingency plans.

Around the world, the stock exchange operator Euronext told companies to phone in their trades, banks in Hong Kong reported disruption, Air India rerouted its email, and two listed companies delayed their results announcements. Even OpenAI and Anthropic reported problems connecting to Microsoft 365 tools.

Why so much more than email stopped

Most businesses don't think of Microsoft 365 as their booking system or their CRM. But over the years, a lot of everyday business software has been wired into it:

sign-in/

"Sign in with Microsoft"

Many business apps let staff log in with their Microsoft work account. If Microsoft's sign-in has a problem, those apps may as well be down too, however well they're running themselves.

bookings/

Booking confirmations

Microsoft Bookings runs on Exchange Online calendars, and plenty of other booking tools send their confirmations and reminders through an Outlook mailbox. No mailbox, no confirmations.

crm/

CRMs that live in Outlook

CRMs that log emails, sync calendars or pull contacts from Outlook lose their view of what's happening with customers until the connection comes back.

files/

Spreadsheets on SharePoint

The job sheet, price list or rota that "everyone works from" is often an Excel file on SharePoint or OneDrive. That was affected too.

workflows/

Automated workflows

Approvals, alerts and hand-offs built on Microsoft's automation tools, or triggered by emails arriving, quietly stop when the email does.

ai/

AI assistants

Copilot went down with everything else. Any process that now depends on an AI assistant built on the same cloud fails at the same moment.

None of these tools are bad. The risk is that they all lean on the same platform, so when it falls over they fall over together, and there's nothing you can do but wait.

Could it happen again, now AI is moving into business systems?

Almost certainly, yes. This was the second major Microsoft 365 outage of 2026: in January, an outage dragged on for nearly ten hours, reported The Register. In July, an Azure outage in the US was traced to a bug in Microsoft's automated network maintenance system, which removed network routes from more devices than intended, according to Microsoft's preliminary review. And in July 2024, a faulty security update from CrowdStrike crashed what Microsoft estimated was 8.5 million Windows devices worldwide.

The big cloud platforms are extraordinarily reliable most of the time. But they're also enormous, and very concentrated. The UK competition regulator found that AWS and Microsoft each account for 30 to 40% of UK cloud spending. When one of them has a problem, a large share of the economy has it at the same time.

Now add AI. Microsoft says this outage had nothing to do with AI agents, and we've no reason to doubt that. The question is what comes next. Gartner predicted that 40% of enterprise applications would include task-specific AI agents by the end of 2026, up from less than 5% in 2025. Those agents are being given access to email, calendars, CRMs and finance systems, often all inside one supplier's cloud. Gartner also expects that by 2027, 40% of enterprises will scale back or switch off autonomous AI agents because of governance failures.

More automation means changes made faster than people can check them, more systems depending on each other, and more things that stop when one shared service does. The July Azure incident shows how an automated process can widen a small mistake. We're not saying an AI agent will cause the next big outage. We are saying that as AI is built into more of the same few platforms, the number of things that break at once when one of them fails is going up, not down.

Why a bespoke system keeps your business running

We build bespoke business software: booking systems, CRMs, job management, client portals and compliance systems, made around the way a business actually works. They don't depend on Microsoft to run:

  • 0Microsoft accounts needed

    Your system has its own secure sign-in, so staff can log in even when Microsoft can't check their account.

  • 1system, yours

    It isn't one tenant among hundreds of millions on a shared platform. It runs on our own infrastructure in UK data centres.

  • £0per-seat fees

    You're not renting each user a licence, and your core operations don't hang on someone else's subscription.

In practice, that means that when Outlook goes down, your team can still sign in, look up a booking, update a job and see a customer's history. If you want, we'll send the system's own emails (confirmations, reminders, alerts) through a separate route from your office mailbox, so customers keep hearing from you too.

No honest developer will promise that any system never goes down. Ours run on servers too. The difference is that a problem affects one system rather than hundreds of millions of users at once, and fixing it is our team's whole job, not a ticket in a queue. You also own your system and your data, so you're never locked in.

You don't have to give up Microsoft 365 for email and documents, either. The aim is simply that the system your business runs on doesn't stop when your email does. If your core processes currently live in spreadsheets, Access databases or a tangle of connected apps, our legacy system conversion service moves them into one system you control. See what that looks like in our case studies, or read where your business data actually lives.

Six things to do before the next outage

01/

List what depends on Microsoft

Write down every system your business uses and ask: does it log in with Microsoft, send email through Outlook or keep files on SharePoint? The answers are usually a surprise.

02/

Find your "can't work without it" systems

Bookings, orders, jobs and customer records are what keep money coming in. Those are the ones that most need to keep running on their own.

03/

Have a second way to talk

Agree how staff will contact each other and customers if email and Teams go down: a phone tree, a WhatsApp group, a text message service.

04/

Keep your data reachable

Make sure key information can be reached, or exported, without going through the platform that's down.

05/

Write a one-page outage plan

Who decides what, how customers are told, and what can be done by hand until systems return.

06/

Think before connecting AI to everything

Before giving an AI assistant access to your core systems, ask what happens to your business when that assistant, or the cloud it runs on, is unavailable. Our article on AI agents and UK GDPR covers the data protection side.

Microsoft 365 outage: quick answers

What caused the Microsoft 365 outage on 12 November 2026?

Microsoft says the outage was caused by an issue during an earlier network capacity upgrade, which surfaced after a more recent network change and left servers unexpectedly unavailable. Its full post-incident review has not yet been published.

Was the Microsoft 365 outage a cyberattack?

Microsoft says there is no indication of malicious activity, and that the outage was not related to a cyberattack or AI agents. On what is known so far, it appears to have been a technical fault rather than an attack.

How long did the Microsoft 365 outage last?

Problems began on the afternoon of Thursday 12 November 2026, UK time. Recovery was gradual, and Microsoft confirmed full restoration on Saturday 14 November.

Can bespoke software keep working when Microsoft 365 is down?

Yes, if it's built not to depend on it. The bespoke systems Cirrus Design Studio builds have their own sign-in and run on our own UK infrastructure, so they don't need Microsoft 365 or Azure to work.

Is your business one outage away from a standstill?

We'll look at the systems your business runs on, show you which ones stop when Microsoft does, and explain what a system you own could look like. The review is free, with no obligation.

Book a free systems review Why bespoke?

Related articles