Outlook stays dark for a second day as Microsoft blames 'elevated load'

Outlook has now been failing for a second consecutive day, and Microsoft still cannot say precisely why. The outage began shortly after noon ET on November 12, when users worldwide lost access to Outlook and services that interact with Exchange Online, including Teams. Microsoft has since restored some of those services. Outlook has not come back.

The blast radius reaches past offices. Any organization running Outlook—government agencies, hospitals, emergency services, schools—has been affected. When a platform this large fails, a large part of an employee's workflow fails with it. For the first few hours, social media treated the downtime as an unscheduled holiday. The humor thinned as the hours stacked up.

A near-$4 trillion company with effectively unlimited technical resources has now let one of the world's largest business email platforms limp through a multi-day interruption. That is rare. It is also, so far, unexplained.

What does Microsoft actually know?

Very little, judging by its own statements. The Microsoft 365 Status account on X posted: "We've determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors."

Note the hedging. "Likely contributing" is not a root cause. Other reports point to a possible configuration change, but that remains unverified. In a follow-up post, the account added that its "investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health." Again: "may originate." Two conditionals in one sentence.

The Service Health Status page calls the event a "service degradation" and confirms multiple Microsoft 365 services "that interact with Exchange Online and email services are impacted." Traffic is "being gradually restored," with improvements in "mailbox access and delayed email processing"—but the notice concedes that "some users may continue to experience intermittent issues."

One theory Microsoft has ruled out, at least for now: attack. "At this time, we have no evidence of malicious activity associated with this incident," the status page states. Fast Company has reached out to Microsoft for comment.

Why are the updates drawing fire?

Microsoft has communicated regularly, mostly through the Microsoft 365 Status account. Regular is not the same as useful. Critics on social media call the updates so vague they are nearly worthless. A Reddit thread speculates the vagueness means Microsoft still lacks a good grasp of the exact cause.

Redditor simAlity mocked one update as: "Translation: We ain't got the first clue WTF is going on but it doesn't appear to be anything we have done (on purpose) and we don't know when it will be fixed." On X, user @esrtweet asked whether Microsoft had really just admitted "it is unpredictable when your cloud servers will stop collapsing under load."

Do the layoffs and buyouts matter here?

Users are connecting dots Microsoft has not connected. In July, the company cut around 4,800 employees. Weeks before the outage, it began offering buyouts to 60,000 workers—more than 25% of its workforce—to help fund its AI infrastructure plans.

"I have no doubt there's a 60 year old engineer out there who took Microsoft's buyout offer from last month that did a bunch of undocumented work his bosses didn't know about to keep things running and could fix this in 2 minutes," wrote X user @OldManFay12. User @IAmSoleyman put it more bluntly: companies "keep talking about replacing people, right up until something breaks and they need people to fix it." It is currently unknown whether recent departures contributed to the outage or to the slow resolution.

How has MSFT stock reacted?

Shares traded around $515.06 in premarket trading, down roughly 1.5% from the previous close of $523. That dip may reflect the outage—or it may not. A few percent either way is normal for big tech right now, with midterm elections and the Jensen Huang Nvidia scandal already swinging the sector.

Until Microsoft names a root cause, expect the pressure on both its infrastructure and its headcount strategy to keep building.