Saturday, 21 November 2026UK SME IntelligenceGet the weekly brief
Operations

Microsoft 365 outage: live status, and what UK businesses should do now

Outlook, Teams and SharePoint have been disrupted since Thursday afternoon. Live status from Microsoft, what is affected, and what to do while you wait.

Illustration of a navy cloud whose orange plug has been pulled out of a wall socket, with envelopes drifting around it

Microsoft 365 has been disrupted since Thursday 12 November, and at 5.42am on Saturday 14 November Microsoft took the business incident off its public status page, which now shows Microsoft 365 as “Available”. It has not posted a final “resolved” note for business accounts there. For personal accounts, it said at 3.51am that services had “fully recovered” and the backlog of email had been processed. Microsoft dates the start of the Exchange Online incident to 4.17pm UK time on Thursday (Downdetector, citing Microsoft), when the trouble was in the Americas, and UK reports to Downdetector jumped tenfold at 5.43pm (CNN). Outlook on the web, desktop and mobile were hit, along with Teams calendars, SharePoint sharing, Copilot and a long list of services that depend on email (Microsoft).

The box above is our live feed: it re-checks Microsoft’s public status page every two minutes, so you can leave this page open and see within minutes if Microsoft posts anything new.

If Outlook is still not working: what still works

Microsoft’s last public incident post for business accounts, at 10pm on Friday, said the damage was concentrated in anything that touches email (Microsoft). If you are still having problems, that leaves more of a working day than it feels like:

  • Calls and meetings: use Teams. Microsoft says joining calls and meetings, group chats and channel messages are mostly not affected. What fails is the email side of Teams: calendars, scheduling and invites. So send meeting links by Teams chat or text instead of calendar invites.
  • Files: share from SharePoint inside the business. Opening files stored in SharePoint works. Sharing with people outside your organisation may fail, so for customers, attach the file to a text or send it another way.
  • Mail: read what is already on your PC. Classic desktop Outlook keeps an offline copy of recent mail, so you can still read and draft. Do not remove your Outlook profile or reinstall: that can throw the copy away, along with anything waiting in your Outbox.
  • Apps: stay signed in. For Power Apps and Field Service mobile apps, Microsoft says users “who are already signed in can potentially avoid impact by not signing out, clearing app data, or reinstalling”. Staying signed in is a sensible precaution in other Microsoft apps too, though Microsoft has given that advice only for these two.
  • What does not work: Outlook on the web, desktop and mobile may not reach your mailbox, email is delayed, Copilot Chat, Planner and To Do may fail, and some admin centre pages may not load.

On a personal Outlook.com or Microsoft 365 Personal or Family account? You were covered by a separate consumer incident, shown in the second row of the box above. Microsoft listed Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams and Microsoft 365 for the web. It closed that incident at 3.51am on Saturday, saying services had fully recovered and the backlog of email had been processed, and it gives the end time as 4.10pm on Friday (Microsoft).

Is my email lost? A clock for delayed mail

Mostly, no. It is delayed. On Friday morning Microsoft said: “To help preserve delayed mail during this event, we’ve extended email timeout to 48 hours” (Microsoft 365 Status). Microsoft’s usual window for retrying a stuck message is one day (Microsoft Learn).

What that means in practice depends on who sent the message:

  • Mail sitting in Microsoft’s queues, including from customers and suppliers who are on Microsoft 365 too, gets the 48-hour window. Retry windows normally run from when a message first queued, so mail caught at the very start of the outage, at 4.17pm on Thursday, could begin to bounce from about 4.17pm on Saturday 14 November if it still has not been delivered. Microsoft has not said exactly how it counts the 48 hours, so treat this as the earliest likely time.
  • Mail from other providers that could not be handed to Microsoft stays on the sender’s server, which keeps retrying for as long as its own settings allow.

If a message does fail, the bounce goes to the person who sent it, not to you. So the rule for today: if something important has not arrived by Saturday afternoon, phone the sender and ask them to resend. Our guide on what to do when your email is down covers the first hour and the first day.

The credit clock

For an office that has had no email on the web since 4.17pm on Thursday, the earliest start Microsoft gives, its 99.9% monthly uptime promise was broken just after 5pm that day. Its 50% credit tier was reached at 11.29pm on Thursday, and its 100% tier at 4.17am on Saturday for anyone whose downtime lasted that long. Most users’ real downtime was shorter, because Microsoft restored service region by region. Credits are not automatic and for this outage must reach Microsoft by 31 December 2026 under its service level agreement (Microsoft). Our compensation guide has the full maths, the evidence to gather and a claim template.

