Microsoft's suite of productivity tools suffered notable service interruptions on Thursday, with users across the United States reporting problems accessing Outlook, Microsoft 365 and Teams.
Outage monitoring site Downdetector.com recorded more than 130,000 reports of issues with Outlook at 1:27 p.m. ET. Downdetector compiles status reports from a variety of sources to identify outages; the site cautions that the number of reports it shows may not correspond exactly to the final count of affected customers.
Earlier in the day, Microsoft said it had resolved a Teams disruption that impacted users in North America and described the incident as fully addressed. The company subsequently communicated that the same underlying issue could also be affecting Microsoft 365 service connectivity for users in other regions, indicating the outage may have had a broader footprint than the initial Teams disruption.
Downdetector also logged more than 46,000 user reports related to Microsoft 365 and approximately 3,000 reports of users experiencing trouble accessing Teams. These tallies reflect user-submitted problem reports captured by the tracking platform.
In the middle of the outage timeline, a site message promoted InvestingPro, noting the service can provide alerts on market-moving headlines and that it was available at a 55% discount. The message also highlighted valuation tools and service features, including a Fair Value estimate for MSFT that aggregates multiple valuation models.
Microsoft's public updates characterized one disruption as resolved for a defined region while acknowledging possible residual connectivity effects for the broader Microsoft 365 service elsewhere. The outages and the sequence of company statements created a dynamic where some services were declared remediated while other elements of the productivity suite continued to show elevated volumes of problem reports on monitoring platforms.
Contextual note: The numbers cited above come from Downdetector's aggregated reports at the times referenced and from Microsoft's own statements about service status. The final scope and ultimate root cause of the incidents were not detailed in the statements provided.