On Monday morning, April 27, 2026, as the workweek began in earnest across the United States and the United Kingdom, thousands of professionals found themselves locked out of their Microsoft Outlook accounts. Instead of the usual flood of emails, many were greeted by error messages, unexpected sign-outs, and a frustrating inability to log in. The outage, which began just before 5 a.m. Eastern Time, quickly escalated, with users taking to social media and outage monitoring sites to voice their concerns and seek answers.
According to Mashable, the trouble started early, with Microsoft 365 Business and Enterprise customers reporting widespread service interruptions. The company itself confirmed the problem on its official Microsoft 365 service status page, directing users to X (formerly Twitter) for more information. Yet, as the hours ticked by, the updates offered little solace or clarity. Around 9:35 a.m. ET, the Microsoft 365 Status account posted that the issues were ongoing, signaling to users that a quick fix was not in sight.
Downdetector, a popular outage monitoring platform, saw a dramatic spike in user error reports beginning around 5 a.m. ET. By 8:50 a.m., nearly 1,100 reports had been logged, and by 9:38 a.m., the number had surged to over 1,200, as reported by CNET. The majority of these users identified login issues as their primary problem, with 68% stating they were completely unable to access their accounts. The problem was not confined to a single region; in the UK alone, over 800 users reported similar difficulties, according to Hindustan Times, with another 400 users affected elsewhere.
For many, the disruption was more than just an inconvenience. As professionals scrambled to start their day, the inability to access work emails during peak business hours caused delays and confusion. Some users, especially those relying on the iPhone Mail app, found themselves signed out and unable to log back in, often encountering a cryptic “Too many requests” error message. One user, quoted by USA Today, lamented, “Outlook accounts were signed out of on my iPhone Mail app. When trying to login, I’m taken to a page that says ‘Too many requests.’ Logged in in my browser just fine.”
Microsoft was quick to acknowledge the issue, classifying it as a “service degradation” on its Service Health dashboard. The company’s engineering teams sprang into action, but the exact cause remained elusive. In a statement echoed across multiple outlets, Microsoft explained, “We're investigating an issue where users may be experiencing intermittent issues accessing http://Outlook.com. We've discovered some users may experience intermittent sign‑in failures, including ‘too many requests’ errors, or unexpected sign‑outs. We're analyzing service telemetry further to identify any potential next steps and mitigation actions.”
The company’s Service Health Status page provided more detail, noting that users might experience intermittent failures signing in to Outlook.com, including “too many requests” errors and unexpected sign-outs. Microsoft’s investigation pointed toward client sign-in scenarios as a possible contributor to the problem, and the team focused on validating interactions across various service components. As BleepingComputer reported, “Our investigation indicates client sign-in scenarios may be contributing to the reported behaviour, and we're focused on validating interactions across service components to identify next steps.”
As the outage dragged on, Microsoft attempted to revert a recently introduced change in hopes of alleviating the impact. At 9:46 a.m. EDT, the company announced, “We're reverting a recently introduced change to determine if this action provides relief from impact upon completion. In parallel, we're continuing to analyze customer reports, and we're closely monitoring service telemetry to identify our next steps.” However, by late morning, it was clear that this measure had not resolved the issue. “We're continuing to investigate the unexpected increase in error rates affecting two separate error scenarios to identify any potential root cause which may be responsible for this,” Microsoft stated in a subsequent update. The company also noted that the errors were affecting, but not limited to, iOS users.
While Outlook bore the brunt of the disruption, other Microsoft services, such as Teams, appeared to be largely unaffected. As CNET observed, “Microsoft's full suite of consumer products is largely unaffected by this service outage -- and that includes Microsoft Teams.” This offered a small measure of relief for organizations that rely heavily on Teams for meetings and collaboration, even as their email communications remained in limbo.
The ripple effects of the outage were felt not just in the United States, but also across the Atlantic. Hindustan Times highlighted that the disruption began shortly before 10 a.m. local time in both the US and the UK, affecting Outlook and Hotmail services alike. The communication between Microsoft servers and third-party email clients was identified as a potential culprit, though the company cautioned that local solutions would likely be ineffective until the underlying server-side problems were fully addressed.
For many users, the lack of clear communication from Microsoft added to their frustration. As Mashable reported, some customers criticized the company for the limited information provided, with the Microsoft service status page directing users to X for updates, and the support profile on X pointing users back to the website status page. The circular communication left many feeling stranded as they awaited meaningful updates.
It’s worth noting that this was not the first time in 2026 that Microsoft Outlook had experienced a significant outage. According to Mashable, a similar incident occurred in January, raising concerns about the reliability of the platform during critical work hours. In addition, Microsoft Copilot, the company’s AI-powered assistant, had suffered its own outage the previous week, though that issue was reportedly resolved after prolonged monitoring, as reported by India Today.
As Microsoft continued its investigation, the company assured users that it was “running tests to reproduce impact in our internal environment to obtain additional logging to isolate the source of the unexpected error messages.” Despite these efforts, the root cause remained under scrutiny, and the company emphasized that it was closely monitoring service telemetry for further mitigation steps.
The Monday morning Outlook outage served as a stark reminder of the central role that digital communication platforms play in modern work life. For countless professionals, a single service disruption can bring productivity to a grinding halt. As Microsoft’s engineers worked behind the scenes to restore normalcy, users around the world waited anxiously for their inboxes to spring back to life—hoping that, next Monday, the only thing they’d need to worry about was the usual deluge of emails.