Microsoft 365 Outage Hits 430 Million Users Worldwide

Published (Updated )

Microsoft 365 Outage Hits 430 Million Users Worldwide
For a lot of people, the working day starts in Outlook. Email is checked first, the calendar is checked second, and Teams is opened soon after. On Thursday 12 November 2026, that routine broke for a large number of users around the world. Outlook would not load properly, Teams had problems, and other Microsoft 365 services were affected too.
The outage began on Thursday 12 November 2026. It was first reported at about 7:40am PT, which was 10:40am ET, when Microsoft said it was probing Teams problems in North America. From there, the reports spread. What started as a problem in one region became a worldwide outage that lasted for over a day. Microsoft 365 has over 430 million users, so when a service used by that many people has a bad day, the effects show up in offices, schools, hospitals and homes, often at the same time.

When the outage started
The first public sign came on Thursday morning in the United States. At about 7:40am PT, or 10:40am ET, Microsoft said it was looking into Teams problems in North America. For many users, that was the first they heard that something was wrong. For others, the first sign was simpler. Outlook would not open, or it would open and then stop working. Messages would not send, and inboxes would not load.
As the morning went on, the picture became wider. It was not only Teams, and it was not only North America. Reports came in from other regions as well. People in different time zones were hitting the same problems at different points in their working day. Some were starting work and could not get into their email. Others were in the middle of the day and lost access to files and meetings. Microsoft kept updating its status pages as the day went on, and later said recovery efforts were not going as expected at one point. That is a plain way of saying the fix was taking longer than planned.
How big the outage was
The size of the outage can be seen in the user reports collected by Downdetector. At the peak, there were about 130,000 Outlook reports and about 50,000 Microsoft 365 reports. Those are reports from users, not a count from Microsoft itself. They show how many people took the time to say the service was down, and they rose sharply as the outage spread. Reports came from 74 countries, which shows the outage was not limited to one country or one region.
Microsoft 365 has over 430 million users. Microsoft reported that paid commercial seats exceed 450 million in January 2026, and the 430 million figure is used here for users. Even a small share of those users hitting a problem at the same time would mean a large number of people affected. The Downdetector figures, with more than 100,000 Outlook reports at the peak, point to a widespread problem, not a small one.
The effects were not only in offices. In India, SpiceJet reported three flight cancellations. Hospitals in Canada and services in Australia were also affected, according to reports. Those examples show how a cloud outage can reach beyond email and meetings. When a service is used by airlines, hospitals and other organisations, a problem with that service can affect travel and care as well as office work.

What stopped working
Outlook was one of the main services affected. People reported that they could not open their inbox, could not send email, or could not get into their mailbox at all. For many workers, that is the first problem that matters. Email is still how a lot of business gets done, from client messages to internal updates to meeting invites. Teams was also affected, and that matters because Teams is where many people hold meetings, send quick messages and share files during the day.
Copilot was affected too. Copilot is Microsoft's AI assistant in Microsoft 365, and it is built into the tools people use for writing, summarising and working with documents. When Copilot is down, people lose that help, and they have to do the work by hand. The list of affected services was long. It included Exchange Online, SharePoint Online, OneDrive, Word, Excel, PowerPoint and Defender XDR, as well as Outlook, Teams and Copilot. Exchange Online is the service behind business email. SharePoint Online and OneDrive are where files are stored and shared. Word, Excel and PowerPoint are the document apps many people use every day. Defender XDR is a security service. When so many services are listed together, it is a sign that the problem was in the shared systems behind them, not in one app alone.
What Microsoft said caused it
Microsoft said there was no evidence of malicious activity, and that the outage was not a cyberattack. The company also said it was not related to cyber or AI, or to agents. That point matters, because a large outage often leads to quick guesses about hacking or about a new AI feature going wrong. In this case, Microsoft was clear that neither of those was the cause.
Instead, Microsoft said the issue was introduced during an earlier network capacity upgrade, and that it surfaced after a recent network change. In plain terms, a change made to the network, as part of work to add capacity, led to a problem that showed up later. The company also said there was elevated load on infrastructure. That means the systems were under more pressure than usual, which can make a problem worse once it starts. Microsoft said it paused deployments, moved traffic and restarted servers. Pausing deployments means stopping further changes while the problem is fixed. Moving traffic means sending users to systems that are working better. Restarting servers is a common step to clear a fault and get a service back to a known good state.
As of 13 November, Microsoft had not yet shared a full postmortem or a definitive root cause. A postmortem is the detailed report a company writes after an outage, explaining what happened, why it happened, and what will change to stop it happening again. Until that report is published, the full story is not yet known. The early explanation about a network capacity upgrade and a recent network change is what Microsoft has shared so far, not the final word.
The slow return to normal
By Friday 13 November in the afternoon, most services were back or recovering. That is a welcome change from Thursday, but it does not mean everything was back to normal for everyone at once. Recovery from a large outage is often uneven. Some people get back in quickly. Others wait longer, or find that some features work while others do not. The Downdetector numbers show that fall. Outlook reports fell to just over 3,000 by 11:57am ET on Friday, and to under 2,000 before 3pm ET. That is a large drop from the peak of about 130,000 reports.
Even so, some users still had delayed email and mailbox access on Friday. Delayed email means messages arrive later than they should. Mailbox access problems mean people still cannot get into their inbox, or cannot do everything they normally do there. Those are the kinds of problems that linger after the main outage is over. The service may be back for most people, but a smaller group can still be waiting. For people who depend on email for their work, even a delay can be a problem. A message that arrives hours late can miss a deadline, or leave a client waiting.
Teams and Copilot, and why they matter
Teams and Copilot deserve a closer look, because they show how much has changed in how people work. Teams is not only a chat app. For many companies, it is where meetings happen, where files are shared, and where quick questions are asked during the day. When Teams is down, that whole way of working is interrupted. Copilot is newer, but it is already part of the daily routine for some users. It helps with writing, summarising documents and finding information. When Copilot is down, people lose that help.

