Google Withdraws EU Antitrust Complaint as DMA Probes Cloud Market Dynamics

Google’s quiet withdrawal of its formal antitrust complaint against Microsoft’s cloud practices is a consequential tactical pivot: the company has stepped out of a one‑on‑one regulatory fight and handed the contest to Brussels, where the European Commission’s newly launched market investigations under the Digital Markets Act (DMA) will now probe whether hyperscale cloud providers have created structural barriers to competition.

Background​

In September 2024 Google Cloud lodged an antitrust complaint with the European Commission alleging that Microsoft’s licensing and commercial practices made it harder and more expensive for enterprises to run Microsoft workloads on rival clouds. That filing put a spotlight on a cluster of familiar industry complaints: differential licensing for Windows Server and SQL Server when hosted on non‑Azure platforms, migration friction including data egress costs, and packaging or managed‑service integrations that appear to favour Azure. The Commission’s response escalated the dispute from private grievance to public sector inquiry. On 18 November 2025 the European Commission announced three coordinated market investigations under the DMA: two company‑level probes into Microsoft Azure and Amazon Web Services (AWS) to assess whether they operate as “important gateways” in cloud markets, and a horizontal sectoral review to determine whether the DMA’s toolbox is fit for cloud infrastructure. The Commission set an accelerated timetable for the company‑level inquiries—roughly 12 months—while the horizontal review is expected to run longer. Ten days after the DMA probes were announced, Google updated its original blog post and formally withdrew its complaint, explicitly saying the Commission’s market investigations provide a superior vehicle to address systemic cloud licensing and portability issues. The company reiterated the substance of its concerns but said the complaint was now redundant given the Commission’s new process.

---

What Google alleged — the substance of the complaint​

Google’s original filing distilled enterprise grievances into several technical and commercial themes:

• Differential licensing and surcharges: Google and other complainants argued that Microsoft effectively levied higher costs on customers who run Windows Server, SQL Server and other Microsoft server products on rival clouds, compared with running those same products on Azure. These pricing differentials were framed as a de‑facto penalty for migration.
• Migration and egress friction: Complaints highlighted data egress fees, slow or brittle export tooling, and contractual clauses that raised the real‑world cost and complexity of moving production workloads away from Azure.
• Control‑plane and API lock‑in: The argument here was not only about money but also about technical friction. Managed services, proprietary control‑plane APIs, and tight integration with Azure ecosystem services can increase engineering work and risk for customers trying to port workloads.
• Self‑preferencing and marketplace dynamics: Concerns extended to bundling, marketplace positioning, and other commercial behaviours seen as favouring first‑party Azure services over independent alternatives.

It is important to treat specific numerical claims with care: some industry commentary referenced dramatic figures—reports of “up to 400%” markups or aggregate costs in the hundreds of millions to billions of euros—but these derive from selective contract scenarios, trade‑group analyses, or company statements and are contested. Regulators will need documentary evidence to verify or reject those precise numbers; they remain allegations until proven.

---

Why Google withdrew the complaint — strategic logic​

Google’s withdrawal is not a retraction of the substance of its allegations. Rather, it is a calculated legal and policy decision with several pragmatic rationales:

• The DMA framework provides ex‑ante enforcement tools that can deliver systemic, sector‑wide remedies—such as mandated interoperability, non‑discrimination obligations, or API access—rather than the bespoke, ex‑post redress typically available through individual antitrust complaints. Google judged those tools better suited to addressing the structural issues it raised.
• A Commission‑led probe can compel a broader evidentiary record. Market investigations reach across multiple participants and contracts; they can require document production and sworn testimony from many players, producing a systemic factual picture rather than fitting the dispute into a single, bilateral complaint.
• The move reduces the optics of a unilateral commercial fight. When one major cloud vendor sues another, critics can frame the action as competitive gamesmanship. By stepping back and deferring to Brussels, Google positions itself as a constructive participant in a public rule‑making process while retaining the right to feed evidence and submissions into the DMA probes.

Taken together, Google’s action is a tactical “hand‑off” to regulators: it abandons the headline litigation posture but stays deeply engaged as an evidence‑provider and policy advocate.

---

The European Commission’s DMA market investigations — what they can actually do​

The DMA was built to police large digital platforms with asymmetric market power. Its principal strengths in the cloud context are:

• Ex‑ante powers: The ability to impose forward‑looking obligations (e.g., non‑discrimination, data portability, API interoperability) before harms become entrenched, rather than relying solely on retrospective penalties.
• Designated remedies and enforcement levers: If a provider is designated a gatekeeper, the Commission can order specific behavioural or technical changes and back them with steep fines and periodic penalty payments for non‑compliance.
• Sector‑wide reach: Market investigations can collect evidence from a wide set of stakeholders—hyperscalers, independent cloud providers, systems integrators, large enterprise buyers and public sector purchasers—creating a more complete record.

