Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)
ReleaseInsight · On RadarZDNet AI→ original

Microsoft outage: nearly 83,000 Outlook complaints on Downdetector, Teams and Copilot down too

On Thursday, November 12, Microsoft's Outlook, Teams, OneDrive and Copilot went down at the same time. The number in the headline is the count of user complaints on Downdetector: nearly 83,000 for Outlook, under 26,000 for Teams later on, and under 2,000 for Copilot. Microsoft says traffic did not spike. Instead, some servers dropped out, and the remaining ones could not handle the load. That is why teams need a backup communication channel outside Microsoft.

AI-processed from ZDNet AI; edited by Hamidun News
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceZDNet AI ↗
Editor-in-Chief
Key metric #110:40 ET: Microsoft acknowledged the problem. At 12:00 ET, it announced a fix.
At 1421 ET, the status page still wasn't loading. ZDNET was only able to open it at 15:05 ET.
Key metric #3All rollouts are paused, and the affected servers are being restarted.

On Thursday, November 12, Microsoft's Outlook email, Teams chat, OneDrive cloud storage and Copilot assistant all stopped working at once. For many companies, that means a lost workday: emails don't send, calls don't connect, and files won't open. The number in the headline, nearly 83,000, is the count of Outlook complaints on Downdetector. That is a service where people report outages themselves: the more complaints, the wider the problem. It is not the number of failed servers or affected companies. It is a handy indicator of scale and trend.

What we know about the scale of the outage

At first, it looked like the problems were limited to Microsoft 365 and access to Outlook. Later, it became clear the outage was broader. Starting in the morning Eastern Time (ET), users began reporting problems with Outlook, Teams and Copilot. By 13:00 ET, Outlook complaints had reached nearly 83,000, and by 14:38 ET, they had dipped to just under 75,000. Teams complaints rose to just under 26,000, and Copilot complaints to just under 2,000.

The timeline looked like this:

  • 10:40 ET: Microsoft posted on X that it was investigating the problem.
  • 12:00 ET: The company said the issue had been resolved.
  • 13:43 ET: In the replies under that post, users were still reporting that Teams, Outlook and OneDrive weren't working.

ZDNET spoke with a employee at a law firm who uses Outlook. By 14:00 ET, she could neither send nor receive email. Searching her mailbox and opening older messages still worked. Her email last worked normally at 12:44, roughly 40 minutes after Microsoft's statement about the fix. Her firm told her the outage was global.

What Microsoft itself says

Later, the company gave a more specific explanation. According to Microsoft, the elevated load did not come from a rise in traffic. Some servers unexpectedly became unavailable, and the remaining infrastructure could not keep up with requests. It's like a supermarket where five of ten checkouts suddenly close: the number of shoppers stays the same, but the lines at the open registers grow.

Microsoft has paused all update rollouts and is restarting the affected servers to safely bring them back into service. The company pointed users to the Microsoft 365 admin center for details, under incident IDs EX1550543 and MO1550821. If the admin center is unavailable, there is the status page at status.cloud.microsoft.

Why the servers dropped out remains unknown. ZDNET explicitly notes that no cause has been named. Without one, repeat failures cannot be ruled out.

There is also an unpleasant detail: Microsoft's status page itself was still not loading at 14:21 ET, and ZDNET only managed to open it at 15:05. When the official source of information goes down along with the service, administrators are left searching social media for news.

What teams should do

A cloud office platform remains a single point of failure, even when it is run by one of the largest vendors. A few practical steps:

  • Choose a backup communication channel for your team in advance, such as Slack, Telegram or a phone bridge. Agree on it before an outage, not during one.
  • If you build products or agents on top of Outlook, Teams or Copilot, plan for degradation: retry queues, clear user-facing messages, and timeouts instead of endless waiting.
  • Subscribe to alerts not only on the status page but also on X and in the Microsoft 365 admin center.
  • For critical processes, such as legal deadlines or client mailings, keep a workaround plan that doesn't depend on email.

ZDNET's coverage is marked as a developing story. Details about the cause of the outage and full recovery may change, so rely on Microsoft's official updates.

Story

Key Questions Answered

What we know about the scale of the outage?

At first, it looked like the problems were limited to Microsoft 365 and access to Outlook. Later, it became clear the outage was broader. Starting in the morning Eastern Time (ET), users began reporting problems with Outlook, Teams and Copilot. By 13:00 ET, Outlook complaints had reached nearly 83,000, and by 14:38 ET, they had dipped to just under 75,000. Teams complaints rose to just under 26,000, and Copilot complaints to just under 2,000.

What Microsoft itself says?

Later, the company gave a more specific explanation. According to Microsoft, the elevated load did not come from a rise in traffic. Some servers unexpectedly became unavailable, and the remaining infrastructure could not keep up with requests. It's like a supermarket where five of ten checkouts suddenly close: the number of shoppers stays the same, but the lines at the open registers grow. Microsoft has paused all update rollouts and is restarting the affected servers to safely bring them back into service.

What teams should do?

A cloud office platform remains a single point of failure, even when it is run by one of the largest vendors. A few practical steps: Choose a backup communication channel for your team in advance, such as Slack, Telegram or a phone bridge. Agree on it before an outage, not during one. If you build products or agents on top of Outlook, Teams or Copilot, plan for degradation: retry queues, clear user-facing messages, and timeouts instead of endless waiting.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Hands-On AI Engineering · Hamidun Academy

Build & Ship Production AI Agents Without Boilerplate Code

Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.

Start 72h Free Trial →Vibe-Coding Intensive
What do you think?
Loading comments…