Microsoft 365 has now been affected for more than 17 hours. The outage began on Thursday, November 12, around 17:17 CET, in Exchange Online, the business email service behind Outlook, and spread to Teams, SharePoint Online, Microsoft 365 Copilot, Defender XDR, Intune, and other services. By mid-morning on Friday the 13th, Microsoft’s status page was still showing degraded service for both business and personal accounts, and the company has given no timeline for a full recovery.
The Microsoft 365 outage in 20 seconds
- Exchange Online, Teams, SharePoint, Copilot, Defender, and Intune have been down since Thursday.
- Microsoft is ruling out malicious activity for now.
- It’s rolling back a network change, but hasn’t confirmed the root cause.
- There’s no timeline for full recovery.
Microsoft moved the updates to its public status page because administrators may not have access to the Microsoft 365 admin center, where these incidents are normally posted. The internal advisories are tracked as MO1550821 and EX1550543. OpenSecurity has detailed which features are affected and what security risks the outage creates, such as Safe Links being unable to verify links in Outlook and Teams.
Servers Crashing Again as Soon as Traffic Returns
Microsoft’s overnight updates describe a self-feeding infrastructure problem. According to the company, the elevated load didn’t come from more users; rather, many servers went out of service after failing automated health checks, so the remaining ones absorbed their traffic. Microsoft paused all deployments, rerouted traffic, and restarted machines, but some stopped responding again as soon as they took on load.
It later pointed to a process that establishes secure connections on the affected servers as a possible factor, and began rolling back a recent network configuration change that coincides with when the incident started, though without confirming it as the cause. By Friday, Microsoft acknowledged the measures weren’t having the expected effect because several machines remained stuck in a bad state, and it reported a traffic spike between its routing services and backend servers, partly caused by its own load redistribution. The response involves adding more virtual machines. According to outlets tracking the incident, there have been partial recoveries in some regions that haven’t held.
The Cost of Concentrating Email, Collaboration, and Security
The incident illustrates a risk many organizations take on without really measuring it. In Microsoft 365, email, calendars, messaging, documents, the Copilot assistant, device management through Intune, and part of Defender’s email protection all depend on the same platform. When Exchange Online fails, the effect cascades: calendar and meeting scheduling stop working in Teams, Copilot can’t read email, and Defender’s link verification stops responding too.
Nor is this an isolated case this year. In January, Microsoft 365 was down for nearly ten hours in North America, and in late August thousands of Outlook users lost access to their inboxes. cloudnews.tech also reported on a similar cascading Azure Front Door failure that took down Microsoft 365 and Xbox last year. For IT leaders, the lesson is a familiar one that’s rarely applied: a continuity plan should include a communication channel that doesn’t depend on the same provider, should identify which processes stop if email goes down for a full day, and should review what the contracted service-level agreement actually covers. Service-credit refunds offset part of the subscription fee, not the impact on the business.
The incident also lands in the middle of Europe’s ongoing debate about dependence on major US cloud providers. A technical failure like this one has nothing to do with data sovereignty, but it does have to do with concentration: the more critical functions rest on a single platform, the bigger the blast radius of any error within it.
Frequently Asked Questions
When did the Microsoft 365 outage start?
On Thursday, November 12, 2026, around 17:17 CET, with problems in Exchange Online that spread to other services.
What caused the outage?
Microsoft hasn’t confirmed this. It points to servers failing health checks and is rolling back a network configuration change, and says there’s no evidence of malicious activity.
Does it affect personal accounts too?
Yes. Microsoft is reporting an incident in its consumer products affecting Outlook.com, OneDrive, OneNote, To Do, Teams, and Microsoft 365 for the web.
Sources:
- Microsoft: Service Health Status
- OpenSecurity: La caída de Microsoft 365 supera las 17 horas
- ITdaily: Microsoft 365 still down
- BleepingComputer: Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide
- CNBC: Widespread Microsoft outage takes down Outlook and other 365 services
This article is also available in Spanish: “Microsoft 365 sigue caído: Outlook y Teams fallan desde el jueves,” on revistacloud.com.