That said, applying the DMA to cloud infrastructure raises serious practical challenges. The DMA’s numeric thresholds (turnover, user counts, market capitalisation) are not a neat fit for enterprise contract‑driven services. Cloud users are largely businesses that sign bespoke agreements, not discrete consumer accounts tracked by platform metrics. Brussels therefore launched a twin strategy: company‑level inquiries into AWS and Azure to assess qualitative gatekeeper function, and a horizontal study to test whether DMA tools require adaptation for cloud markets.

---

Where other regulators stand — a pattern of concern​

Regulatory unease about cloud concentration and switching frictions is not limited to Brussels. The UK Competition and Markets Authority (CMA) has been probing cloud market structure and in 2025 reported that Microsoft and Amazon each hold large shares of customer spend, with significant barriers to switching resulting from egress fees and restrictive licensing practices. The CMA has recommended further investigation into whether the firms should be designated with “strategic market status” under UK digital markets law. Those UK findings echo EU concerns about vendor lock‑in and the competitive effect of licensing differentials. Across jurisdictions, the pattern is consistent: national and supranational authorities see high market concentration among hyperscalers and evidence of contractual/technical features that hinder customer mobility.

---

Microsoft’s response and the CISPE settlement​

Microsoft has defended its commercial and licensing practices, arguing that it has made concessions and commitments to address legitimate interoperability and partner concerns. In mid‑2024 Microsoft reached an agreement with the European cloud trade group CISPE (Cloud Infrastructure Service Providers in Europe) that included product commitments and a lump‑sum compensation to CISPE to reimburse litigation and campaign costs. Reuters reported the figure at about €20 million (roughly $21–22 million). That settlement led CISPE to withdraw its formal complaint, although the agreement excluded some large providers and left unresolved questions, prompting criticism that Microsoft had effectively “paid off” one complainant without addressing broader industry concerns. Industry reaction to the CISPE deal was mixed: some European hosters welcomed the product changes and the establishment of an observatory to monitor compliance, while rival hyperscalers and trade groups questioned the settlement’s scope and transparency. Google explicitly criticized the agreement at the time, arguing it did not fully resolve the competitive harm it alleges.

---

Practical implications for enterprises and public procurers​

The shift from private complaints to DMA‑led market probes should prompt immediate, actionable steps for IT leaders and procurement teams. The regulatory process will take months, and firms must manage commercial risk while the policy landscape evolves.
Key, practical moves:

• Audit licensing exposure
• Inventory contracts involving Microsoft server products, SQL Server, Entra ID, and their cloud licensing terms.
• Quantify exit costs, egress fees, and any surcharges linked to running Microsoft workloads on non‑Azure providers.
• Push for contractual portability clauses
• Negotiate specific migration assistance and portability guarantees in new agreements, including defined export windows, support for data‑format portability, and capped egress or migration fees.
• Design for multi‑cloud portability
• Where feasible, minimize use of vendor‑specific managed services that are hard to replicate elsewhere. Use containers, standard orchestration layers, and IaC (Infrastructure as Code) templates to reduce migration engineering effort.
• Build governance and scenario planning
• Model the financial and technical impact of regulatory outcomes (e.g., gatekeeper designation, new DMA obligations). Have contingency plans for supplier change or split‑deployment strategies.
• Engage with the process
• Large enterprise customers and public bodies are influential stakeholders in regulatory enquiries. Where appropriate, submit anonymized evidence to regulators or engage via industry associations to highlight practical switching costs that regulators should consider.

These are not just defensive measures. Firms that prepare proactively—demanding clearer contractual terms and designing for portability—reduce vendor lock‑in and increase negotiating leverage regardless of regulatory outcomes.

---

Legal and technical risks the Commission must weigh​

The Commission faces a hard technical and legal balancing act. Policy ambition to foster portability and contestability must be squared with:

• Engineering realism: Mandating API exposure or identity portability can have complex security and backward‑compatibility consequences. Exposing internal control‑plane APIs or requiring Entra ID decoupling may be technically feasible in some cases but risky or disruptive in others.
• Innovation incentives: Regulators must avoid rules that strip vendors of the ability to differentiate by developing integrated, optimised services. For cloud providers, product improvements often arise from tight platform integration and vertical optimisation.
• Enforcement complexity: The cloud sector is global and contract‑driven. Tailoring DMA obligations to a market dominated by long‑term enterprise agreements will require carefully calibrated, technically informed remedies backed by credible monitoring and audit capacity.

