FTC’s Microsoft Antitrust Investigation Continues in 2026.

A major antitrust investigation into Microsoft—led by the U.S. Federal Trade Commission (FTC)—is still active as we head through 2026. While most headlines focus on “big tech politics,” enterprise buyers should care for a simpler reason: regulatory scrutiny tends to surface (and sometimes accelerate) changes in pricing, packaging, and commercial terms—and those changes land directly in your renewal math and your support outcomes.

• The FTC’s ongoing antitrust investigation into Microsoft could influence licensing, pricing, and support models for enterprises.
• Antitrust pressure often shows up first in bundling, contract terms, and support economics—raising costs without improving outcomes.
• Overpaying for underperforming support diverts budget and engineering time away from innovation and modernization.
• Medium-and-larger enterprises can reduce risk by decoupling support from spend and adopting more competitive support models.

Reuters reported that the FTC is moving ahead with a broad Microsoft antitrust probe, citing reporting that FTC staff have been gathering information by meeting with companies and other groups.

Separately, SAMexpert describes the investigation as sweeping in scope—reaching into areas like cloud dominance, bundling practices, AI-related activity, and security-related concerns.

For enterprise IT and procurement teams, that combination signals three practical realities:

• Commercial volatility risk: antitrust scrutiny often converges on the commercial levers—packaging, bundling, and licensing mechanics—that influence price and switching friction.
• Service priority risk: internal attention gets pulled toward legal/regulatory response, executive messaging, and product/commercial adjustments—right when customers are trying to reduce downtime and accelerate modernization. (This is a pattern risk, not a guaranteed outcome.)
• Negotiation leverage shifts: investigations can create pressure to show “fairness” and “openness,” which can increase buyer leverage—if you walk into renewal with a plan.

Even though the investigation is still ongoing, there are still parts of the process that are public knowledge.  Below, you’ll find a collection of what you need to know about the Microsoft antitrust probe.

1) The probe is ongoing—and has carried across administrations

Reuters reported in March 2025 that the FTC was continuing the Microsoft antitrust probe. SAMexpert also notes that the investigation continued through 2025 with no public enforcement action announced by the end of that year.

2) The scope is broad (not a single-product complaint)

Public reporting has described the investigation as wide-ranging—touching Microsoft’s software licensing and cloud computing businesses. Other reporting points to scrutiny around bundling practices and competitive dynamics in cloud markets.

3) “Antitrust” here is less about headlines and more about market mechanics

When regulators investigate a platform-scale vendor, they typically examine:

• How products are packaged together
• Whether commercial terms penalize alternatives
• Whether switching costs are artificially amplified
• Whether dominance in one area is used to win another

Even without predicting an outcome, that’s enough to justify one conclusion for enterprise buyers: assume change is possible—and structure your support and renewal strategy so you’re not trapped by it.

Antitrust probe notwithstanding, even our clients at US Cloud have found Microsoft’s product-packaging and pushing to be cumbersome. The tech giant’s selling strategy often comes at the cost of personalized and targeted support.

Here’s the pattern procurement and IT leaders recognize: the biggest costs rarely come from a single line item. They come from how the ecosystem is designed.

Bundling and “all-in” pressures can blur value

If your organization is paying for support as part of a broader bundle—especially where cost correlates with overall spend—then you may be paying a “Microsoft tax” that has little relationship to the metrics that actually affect your Microsoft support:

• ticket volume
• severity distribution
• resolution outcomes

That “pay-more-as-you-buy-more” dynamic is exactly the kind of market structure regulators often examine in antitrust contexts, because it can reinforce dominance through cost and complexity rather than performance. Microsoft’s percentage-based approach to pricing (which forces customers to pay more for support they often don’t even need as they grow) makes Microsoft a strong candidate for investigation in this area.

Cloud + licensing terms can increase lock-in risk

Multiple reports have described regulators’ interest in cloud and licensing practices. If licensing makes it more expensive or operationally harder to run Microsoft workloads outside of Microsoft’s preferred environment, that becomes a competition concern as well as an enterprise cost concern.

Support outcomes become the “silent multiplier”

Support is where the “overpaying for underperformance” story becomes painfully measurable:

• delays become business disruption
• escalations become internal labor
• “vendor process” becomes your team’s lost time

When a provider’s model produces handoffs, queueing, and repetition, you don’t just pay the invoice—you pay with engineering capacity that could have modernized the environment in the first place.

This is the part IT and procurement leaders don’t always say out loud:

Most support renewals are treated as risk reduction—yet the structure of many support models can actually increase operational risk.

Why?

• Support delays slow incident recovery, which increases outage cost and change-failure risk.
• Tiering and handoffs multiply “time-to-triage,” forcing internal SMEs to re-explain context.
• Spend-linked pricing can rise even when support need doesn’t, pushing budgets away from modernization.

And when an antitrust investigation is active, your organization should also account for:

• potential packaging shifts
• contract term adjustments
• renewed emphasis on defending business practices—which are often not designed to make your next escalation any easier

Again: none of this guarantees worse service tomorrow. It does mean your best move is to reduce dependency on any single structure that limits your options.

When it’s time to reduce your dependency on Microsoft to avoid paying for antitrust pressures, you’ll need a plan. It won’t be helpful for you to jump to another solution without thoroughly evaluating it first.

1) Run a “Support Value Reality Check” (BEFORE any renewal conversation)

Use these questions to quantify whether you’re paying for outcomes—or paying for inertia:

• Cost-to-need alignment: Are you paying based on overall Microsoft spend, or on the support capacity you actually use?
• Time-to-resolution drivers: How often do your tickets stall due to tiering, handoffs, or “reproduction steps” loops?
• Escalation friction: Do escalations feel like a process to manage—or a solution path?
• Opportunity cost: How many engineering hours per month are consumed by vendor coordination, rework, or workaround-building?

Document answers with internal evidence (ticket timestamps, severity mix, engineering time estimates). This becomes negotiation power.

2) De-couple support from vendor spend where possible

If your support price rises because your product spend rises, you’re effectively taxed for growth—even if support demand stays the same.

A healthier enterprise posture is to opt for support priced to support need (capacity, scope, SLAs, engineering depth), not to unrelated consumption. The only way to take this route for Microsoft support is to get out of the common Microsoft trap by unlinking your Enterprise Agreement from your Microsoft support.

3) Add competitive tension—even if you don’t switch tomorrow

In an antitrust environment, competitive reality matters more than ever:

• alternative support coverage
• third-party engineering depth
• credible switching options

Having options for any of these can increase leverage. Even if you keep some Microsoft support in place for specific escalations, building a parallel path changes the negotiation.

4) Protect modernization budgets explicitly

What could your enterprise do with the money and time they’re losing to Microsoft over support?

Make it explicit in renewal planning:

• “Every dollar we overpay for support is a dollar we can’t put into security hardening, cloud optimization, or modernization.”
• “Every week we lose in support delays extends project timelines and operational risk.”

Procurement leaders respond when support is framed as a modernization enabler—or a modernization blocker.

When buyers have choices, the support experience tends to optimize for outcomes:

• faster time-to-triage
• fewer handoffs
• deeper engineering involvement earlier
• pricing tied to what you use

That’s the gap many medium-and-larger enterprises are trying to close—especially when they’re tired of paying full price for sub-par support.

US Cloud is built for medium-and-larger enterprises that want to keep Microsoft environments stable while reclaiming budget and time:

• Better support outcomes by design: experienced engineers, fewer handoffs, faster path to resolution
• Lower cost structure—often around half the cost versus traditional models, so those dollars can fund modernization rather than support overhead. Larger enterprises can around 75% on support costs.

Importantly, this posture reduces single-provider dependency: if market terms shift due to antitrust pressure, your environment stays supported without forcing you into a rushed renewal.

You don’t need to forecast regulators to protect your organization. You just need to monitor the areas most likely to affect enterprise buyers:

• Changes in bundling/packaging: what gets included, what becomes add-on, what terms shift
• Licensing and portability: anything that affects workload placement economics across clouds
• Commercial enforcement: how strictly terms are applied during renewals and audits
• Support experience signals: response-time drift, escalation friction, or shifting priority patterns

The point isn’t fear. It’s resilience: the ability to keep systems supported and budgets rational no matter what happens next.

The FTC’s Microsoft antitrust investigation continuing into 2026 is a signal that regulators are still asking hard questions about market structure and business practices. For enterprise IT and procurement, that should trigger an equally practical response:

Don’t renew on autopilot.

Treat support as a strategic lever—one that can either drain modernization budgets or accelerate them.

If you’re approaching a renewal, use this moment to re-price support around real need and real outcomes. US Cloud helps medium-and-larger enterprises keep Microsoft environments supported with better support—often at roughly half the cost—so you can redirect money and engineering time into modernization, security, and innovation.