Microsoft Outlook picked a particularly bad time to stop working: right in the middle of the workday.
A widespread Microsoft 365 outage on Thursday, Nov. 12, left users struggling to access email, send messages, and connect to workplace applications. More than 130,000 Outlook outage reports appeared on Downdetector shortly after 1 p.m. ET, while tens of thousands of additional complaints involved Microsoft 365 and Teams.
Microsoft has identified infrastructure problems, including unexpectedly unavailable servers, and has begun restoring some affected systems, although its investigation into the underlying cause is ongoing.
Microsoft Outlook outage triggers more than 130,000 reports
The problems escalated Thursday afternoon as users encountered errors loading Outlook inboxes, connecting to email accounts, and sending or receiving messages.
According to Reuters, Downdetector recorded more than 130,000 Outlook problem reports around 1:27 p.m. ET. The outage tracking service also registered more than 46,000 reports involving Microsoft 365 and approximately 3,000 involving Teams.
Those figures represent user-submitted reports rather than confirmed counts of affected individuals. Microsoft has not disclosed how many people or organizations experienced problems, meaning the full scale of the disruption remains unknown.
Microsoft acknowledged the outage through its Microsoft 365 Status account on X, initially reporting problems accessing Exchange Online mailboxes through multiple connection methods in the Americas.
The company later warned that connectivity issues could affect users in other regions.
According to The Associated Press, users reported difficulty loading inboxes and sending or receiving messages. Although outage reports declined from their afternoon peak, some customers continued experiencing problems.
The incident follows a March Outlook and Microsoft 365 disruption that also left users reporting login failures and email connectivity problems.
What caused the Microsoft 365 outage?
Microsoft’s investigation has identified infrastructure problems involving servers that unexpectedly became unavailable.
The company initially reported elevated load across multiple regions, which appeared to be contributing to connectivity errors. Microsoft subsequently clarified that the increased load was due to server outages rather than an overall increase in customer traffic.
According to WIRED, Microsoft said affected servers were failing automated health checks, causing them to become unavailable and placing additional pressure on the remaining infrastructure.
The company began investigating a component responsible for processing those health checks. As reported by The Verge, Microsoft initially tested a targeted configuration change designed to bypass the suspected component on a subset of affected servers.
However, some affected servers had become unresponsive, complicating Microsoft’s efforts to determine whether the change was working. Engineers began restarting those servers and applying the approach to additional infrastructure.
In a subsequent update, Microsoft reported successfully testing an alternative health-check method that allowed a subset of affected servers to return to service.
The company began deploying the change more broadly while preparing an automated process to detect and restart unresponsive servers.
Microsoft was also investigating a small number of recent configuration updates as potential contributors to the outage. Although these findings provide a clearer picture of the infrastructure failures, Microsoft has not confirmed the underlying cause.
Which Microsoft services are affected?
Although Outlook has attracted the most attention, Microsoft’s broader service advisory identified several business applications that could experience connectivity problems.
Potentially affected services include:
- Outlook and Exchange Online: Users may be unable to access mailboxes through Outlook on the web or connection methods involving MAPI, Exchange ActiveSync, and REST APIs.
- Microsoft Teams: Some users reported connectivity and collaboration problems. Microsoft separately reported restoring an earlier Teams incident affecting North America.
- SharePoint Online: Microsoft’s broader advisory identified the document management and collaboration platform as potentially affected.
- Microsoft 365 Copilot: Microsoft’s AI assistant was included among potentially affected services.
- Microsoft Defender XDR: Microsoft’s extended detection and response platform was also listed in the advisory.
- Microsoft Planner: The task and project management application was identified as potentially affected.
- Microsoft To Do: Microsoft’s personal task management application was also included in the expanded advisory.
- Microsoft Purview: Microsoft’s broader incident information identified potential disruptions involving compliance and data protection capabilities, including data loss prevention, data classification, and communication compliance.
The company has not established that every listed service is experiencing the same level of disruption.
The extent of the impact may vary depending on the application, connection method, region, and organization.
What businesses and IT administrators should do
For organizations relying on Microsoft 365, the immediate challenge is maintaining communication while Microsoft works to restore affected services.
IT administrators should consider the following steps:
- Check Microsoft’s service health dashboard. Administrators can monitor Exchange Online incident EX1550543 and the broader Microsoft 365 incident MO1550821 through the Microsoft 365 admin center.
- Avoid unnecessary configuration changes. Because Microsoft has identified problems within its infrastructure, reinstalling Outlook or changing local email settings is unlikely to resolve the underlying issue.
- Use alternative communication channels. Organizations should consider temporarily using independent messaging services, phone calls, or other established communication systems for urgent work.
- Keep employees informed. A brief internal notice explaining the outage can reduce duplicate help desk tickets and discourage unnecessary troubleshooting.
- Monitor service restoration. Once Microsoft reports recovery, administrators should verify that affected users can reconnect, access mailboxes, and resume normal workflows.
Businesses should also avoid assuming that switching from the Outlook desktop application to Outlook on the web will solve the problem.
Microsoft identified multiple Exchange Online connection methods as potentially affected, including Outlook on the web, MAPI, Exchange ActiveSync, and REST APIs.
For administrators, the situation recalls a February Microsoft 365 admin center outage that prevented some IT teams from accessing the tools they needed to manage and troubleshoot their environments.
When will Microsoft Outlook be working again?
As of approximately 4:30 p.m. ET Thursday, Microsoft’s latest incident updates described progress toward restoring affected infrastructure, although the company had not announced a confirmed time for full recovery.
Microsoft reported successfully validating an alternative health-check method on a subset of affected servers, allowing those systems to return to service.
Engineers were applying the change more broadly while developing an automated recovery process to identify and restart unresponsive servers.
The company was also reviewing several recent configuration updates that could have contributed to the outage. However, Microsoft had not confirmed whether those changes caused the incident.
Both the Exchange Online incident (EX1550543) and the broader Microsoft 365 incident (MO1550821) remained classified as service degradation in the incident records reviewed. Although Downdetector reports declined from their afternoon peak, fewer reports do not necessarily mean all affected services have recovered.
Organizations can follow updates through the Microsoft 365 service status page or the Microsoft 365 admin center.
The outage also raises a broader business continuity question: What happens when email, collaboration tools, and other critical applications depend on the same cloud provider?
A June Microsoft Teams file outage previously highlighted the importance of testing fallback procedures and verifying access to critical files after service disruptions.
For IT teams, the immediate priority is maintaining reliable communication and confirming that services are functioning normally as Microsoft restores access. Longer-term, the incident underscores the importance of maintaining alternative communication channels and recovery procedures in situations where a primary cloud platform becomes unavailable.
Related reading: For more context on Microsoft’s recurring cloud service disruptions, read how a January Microsoft outage left thousands without email for eight hours, disrupting critical business operations across North America.