Microsoft 365 outage ends after 30 hours, leaving HR teams to rethink email dependency

Microsoft restored Microsoft 365 service late Friday after an outage of roughly 30 hours cut off email for people and organizations in more than 70 countries, the company's incident log shows. The disruption hit workplace communication at a scale few employers plan for: Microsoft reported in January that it has more than 450 million paid commercial Microsoft 365 seats, roughly one for every 18 people on Earth.

For HR and internal communications teams, the outage was a live test of business continuity planning. Pennsylvania lawmakers went about 18 hours without email. A Colorado jail could not take online bond payments. Unity Health Toronto, a hospital network, declared a Code Grey, the alert for a systems failure, though it said patient care continued without disruption. The UK Supreme Court was not receiving email, Singapore reported disrupted government systems, and New York's Emergency Management office warned of delays reaching city agencies.

What caused the outage?

Microsoft says a failure introduced during an earlier network capacity upgrade in its Microsoft 365 cloud surfaced after a more recent network change. The company has not given more details. It offered a public apology and promised a detailed post-mortem.

Charles Lamanna, Microsoft's executive vice president of Copilot, Agents and Platform, said on X Friday afternoon that "cascading failures + thundering herds at our network perimeter" made recovery more difficult than normal. A thundering herd occurs when huge numbers of devices try to reconnect at the same time, overwhelming systems as they come back online.

Lamanna said the post-mortem would come "shortly," with a "step-by-step timeline and our many repair items to avoid similar outages in the future." He added that Microsoft "will be very specific on what happened." In its customer notice, Microsoft committed to a preliminary post-incident report within two business days and a final report within five.

How did workplaces cope?

The workarounds ranged from the analog to the absurd. In Japan, securities firms and asset managers fell back on fax machines when trade-confirmation emails stopped arriving, Business Upturn reported, citing Nikkei. In the U.S., a plumber told former Microsoft executive Steven Sinofsky on X that he had missed an appointment because of the "Outlook outage." Sinofsky, who ran the Office group during the May 2000 "I Love You" worm, noted that this one was not the application's fault. "This time it is the data center layer," he wrote.

Microsoft said Friday afternoon it was watching the backlog of delayed email "to ensure all process successfully before considering the issue resolved." The University of Washington's IT department told users that email delayed during the outage would be delivered as mail queues continued to be processed.

Some coped with levity. CNN chief media analyst Brian Stelter said he received "a deluge of emails from PR people pitching their clients to talk about the Outlook outage," most sent during the outage, "which, fittingly, prevented the pitches from reaching me." The security company Malwarebytes wrote: "We regret to inform you that Teams and Outlook are coming back online after a global outage."

Is this part of a pattern?

The Microsoft 365 outage was at least the fourth significant one this year. A January outage lasted nearly 10 hours. In July, a bug in Microsoft's automated network maintenance system disrupted Azure and Microsoft 365 services for hours. On Aug. 31, an Exchange Online outage also hit Teams, OneDrive and SharePoint.

The outage, like prior incidents involving AWS and others, became the latest example of how much depends on one company's cloud. Not everything Friday was Microsoft's fault: federal officials blamed aging FAA telecom gear for the nationwide ground stop, and Homeland Security Secretary Markwayne Mullin said there was "no connection between this and Microsoft." Microsoft had already posted that it had "no indication that the FAA's nationwide ground stop is related to any Microsoft services."

With the incident log now showing four major outages in a single year, employers that rely on Microsoft 365 for recruiting, payroll notifications and day-to-day employee communication may want to revisit redundancy plans before the post-mortem lands.