The outage also shows how much depends on a small number of large cloud services. Microsoft 365 is one of those services. It is used by businesses, schools, hospitals and government offices, as well as by individuals. When it has a problem, the problem is felt in many places at once. For businesses, the lesson is practical. It is worth having a backup way to reach people when email and Teams are down, and worth checking, after the service is back, whether any messages were delayed or missed.
For Microsoft, the lesson is about the network changes that led to the problem. The company said the issue was introduced during an earlier network capacity upgrade and surfaced after a recent network change. Until the full postmortem is published, it is not clear what exactly went wrong, or what will change. What is clear is that a change meant to add capacity ended up causing a worldwide outage. The outage on 12 November 2026 will be remembered as a day when Outlook, Teams and Copilot were down for many people, for over a day. The numbers tell part of the story: about 130,000 Outlook reports at the peak, reports from 74 countries, and a user base of over 430 million people. The rest is in the small details: the email that did not arrive, the meeting that could not be joined, the flight that was cancelled, and the work that had to wait until Friday afternoon.
FAQs
When did the Microsoft 365 outage start?
The outage began on Thursday 12 November 2026. It was first reported at about 7:40am PT, or 10:40am ET, when Microsoft said it was probing Teams problems in North America.
Which services were affected by the outage?
Outlook, Teams, Copilot, Exchange Online, SharePoint Online, OneDrive, Word, Excel, PowerPoint and Defender XDR were affected.
How many users does Microsoft 365 have?
Microsoft 365 has over 430 million users. Microsoft reported that paid commercial seats exceed 450 million in January 2026.
How many outage reports were recorded on Downdetector?
At the peak, Downdetector recorded about 130,000 Outlook reports and about 50,000 Microsoft 365 reports, with reports from 74 countries.
Was the outage caused by a cyberattack?
No. Microsoft said there was no evidence of malicious activity, and that the outage was not a cyberattack. It also said it was not related to cyber or AI, or to agents.
What did Microsoft say caused the outage?
Microsoft said the issue was introduced during an earlier network capacity upgrade and surfaced after a recent network change, with elevated load on infrastructure. It paused deployments, moved traffic and restarted servers.
When were services back to normal?
By Friday 13 November in the afternoon, most services were back or recovering. Downdetector Outlook reports fell to just over 3,000 by 11:57am ET on Friday and under 2,000 before 3pm ET, though some users still had delayed email and mailbox access.
Was this article helpful?

Written By
TechorCoffeeContributing Writer
TechorCoffee is a technology reporter and software creator writing reviews and tutorials for TechOrCoffee.
Comments (0)
Leave a Comment
Read Next

Tue Oct 13 2026
Apple iPhone Duo Price in the US and Europe (2026)
Compare Apple iPhone Duo prices in the US and Europe for 2026. Explore storage options, pricing in USD and EUR, key features, and release date.

Mon Oct 26 2026
Instagram Now Available on Apple TV: Check Out the Details
Social Media will be featured on your home screens! People can now scroll reels and watch videos in their living space with just one step.

Sat Nov 14 2026
Samsung Smart Glasses Open Pre-Orders With Gemini AI
Samsung's Android XR smart glasses opened for pre-order on 12 November with Gemini AI, a camera and no display. What they do and who they suit.