The incident IDs admins need

Microsoft tracks this outage under two references. EX1550543 is the Exchange Online incident, named in Microsoft’s first post (Microsoft 365 Status). MO1550821 is the wider Microsoft 365 incident, which Microsoft has named alongside EX1550543 since Thursday evening (Microsoft 365 Status). Use them to find the incident in Service health, to subscribe to its updates, and in any credit claim. Check them against your own tenant: what Service health shows is what counts.

Timeline so far (UK time)

  • Thu 12 Nov, 4.17pm: start of the Exchange Online incident, by Microsoft’s own timing.
  • 5.43pm: UK reports to Downdetector jump tenfold (CNN).
  • 5.54pm: Microsoft’s first post on X says it is investigating problems reaching Exchange Online mailboxes in the Americas (Microsoft 365 Status).
  • 7.31pm: Microsoft says the load comes not from extra traffic but from “a number of servers being unexpectedly unavailable” (Microsoft 365 Status).
  • 11.04pm: some servers back in service; “limited recovery” (Microsoft 365 Status).
  • Fri 13 Nov, 3.13am: setback. Microsoft says its changes are “not taking as expected” (Microsoft 365 Status).
  • 9.24am: Microsoft extends the email timeout to 48 hours (Microsoft 365 Status).
  • 11.04am: Microsoft says recovery work is complete on parts of its infrastructure in the Asia Pacific region and is being extended to other regions, with improvements in mailbox access and delayed email (Microsoft).
  • Noon: Microsoft reports “encouraging recovery progress in Europe”, with email delivery improving across a growing share of affected infrastructure and North America also improving, though some users may still see intermittent problems (Microsoft).
  • 2pm: Microsoft says service availability is still improving, with email queues “significantly reduced and approaching normal levels”. Some users may still have intermittent access problems or delayed mail while it restores the remaining affected infrastructure (Microsoft).
  • 5.57pm: Microsoft apologises and says it is seeing “broad recovery and stability across our services”. It says the incident was “introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change”, that it has addressed the underlying issue, and that it is still restoring service to remaining customers and regions. Its next update is due by 8pm (Microsoft).
  • 8.02pm: Microsoft says it is still “draining queued messages and rebalancing traffic”, so sign-in and access may improve before email delivery catches up. It has no estimate for full recovery yet, and its next update is due by midnight (Microsoft).
  • 10pm: Microsoft says it is seeing “sustained service recovery” and believes “the majority of those impacted scenarios have been addressed”. Because the incident was so severe, it will keep monitoring “for an extended period”, and it will not consider the issue resolved until the backlog of delayed email has been processed. Its next update is due by 2.30am on Saturday (Microsoft).
  • Sat 14 Nov, 3.51am: Microsoft closes the separate incident for personal accounts, saying services “have fully recovered and the backlog of email messages has been processed”. It gives the end time for that incident as 4.10pm on Friday (Microsoft).
  • 5.42am: Microsoft takes the business incident off its public status page, which now shows Microsoft 365 as “Available”. The update it had promised by 2.30am had still not appeared there at 4.45am, and it posts no final note for business accounts on the public page (Microsoft).

Microsoft says it has “no evidence of malicious activity” and that this “was a technical issue not related to cyber or AI / agents”. It will publish a full post-incident report once its review is complete.

Who has been hit in the UK

The disruption reached well beyond offices:

  • The NHS. Hospitals and GP surgeries were hit. GPs could not reach NHS email to see prescription requests or send referrals, and the National Pharmacy Association warned that patients could face prescription delays (The Guardian, via AOL).
  • Police. Several forces, including the Met, Greater Manchester Police and North Yorkshire Police, warned that online forms might not work and asked people to phone instead (same report).
  • Parliament. All parliamentary email was affected, though Teams still worked (W4MP).
  • Rail. National Rail warned on Friday morning that the outage may be affecting customers’ ability to access train tickets sent by email, and told passengers who cannot open a ticket to ask staff (National Rail).

How to be told the moment it is fixed

