On a Thursday afternoon, just after one o'clock, a large share of the people who depend on Microsoft's workplace tools found themselves locked out of their email, and the failure rippled outward to Teams and Copilot as well. Roughly 130,000 users filed reports of trouble, the quiet kind of breakdown that reminds us how much of ordinary work now rests on servers we never see. Microsoft traced the trouble to strained infrastructure in the Americas, where machines that should have passed their routine self-checks instead went dark, and it has not yet said why. The company is now testing a repair
Microsoft Outage Disrupts Outlook, Teams and Copilot as Email Access Fails Across the Americas
Nearly 130,000 people had reported trouble reaching Outlook
Mark
Start with scale. How big was this?
Mimi
Nearly 130,000 Downdetector reports about Outlook just after 1 pm. Thousands more for Teams, Copilot and Microsoft 365 generally.
Luke
Worth saying what that number is. Downdetector counts user reports, not affected accounts. It's a signal of scale, not a headcount.
Mark
So what did Microsoft say went wrong?
Mimi
Exchange Online mailboxes were hard to reach in the Americas. Some infrastructure was under elevated load, and a number of servers became unavailable after failing automated health checks.
Luke
Note the hedging, though. Microsoft said the load was "likely contributing" to the errors. That's not a confirmed root cause.
Mark
And the reason the health checks failed?
Mimi
Not clear yet. Microsoft is testing a fix and rolling out an alternative method for those checks to bring servers back.
Luke
Right, and we don't know yet whether it worked. Reports have fallen from the peak, but the source doesn't say the outage is over.
Mark
What about Teams?
Mimi
Microsoft said it had restored Teams problems in North America earlier, but some users still reported connectivity trouble.
Luke
So "restored" was the company's claim, and user reports pointed the other way for some people. Both are true at once.
Le Pouls
- Roughly 130,000 Outlook reports flooded Downdetector just after 1 pm, as people found themselves unable to send, receive or even load their inboxes.
- The disruption spread beyond email, catching Teams, Copilot and the wider Microsoft 365 suite in the same tangle of failures.
- Microsoft pinned the breakdown on Exchange Online servers in the Americas that buckled under elevated load and failed their automated health checks.
- Engineers are testing a fix and rolling out an alternative health-check method, while reports have fallen from their peak and some Teams problems linger.
On a Thursday afternoon, just after one o'clock, a large share of the people who depend on Microsoft's workplace tools found themselves locked out of their email, and the failure rippled outward to Teams and Copilot as well. Roughly 130,000 users filed reports of trouble, the quiet kind of breakdown that reminds us how much of ordinary work now rests on servers we never see. Microsoft traced the trouble to strained infrastructure in the Americas, where machines that should have passed their routine self-checks instead went dark, and it has not yet said why. The company is now testing a repair and a different way of checking its servers, and the disruption is easing, though its full cause remains an open question.
Just after 1 pm on Thursday, complaints began piling up on Downdetector, the site where people log service failures. Within minutes, nearly 130,000 users had reported trouble reaching Outlook. Many could not send or receive messages, and some could not load their inboxes at all.
The trouble did not stop at email. Thousands of users also reported problems with Teams, Copilot and the wider Microsoft 365 suite, so much of the company's workplace software faltered at once.
Microsoft, based in Redmond, Washington, said it was investigating and named the cause in its updates: Exchange Online mailboxes were failing to connect across multiple methods in the Americas. The company said part of its infrastructure was under elevated load, and that a number of servers had become unexpectedly unavailable after failing automated health checks, the routine tests that confirm servers are working. Why those checks failed has not yet been explained.
Microsoft said it was testing a fix and rolling out an alternative way to run the health checks, aiming to bring the affected servers back online. Earlier it had announced that Teams problems in North America were restored, but some users still reported connection issues. Reports have since dropped from the peak, though the full picture is not yet clear.
Just after 1 pm on Thursday, the complaints started stacking up on Downdetector, the site where users log service failures. Within a short time, nearly 130,000 people had reported trouble reaching Outlook, Microsoft's email service. Many said they could not send or receive messages. Others could not get their inboxes to load at all.
Outlook was not the only product affected. Thousands of users also reported problems with Teams, Microsoft's workplace messaging app, along with Copilot, its AI assistant, and the wider Microsoft 365 suite. The reports have since dropped from that early peak, but the disruption was broad enough to touch much of the company's workplace software at once.
Microsoft, based in Redmond, Washington, said it was investigating, with particular focus on its email and Teams applications. In updates posted on social media, it said it knew that users were "experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas." That places the problem in a specific service, Exchange Online, and in a specific region.
The company's explanation was technical. It said a portion of its infrastructure was "experiencing elevated load," which it described as "likely contributing to the connectivity errors." It then narrowed the cause: a number of servers had become "unexpectedly unavailable" because of a problem that made them fail during "automated health checks." Those are the routine tests a system runs to confirm that servers are working properly.
What triggered that failure was not immediately clear. Microsoft did not say why the checks went wrong, and no cause had been established when the reporting was published.
The company did describe its response. Microsoft later said it was testing a fix and rolling out an alternative method for performing the health checks, with the aim of bringing the affected servers back online. The Microsoft 365 Status account wrote on X: "We're aggressively pursuing all pathways to reduce impact."
Earlier in the day, Microsoft had said it "successfully restored" problems related to Teams in North America. That recovery was incomplete, though, because some users continued to report connectivity issues even after the announcement.
For now, the picture is one of improvement without a full resolution. Report volumes are down from the 130,000 peak, a fix is being tested, and the alternative health-check method is being deployed. The things to watch are whether the affected servers come back online, whether lingering Teams problems clear, and whether Microsoft eventually explains what made the health checks fail.
Citations marquantes
We're aggressively pursuing all pathways to reduce impact.— Microsoft 365 Status account on X
A portion of infrastructure was experiencing elevated load, likely contributing to the connectivity errors.— Microsoft (paraphrased)
Envie de l'histoire complète ?
Lire l'original sur The Hindu Business Line ↗