Incident sheet · /infrastructure

Filed
Read
3 min · 621 words
Severity
Routine

24 Hours Down, Zero Defections: Why Microsoft Outages Don't Cost It Customers

A 24-hour Microsoft 365 outage stalled Congress, hospitals and utilities. Survey data shows why customers can't leave — and why the FTC's two-year licensing probe now has fresh urgency.

Microsoft keeps failing. Why can’t its customers leave?
FeedMicrosoft keeps failing. Why can’t its customers leave? — Pexels / pixabay

Event log

  1. A Microsoft outage on Thursday–Friday knocked out Outlook, Teams, Copilot, Defender and Intune for nearly 24 hours.
  2. Nine in 10 surveyed US decision-makers report concrete harm from Microsoft licensing; 65% report three or more harms.
  3. Eight in ten would move workloads off Azure if licensing restrictions were lifted; 61% chose Azure only to avoid fees.
  4. The FTC's inquiry into Microsoft licensing has run for two years, covering Azure-related exclusionary conduct.
  5. Respondents who evaluated a Microsoft competitor were 2.2 times more likely to face a costly audit.

For almost 24 hours last week, a single botched network upgrade at Microsoft knocked out Outlook, Teams, Copilot, Defender security screening and the Intune device-management dashboards that administrators rely on — and millions of American workers, from congressional staff in a packed lame-duck session to hospitals, schools and utilities, could do nothing but wait.

Microsoft says the cause was a failed network upgrade, not a cyberattack. That's little comfort. Every technology provider has bad days; the test is the consequence. In a competitive market, repeated failure costs a company its customers. For Microsoft, it doesn't.

Customer captivity is the problem, and it's not an accident. Microsoft's licensing is built to make leaving expensive and diversifying impractical. Its dominant productivity suite is bundled with communications, security and AI tools, pricing out rivals. Customers who run Microsoft software on any cloud other than Azure pay more for the privilege. That's why one network failure reached so far — everything customers depend on sat behind one vendor's network, with no practical way out.

Is this really new?

No. In January, a separate Microsoft 365 outage dragged on for nearly ten hours. In 2025, attackers exploited a critical SharePoint flaw and breached federal agencies. In 2024, Russian hackers reached Microsoft's internal emails and source code. In 2023, Chinese hackers breached the email accounts of senior US government officials through a flaw in Microsoft's cloud email service. The federal Cyber Safety Review Board later called Microsoft's security culture "inadequate" and said it "requires an overhaul."

At a 2024 House hearing, Microsoft President Brad Smith said public sector clients "don't want to switch." The truth is they can't switch easily — the licensing terms have closed off the exit.

What does the data say about customer harm?

In August, the Coalition for Fair Software Licensing surveyed US software and cloud decision-makers. The numbers read like a monopoly textbook:

  • Nine in 10 report at least one concrete harm from Microsoft's licensing; 65% report three or more — penalties, forced Azure choice, costly audits, raised prices, or AI project delays.
  • 83% say Microsoft's rules meaningfully limit which cloud providers they can realistically consider.
  • 61% of organizations that shopped around picked Azure to avoid fees, not because it was the better product.
  • Eight in ten would move workloads off Azure if the restrictions were lifted.
  • Two-thirds kept a workload on their own servers rather than migrating, specifically to dodge restrictive licensing terms.

The costs don't stay inside IT departments. More than half of respondents — 56% — raised prices on their own customers to cover higher licensing costs. A third slowed hiring or cut staff.

Even looking around is punished: respondents who evaluated a competitor were 2.2 times more likely to face a costly audit.

What does this change for regulators?

The fix, customers say, is simple. 94% support letting businesses run software they already own on any cloud without added fees, and 86% want federal regulators to examine licensing practices that limit cloud choice.

The FTC is already positioned. Its inquiry into Microsoft's licensing has run for two years, probing licensing arrangements, interoperability and potentially exclusionary conduct around Azure. The stakes go beyond pricing: the same licensing that locked customers into one productivity suite now pulls the rest of their computing onto Microsoft's cloud.

Microsoft's playbook after incidents like this is well established — apologize, promise a post-incident report, offer fixes that deepen dependence on its ecosystem. Regulators now have the evidence, the authority, and last week's blackout as a vivid reminder of the cost of doing nothing.

Customers who are free to leave are customers a company has to keep earning.

via cio.com/feed/ (Source)

Filed under

  • microsoft
  • microsoft-365
  • azure
  • vendor-lock
  • software-licensing
Share this article:

More from Olivia Hart

Olivia Hart

Show full bio

News editor covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.

207 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›