Your inbox stopped working in the middle of the workday — and it was not your computer, your Wi-Fi, or your password. On Thursday, November 12, 2026, Microsoft 365 went down across the Americas and then worldwide, locking businesses out of Outlook, Teams, SharePoint, Copilot and more. Google Trends tells the story of the scale: “microsoft outage” hit #1 in the United States with more than 2 million searches, up over 1,000%, and “outlook” trended in the UK, Germany, Spain, Italy and the Netherlands at the same time.
This is a developing story — Microsoft had not confirmed a root cause or a restoration time as of mid-afternoon — but what is already confirmed is enough to act on. Here is what happened, what Microsoft has actually said, and the seven checks every business should run this week.
1. What happened: the timeline so far
The outage hit right in the middle of the North American workday. User reports on Downdetector, the outage-tracking site, began climbing at around 12:39 p.m. ET. By 1:09 p.m. ET, reports about Outlook alone had peaked at 128,874. Reports about Microsoft 365 as a whole peaked at more than 47,000 at around 1:20 p.m. ET, Teams drew about 2,000 reports and Copilot about 4,400 near 1 p.m. Reuters, reporting later in the afternoon, counted more than 97,000 Outlook reports at 2:07 p.m. ET, more than 38,000 for Microsoft 365 and about 4,500 for Teams.
Microsoft acknowledged the problem publicly at 12:54 p.m. ET through its Microsoft 365 Status account, saying it was investigating reports of users having issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. At around 1:07 p.m., the company widened the scope: the issue may affect Microsoft 365 service connectivity for users in any region. Reports from France put the first surge there at around 6:30 p.m. Paris time.
One caveat on the numbers: Downdetector counts user reports, not confirmed failures. The figures measure how many people hit a problem and reported it, not the total number of affected users — which Microsoft has not disclosed. Even so, a six-figure report count in under an hour is the signature of a very large outage, not a local glitch.
2. What actually broke: it was not just email
Outlook was the most visible symptom, but the incident went much wider. Microsoft is tracking it under two incident IDs in the Microsoft 365 admin center: EX1550543 for Exchange Online mailbox access, and MO1550821 for broader Microsoft 365 connectivity.
Services named in Microsoft’s advisories and in press coverage include:
- Exchange Online — the cloud email service behind Outlook, unreachable through Outlook on the web, the desktop app, mobile sync, and third-party apps using MAPI, Exchange ActiveSync (EAS) and the REST API.
- Microsoft Teams — hit by the same incident, after a separate Teams disruption in North America earlier in the day that Microsoft said had been fully resolved.
- SharePoint Online and OneDrive — file access affected alongside mail.
- Microsoft Copilot 365 — the AI assistant went down with the suite it sits on.
- Microsoft Defender XDR — the security console was listed among the potentially impacted services.
- Office apps and the Microsoft 365 admin center itself — the very dashboard administrators use to check service health was reported unreachable at points, and Microsoft’s own public status page was reported unavailable at times during the disruption.
Reuters also reported that the disruption hit connectors used by OpenAI’s and Anthropic’s AI services — a reminder that a Microsoft outage now ripples into the AI tools businesses increasingly depend on.
3. What Microsoft says caused it — and what it has not said
Microsoft’s explanation so far is careful and incomplete. The company said it had identified connectivity errors affecting a portion of the Exchange Online infrastructure responsible for receiving and processing user access requests, and that it was collecting networking logs to determine the source. By around 1:35 p.m. ET, it added a working theory: “a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors,” and that it was “reviewing an unexpected increase in a specific type of service traffic to determine whether it’s contributing to the elevated load.”
What Microsoft has not said matters just as much:
- No confirmed root cause. Elevated load and unusual traffic are a working theory, not a final answer. The same phrasing is equally consistent with a configuration error, a runaway internal process, or a flood of malformed requests from outside — Microsoft has not named one.
- No cyberattack attributed. Microsoft has not attributed the outage to a cyberattack, and no threat actor has claimed it. Searches for “microsoft cyber attack” spiked during the outage, but that is speculation, not evidence.
- No restoration timeline. As of mid-afternoon, Microsoft had not published a confirmed time for full service restoration.
Mitigation steps Microsoft has confirmed: all deployments and configuration changes paused as a precaution, connection traffic redistributed across its broader worldwide infrastructure (begun at around 1:48 p.m. ET), and affected servers restarted. Treat any cause or fix timeline you see on social media as unconfirmed until Microsoft posts a final incident summary.
4. Why this outage hit harder than a normal one
Three things made November 12 worse than a typical service blip.
First, the timing. The outage peaked between 1 and 2 p.m. ET — prime working hours across North America and the end of the working day in Europe. Email, chat and files all failed at once, so there was no easy fallback inside the same suite.
Second, email is the business nervous system. For most small businesses, Outlook is not just email: it is client communication, appointment confirmations, invoices, order updates and password resets. When Exchange Online stops, the business does not just lose a tool — it loses its connection to its customers for the duration.
Third, the AI layer went down too. Copilot 365 was listed among the affected services, and connectors used by OpenAI’s and Anthropic’s AI services were disrupted. Businesses that have built workflows on top of Microsoft’s AI — drafting, summarising, answering — discovered that their AI assistant shares the same single point of failure as their inbox. That is a new kind of dependency, and it failed on its first big test of the day.
There is also an uncomfortable detail: the admin center — the tool businesses use to verify an outage — was itself reported unreachable at points. When the status page cannot be reached, teams waste the first hour arguing about whether the problem is theirs.
5. The pattern: this is the third big cloud lesson in a month
November 12 is not an isolated incident. On October 20, 2026, a Google Cloud outage in its London region knocked Revolut payments offline across Europe — card payments, transfers, ATM withdrawals and sign-ins — with more than 1,500 Downdetector reports. That outage was traced to a power event in the region. Now, less than a month later, Microsoft’s turn has arrived.
The pattern is the lesson: every major cloud provider fails, and the failures are getting closer together. Google in October, Microsoft in November. The question is not which provider is safe — none of them is — but what your business does when its provider has a bad afternoon.
Two other context points from this week are worth separating from the outage itself. Microsoft released a fix on November 10, 2026, for an Outlook flaw that was already being exploited, and CISA added it to its known exploited vulnerabilities list. That is a security patch, not the cause of today’s outage — do not confuse the two. And the outage is a different event from the Google Cloud incident and from the Android botnet takedown Google announced on November 2. Same month, same theme, different failures.
6. Locked out right now? Do this first
If your team is still unable to reach Outlook or Teams, work the problem in this order:
- Confirm it is Microsoft, not you. Check the Microsoft 365 admin center Service Health panel under incident EX1550543, or the Microsoft 365 Status account. Do not restart servers, reset passwords or rebuild mail profiles — none of that fixes a cloud-side outage, and mass password resets during an outage create a second problem.
- Switch to a backup channel and say so. Post a short notice on your website, your Google Business Profile or your social accounts: email is down, here is how to reach us instead. Customers forgive a delay they understand; they do not forgive silence.
- Use a channel outside Microsoft. A personal Gmail, a phone call, WhatsApp Business or SMS — whatever your customers actually use. The point of a backup channel is that it does not share the same provider as the thing that failed.
- Do not assume data is lost. An Exchange Online connectivity failure means mailboxes are unreachable, not deleted. Messages sent to you during the outage are normally queued and delivered once service returns. Tell your team that, so nobody starts “fixing” things by deleting accounts.
- Keep a written log. Note the time your team lost access and the time it returned, per person. You will need it for any service-credit claim and for your own post-incident review.
- Watch for phishing. Outages are prime phishing season: fake “your mailbox is full” and “reconnect your account” emails spike within hours. Remind the team not to click any link promising to restore access.
7. The 7 resilience checks to run this week
Once service is back, do not just move on. The businesses that survive the next outage are the ones that treat this one as a drill. Run these seven checks:
- Own your domain and DNS. Your business email should run on a domain you control, with DNS you can change. If your provider fails, you need the ability to point mail elsewhere — that option does not exist if a vendor owns your domain.
- Keep a second way to reach every customer. A phone number list, a WhatsApp Business account, or a second email provider. If every customer contact lives only inside Outlook, one outage cuts every line at once.
- Export what you cannot afford to lose. A regular export of key contacts, open orders and active conversations, stored outside Microsoft 365. Not a full backup strategy — a lifeboat.
- Write the outage page now. A short, pre-written notice for your website and social accounts: “Our email is temporarily down. Reach us here instead.” Writing it during an outage, while the admin center is unreachable, is too late.
- Check your Microsoft 365 contract. Know your plan’s service-level agreement and how to claim service credits after an outage. Most small businesses never read the SLA until they need it.
- Separate your AI from your inbox. If your AI assistant, chatbot or automation only works when Microsoft 365 works, it has the same single point of failure. Map which of your AI tools depend on Microsoft services and which do not.
- Run a 30-minute drill. Once this quarter, simulate an email outage for half an hour: team switches to the backup channel, the notice goes up, one person logs the timeline. The next real outage then costs you minutes, not a day.
8. What to watch next
Three things will tell you how serious this incident really was. First, Microsoft’s final incident summary — the root cause, how long the outage lasted, and how many customers were affected. Until that is published, treat every explanation as provisional. Second, whether the “unexpected increase in a specific type of service traffic” turns out to be internal or external — that distinction decides whether this was an engineering failure or an attack, and Microsoft has not answered it yet. Third, the service-credit process — if your business lost a working day to this outage, check the Microsoft 365 admin center for the incident record and your plan’s SLA terms.
One more thing to watch: Microsoft’s next scheduled update was expected later in the afternoon. If service is not fully restored by the time you read this, check the admin center under EX1550543 rather than trusting social media for the current status.
The Bottom Line
On November 12, 2026, Microsoft 365 — email, Teams, SharePoint, Copilot and the admin tools themselves — went down in the middle of the workday, with Outlook reports peaking at nearly 129,000 in a single hour and the problem spreading from the Americas to the rest of the world. Microsoft blames elevated load on part of its infrastructure and an unexpected traffic spike; no root cause is confirmed and no cyberattack has been attributed. The outage is a reminder that arrived twice in one month: Google Cloud in October, Microsoft in November. Your business cannot prevent the next cloud outage. It can decide, this week, whether the next one costs it a day or an hour.
If your business runs on Microsoft 365 and today exposed a gap — no backup channel, no outage notice, no exported contacts — that is exactly the kind of resilience work we do. Book a free consultation and we will map your single points of failure and fix the cheap ones first.
Sources: Reuters (Nov 12, 2026); Techaeris (Nov 12, 2026); Neowin (Nov 12, 2026); How-To Geek (Nov 12, 2026); Sortiraparis (Nov 12, 2026); Impress Computers (Nov 12, 2026); Google Trends “microsoft outage” (US #1, 2M+, +1,000%, Nov 12, 2026); Microsoft 365 Status (@MSFT365Status), incidents EX1550543 and MO1550821. Downdetector figures count user reports, not confirmed affected users. This is a developing story: Microsoft had not confirmed a root cause or a restoration time as of mid-afternoon on Nov 12, 2026.
Related reading: One Cloud Region Went Down and Europe’s Banks Stopped Working: 7 Resilience Lessons for Your Business (2026) · Google Just Took Down a 1.3 Million-Device Android Botnet Hidden in TV Boxes (2026) · Binance Just Lost $6.3 Billion in the Largest Crypto Hack Ever (2026) · How to Build an AI Chatbot for Your Website in 2026
