Google Drops 2024 Antitrust Complaint as EU DMA Probes Cloud Giants

Google’s decision to withdraw its 2024 antitrust complaint against Microsoft marks a tactical pivot in a broader contest over cloud market rules and regulatory remedies after the European Commission launched a separate, wider Digital Markets Act (DMA)–style investigation into cloud computing services in November 2025.

Background​

On September 25, 2024, Google Cloud filed a formal antitrust complaint with the European Commission alleging that Microsoft’s cloud-related licensing and product-bundling practices artificially privileged Microsoft Azure and created barriers for rival cloud providers. The complaint centered on claims of vendor lock-in, allegedly aggressive licensing markups for running Microsoft server software on competing clouds, and contractual terms that made switching providers more costly and operationally complex.
In July 2024 Microsoft reached a settlement with CISPE (Cloud Infrastructure Services Providers in Europe), a European cloud trade group, under which Microsoft committed to product and licensing changes intended to address some of the trade body’s concerns. That deal included the creation of an independent observatory to monitor progress and a lump-sum payment to CISPE; public reporting around the settlement placed the figure in the low tens of millions of euros. CISPE withdrew its complaint to the Commission as part of that settlement.
On November 18, 2025 the European Commission formally announced three market investigations under the DMA: two company-specific market probes to assess whether Amazon Web Services and Microsoft Azure function as “gateways” or gatekeepers in cloud infrastructure, and a third horizontal examination of whether the existing DMA tools are fit-for-purpose in cloud markets. Ten days later, on November 28, 2025, Google publicly withdrew its 2024 complaint, stating that the Commission’s decision to address “problematic practices affecting the cloud sector under a separate process” made the bilateral complaint redundant.

Why the withdrawal matters​

Google’s withdrawal is not an abandonment of the underlying concerns about market fairness; rather, it is a strategic realignment. The Commission’s DMA-style market investigations promise systemic, ex ante remedies that could have far-reaching consequences beyond a single-case adjudication.

• A company-level antitrust case targets a specific set of contractual acts and remedies that affect one complainant and one defendant.
• A DMA-style market investigation can produce sectoral remedies, potential gatekeeper designations, and prescriptive obligations that reshape how cloud infrastructure markets operate across the EU.

By relocating the argument from a bilateral complaint to a Commission-led, DMA-flavored inquiry, Google is effectively handing the dispute to a process that can deliver structural and behavioral orders affecting entire cloud ecosystems — remedies more powerful than a case-specific adjudication.

---

Overview of the regulatory axis: antitrust vs. DMA​

Antitrust investigations (traditional ex post enforcement)​

Antitrust enforcement (the European Commission’s traditional competition law function) targets past or ongoing conduct that may violate Articles 101 or 102 of the Treaty on the Functioning of the EU. Remedies typically include fines, orders to stop abusive conduct, and commitments that the defendant may propose to resolve competition concerns.

The Digital Markets Act (ex ante, prescriptive regulation)​

The DMA creates a proactive, rules-based regime aimed at so-called gatekeepers — platforms whose services act as bottlenecks between consumers and businesses. Key aspects:

• Gatekeeper designation under the DMA carries a set of mandated obligations (non-discrimination, interoperability requirements, data-portability obligations, and restrictions on self-preferencing).
• The Commission can designate gatekeepers not only through numerical thresholds but also via qualitative market investigations; this makes gatekeeper status achievable even when traditional thresholds are not met.
• Non-compliance exposes firms to heavy sanctions: fines of up to 10% of global turnover for first-time breaches, rising significantly for repeat or systematic violations. The DMA also enables periodic penalty payments and, as a last resort, structural remedies.

Moving a dispute into the DMA arena can therefore produce fast, broad, and preventive remedies that antitrust cases — with their longer timelines and narrow remedies — cannot easily deliver.

---

Timeline of the cloud dispute (key dates)​

• September 25, 2024 — Google Cloud files an antitrust complaint at the European Commission alleging anticompetitive licensing and vendor lock-in by Microsoft.
• July 10, 2024 — Microsoft and CISPE reach a settlement in the CISPE complaint; CISPE withdraws its formal complaint to the Commission and establishes an observatory to monitor compliance.
• November 18, 2025 — European Commission opens three market investigations under the DMA targeting AWS, Microsoft Azure, and the DMA’s applicability to cloud markets.
• November 28, 2025 — Google withdraws its 2024 antitrust complaint, citing the Commission’s market investigations as a more suitable vehicle to address systemic issues.

