On 22 January 2026, a widespread disturbance hit the Microsoft 365 suite, which impacted on the Outlook, Teams, and Exchange apps. The outage caused large-scale service outages, which added to a past occurrence that happened on January 21. 

There was an apparently abrupt failure of email delivery and administrative features as reported by users which resulted in massive downturns of the corporate structures throughout North America.

Outage Hits Hard

As of 4:00 pm, Downdetector provided more than 15,000 deactivation reports. Sixty percent were related to Exchange email malfunctions, 33% to the Microsoft 365 Admin Centre, and 7% to having problems with the backend server. 

The complaints posted on X included missing external mail, authentication delay, and stalled workflow processes. Microsoft blamed misplaced traffic-processing logic and immediately took load-balancing actions to fix the failure.

The Statement

We're investigating a potential issue impacting multiple Microsoft 365 services, including Outlook, Microsoft Defender and Microsoft Purview.

About 45 minutes later, they wrote,

We've identified a portion of service infrastructure in North America that is not processing traffic as expected. We're working to restore the infrastructure to a healthy state to achieve recovery.

Quick Background

It was due to a January 21 outage caused by complications with the third-party networking that had been fixed by 1:30 pm. 

By the evening of January 22, reported cases had dropped, as the underlying infrastructure had started to come back online, but the system wide effects were not regained immediately signifying that the aftermath was long-term.

Road to Recovery

Microsoft then responded by publishing an update with the status:

We have brought the impacted infrastructure back to a healthy state, as well as continued traffic optimization. 

At its highest point, Microsoft 365 and Outlook experienced peak disruptions respectively, and then fell below by 4:20 pm to indicate gradual system recovery. It was later on January 22 that full service became possible but the recurrence provides evidence of the need to have a strong level of redundancy in cloud operations. 

However, Microsoft has provided an update again. 

We're continuing to refine our load balancing configurations to address residual imbalances across the environment.