Microsoft 365 Outage: Outlook, Teams, SharePoint, Copilot and Defender XDR Disrupted Worldwide, What Microsoft Confirmed and What to Do Before the Next One
A global Microsoft 365 outage starting Thursday disrupted Outlook email, Teams, SharePoint, Copilot and Defender XDR. Microsoft blames a network capacity upgrade, says it was not a cyberattack, and says service was restored Saturday.
Where Worldwide
On this page 8 sections
A global Microsoft 365 outage that began on Thursday disrupted Outlook email, Teams, SharePoint, Copilot and Microsoft's Defender XDR security tool, and users were affected into Friday. Microsoft says the cause was a problem from an earlier network capacity upgrade, not a cyberattack, and on Saturday it said service had been restored across its products.
If your team lost email and chat for parts of two working days, the next question is what Microsoft has actually confirmed, what it has not, and what to set up so the next outage costs you less. This post covers all three.
What happened in the Microsoft 365 outage
Microsoft's statements, as reported by BleepingComputer and CNBC, are the only sources for the details here. We could not find a fuller primary record from Microsoft, so we have kept to what those reports quote and attribute to the company.
According to BleepingComputer, Microsoft says the incident began Thursday at 1:26 PM ET. It was tracked as MO1550821. The services listed as disrupted were:
- Exchange Online, the service behind Outlook email
- Microsoft Teams
- SharePoint Online
- Microsoft 365 Copilot
- Microsoft Defender XDR
CNBC reported that the outage affected users of Outlook, Teams and 365 on Thursday and Friday.
During recovery, Microsoft said: "We have addressed the underlying issue and continue to restore service to remaining customers and regions." It later said: "We are seeing broad recovery and stability across our services."
On Saturday, Microsoft said service had been restored across products. The company also apologized: "We are deeply sorry for the disruption this incident has caused our customers and partners."
What caused the Microsoft 365 outage
Microsoft attributed the incident to an issue during an earlier network capacity upgrade. That is the whole explanation in our sources. Microsoft has not said, in anything we have seen, what the upgrade changed, what went wrong with it, or why the problem appeared later rather than at the time of the upgrade.
Was the Microsoft 365 outage a cyberattack?
No, according to Microsoft. Its statement was direct: "This was a technical issue not related to cyber or AI / agents."
That matters if staff are worried their accounts were compromised. Based on what Microsoft has said, this was a failure on Microsoft's side, not an attack on your company. There is no sign in our sources that anyone needs to reset passwords because of this outage.
What is confirmed and what is not known
| Question | Status |
|---|---|
| When it started | Confirmed: Thursday at 1:26 PM ET, per Microsoft |
| Which services | Confirmed: Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot, Defender XDR |
| Incident ID | Confirmed: MO1550821 |
| Cause | Confirmed at a high level: an issue during an earlier network capacity upgrade |
| Was it an attack | Microsoft says no |
| When it ended | Microsoft said Saturday that service was restored across products |
| How many users or companies were hit | Not known |
| Which countries or regions were worst affected | Not known beyond Microsoft saying it was restoring "remaining customers and regions" |
| Whether any email or files were lost or delayed | Not known |
| Whether Defender XDR alerts were delayed or missed | Not known |
| Whether Microsoft will offer service credits | Not known |
| Whether a detailed post-incident report will be published | Not known |
Where our sources are silent, we are not going to guess. If Microsoft publishes more, the right move is to read it before drawing conclusions.
Why the Microsoft 365 outage matters for a business
For many companies, Microsoft 365 is not one tool. It is email, calendars, internal chat, shared files, an AI assistant and, increasingly, the security console that watches for attacks. This outage showed what that means in practice: one problem inside Microsoft's network touched all of them at once.
Two points stand out.
Your security tool was on the list. Defender XDR is what some companies rely on to spot suspicious sign-ins and malware. Microsoft has not said whether alerts were delayed or lost during the outage. If your security monitoring runs through Microsoft, it is worth knowing that it can go quiet at the same moment as your email.
You cannot fix it yourself. When a cloud service fails on the provider's side, nobody in your office can restart it. What you control is how prepared you are: whether staff know where to go, whether customers can still reach you, and whether the work that matters most can continue for a day without the usual tools. We wrote about that side of things in When Your Systems Go Down, Who Do You Call?.
None of this means leaving Microsoft 365. It means deciding, before the next outage, what the business does when it is unavailable.
What to do this week after the Microsoft 365 outage
| Task | Why | How to check |
|---|---|---|
| Confirm important email from Thursday and Friday arrived | It is not known whether anything was delayed or lost | Ask staff which messages they were expecting; follow up with key customers and suppliers |
| Review security activity from the outage window | It is not known whether Defender XDR alerts were affected | Once the console is working, look back over Thursday and Friday for alerts or sign-ins you would normally have acted on |
| Record what the outage cost you | Useful if you raise it with Microsoft or your reseller | Note hours lost, missed orders or calls, and the incident ID MO1550821 |
| Keep a contact list outside Microsoft 365 | If Teams and Outlook are down, so is the company directory inside them | A printed or offline list of staff, customer and supplier phone numbers |
| Agree a backup communication channel | Staff need to know where to talk when Teams is down | Pick one channel not hosted on Microsoft 365 and test it with the whole team |
| Keep offline copies of critical documents | SharePoint was on the affected list | Price lists, contracts, procedures and contact sheets available on a device without signing in |
| Decide who tells customers | Silence looks worse than a short notice | Name one person, and make sure your website and phone line are not on the same provider as your email |
| Decide who watches for updates | Someone needs to tell staff when service is back | Assign it to your IT lead or provider, not everyone at once |
If your website, email and file storage all depend on a single provider, it is worth reviewing which of those you could host or back up separately. Our self-hosting and infrastructure page explains what that can look like.
Microsoft 365 outage questions people are asking
Is Microsoft 365 down right now?
Microsoft said on Saturday that service had been restored across products. If you are still seeing problems, they may have a different cause, so check with whoever runs your IT.
Is Outlook down? Is Teams down?
Both were affected on Thursday and Friday. Microsoft said Saturday that service was restored.
What caused the Microsoft 365 outage?
Microsoft attributed it to an issue during an earlier network capacity upgrade. It has not given more detail in our sources.
Was the Microsoft outage a hack?
No. Microsoft said it was a technical issue not related to cyber or AI.
Which Microsoft services were affected?
Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR.
How long did the Microsoft 365 outage last?
Microsoft says it began Thursday at 1:26 PM ET. Users were affected Thursday and Friday, and Microsoft said Saturday that service was restored. Exact recovery times for individual companies are not known.
Did we lose any email in the outage?
Not known. Microsoft has not said either way in our sources, so check with staff and key contacts.
What is MO1550821?
It is the ID Microsoft used to track this incident. Keep it if you raise the outage with Microsoft or your reseller.
Do we need to reset passwords?
Nothing in Microsoft's statements points to that. It said the outage was not related to cyber activity.
The bigger lesson
Cloud services are reliable most of the time, and that is exactly why so few businesses plan for the day they are not. This outage did not come from attackers. It came from routine maintenance on Microsoft's own network, and it still stopped email, chat, files and security monitoring together. The fix is not a different vendor. It is a written plan, a contact list that lives outside the system, and a test run before you need them.
For help building systems that keep working when a provider goes down, see security hardening or get a quote.
Get security alerts by email, with the free checklist, at /security-alerts.
Sources: BleepingComputer: Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide; CNBC: Microsoft outage.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
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.
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 QuoteKeep reading
Coles Cyber Security Incident: What Australia's Second-Largest Retailer Has Confirmed, What Is Not Known, and What Businesses Should Do Now
Coles Group says it is investigating a cyber security incident. Coles has not said whether customer or Flybuys...
Apple Secure Exclaves: Camera and Microphone Data Walled Off From the OS, Apps and Apple, What Is Confirmed and What Businesses Should Do
Apple says its new Secure Exclaves process camera and microphone data where the operating system, apps and App...
Siri Conversation History: The Siri App Kept Conversations "Forever" by Default on a Researcher's Device, What Is Confirmed and How to Shorten It
A forensic researcher found the Siri app keeps a database of conversations, with retention set to "Forever" by...