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 by
ENow protects and optimizes Microsoft 365, Copilot, and Entra ID, giving modern IT leaders clarity and simplicity to manage complex environments. From proactive monitoring to license optimization, adoption, and identity governance, ENow enables IT teams to manage, scale, and secure their Microsoft environment with confidence; all in one place, without the chaos.
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.
Did the latest Microsoft outage impact your company? On November 25, 2024, just days before Thanksgiving, Microsoft users experienced issues with Microsoft 365 features and services. By noon Eastern time, more than 5,300 people globally had reported issues with Exchange, Outlook, SharePoint, and Teams.
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…
Earlier this week, on Tuesday, July 18th, at approximately 4:47 AM EST, Microsoft communicated via @MSFT365status that they were looking into a service incident issue in which "some" users may have been unable to send Exchange Online emails. In this initial tweet, Microsoft was very quick with specifics as to the cause: a recent change to its free/busy infrastructure.
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.