Microsoft 365, Outlook and Teams went down on November 12. See what failed, what Microsoft says caused it, and what to do when email is down.
If you tried to open Outlook on Thursday and got a spinning wheel, an error message, or nothing at all, you were far from alone. A large Microsoft 365 outage on November 12, 2026 left people around the world unable to send email, open their inboxes, or reach some of the tools they rely on to get through a workday. By Friday morning, the problems were still being worked on.
This post walks through what happened, which services were hit, what Microsoft says went wrong, and what you can do the next time your email and chat vanish at the same moment.
What happened during the Microsoft 365 outage
The trouble started on Thursday, November 12, and the first signs were simple and frustrating. Email would not send or arrive, mailboxes would not load, and some Microsoft apps refused to open. Microsoft said the earliest problems involved Exchange Online, the service that powers Outlook mailboxes, with users in the Americas having trouble connecting. As the day went on, the list of affected services grew.
Outage trackers gave a sense of the scale. Reports for Outlook on Down detector climbed past 130,000 at their peak, and one count reached 138,058. Down detector recorded affected users in 74 countries. As Microsoft worked through the problem, the numbers slowly fell: roughly 59,000 reports by mid-afternoon Eastern time, a little over 37,000 in the early evening, and still more than 25,000 early Friday UTC. Falling numbers did not mean everyone was back, and reports said the disruption had lasted more than eight hours by Friday morning.
Microsoft said the issue could affect Microsoft 365 connectivity for users in any region. That is a notable statement, because most outages hit one data center or one part of the world. This one did not stay put.
Which services were affected
The outage centered on services that depend on Exchange Online. Microsoft pointed out that features not tied to Exchange Online kept working, which is why different people had very different experiences.
Outlook and email
Outlook took the hardest hit. People had trouble reaching their mailboxes on the web, desktop, and mobile apps, and email delivery was delayed. Some users with Google Workspace accounts also reported problems reaching Google-hosted email through Outlook on desktop and mobile. That is a good reminder that the Outlook app can be the point of failure even when the mail service behind it is fine.
Microsoft Teams
Teams fared better than Outlook. Core messaging and online meetings largely kept working. Calendars, meeting scheduling, and chat creation had problems for organizations that use Information Barriers, which are rules that limit who can communicate with whom. Microsoft also listed Teams among the services with possible disruption, so some people did notice trouble.
Copilot and the wider Microsoft 365 family
Microsoft 365 Copilot users had trouble loading Copilot Chat and getting responses, and access to work data such as email, calendars, and files was disrupted. Some people could not open recently used files, and certain admin center pages failed to load. Microsoft's service notices also named SharePoint Online and Defender XDR, along with a longer list that included Planner, To Do, Purview, Graph, Fabric, Power BI, Universal Print, Windows 365, some Intune functions, and several Microsoft 365 Education features.
Third-party tools that connect to Microsoft 365
The ripple effects reached other companies. OpenAI said it was investigating an issue with its Microsoft connectors that could block new connections and cause some tools to malfunction. Anthropic reported an upstream provider issue affecting its Microsoft 365 connector. One company, Workhorse Group, moved its third-quarter results announcement from November 12 to November 16 because of the disruption. When a service this widely used goes down, the damage spreads well beyond the apps themselves.
What Microsoft says caused it
Microsoft has shared a partial explanation, and it has been updating it as the investigation continues. The company said a process responsible for establishing secure connections on affected servers became overwhelmed, and the servers stopped processing requests. Some servers then became unavailable after failing automated health checks, which left the remaining infrastructure under elevated load.
The first assumption many people make is that a surge in traffic did it. Microsoft said otherwise. In its words, the elevated load was not driven by an increase in traffic but by a number of servers being unexpectedly unavailable. Fewer servers were left to handle the same amount of work, and connection errors followed.
Why the health checks failed, and why processor usage rose on those servers, had not been explained when the early reports were published. Microsoft said the failures may originate from a specific component responsible for processing server health. It first said it had not identified any recent change correlated with the start of impact. Later it said it was reviewing a small number of configuration updates as possible contributors, and it was also reversing a recent network configuration change that coincided with the outage's start to see whether it played a part.
Was it a cyberattack?
Microsoft says no. Executive Vice President Charles Lamanna confirmed the outage was not caused by a cybersecurity breach, and the company's service advisories reported no malicious activity. The outage did come two days after November's Patch Tuesday, which included a fix for an Outlook spoofing flaw that Microsoft says attackers have exploited. Microsoft has not linked that flaw to the outage, so treat the timing as a coincidence unless the company says otherwise.
How Microsoft tried to fix it
The recovery work has been methodical, and a little slow, which is common with problems at this scale. According to Microsoft's updates, the company redistributed connection traffic across its worldwide infrastructure paused all deployments and configuration changes as a precaution restarted affected servers and tested an alternative health check method on a subset of them before wider rollout prepared an automated recovery process to detect and restart unresponsive servers limited which types of traffic can reach affected infrastructure in some locations, planning to restore it gradually as things stabilize.
Microsoft also gave a candid warning. Servers that had restarted could become unresponsive again once they started receiving traffic, and one update said recovery efforts were "not taking as expected." That honesty is useful, because it explains why some people saw Outlook come back for an hour and then fail again. Recovery was partial and uneven, and Microsoft had not given a full recovery time in the updates available.
Who felt it most
Office workers were the obvious victims, but the effects went further. In Australia, some public services were affected, and Service NSW asked customers to delay in-person visits and use online services where possible. Some hospitals and healthcare institutions reported clerical problems, though they said patient care was not affected.
For small businesses, the cost is often quieter. A missed email from a client, a delayed invoice, or a meeting that quietly never happened can take days to sort out. For larger organizations, IT teams spent the day answering the same question over and over: is it us, or is it Microsoft?
Not the first time
Outages like this are not new, and users have long memories. Coverage of this event noted that Outlook went down for about 19 to 21 hours worldwide in July of last year, and that in August of this year it took Microsoft 67 hours to fully fix an outage. Each incident has its own cause, so it is not fair to treat them as one long story. Still, the pattern shows why businesses that run everything through one provider keep asking about backup plans.
What to do when Outlook, Teams, or Microsoft 365 goes down
You cannot fix a Microsoft-side outage, but you can make it less painful. Here is a practical checklist.
Confirm it is an outage first
Before you reset your password or reinstall anything, check whether the problem is widespread. Look at an outage tracker like Downdetector and Microsoft's own service status. During this outage, Microsoft's status page was hard to load, so following the Microsoft 365 Status account on X was a more reliable way to get updates.
Admins: check the Microsoft 365 admin center
If you manage a Microsoft 365 tenant, open the service health section of the admin center. For this event, Microsoft referenced incident IDs EX1550543 for the Exchange Online disruption and MO1550821 for the broader Microsoft 365 incident. Tracking those IDs lets you give your staff accurate updates instead of guesses.
Switch to another way of communicating
If Teams meetings still work, use them. If they do not, fall back on phone calls, text messages, or another approved chat tool. Tell clients that email may be delayed so they do not assume you are ignoring them.
Back up your contacts
One practical tip from outage coverage is to export your Outlook contacts to a CSV file. In Outlook, go to Open and Export, choose Import/Export, select Export to a file, pick Comma Separated Values, and finish the wizard. The file can be imported into services like Gmail or Yahoo Mail. This will not help people who must use Outlook for a work account, but it is a cheap safeguard for personal use.
Avoid piling on the problem
Repeatedly signing in, resetting accounts, or restarting servers can add load or create new issues, especially if the real cause is on Microsoft's side. Wait for official updates before making changes you cannot easily undo.
How businesses can prepare for the next outage
No cloud service is immune, and the best time to plan is before something breaks. A few habits make a big difference:
Keep an offline list of key client and team phone numbers.
Agree in advance on a backup channel for urgent messages.
Write a short outage playbook that says who checks status, who informs staff, and who contacts customers.
Know which of your tools depend on Exchange Online or Microsoft 365 connectors, since those can fail together.
Review any service agreement or credit terms with your provider so you know what to expect.
Outages also expose hidden dependencies. This one affected AI tools and connectors that many teams had stopped thinking about, which is a good reason to map out what really depends on what.
What to watch for next
Two questions remain open. The first is a full explanation: why the health checks failed, why processor usage rose, and whether a configuration change played a role. Microsoft typically publishes a post-incident review after major events, and that report should answer those questions. The second is whether recovery holds, since Microsoft warned that restarted servers could fail again once traffic returns.
If you are still seeing problems, check Microsoft's official channels for the latest status, because the situation may have changed since this post was written.
Final thoughts
A big outage is a bad day for anyone who depends on email and chat, and November 12 was one of those days. The encouraging part is that Microsoft ruled out a cyberattack, kept sharing technical details as it learned them, and paused risky changes while it worked. The less comfortable part is how many other tools and organizations went down with it. Keep a backup channel handy, know where to check status, and expect that the next outage will happen eventually.
Frequently asked questions
Why was Outlook down on November 12, 2026?
Microsoft said a process that sets up secure connections on affected servers became overwhelmed, and some servers failed automated health checks and became unavailable. That left fewer servers to handle connections, which caused errors and delays. The deeper root cause had not been fully explained in early reports.
Which Microsoft services were affected?
Outlook and Exchange Online were hit hardest. Microsoft also listed Teams, SharePoint Online, Microsoft 365 Copilot, and Defender XDR, and reports described problems with services such as Planner, To Do, Purview, Power BI, and Windows 365.
Was Microsoft Teams down?
Core Teams messaging and online meetings largely kept working. Calendars, meeting scheduling, and chat creation had problems for organizations using Information Barriers, and some users still reported trouble.
Was the outage caused by a cyberattack?
No. Microsoft executive Charles Lamanna confirmed it was not caused by a cybersecurity breach, and the company's advisories reported no malicious activity.
How many people were affected?
Downdetector showed Outlook reports peaking above 130,000, with users in 74 countries. Those figures reflect user reports, not an official count of affected accounts.
Is Microsoft 365 working again?
Recovery was partial and uneven in the reports available. Microsoft had not given a full recovery time and warned that restarted servers could fail again when traffic returned. Check Microsoft's official status channels for the latest update.
What are the Microsoft incident IDs for this outage?
Microsoft referenced EX1550543 for the Exchange Online disruption and MO1550821 for the broader Microsoft 365 incident in the admin center.
Where can I check Microsoft 365 service status?
Admins can use the service health page in the Microsoft 365 admin center. Everyone can check outage trackers like Downdetector and follow the Microsoft 365 Status account on X, which was easier to reach than the status page during this outage.
What should I do while Outlook is down?
Confirm the outage, avoid repeated sign-ins and resets, switch to a backup channel such as phone calls or another chat tool, and let clients know email may be delayed. Exporting your contacts to a CSV file beforehand is a useful safeguard.
How can businesses prepare for a future Microsoft 365 outage?
Keep offline contact lists, agree on a backup communication channel, write an outage playbook, and map which tools depend on Microsoft 365 services so you know what could fail together.
References
Business Standard - https://www.business-standard.com/technology/tech-news/microsoft-365-outage-continues-as-company-sees-limited-recovery-in-services-126111300464_1.html
SecurityWeek, - https://www.securityweek.com/microsoft-365-outage-disrupts-outlook-exchange-online-and-teams/
Tom's Guide - https://www.tomsguide.com/news/live/microsoft-outlook-down-live-updates-outage-11-12-26
