Microsoft 365 Outage Disrupts Outlook and Teams for Thousands Across North America
A major outage in Microsoft's North American infrastructure disrupted core Microsoft 365 services including Outlook and Teams for several hours, impacting thousands of businesses and institutions during the workday before partial restoration was achieved.
Microsoft investigating outage affecting Microsoft 365, Outlook and other services
Microsoft down — live updates on outage affecting 365, Office, Outlook, Teams for more than five hours
Microsoft 365 down for thousands of users, Downdetector shows
Is Microsoft down? Outage reported by thousands of users
Microsoft 365 and Outlook are down for many – here's everything we know about issues affecting the apps, as a disruption is confirmed
A major Microsoft outage disrupted email and collaboration tools for thousands of businesses across North America on Thursday, knocking out core Microsoft 365 services including Outlook and Teams for several hours in the middle of the workday.cbsnews +1 User reports on tracking site Downdetector peaked at around 15,000–16,000 incidents in the afternoon before gradually declining later in the evening.tomsguide +1
The problems began early Thursday afternoon U.S. time, with users suddenly unable to send or receive email, join Teams meetings or access key admin functions. Microsoft acknowledged the incident under ID MO1221364 and said it affected “multiple Microsoft 365 services, including Outlook, Microsoft Defender and Microsoft Purview,” primarily for customers routed through specific North American infrastructure.cbsnews +2
What Went Wrong in Microsoft’s North American Infrastructure
Microsoft said it had “identified a portion of service infrastructure in the North America region that [was] not processing traffic as expected,” causing intermittent failures across Outlook, Teams and related services.reuters +1 Many Outlook users saw a “451 4.3.2 temporary server issue” error when trying to send or receive mail, while others were unable to access the Microsoft 365 admin center at all.wcnc
Engineers initially focused on restoring that segment of infrastructure to a “healthy state” and then redirecting traffic to alternate servers to ease congestion.reuters A targeted load‑balancing change intended to speed recovery instead created new imbalances, forcing Microsoft to refine routing throughout the evening as reports slowly declined from more than 15,800 incidents to under 4,000 by early evening Eastern time.tomsguide +1
How Businesses and Institutions Were Hit Mid-Workday
The outage landed squarely during North American business hours, freezing email for companies that rely on Outlook as their primary communications channel and complicating remote work that depends on Teams meetings and shared documents.cbsnews +1 Roughly two‑thirds of affected users reported Exchange/Outlook issues, while about a quarter cited problems with the Microsoft 365 admin center, according to one snapshot of Downdetector data.usatoday
Organizations including universities and local governments issued alerts warning staff and students of degraded service and delayed email delivery.mysanantonio +1 Some IT administrators complained they “cannot even email” to update colleagues as the outage dragged on, while others turned to internal chat tools or personal accounts to keep operations running.cbsnews The disruption followed several other high‑profile Microsoft and cloud outages in recent years, further intensifying scrutiny of the company’s resilience planning.gvwire
The Bigger Picture
By Thursday evening, Microsoft said it had restored the affected infrastructure and was continuing to rebalance traffic, with most users seeing gradual improvement though some residual issues persisted.reuters +1 The episode underscored how heavily businesses now depend on a handful of cloud platforms for routine operations: a fault in one regional segment of Microsoft’s network was enough to stall email and collaboration across industries. With regulators and major customers already wary after previous incidents, pressure is likely to grow for a fuller technical explanation, concrete safeguards against recurrence, and clearer real‑time communication the next time a critical cloud backbone stumbles.