Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

Microsoft keeps failing. Why can’t its customers leave?

For almost 24 hours last week, millions of Americans lost access to the tools they use to work. A global Microsoft outage knocked out Outlook, Teams and Copilot from Thursday afternoon well into Friday. Congressional work stalled in the middle of a packed lame-duck session. Hospitals, schools, utilities and the agencies that deliver critical services had no way to reach their own staff and, in many cases, no backup. Their only option was to wait while one company repaired its own network.

Microsoft says the cause was a botched network upgrade, not a cyberattack. That is 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 does not.

Customer captivity is the problem. The outage struck Microsoft’s productivity suite, where its dominance is oldest and deepest, and it reached so far because customers have been steered, by design, into buying everything from one vendor with no practical way out. 

Every Microsoft customer who lost email last week was living with a choice made long ago: by Microsoft, not the customers themselves. It’s central to Microsoft’s business strategy. The company’s licensing is built to make leaving expensive and diversifying impractical. Its dominant productivity software is bundled with communications, security and AI tools, which prices out rivals and limits their access to customers. Customers who want to run Microsoft software on any cloud other than Azure pay more to do so. That’s why a single network failure reached so far: Microsoft’s Defender security screening and the Intune dashboards that administrators use to manage devices went dark along with other services.

This isn’t the first warning. This January, a separate Microsoft 365 outage dragged on for nearly ten hours. In 2025, a global attack exploited a critical SharePoint flaw and breached federal agencies. In 2024, Russian hackers got into Microsoft’s corporate systems and reached internal emails and source code. In 2023, Chinese hackers exploited a flaw in Microsoft’s cloud email service to breach the email accounts of senior U.S. government officials. The federal Cyber Safety Review Board later called Microsoft’s security culture “inadequate” and said it “requires an overhaul.”

Outages and breaches keep happening, and customers keep staying. That is not how a competitive market behaves. The ability to let quality slide without losing customers is a hallmark of monopoly power.

At a 2024 House hearing, Microsoft President Brad Smith said public sector clients “don’t want to switch.” The truth is that they can’t switch easily, because Microsoft’s licensing terms have closed off the exit.

American business leaders tell the same story. In August, the Coalition for Fair Software Licensing surveyed US software and cloud decision-makers:

  • Nine in 10 report at least one concrete harm from Microsoft’s licensing, and 65% report three or more. Harms include a penalty, forced Azure choice, staying on-prem, costly audit, raised prices, AI platform constraint or AI project delay.
  • 83% say Microsoft’s rules meaningfully limit which cloud providers they can realistically consider.
  • 61% of organizations that shopped around chose Azure to avoid fees, not because it was the better product.
  • Eight in ten say they would move workloads away from Azure if the licensing restrictions were lifted.
  • Companies avoid moving to the cloud altogether to avoid Microsoft’s restrictions and increased licensing fees. Two-thirds have kept a workload on their own servers, rather than migrating to the cloud, to dodge restrictive licensing terms.

Microsoft’s costs don’t stay in IT departments. More than half of respondents (56%) raised prices on their own customers to cover higher licensing costs, and a third slowed hiring or cut staff. 

Customers who test the market also pay a price. Respondents who evaluated a competitor were 2.2 times more likely to face a costly audit.

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

The FTC is already positioned to deliver. Its inquiry into Microsoft’s licensing has run for two years, and it is probing licensing arrangements, interoperability and potentially exclusionary conduct around Azure. That matters because the licensing that locked customers into one productivity suite is used to pull the rest of their computing onto Microsoft’s cloud.  Last week’s outage shows what’s at stake. Market dominance isn’t only a pricing problem. Customers who are free to leave are customers a company has to keep earning. 

Microsoft’s playbook is well established. It apologizes, promises a post-incident report and offers fixes that deepen dependence on its ecosystem. Regulators must refuse to accept this model any longer. The FTC has the evidence, the authority and now a vivid reminder of the cost of doing nothing. 


Read More from This Article: Microsoft keeps failing. Why can’t its customers leave?
Source: News

Category: NewsNovember 19, 2026
Tags: art

Post navigation

NextNext post:FAA ground stop offers IT leaders stark modernization lessons

Related posts

FAA ground stop offers IT leaders stark modernization lessons
November 19, 2026
The dark side of AI in hiring: When job applicants become security threats
November 19, 2026
AI leadership: 3 success lessons from CBA’s chief AI officer
November 19, 2026
Trusted AI by design, not by default
November 18, 2026
Keep skyrocketing AI costs in check
November 18, 2026
Rewrite the rules of enterprise recovery
November 18, 2026
Recent Posts
  • Microsoft keeps failing. Why can’t its customers leave?
  • FAA ground stop offers IT leaders stark modernization lessons
  • The dark side of AI in hiring: When job applicants become security threats
  • AI leadership: 3 success lessons from CBA’s chief AI officer
  • Trusted AI by design, not by default
Recent Comments
    Archives
    • November 2026
    • October 2026
    • September 2026
    • August 2026
    • July 2026
    • June 2026
    • May 2026
    • April 2026
    • March 2026
    • February 2026
    • January 2026
    • December 2025
    • November 2025
    • October 2025
    • September 2025
    • August 2025
    • July 2025
    • June 2025
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.