Microsoft Service Incident MO1221364 on January 22, 2026
On January 22, 2026, a significant service incident began affecting Microsoft 365 users throughout North America, causing widespread accessibility issues and feature failures.
Read the latest updates, root causes, and resolutions on Microsoft Office 365 service outages.
Posts about:
On January 22, 2026, a significant service incident began affecting Microsoft 365 users throughout North America, causing widespread accessibility issues and feature failures.
On October 29, 2025, customers and Microsoft services that were leveraging Azure Front Door (AFD) experienced latencies, timeouts, and errors. Numerous downstream services were impacted.
Microsoft reported this outage on the Microsoft 365 Service Health Page as MO1181369.
On 26 December 2024, a data center power event caused intermittent connection issues to downstream Microsoft 365 services.
Microsoft reported this outage on the Microsoft 365 Service Health Page as MO966473.
A global IT outage affected Microsoft 365 and Azure Services on July 30, 2024. The issue was traced back to a DDoS attack, which caused performance issues with Azure Front Door (AFD) and Azure Content Delivery Network (CDN) .
A global IT outage significantly impacted Microsoft 365 and Microsoft Azure services and countless businesses, starting on July 18, 2024. The issue was traced back to an update to the Crowdstrike Falcon agent, which caused widespread disruptions.
In the wake of the embarrassing and widely publicized Midnight Blizzard app breach, are you are aware that Microsoft also suffered from a massive Teams outage on 1/26/24 for almost 13 hours, which substantially impacted global communication abilities?! And then again on 1/29/24?!
It would have been hard for many out there NOT to have felt the pain at some point…
On back-to-back days this week, customers and users of Microsoft Outlook (June 27th) and Microsoft Teams (June 28th) were unable to access these services. Initially, Microsoft communicated these service issues to its customers and indicated that the impacts were isolated to its North American customers, but community responses and feedback suggested the impacts stretched beyond the NA region.
On March 27, 2023, at approximately 10:17 AM ET, the Microsoft @MSFT365status Twitter account reported that Microsoft was investigating an issue in which some users were experiencing delays and even failures when trying to open links through Safe Links.
On March 17, 2023, at approximately 6:45 AM ET, Microsoft announced via their Twitter account, @MSFT365status, that they had investigated an issue in which some users may have been unable to manage other users in the Microsoft Teams admin center.
On April 28, 2022, at ~10:04 AM EST, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users were unable to make or receive calls using Microsoft Teams.
For IT pros or system admins with Microsoft admin center access, the incident number to reference the issue was TM365276. This service incident comes 1 day after a minor service incident involving Microsoft Sway.