Those trade‑offs explain why the Commission opened a horizontal review in addition to company‑level inquiries: the horizontal study can surface bespoke technical assessments and standardisation pathways so any DMA‑style obligations are workable and proportionate.

---

Who stands to win or lose​

• Potential short‑term winners include European cloud hosters and independent providers if regulators press for stronger portability, as they would face fewer artificial pricing barriers and could better compete for Microsoft‑centric workloads.
• Large enterprise customers could also benefit from clearer contractual rights and lower switching friction in the long term, assuming regulators require more transparent, portable licensing.
• Microsoft and AWS face scrutiny over market power and may be required to change some commercial practices, but they also possess resources to comply with complex obligations and to litigate or negotiate the fine detail. A gatekeeper designation would impose burdens, but hyperefficient cloud providers could amortise compliance costs at scale.
• Google Cloud has, by design, shifted the battlefield: rather than litigating a single complaint, it has positioned itself to influence a regulatory framework that could force systemic change—potentially a strategic win if the Commission adopts its priorities.

---

What to watch next — timeline and milestones​

• Now–3 months: Commission issues targeted information requests; firms and industry bodies must respond with contracts, technical documentation and evidence. Public consultations and targeted hearings may follow.
• 3–12 months: Preliminary findings in company‑level probes; the Commission could move to gatekeeper assessments and, depending on outcomes, propose designation and initial obligations.
• 12–18 months: Horizontal study conclusions and potential DMA adaptations for cloud; any formal designation or sectoral obligations could follow, subject to appeal and implementation phases.
• Parallel national developments: The UK CMA and other national authorities may continue their own processes; divergent national remedies could complicate compliance for global providers.

Enterprises should assume a prolonged regulatory phase and plan for incremental changes rather than immediate, sweeping outcomes.

---

Strengths and weaknesses of regulatory attention​

Strengths:

• The DMA process provides the Commission with tools to impose systemic remedies that could expand cloud competition and reduce vendor lock‑in across Europe. Those remedies would be more durable than negotiated settlements that cover only specific complainants.
• A multi‑stakeholder evidence record reduces the chance of one‑sided litigation outcomes influenced primarily by asymmetric commercial interests. A regulator‑driven process can weigh broader public‑interest considerations, such as digital sovereignty and AI‑era infrastructure resilience.

Risks:

• Poorly calibrated rules could introduce technical friction, raise compliance costs, and slow product innovation. Compulsory API exposure or poorly designed portability mandates could create security or operational risks.
• Disparate national outcomes (e.g., divergent CMA remedies in the UK versus DMA obligations in the EU) could fragment compliance requirements for global providers and increase complexity for enterprise customers.
• Empirical verification remains hard: headline numbers about markups or aggregate damages are often derived from confidential contracts. Regulators will need granular documentary evidence to translate allegations into defensible remedies. Where that evidence is absent or contradictory, remedies risk being overbroad or under‑anchored.

---

Bottom line and strategic read for IT leaders​

Google’s decision to withdraw its antitrust complaint against Microsoft is not the end of the story; it is a strategic recalibration that transfers the dispute into a public, DMA‑driven regulatory process with broader reach and potentially faster, systemic remedies. Enterprises should treat the next 12–18 months as a period of regulatory flux and prepare by auditing exposure, demanding clearer portability terms, and architecting workloads for resilience and portability.
Regulators have a real opportunity to rebalance contestability in cloud markets. But the technical and contractual complexity of cloud platforms means that meaningful remedies will require careful, evidence‑based design and cross‑industry collaboration. The next wave of Commission evidence collection and public consultations will shape not only how enterprises license Windows Server and SQL Server in cloud deployments but also how competition and sovereign cloud strategies are governed in the AI era.

---

Appendix — Immediate checklist for procurement and IT teams​

• Inventory: List all contracts with Microsoft product dependencies and note any migration clauses, audits, egress fees, or cross‑platform surcharges.
• Negotiate: Add explicit portability commitments and defined migration assistance in new procurement rounds.
• Architect: Prioritise containerisation, standard orchestration and IaC to lower migration engineering costs.
• Govern: Establish a cross‑functional team to model regulatory scenarios and their P&L and technical impacts.
• Engage: Where possible and appropriate, feed anonymised evidence to regulators or participate via industry associations.

Proactive action will be the most effective defence against regulatory uncertainty and the best way to extract commercial leverage from shifting policy dynamics.

---

Google’s withdrawal signals a strategic realignment of tactics rather than a retreat from the argument over cloud portability and fair licensing. The real contest now belongs to Brussels’ DMA machinery—and the months ahead will determine whether Europe engineers a set of workable, technically sound rules that restore contestability without stifling platform innovation.

---

Source: IT Pro Google drops cloud complaint against Microsoft