Microsoft 365 outage: Outlook failure reports topped 130,000

DownDetector logged more than 130,000 Outlook failure reports on Thursday, with the peak hitting 7,941 complaints at around 3 p.m., as Microsoft's flagship email service went unstable for much of the day.

The disruption did not stay contained. Microsoft Teams, the company's AI assistant Copilot and the Microsoft Store all registered failures on DownDetector during the same period. By early evening, users were still struggling to reach Outlook, according to the outage-tracking site.

The trouble began in the early afternoon, when DownDetector counted 6,793 email-service failure reports. A Microsoft profile on X, the former Twitter, confirmed the problem: "Embora estejamos trabalhando para mitigar o impacto, confirmamos que o problema pode afetar a conectividade do serviço Microsoft 365 para usuários em qualquer região" — in English, "While we are working to mitigate impact, we confirm the issue may affect Microsoft 365 service connectivity for users in any region."

What did Microsoft say caused it?

The company first attributed the failures to a piece of infrastructure facing "uma carga elevada em várias regiões" — "an elevated load across multiple regions." It then corrected itself. The real cause, Microsoft said, was "servidores que estão inesperadamente indisponíveis" — "servers that are unexpectedly unavailable" — which pushed excess strain onto the wider system.

In an early-evening post, Microsoft described the mechanics in unusually candid terms: "Estamos abrindo todas as vias disponíveis para restaurar o serviço, pois as ações tomadas até agora não forneceram o alívio esperado. Encontramos um processo central em servidores afetados que está ficando sobrecarregado, causando perda de capacidade" — "We are opening every available avenue to restore service, because the actions taken so far have not provided the relief we expected. We have identified a core process on affected servers that is becoming overwhelmed, causing a loss of capacity."

The recovery plan followed a staged pattern. "Para validar uma possível recuperação, estamos isolando uma porção de infraestrutura, reiniciando componentes afetados e reintroduzindo tráfego para confirmar que os serviços permanecem estáveis antes de aplicar a mudança de forma mais ampla" — "To validate a potential recovery, we are isolating a portion of infrastructure, restarting affected components and reintroducing traffic to confirm services remain stable before applying the change more broadly."

What does this change for Microsoft 365 customers?

For marketing and operations teams that run their day on Outlook and Teams, Thursday confirmed a single-vendor dependency can stall campaigns, client replies and internal coordination at once — and that Microsoft's own initial diagnosis can shift mid-incident. Complaint volumes on DownDetector fell through the evening, and the Teams access issue reported in the early afternoon was declared resolved roughly an hour later, according to the company's X post.

Users on social media treated the outage with humor rather than panic. "Gente o Outlook de vocês parou?" ("Guys, has your Outlook stopped?"), one profile asked on X. Another wrote: "O Outlook caindo bem antes de eu ter que entregar o trabalho que não fiz" — "Outlook going down right before I have to hand in the work I didn't do." A third asked: "O Outlook tá com uma pane geral, será que posso tirar o dia de folga?" — "Outlook is having a total blackout, can I take the day off?"

Microsoft had not confirmed full restoration of Outlook by the end of Thursday. The staged isolation-and-restart approach it described means businesses should expect a gradual, region-by-region return to normal capacity rather than a single switch-back — and should treat any Microsoft 365-dependent deadline on Friday morning with caution.