Microsoft confirmed a widespread Teams outage on Thursday morning, with disruptions beginning shortly after 10:30 a.m. ET. Microsoft 365 services, including OneDrive and Teams, began experiencing issues just before 11 a.m. ET, and the company said it was aware of the problem and investigating. The outage affected business and enterprise users across North America, leaving many unable to send messages, join meetings, or access shared files during peak working hours. For companies that run daily operations through Teams, even a short disruption can stall meetings, approvals, and client communication.
What Triggered the Teams Outage
Business and enterprise users began reporting problems with Microsoft 365, Outlook, Teams, SharePoint, OneDrive, Copilot, Azure, Xbox Live, and the Microsoft Store shortly after 10:30 a.m. ET. The pattern suggested a broader infrastructure issue rather than an isolated Teams outage, since several unrelated services failed around the same window. When multiple products break at once, engineers usually look first at shared authentication or networking layers rather than individual app code.
Microsoft’s engineering teams moved quickly to investigate the scope of the disruption. The company stated it was investigating reports of issues with Microsoft 365 services and confirmed its teams were actively analyzing service health data. That response mirrors how Microsoft typically handles large-scale service disruptions, prioritizing containment before publishing a root cause. Formal incident numbers and detailed explanations tend to follow only after initial stabilization work is underway.
How Users Experienced the Outage
Reports painted a frustrating picture for anyone relying on Teams for daily work. Some users described being kicked out of live video presentations or left staring at blank screens while chat messages failed to send. Others ran into unrelated but simultaneous failures that made the outage feel even more disruptive.
- Users attempting to log into Outlook were stuck in repeated authentication loops that never completed
- Files in SharePoint and OneDrive became temporarily inaccessible, showing freezing screens or error popups.
- Some Teams users saw channels and chats load normally but could not send new messages.
- A portion of users reported meetings that could not be saved to the calendar despite editing existing ones.
Read more: Microsoft Update Blocked
Scale of the Teams Outage
The numbers reported by outage-tracking services give a sense of how widespread the disruption became. More than 600 reports had piled up on Downdetector by 10:48 a.m. related to the Teams app not working. That figure climbed steadily as the morning went on and more employees logged in for work across different time zones.
Independent monitoring also picked up the disruption. Outside monitoring confirmed the issue from multiple global locations, indicating the outage was affecting more than a small, isolated group of users. When external monitors and user reports align this closely, it typically points to a genuine service-wide failure rather than a regional glitch limited to one data center.
Is This the First Recent Teams Outage
This is not an isolated event for Microsoft’s productivity suite. A Microsoft 365 outage in January affected thousands of users for several hours before Microsoft resolved the issue, and another hours-long Outlook outage occurred in April. The recurrence raises fair questions about the resilience of Microsoft’s backend infrastructure, even though each incident so far has been resolved within a single day.
Historical patterns show these disruptions often trace back to networking or authentication layer failures rather than the individual apps themselves. That would explain why a Teams outage frequently arrives bundled with Outlook and SharePoint problems instead of appearing in isolation. IT administrators who have lived through prior incidents say the bundled failure pattern is now familiar enough to anticipate.
Read more: Microsoft 365 Prices Rise
What Microsoft Has Said Publicly
Microsoft has leaned on its official status channels to keep users informed during the disruption. In past incidents of similar scale, the company has used comparable language, noting a networking issue impacting the service and describing a failover process meant to restore access gradually rather than all at once.
That approach favors speed of communication over immediate technical detail, which can leave some enterprise customers wanting more specifics while recovery work continues. For now, Microsoft has not published a full incident report explaining the underlying cause of Thursday’s Teams outage.
What Affected Users Should Do
Anyone still experiencing problems from the Teams outage should first check the Microsoft 365 Service Health Dashboard, since it usually reflects real-time status faster than third-party trackers. Restarting the Teams desktop client or switching to the web version has resolved access issues for some users during past outages.
Clearing cached credentials often fixes the authentication loops reported by Outlook users during the same window. IT teams managing larger organizations should monitor the admin center directly rather than relying solely on public statements, since incident updates there tend to arrive before broader public confirmation of the Teams outage. Microsoft typically posts a resolution notice once services stabilize, followed by a more detailed summary once the root cause behind the outage is confirmed.
