A major disruption has taken Microsoft 365 services offline, leaving users worldwide unable to access Outlook, Microsoft Teams, Copilot and related cloud infrastructure. The company is actively investigating and working to restore normal operations across its affected systems.
User reports of service failures began arriving Thursday afternoon, with Downdetector tracking a surge in complaints spanning Outlook, Microsoft 365, Teams, Copilot, Azure, OneDrive, and the Microsoft Store. Multiple independent reports reached BleepingComputer from affected users unable to reach Microsoft's services.

Microsoft's 365 admin center advisory, identified as MO1550821, confirmed that customers cannot connect to Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot, and Microsoft Defender XDR. The incident began Thursday at 1:26 PM ET, though the company had been tracking Exchange Online connectivity issues in the Americas since earlier that morning.
Root cause and response
Microsoft initially suspected elevated infrastructure load across multiple regions was responsible for the outage. However, investigation revealed the actual problem: a number of servers became unexpectedly unavailable, placing strain on the remaining systems.
We 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.
Microsoft, in an update on X
To address the crisis, Microsoft has halted all deployments and rebalanced connection traffic across its global infrastructure. The company is redirecting traffic away from compromised systems and restarting affected servers to rebuild capacity and restore service availability.
Although the outage was initially reported in the Americas, Microsoft later clarified that users across any geographic region could experience problems.
Earlier Teams incident Thursday
The broader Microsoft 365 outage follows a separate Teams disruption that struck earlier the same day. Tracked as TM1550488, this incident lasted from 9:45 AM to 10:53 AM ET and affected users in North and South America.
The earlier Teams incident caused message delivery failures, errors when creating or updating conversations, and inability to retrieve chat history. Microsoft attributed the problem to resource contention within its infrastructure, which drove up resource consumption and prevented normal message processing.
Microsoft has stated that the earlier Teams incident has been fully resolved. The company has not clarified whether the two incidents share a common cause, and the ongoing Microsoft 365 outage remains unresolved.