Microsoft 365 and Outlook outage: what happened on Nov 12 and what businesses should learn
A timeline of the Nov 12, 2026 Microsoft 365 and Outlook outage, the cause Microsoft has given so far, and practical steps to keep your business running.

On Thursday, 12 November 2026, a large share of Microsoft 365 users could not reach their mailboxes in Outlook. The problem started in the Americas, Microsoft soon warned it could affect other regions, and users also reported trouble with Teams, SharePoint and Copilot.
This post sums up what is confirmed, hour by hour, separates it from the exaggerated claims circulating on social media, and explains how a business can prepare for an outage like this.
This post is based on Microsoft’s status updates and press coverage as of 13 November 2026. Microsoft has not yet published a final root cause or post-incident report.
What happened: the timeline
Microsoft tracks the event in the admin center as EX1550543 (Exchange Online) and MO1550821 (wider Microsoft 365 connectivity). Times are US Eastern (ET):
- 12:54 pm: Microsoft said it was investigating reports that users in the Americas could not access Exchange Online mailboxes “through multiple connection methods”.
- 1:07 pm: The company said the issue might affect Microsoft 365 connectivity for users in any region, not only the Americas.
- Around 1:20 pm: Outlook reports on Downdetector peaked at just over 130,000; Microsoft 365 peaked at about 45,000.
- Early afternoon: Microsoft said the load was not caused by a traffic surge. Instead, a number of servers were unexpectedly unavailable, leaving the remaining servers to carry the traffic.
- 2:50 pm: Microsoft was testing a configuration change for the health-check failures and restarting affected servers.
- 4:00 pm: An alternative health-check method had returned a subset of servers to service, and Microsoft began applying it more broadly. It was also preparing automated recovery to restart unresponsive servers.
- 13 November: Because recovered servers could become unresponsive again under load, Microsoft temporarily limited which types of traffic could reach the affected infrastructure.
According to press reports, Microsoft also paused deployments and moved traffic away from the affected infrastructure. There were signs of improvement by the evening, but Microsoft had not yet declared full recovery.
The cause Microsoft has described
Microsoft’s updates so far describe this chain of events:
- Some Exchange Online servers failed automated health checks and were taken out of service.
- The remaining servers took on their load. A process that sets up secure connections was overwhelmed, and those servers stopped handling requests too.
- Microsoft said it suspected a component that processes server health checks and took steps to stop more servers from failing them.
In short, the problem was not “too many users”. A fault in one infrastructure component turned into a cascading failure: every server that drops out adds load to the rest, and the overloaded ones drop out in turn.
Cyberattack? Microsoft has reported no evidence of malicious activity. The final root cause has not been published yet; we will update this post when the post-incident report is out.
Why the viral “everything is down” lists mislead
Alongside the outage, long lists claiming that AWS, Google, Cloudflare, Zoom, Steam, X and many others were down spread quickly. They are built from Downdetector spikes and should be read carefully:
- Downdetector counts user reports. It does not measure whether a service is actually working.
- When Outlook will not open, people blame Gmail, their ISP or their browser. Big outages always create smaller spikes for unrelated services.
- The confirmed impact was on Microsoft 365. Some users connecting to Google-hosted mail through the Outlook desktop and mobile apps also reported problems; that does not mean Google was down.
To check a service, go to the provider’s official status page and the incident entries in your admin panel first.
The real lesson for businesses: single points of dependency
A platform like Microsoft 365 has very high yearly uptime. Yet a few hours of downtime can stop a company whose email, calendar, files and meetings all hang off the same account. The question is not “is the cloud reliable?” but “what do we do during those few hours?”
Ask yourself:
- If Outlook and Teams go down together, how does the team reach each other?
- If a client’s email never arrives, which channel do we use to tell them?
- Can we reach last week’s critical emails and attachments independently of the provider?
- Who manages our domain and DNS, and can we make changes when we need to?
An outage readiness checklist
- Set up a backup communication channel. Have an emergency group for the team that does not depend on your Microsoft account (phone or a separate messaging app), and a place on your website where you can post a notice for customers.
- Back up your mailboxes. Microsoft 365’s own retention features are not a backup. A regular copy in a separate location helps during an outage as well as after accidental deletion or ransomware. See our Backup & Business Continuity service.
- Keep control of your domain and DNS. Being able to change MX records is a precondition for routing incoming mail elsewhere during a long outage. When we set up Domain & Business Email, we make sure that control stays with your company.
- Watch the status notifications. Route Microsoft 365 service health alerts to a channel other than the IT owner’s mailbox; if email is down, an alert sent by email will not arrive either.
- Write a short outage plan. Who decides, who tells customers, which work can wait. A one-page plan saves hours when people panic.
- Keep offline copies of key files. Synced local copies of frequently used OneDrive and SharePoint documents let part of the work continue during an outage.
As part of Server & IT Management, we can review your current setup together and show how much of it depends on a single point.
Conclusion
The 12 November outage showed that even at one of the world’s largest cloud providers, a single component fault can turn into hours of disruption. According to Microsoft, the cause was not an attack but cascading load from servers failing their health checks. The viral “everything is down” lists do not reflect the confirmed impact.
For businesses, the lesson is not to switch providers but to plan for the outage itself: a backup channel, an independent backup, DNS under your control and a written response plan. If you would like to prepare together, get in touch.
Bu yazı Türkçe olarak da mevcut — Türkçe oku →
Frequently Asked Questions
Nothing Microsoft has said so far points to an attack. The company explained the problem as Exchange Online servers failing automated health checks and unexpectedly going out of service. For the definitive root cause, wait for the post-incident report in the Microsoft 365 admin center.
The long lists shared on social media are based on spikes in Downdetector reports. During a big outage people often blame the wrong service, so unrelated companies see report spikes too; that does not prove they were down. The confirmed impact was on Microsoft 365. Some users who reach Google-hosted mail through the Outlook app were also reported to be affected.
Pick a backup channel for critical communication, back up mailboxes regularly, keep control of your domain and DNS, and write down who does what during an outage. Switching cloud providers is rarely necessary; being prepared makes the real difference.