Microsoft 365 Services Experience Widespread Outage
Just the facts

Microsoft 365 Services Experience Widespread Outage

Summary

On January 22, 2026, Microsoft 365 services, including Outlook and Teams, faced significant disruptions, affecting thousands of users across North America.

On January 22, 2026, Microsoft 365 services, including Outlook and Teams, experienced significant disruptions, affecting thousands of users across North America. Reports of issues began around 2:00 p.m. Eastern Time, with users encountering difficulties accessing emails, files, and meetings.

Microsoft acknowledged the problem, stating, "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."

The outage impacted various services, including Exchange Online, SharePoint Online, OneDrive, and Microsoft Teams. Users reported receiving error messages such as "451 4.3.2 temporary server issue" when attempting to send or receive emails through Outlook.

By 4:14 p.m. ET, Microsoft reported that it had "restored the affected infrastructure to a healthy state" and was "directing traffic to alternate infrastructure to achieve recovery."

The company advised users to monitor the Microsoft 365 admin center or status page for further updates.

Fact-checking

Fact-check the facts of the article using external sources and databases.

✓
Confirmed

On January 22, 2026, Microsoft 365 services, including Outlook and Teams, experienced significant disruptions, affecting thousands of users across North America.

✓
Confirmed

Reports of issues began around 2:00 p.m. Eastern Time, with users encountering difficulties accessing emails, files, and meetings.

✓
Confirmed

Microsoft acknowledged the problem, stating, '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.'

✓
Confirmed

By 4:14 p.m. ET, Microsoft reported that it had 'restored the affected infrastructure to a healthy state' and was 'directing traffic to alternate infrastructure to achieve recovery.'

Keep reading — for free

Create a free account to follow the news. No card required.