A massive Microsoft Outlook outage left users across the United States struggling to access their emails Thursday, November 12, as widespread technical problems disrupted several of the company’s most popular workplace platforms.
The disruption affected Microsoft Outlook, Exchange Online, Teams, SharePoint Online and Microsoft 365 Copilot, creating problems for individuals and businesses relying on the services for daily communication.
According to outage-tracking website Downdetector, reports of Outlook problems began climbing around 12:39 p.m. ET. Within an hour, complaints skyrocketed, surpassing 129,000 reports by approximately 1:09 p.m. By 1:30 p.m., more than 140,000 outage reports had been recorded.
Users reported being unable to log into their accounts, access inboxes, send messages or receive emails. Others experienced connectivity errors and delays while attempting to use Microsoft’s workplace applications.
Microsoft acknowledged the problems Thursday afternoon through its official Microsoft 365 Status account on X.
“We’re investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas,” the company announced at 12:54 p.m. ET.
The disruption initially appeared concentrated in North America, although Microsoft later warned that users in other regions could also experience connectivity problems.
Made to order and shipped to your door.
The company confirmed the broader impact on its service health page, stating, “Users may be unable to connect to multiple Microsoft 365 services.”
As complaints continued mounting, Microsoft began identifying possible technical issues behind the widespread failures.
At 1:35 p.m. ET, the company provided an update, explaining, “We’ve determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors.”
Microsoft also confirmed it had “begun redistributing connection traffic across our broader worldwide infrastructure to help balance the load.”
The troubleshooting efforts involved transferring activity away from strained systems and onto other infrastructure capable of handling additional connections.
However, the company later determined that the problem was more complicated than an ordinary increase in user traffic.
“We’re aggressively pursuing all pathways to reduce impact,” Microsoft stated at 2:12 p.m. ET.
The company outlined several immediate measures intended to stabilize its services.
“We’ve paused all deployments, we’re moving additional traffic off the affected infrastructure, and we’re restarting affected servers to return them to service.”
Microsoft also revealed that unexpectedly unavailable servers were putting additional pressure on the systems that remained operational.
The company said it had “determined the elevated load isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure. We’re working to safely return them to service.”
By approximately 2:45 p.m. ET, Microsoft’s investigation had identified another significant development. Certain affected servers were failing automated health checks, causing them to become unavailable and forcing additional workloads onto functioning servers.
The company began testing a configuration change on a limited number of servers to determine whether bypassing the problematic component could restore service. Engineers were also restarting affected equipment and investigating unusually high processor usage.
The outage extended beyond email, with Microsoft identifying potential connectivity problems involving Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR.
Microsoft had separately resolved an earlier Teams disruption affecting users in North and South America. However, the larger Microsoft 365 incident raised renewed concerns about access to the workplace messaging platform.
The problems created complications for employees and organizations that depend on Microsoft services to exchange documents, coordinate meetings, communicate with colleagues and complete everyday assignments.
The outage also demonstrated how problems involving shared technology infrastructure can affect multiple applications simultaneously, rather than remaining limited to a single product.
Despite the staggering number of complaints, Downdetector’s figures represent submitted outage reports rather than a verified count of individual customers affected. The actual number of impacted users remains unclear.
Microsoft’s administrative incident dashboard identified the Exchange Online problem under reference EX1550543 and the broader Microsoft 365 disruption under MO1550821.
As of approximately 3:05 p.m. ET Thursday, both incidents remained classified as service degradations, with Microsoft continuing its investigation and recovery efforts.
The company had not announced a confirmed timeline for fully restoring the affected services.
Microsoft 365 business administrators can monitor the latest developments through the company’s Service Health Dashboard, while individual customers can check Microsoft’s public service-status information.
For now, users experiencing problems with Outlook and related platforms may continue to encounter intermittent connection failures until the company completes its restoration efforts.