You do not have to keep refreshing. There are five ways to be told:

  1. Leave this page open. The box at the top re-checks Microsoft’s status page every two minutes and changes when Microsoft changes its status.
  2. Microsoft’s own feed. Microsoft’s public status page has an RSS button for its Microsoft 365 business status, which links to https://status.cloud.microsoft/api/feed/mac. Paste that address into any feed reader, or into Slack’s RSS app, to get a new post each time Microsoft updates. We checked that it works on 13 November.
  3. Email alerts from the admin centre (admins only). In the Microsoft 365 admin centre, go to Health > Service health > Customize > Email, tick Send me email notifications about service health, and add up to two addresses (Microsoft Learn). To follow just this incident, open EX1550543 or MO1550821 and choose Manage notifications for this issue. Use an address that is not on Microsoft 365, such as a personal Gmail account: an alert sent to a mailbox you cannot open is no use. Microsoft says some admin centre pages may not load during this incident, so if Service health will not open, use options 1, 2 or 5 for now.
  4. The Microsoft 365 Admin app. Microsoft suggests its mobile app as a way to keep up with Service health from your phone (Microsoft Learn).
  5. @MSFT365Status on X. Microsoft has posted regular updates there throughout this incident, though some were several hours apart overnight (@MSFT365Status).

Once it is fixed, Microsoft says a preliminary post-incident review for a broad incident like this appears in Service health “within 48 hours of incident resolution”, with a final one “within five business days” (Microsoft Learn). Keep a copy: you will want it if you claim a credit.

While you wait

  • Move urgent contact to the phone. Update your voicemail greeting and put a line on your website saying email is delayed and how to reach you.
  • Treat payment requests with suspicion. Criminals use outages. Do not act on any change of bank details that arrives by email; check it by phone on a number you already hold. Microsoft says it does not make unsolicited phone calls to fix your computer or to ask for personal or financial information (Microsoft Learn).
  • Start a log. Write down when the trouble started and stopped for your staff, what failed and what it cost. You will need it for a service credit claim.
  • Plan for next time. Most of what helps costs little or nothing; see how to keep working through the next Microsoft outage.

This page is updated as Microsoft reports progress.

Frequently asked questions

Is Microsoft 365 down right now?
At 5.42am on Saturday 14 November 2026, Microsoft took the business incident off its public status page, which now shows Microsoft 365 as 'Available'. It has not posted a final 'resolved' note for business accounts there, so admins should look for Microsoft's closing note on incidents EX1550543 and MO1550821 in Service health. For personal accounts, Microsoft said at 3.51am on Saturday that services had fully recovered and the backlog of email had been processed. The box at the top of this page re-checks Microsoft's status page every two minutes.
When will Outlook be working again?
Microsoft's public status page has shown Microsoft 365 as 'Available' since 5.42am on Saturday 14 November, though Microsoft has not posted a final note for business accounts there. It never gave a time for full recovery; its status posts gave a time for the next update instead. On Friday morning it completed recovery work in parts of the Asia Pacific region, at noon it reported encouraging progress in Europe, at 2pm it said email queues were approaching normal levels, and at 5.57pm it reported broad recovery, saying it was still restoring service to remaining customers and regions. At 8.02pm it said it still had no estimate for full recovery, and that access may come back before email delivery fully catches up. At 10pm it reported sustained recovery, but said it would keep monitoring for an extended period and would not treat the issue as resolved until the backlog of delayed email had been processed.
Was the Microsoft outage a cyber attack?
No. Microsoft says it has no evidence of malicious activity and that this was 'a technical issue not related to cyber or AI / agents'. Its early explanation was that a number of servers became unexpectedly unavailable, overloading the rest. On Friday evening it said the incident was introduced by an issue during an earlier network capacity upgrade that surfaced after a recent network change. It has promised a full post-incident report.
Will emails sent to me during the outage be lost?
Most should arrive late rather than not at all. Microsoft says it has extended its email timeout to 48 hours to protect delayed messages. If a message does fail, the bounce goes to the sender, so ask key customers to resend anything that bounced.
Can I get compensation from Microsoft for the outage?
Business customers can claim a service credit, a percentage off the bill for the affected service, if Microsoft missed its 99.9% uptime promise. Credits are not automatic, and for this November outage the claim must reach Microsoft by 31 December 2026. Personal plans have no such promise.

Sources & further reading

SME Brief uses sources to support factual claims and help readers go deeper.

The Weekly Brief

One email. The week's UK SME signal, no noise.

Our demand data, the tools, the stories that matter, and one thing worth doing this week.

Free. Unsubscribe anytime. We don't share your address.