Home / Blog / Microsoft 365 outage
Microsoft 365 outage: Outlook, Teams and OneDrive down (12-13 November 2026)
Since Thursday afternoon, 12 November 2026, Microsoft 365 has been failing for people around the world. Work and school mailboxes in Outlook would not load, Teams calendars broke, and 22 Microsoft products were listed as affected, from OneDrive and SharePoint to Copilot, Intune and Defender. As of 07:29 UTC on Friday 13 November Microsoft says its latest fix is working on part of its servers, but the outage is not over and there is no time for a full fix.
What is down
Microsoft's summary: "Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional." In practice that means anything that touches email, calendars or contacts. Each product has its own page with Microsoft's exact words, what still works and what to do:
Also affected: OneNote, Microsoft To Do, Microsoft Planner, Microsoft Intune, Microsoft Power Apps, Microsoft Defender for Office 365, Microsoft Defender XDR, Microsoft Purview, Microsoft Fabric, Power BI, Microsoft Graph, Windows 365, Universal Print, Microsoft 365 admin center, Microsoft 365 apps, Microsoft 365 Education.
Personal accounts were hit too. Microsoft's consumer status says: "We're pursuing multiple workstreams to pinpoint the source of the issue and ensure the recovery of the affected environment. This issue impacts Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web although you may also see issues in other Microsoft 365 services."
What still works
- Teams chats, calls, meetings and standard channels, Microsoft says, as long as you join from a chat or meeting link rather than the Teams calendar.
- Files stored in SharePoint Online open normally, according to Microsoft (SharePoint outage page).
- Power Apps on the web, and mobile apps you are already signed in to.
- Azure, Microsoft's cloud platform, has its own status page and was not part of this incident. Check it on our Microsoft status board.
Timeline
Times in UTC and US Eastern time. Official updates are Microsoft's own, from its posts on incident MO1550821.
Thu, Nov 12
14:45 UTC
9:45 a.m. ET
An earlier, separate Teams incident (TM1550488) hits users in North and South America; Microsoft blames "resource contention" and resolves it at 15:53 UTC. It has not said whether it is linked.
Thu, Nov 12
17:39 UTC
12:39 p.m. ET
Outlook problem reports start climbing on Downdetector.
Thu, Nov 12
17:54 UTC
12:54 p.m. ET
Microsoft 365 Status first posts about problems accessing Exchange Online mailboxes through multiple connection methods in the Americas (incident EX1550543).
Thu, Nov 12
18:07 UTC
1:07 p.m. ET
Microsoft says users in any region may be affected.
Thu, Nov 12
18:26 UTC
1:26 p.m. ET
Microsoft opens the wider incident MO1550821: users may be unable to connect to multiple Microsoft 365 services.
Thu, Nov 12
18:27 UTC
1:27 p.m. ET
Over the next hour and a half Microsoft reports elevated load and servers becoming unexpectedly unavailable. It pauses deployments, restarts servers and bypasses a health check component.
Thu, Nov 12
22:03 UTC
5:03 p.m. ET
Microsoft says a core process on affected servers is becoming overwhelmed, causing capacity loss.
Thu, Nov 12
22:58 UTC
5:58 p.m. ET
Partial recovery: some servers are back and stable.
Fri, Nov 13
00:00 UTC
7:00 p.m. ET
Relapse: servers that came back become unresponsive again once they receive traffic.
Fri, Nov 13
01:12 UTC
8:12 p.m. ET
Microsoft identifies the overwhelmed process as the one handling secure connections and starts reverting a recent network configuration change.
Fri, Nov 13
01:48 UTC
8:48 p.m. ET
Microsoft reports positive results from server restarts.
Fri, Nov 13
02:58 UTC
9:58 p.m. ET
Microsoft says its changes are not taking as expected.
Fri, Nov 13
03:36 UTC
10:36 p.m. ET
Microsoft says there is no indication the outage is the result of malicious activity.
Fri, Nov 13
04:12 UTC
11:12 p.m. ET
A second partial recovery is not sustained.
Fri, Nov 13
04:56 UTC
11:56 p.m. ET
Microsoft describes a surge of calls from routing services to backend servers and scales up virtual machines.
Fri, Nov 13
06:24 UTC
1:24 a.m. ET
Microsoft's consumer status names Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams and Microsoft 365 for the web as affected for personal accounts.
Fri, Nov 13
06:54 UTC
1:54 a.m. ET
Microsoft reports "marginal success".
Fri, Nov 13
07:29 UTC
2:29 a.m. ET
Latest update: positive results for server stability after an upstream authentication and routing configuration patch on part of the infrastructure, being extended to more servers. Not resolved, no time given for a fix.
What caused it
Microsoft has not given a root cause yet. Its updates, in order: elevated load on servers, then servers becoming unavailable; a "core process" on the affected servers overwhelmed, causing a loss of capacity; that process identified as the one handling secure connections; a recent network configuration change being reverted; a surge of calls from routing services to backend servers; and finally a patch to an upstream authentication and routing component, which is the first fix it describes as working. Microsoft executive Charles Lamanna said it was not a cyberattack (reported by CIO&Leader), and Microsoft's own status says: "As of now, we are not aware of any malicious activity that is causing this incident."
Two things made this one long. Recovery came and went: servers that came back at 22:58 UTC stopped answering again once traffic returned, and a second recovery at 04:12 UTC did not hold either. And because Exchange Online sits underneath so much of Microsoft 365, one failing service spread to calendars in Teams, Copilot's access to mail and files, security tools like Defender and admin pages.
How big it was
- Outlook reports on Downdetector peaked at about 130,000 around 1 p.m. ET on 12 November (Techaeris counted 128,874 at 1:09 p.m.; Benzinga, citing Reuters, 138,058 around 1 p.m.).
- Microsoft 365 reports passed 47,000 around 1:20 p.m. ET.
- Reports came from 74 countries and territories.
- Affected organizations named in the news include the US House of Representatives, New Zealand's foreign ministry and embassies, Australian federal police, the NSW online bail court and Service NSW, and NYC Emergency Management. Air India rerouted its email, and Workhorse Group moved its quarterly results to 16 November.
Downdetector counts problem reports from people, not affected accounts; the real number of affected users is far higher.
What to do now
If you use Outlook, Teams or OneDrive at work or school
- It is not you. Do not reset your password, remove your account or reinstall Office: none of that fixes a Microsoft-side outage.
- Classic Outlook on a computer keeps a copy of mail it already downloaded, so older messages may still open.
- Join meetings from links in Teams chats; postpone creating new meetings and events.
- For urgent messages, use a phone call or Teams chat, which Microsoft says largely works.
If you are an IT admin
- Follow incident MO1550821 in the Microsoft 365 admin center under Health, Service health. If the admin center does not load (it is affected too), the public page status.cloud.microsoft and the Microsoft 365 Status account on X carry the same updates.
- Expect delayed mail delivery, failed quarantine releases, Intune enrollment and check-in errors, and Graph calls to mail and calendar timing out. Hold changes and rollouts until Microsoft reports recovery.
- Do not turn off Safe Links or other protection to get around errors; Microsoft lists them as part of the outage.
Questions
Is Microsoft 365 down right now?
As of 07:29 UTC on Friday 13 November, yes: Microsoft rates the incident (MO1550821) "Service degradation" and says users may be unable to connect to multiple Microsoft 365 services. The "Right now" card at the top of this post reads Microsoft's service health page live, every minute.
Is Outlook down for everyone?
Outlook mailboxes on work and school accounts (Exchange Online) are the main problem, in every region. Microsoft's consumer status also lists Outlook.com among the affected services for personal accounts. Some people can still get in, because recovery has come back on some servers and not others.
When will Microsoft fix it?
Microsoft has not given a time. Recovery started and stopped twice overnight. Its latest update reports positive results for server stability after a patch, which it is extending to more servers.
Was it a cyberattack?
Microsoft says: "As of now, we are not aware of any malicious activity that is causing this incident." It has promised a post-incident report with the root cause.
Will I lose emails sent to me during the outage?
Microsoft says email delivery may be delayed, not that mail is lost. Mail servers that send to you normally retry for a while, so most messages should arrive once delivery recovers. If something is urgent, ask the sender to confirm another way.
Does Teams work during the outage?
Mostly. Microsoft says joining calls and meetings, group chats and channel messages are not affected. The Teams calendar, scheduling and editing meetings, live and virtual events, and new private or shared channels fail, because they depend on Exchange Online.
Sources
- Microsoft service health (status.cloud.microsoft)
- Cloud Admin Hub, MO1550821 updates with times
- BleepingComputer
- Techaeris
- Microsoft 365 Status on X
- CNBC
- Reuters, via The Korea Times
- ABC News (Australia) live blog
- ABC7 live updates
- Legal IT Insider
- Benzinga
- RTÉ
- CIO&Leader
- ITdaily
We will update this post as Microsoft posts updates and when it publishes its post-incident report. For live status at any time: Is Microsoft down?
Is It Up or Down is independent and not affiliated with Microsoft. Microsoft, Outlook, Teams and the other product names are trademarks of Microsoft, used here only to identify the products.