
Microsoft 365 outage disrupts Outlook and Teams as recovery continues
Microsoft is working to restore access to multiple Microsoft 365 services after a disruption on November 12 affected email and workplace collaboration tools. Some servers have returned to service, but the company has described recovery as gradual rather than announcing that every affected user can connect normally.
Reuters reported that Outlook, Teams and other Microsoft applications remained disrupted for more than five hours on Thursday. A Microsoft spokesperson confirmed that the company was investigating access problems, primarily involving Exchange Online, the service that supports business email. By early evening in the United States, Microsoft was still returning affected servers to service and observing limited recovery.
Email and collaboration services affected
The disruption extended beyond a single inbox application. Microsoft said connectivity to its services could be affected for users in any region. That statement describes the potential reach of the problem; it does not establish that every customer or every region experienced the same level of interruption.
USA Today’s independently reported live coverage documented access problems involving Outlook, Microsoft 365 and Copilot during the afternoon. It also relayed Microsoft’s warning that users might be unable to connect to services including Teams, SharePoint, Defender and To Do. The report noted that some users regained access as the afternoon progressed, while others continued to experience difficulties.
Microsoft had paused deployments, moved additional connection traffic away from affected infrastructure and restarted servers. At around 4 p.m. Eastern Standard Time, the company said it had validated an alternative service-health check that allowed a subset of servers to return. It was applying that change more broadly and preparing automated systems to detect and restart unresponsive servers.
Server recovery remains gradual
In an ABC7 update, Microsoft attributed the failure to a process on affected servers that establishes secure connections. The company said the process became overwhelmed, preventing those servers from processing requests. This is the operator’s explanation reported during recovery, rather than a completed technical post-incident review.
By around 11:30 p.m. Eastern Standard Time on November 12, Microsoft said it was seeing partial recovery in regions where adjustments had been applied, but those actions were not producing sustained recovery. The company was reviewing further measures to improve infrastructure stability. Restored servers could become unresponsive again as traffic returned, so progress did not establish a customer-wide all-clear.
The outage also reached integrations that depend on Microsoft services. Reuters reported that OpenAI was investigating problems with Microsoft connectors, including new connections and tools not working as expected. Anthropic identified an upstream-provider issue affecting its Microsoft 365 connector. These were specific integration failures, not confirmation that the companies’ entire AI platforms were unavailable.
When checked early on November 13, Microsoft’s public service-health page still displayed service degradation for Microsoft 365 business or enterprise services and consumer products. It said administrators might be unable to access the admin center for health information. The available updates did not establish a complete customer-wide all-clear or a single verified outage duration for every affected user.
Readers can follow activity on SID’s Microsoft 365 page and browse the service-status directory. Website owners can explore SID’s website monitoring and business plans, then create an account for relevant monitoring services. Monitoring supports visibility into disruptions; it does not restore Microsoft’s infrastructure or replace the operator’s recovery updates.
Image credit: ID 163856838 | Website © Transversospinales | Dreamstime.com