(Precise dates are stated to avoid ambiguity in the sequence of legal and regulatory events.

---

The market picture: concentration and market share​

Hyperscale cloud markets are concentrated but dynamic. Available regulatory and market reporting shows the following approximate global shares in infrastructure cloud services:

• Amazon Web Services (AWS): roughly 30%
• Microsoft Azure: roughly 20%
• Google Cloud Platform (GCP): roughly 13%

These headline shares reflect global revenue and capacity snapshots and can vary by region, workload type, or segment (IaaS, PaaS, SaaS). The Commission’s DMA probes will focus on whether certain cloud services — even without meeting numeric DMA thresholds — function as essential gateways for EU businesses and consumers.

---

Core allegations and the technical mechanics​

Allegations against Microsoft (positions attributed to Google and other complainants)​

• Licensing markups and penalties: The complaint alleges that running Microsoft server products such as Windows Server or SQL Server on non-Azure platforms attracts significant pricing penalties or less-favorable licensing conditions, which can materially increase costs for customers who wish to run Microsoft software on rival clouds.
• Tied product advantages and preferential integration: Microsoft’s bundling of services and deep integration between Windows Server, SQL Server, Microsoft 365 apps, and Azure platform services can create convenience advantages that are hard for rivals to match, effectively biasing customer choices toward Azure.
• Operational friction: Differences in update cadences, support, or feature availability can create non-price switching costs that deter migrations to alternative cloud providers.

Microsoft’s stated defenses​

• Microsoft frames many of the changes it has made as pro-competitive improvements and argues that the CISPE settlement addressed the core provider concerns.
• The company emphasizes that cloud customers have abundant choices and that Microsoft’s licensing and product strategies reflect legitimate product differentiation and security considerations.
• Microsoft also contends that certain technical features — for instance, deep platform optimizations — are product benefits rather than exclusionary practices.

Technical specifics that matter​

• Pay-as-you-go licensing for Windows Server and SQL Server on third-party clouds versus reserved or subscription licensing on Azure.
• Feature parity and patch/update timing: whether critical security updates or performance features are delivered identically across Azure and non-Azure environments.
• APIs and interoperability for management, identity, and telemetry services that influence portability, visibility, and operations between clouds.

These technical levers — licensing models, release cadences, APIs, telemetry, and support — are exactly the instruments the Commission’s horizontal review will test to determine whether market structures and contract practices entrench incumbent cloud providers.

---

Strengths of the Commission’s new approach​

• Systemic reach: The DMA-style market investigations allow the Commission to examine and remedy sector-wide dynamics rather than resolving one-off, bilateral disputes.
• Speed and prescriptive power: DMA tools are designed to deliver faster, forward-looking remedies (including prescriptive interoperability or non-discrimination obligations) rather than ex post fines alone.
• Qualitative designation flexibility: The Commission can designate gatekeepers based on market position and gatekeeping function even where numerical thresholds fall short, addressing the reality of infrastructure platforms that exert outsized influence without meeting user-count metrics.
• Potential for consistent remedies: A sectoral focus can yield uniform rules that apply across providers, reducing regulatory arbitrage where one provider settles while others remain unregulated.

---

Risks and unintended consequences​

• Regulatory overreach and compliance costs: Imposing DMA-style obligations on infrastructure platforms could force deep operational and contractual changes, imposing compliance and re‑engineering costs that may be passed on to customers.
• Fragmentation of cloud offerings: Heavy-handed remedies (for example, mandatory feature parity or forced openness on proprietary APIs) could deter innovation or fragment product roadmaps, producing trade-offs between competition and product evolution.
• Legal complexity and forum shopping: Parallel antitrust and DMA processes can generate overlapping remedies, inconsistent rulings, or protracted legal challenges that muddy the business environment for cloud customers and providers.
• Geopolitical and industrial policy tensions: Europe’s drive for sovereign cloud capacity and control over AI infrastructure interacts with antitrust objectives — leading to hybrid outcomes that mix competition policy with industrial strategy.
• Risk of capture or narrow settlements: If some industry groups (or individual cloud providers) negotiate bespoke settlements like the CISPE-Microsoft deal, regulators risk fragmented outcomes where only a subset of players receives relief while others remain disadvantaged.

These tensions create a regulatory design problem: how to open markets without undermining innovation or creating costly compliance burdens.

---

What Google gains — and what it gives up — by withdrawing​

By withdrawing its complaint, Google:

• Gains an opportunity to see regulatory remedies that could apply broadly to Azure and AWS, potentially leveling the playing field across multiple competitors.
• Avoids the time and costs associated with a bilateral antitrust prosecution that could end with a narrow remedies package or an adverse settlement.
• Risks losing the tactical visibility and leverage that a live formal complaint affords (e.g., access to Commission investigation files tied directly to alleged misconduct), though a Commission-led probe may compensate with broader discovery powers.

This is a calculated trade: the prize is scale — sectoral remedies under the DMA — rather than the narrower victory of a single antitrust finding.

---

Implications for enterprise customers and IT decision-makers​

For IT leaders, procurement officers, and systems architects, the regulatory tug-of-war carries immediate, practical implications:

• Procurement strategy: Enterprises should revisit vendor lock-in risk assessments, contractual exit terms, and multi-cloud interoperability requirements. Contractual mobility clauses, data egress costs, and support SLAs should be scrutinized.
• Architecture design: Consider greater emphasis on cloud-agnostic architectures, containerization, and open API standards to reduce switching friction. Evaluate trade-offs between managed platform efficiencies and portability.
• Cost modeling: Recalculate total cost of ownership scenarios that factor in licensing differentials and potential future regulatory remedies that may alter pricing dynamics.
• Compliance planning: For firms operating in the EU, plan for potential changes to cross-border data flows, contractual obligations, and vendor obligations if DMA-style rules are enacted for cloud infrastructure.

Enterprises should not assume remedies will be immediate; regulatory processes can take months and may be subject to appeals and legal challenges.

---

Likely regulatory paths and timelines​

• Company-specific investigations: The Commission intends to conclude the two company-level probes (AWS and Azure) within roughly 12 months from their opening. Those investigations could lead to gatekeeper designations that bring prescriptive obligations into force.
• Horizontal sectoral review: The broader DMA horizontal inquiry may produce policy recommendations on the DMA’s suitability for cloud markets and whether the rules need adaptation — a longer process that could influence future regulatory instruments.
• Parallel antitrust actions: National competition authorities and private litigants may continue or initiate parallel cases. The Commission’s market investigations do not preclude separate antitrust enforcement.

Given these pathways, meaningful change in how cloud vendors license and integrate core software could appear within 12–18 months — but litigation and compliance implementation may extend the horizon.

---

Strategic playbook for cloud vendors and partners​

• Audit licensing mechanics: Vendors should conduct a rigorous review of licensing rules, pay-as-you-go models, and migration penalties to identify items likely to attract regulatory scrutiny.
• Prioritize transparency: Clear, published licensing terms and predictable update cadences reduce the risk of regulatory findings alleging discriminatory or opaque conduct.
• Enhance interoperability: Investing in open standards and cross-cloud tooling lowers switching friction and reduces the gravity of claims about anti-competitive tie-ins.
• Engage regulators proactively: Demonstrable cooperation with monitoring bodies and transparent reporting — rather than opaque settlements that cover only part of the market — will play better in regulatory reviews.
• Prepare for compliance costs: Establish cross-functional teams (legal, engineering, product, sales) to model potential DMA obligations and probable compliance investments.

These steps can reduce regulatory exposure and position vendors to shape implementation in ways that preserve product differentiation while limiting anticompetitive risk.

---

The political economy: an EU agenda with global reverberations​

The Commission’s choice to deploy DMA-style market investigations into cloud infrastructure reflects a broader policy orientation: Europe is actively willing to use ex ante regulation to shape the architecture of foundational digital markets — especially those that underpin the EU’s industrial and strategic autonomy objectives (including AI readiness, data governance, and sovereign cloud capacity).
This posture carries global consequences:

• Technology governance: Outcomes may set de facto global standards for interoperability or licensing conduct when large cloud customers and multinational firms adopt EU-compliant procurement models.
• Competitive dynamics: Any remedial orders that meaningfully lower switching costs or limit self-preferencing could redistribute enterprise workloads and influence market share trajectories among hyperscalers.
• Commercial bargaining: Vendors may adjust pricing and partner programs proactively to avoid stricter post-designation regulation.

Markets, partners, and customers will watch the Commission’s deliberations closely, with outcomes likely to shape cloud commercial strategies worldwide.

---

What to watch next​

• Commission decisions and interim measures: Look for detailed Commission notices, requests for information, and preliminary findings that reveal the technical concerns regulators prioritize.
• Industry responses and lobbying: Observe whether other cloud providers, European sovereign cloud initiatives, or major enterprise customers file positions, submit evidence, or publicly react.
• Settlement dynamics: Be alert for any follow‑on settlements that attempt to carve market exceptions or narrowly bind select providers rather than produce sector-wide remedies.
• Litigation and appeals: Gatekeeper designation or DMA-ordered remedies could trigger legal challenges in EU courts; the timing and outcome of such litigation will shape the ultimate effect.
• Practical product changes: Watch for product announcements from Microsoft, AWS, and others that address portability, licensing transparency, or feature parity — both as competitive moves and as pre-emptive compliance measures.

---

Final assessment​

Google’s withdrawal of its 2024 complaint against Microsoft is a pragmatic hand-off to a higher-stakes regulatory process. The European Commission’s DMA-style investigations, opened in mid-November 2025, offer a route to sector-wide remedies that could change market architecture, reduce vendor lock-in, and impose prescriptive obligations on dominant cloud providers.
This pivot increases the odds that the debate about cloud competition will be settled not by isolated settlements or case-by-case remedies, but by regulatory instruments with systemic impact. For enterprises, the immediate priority is to reassess cloud procurement and architecture for portability and resilience. For vendors, the message is clear: regulatory scrutiny is widening beyond bilateral settlements, and proactive transparency, interoperability, and accountable licensing practices will be essential to navigate an era of more intrusive digital market governance.
Caveats remain: some estimates cited in public complaints — including aggregate figures about annual costs imposed by alleged licensing restrictions — are contested and have not been independently verified in every instance. The Commission’s investigations will explore evidence, technical claims, and market data over the coming months; final outcomes will hinge on detailed empirical findings, legal interpretation, and, potentially, judicial review. Until then, the cloud market faces a period of regulatory uncertainty that will shape commercial contracts, product roadmaps, and competitive strategy for at least the next year.

---

Source: The Wall Street Journal https://www.wsj.com/tech/google-wit...fter-new-probe-launched-f842eb46?gaa_at=eafs/