Microsoft 365 Outage Leaves Outlook and Teams Down Worldwide for a Second Day
Millions of people started their Friday without email. A Microsoft 365 outage that began on Thursday afternoon is still disrupting Outlook, Teams and Copilot around the world, and Microsoft has not said when full service will return.
The problem sits in Exchange Online, the service that runs business email in Outlook. Because so much of Microsoft 365 depends on it, the failure has spread into calendars, meeting scheduling, file access and the company's AI assistant. Microsoft's status page still lists the incident as "service degradation" on Friday morning, more than 18 hours after the first reports.
Downdetector, which tracks user reports of outages, recorded about 130,000 reports for Outlook shortly after 1 p.m. Eastern on Thursday, according to the Associated Press. Reuters put the peak slightly higher, at just over 138,000. Reports came in from 74 countries, and the disruption reached hospitals, police forces, schools, government offices and small businesses.
What stopped working — and what still works
The outage hits hardest where email is involved. Users may be unable to open their mailboxes in Outlook on the web, on desktop or on phones, and email delivery may be delayed. Anything that needs Exchange Online is affected, including Teams calendars, meeting invitations and scheduling, Copilot's access to mail, calendars and files, and some admin and security tools.
Not everything is down. Microsoft says Teams calls, meetings, chats and channel messages are largely working, and files stored directly in SharePoint can still be opened. If you already have a meeting link, it should still work. The split has confused a lot of users: Teams looks fine until they try to book a meeting or check a calendar, and then it fails.
Japan confirmed a significant impact on government IT systems, and in Britain the outage affected GP surgeries, pharmacies, schools, police forces and Parliament, according to local reports. Microsoft has extended its email timeout window to 48 hours, a step meant to protect messages that are stuck in the backlog while systems recover.
How the outage unfolded
Microsoft's own service health record puts the start of the Exchange incident, tracked as EX1550543, at 11:17 a.m. Eastern on Thursday. A separate, earlier Teams incident ran for about an hour that morning and was resolved before the bigger failure took hold. By early afternoon, the reports were pouring in, and Microsoft opened a wider advisory, MO1550821, covering Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR.
Through Thursday evening and into Friday, the picture barely changed. Microsoft said a number of its servers had become unexpectedly unavailable and the remaining infrastructure buckled under the extra traffic. The company traced the trouble to failed automated health checks on some servers and said it was reverting a recent network change that lined up with the start of the problems, while also adding virtual machines to build up capacity.
In an update on Friday morning, Microsoft said it was seeing early signs of stabilization as it carefully brought traffic back, but capacity had not returned to normal and service health was still variable. Repairs in parts of the Asia Pacific region were improving mailbox access and helping delayed emails move through the system, the company said. No full root cause has been published, and Microsoft has promised a full report once the incident is closed.
What Microsoft has said about the cause
Microsoft has said it is not aware of any malicious activity, and a company spokesperson told the Australian Broadcasting Corporation there was no indication the outage was a cyberattack. That matters because an outage of this size, on this scale, invites speculation. So far, everything Microsoft has described points to an internal failure: servers dropping out of service, health checks failing, and a network change that had to be rolled back.
The company has not given a time for full recovery. Its updates describe a careful process of reintroducing traffic in stages, which means some users may see service return while others wait. The advice from IT specialists is consistent: do not reset passwords, rebuild Outlook profiles or reinstall Office. Nothing on the user's side will fix this, and reinstalling software while the service is down can make the recovery messier.
For businesses, the practical step is to check Microsoft's public status page at status.cloud.microsoft, which the company set up for exactly this situation, since some administrators cannot get into the admin centre while the outage is running.
Why it matters
Outages happen. What makes this one hard to ignore is how much of the working day now runs through a single company's cloud. Email is still the spine of most offices, and when it goes down, it takes the calendar, the meeting invites and the AI assistant with it. A company that cannot send email cannot confirm a delivery, close a sale, or tell a patient their appointment has moved.
The timing adds to the damage. The outage began on a Thursday afternoon, which meant the backlog was still there on Friday morning, and for users in Asia and Australia, the working day was already under way when the worst of it hit. Hospitals and police forces do not have the luxury of waiting for a status page to turn green.
There is also a question Microsoft will have to answer once the incident closes: how did a network change take down servers across regions, and why did the recovery take more than a day? The company has promised a root-cause report. For the millions of users who spent two days refreshing their inboxes, that report will be worth reading.
It was a rough week for big tech all round. On the same day the outage began, Nvidia's chief executive resigned after 33 years at the company: Jensen Huang Resigns as Nvidia CEO After 33 Years; Shares Drop as Much as 14%. For the backstory on how that crisis reached the boardroom, read our report from yesterday: Nvidia Board Weighs Ousting CEO Jensen Huang After Second Affair Report and China Spy Claims.
Sources
- MacRumors — Major Microsoft 365 Outage Continues
- EpiFive — Microsoft Outage Today: Outlook, Teams Down — Status and Fixes
- Datafloq — Microsoft 365 Outage: Failing Server Health Checks Took Down Outlook, Teams and Copilot
- Dijitul — Microsoft 365 Outage: What To Do Now
- My Tech Team — Microsoft 365 Outage: What We Know and What to Do Now
Published November 13, 2026. The outage began Thursday, November 12, 2026, and was still listed as "service degradation" on Friday morning, November 13, 2026.

Comments