Google’s surprise withdrawal of its year‑old EU antitrust complaint against Microsoft hands the baton to Brussels’ newly launched, DMA‑driven cloud market investigations and reframes the rivalry over cloud portability from bilateral litigation to a systemic regulatory fight with potentially industry‑wide consequences.
Background / Overview
The dispute traces back to a formal complaint Google Cloud filed with the European Commission in September 2024, accusing Microsoft of structuring licensing, packaging and commercial terms in ways that raised the practical cost of running Microsoft workloads on rival clouds — a set of allegations framed as vendor
lock‑in and self‑preferencing. Over the past year regulators and trade groups have been intervening in different ways. A summer 2024 settlement with CISPE — a coalition representing European cloud providers — addressed some interoperability and licensing frictions, though Google did not sign onto that deal. The Commission then escalated matters: on 18 November 2025 Brussels launched three coordinated market investigations under the Digital Markets Act (DMA), focused on Microsoft Azure, Amazon Web Services (AWS), and a horizontal sectoral review examining whether DMA tools should apply to cloud infrastructure. Ten days after that DMA announcement, Google publicly withdrew its standalone complaint, explaining that the Commission’s broader inquiries provide a superior vehicle to address the structural issues the company had raised. The withdrawal is explicitly tactical: Google is not retracting the substance of its allegations but is redirecting its evidentiary and policy efforts into Brussels’ market probes.
Why the move matters: process, power and reach
The shift from a private Article 102 style antitrust complaint to a DMA‑led market investigation is more than procedural — it alters the palette of remedies and the pace at which Brussels can act.
- The DMA provides ex‑ante powers that can deliver prescriptive, system‑level obligations (interoperability, non‑discrimination, mandatory API exposure) rather than case‑by‑case, ex‑post remedies.
- The Commission’s market investigations can compel documents and testimony across multiple market participants and settle sectoral facts on a timetable that Brussels has signalled will be fast relative to classic antitrust probes.
- If the Commission designates Azure or AWS as DMA “gatekeepers” for cloud services, it could impose binding obligations with ongoing compliance, reporting requirements, and steep penalties for breaches.
That combination of investigatory breadth, speed and regulatory toolkit is precisely the leverage Google sought when it originally filed the complaint — but now it expects Brussels to wield that leverage on a market‑wide basis.
The factual record: what’s verified and what remains contested
What’s verifiable right now:
- Google has formally withdrawn its EU antitrust complaint against Microsoft.
- The European Commission announced three DMA‑based market investigations into cloud services on 18 November 2025.
- Market share snapshots show the hyperscalers dominate infrastructure spending: AWS remains the largest, followed by Microsoft and Google, a fact that underpins Brussels’ interest in systemic remedies. Industry trackers place AWS at roughly 29–30% of global IaaS/PaaS spending, Microsoft around 20–24%, and Google Cloud in the low‑to‑mid teens (roughly 9–13% depending on the dataset and quarter).
What remains contested or unverifiable in public sources:
- Specific numeric claims cited by complainants and trade groups — for example, references to license markups “up to 400%” or aggregate annual “cloud taxes” amounting to hundreds of millions or €1bn — are based on contract excerpts, proprietary cost models or trade‑group studies and cannot be confirmed without regulator access to confidential contracts and billing records. Regulators will need to test those figures directly in evidence‑gathering. Treat those headline numbers as allegations pending verification.
The allegations: technical mechanics that matter
The original complaint and subsequent public commentary concentrate on a handful of technical and contractual levers that can create switching friction:
- Differential licensing: Microsoft’s licensing terms for Windows Server, SQL Server and related products may be structured so that running those products on third‑party clouds carries surcharges or less favourable licensing conditions compared with running them on Azure. Google argues this effectively penalises customers who host Microsoft workloads off‑Azure.
- Migration and egress friction: High data egress costs, limited or cumbersome export tooling and contractual exit penalties can materially increase migration costs and timelines. Those frictions are part of the portability question Brussels will probe.
- Proprietary control‑plane and managed services lock‑in: Managed services and control‑plane APIs that are deeply integrated with Azure may make re‑engineering workloads to run on other clouds expensive, functionally risky or operationally different — therefore raising the engineering cost of true portability.
- Self‑preferencing and marketplace mechanics: Packaging, marketplace placement and first‑party managed services may advantage Azure’s native offerings in discovery, pricing or integration, disadvantaging independent vendors and competitors.
These are precisely the vectors Brussels’ horizontal DMA review intends to test for cloud‑specific contexts. The DMA’s toolkit is attractive because it allows regulators to mandate non‑discrimination and interoperability
before harms become fully entrenched.
How the major players are reacting (and why their positions matter)
What Google has said:
- Google framed its withdrawal as pragmatic — it will continue to engage with Brussels and submit evidence to the DMA probes while leaving the Commission to undertake broader sectoral fact‑finding. Google updated its Cloud blog accordingly and reaffirmed its concerns about openness and choice in cloud markets.
What Microsoft has said:
- Microsoft has repeatedly denied systemic wrongdoing, highlighting previous settlements with European cloud providers and arguing that the market is competitive and its licensing changes are legitimate product differentiation and security decisions. Microsoft also maintains that the CISPE settlement addressed many practical concerns raised by some complainants.
What AWS and third parties are doing:
- AWS has been separately targeted by Brussels’ market investigations. The DMA probes create a rare moment of regulatory attention on the entire cluster of hyperscalers, meaning that both AWS and Microsoft must now defend market practices that underpin enterprise cloud contracts and AI infrastructure investments. Independent European hosters and regional cloud providers will try to use Brussels’ process to secure better interoperability and contractual transparency.
Why the players’ posture matters:
- Big tech firms are balancing legal risk, procurement stability and public image. For Microsoft and AWS, gatekeeper designation would impose structural obligations that could force product rewrites, API exposure, and long‑term compliance regimes. For Google, the DMA route offers the prospect of durable structural remedies that may help its Cloud business compete on more even terms. Each company’s public messaging is therefore calibrated to shape Brussels’ factual record and wider public opinion.
What Brussels can actually do — legal remedies and practical limits
If the Commission concludes that certain cloud services function as DMA‑relevant gatekeepers, potential remedies could include:
- Mandatory interoperability between key platform control planes and third‑party alternatives.
- Non‑discrimination obligations preventing self‑preferencing of first‑party managed services.
- Transparency and contractual fairness rules requiring clearer terms, exit‑cost disclosures, and limits on punitive license surcharges.
- Portability mandates to ease migration of workloads and stateful data between providers.
- Behavioral or structural remedies — ranging from product interoperability orders to, in extreme scenarios, divestiture‑style relief (though the latter is unlikely for infrastructure services and politically fraught).
Practical limits and risks for regulators:
- Cloud infrastructure is technically complex; blunt mandates can inadvertently harm performance, security or innovation if not carefully designed.
- Remedies requiring massive API exposure or real‑time telemetry sharing create operational security and IP protection questions.
- Compliance costs are real and will likely be passed through to customers in the short term.
Brussels will therefore need to partner with technical experts and standard bodies to calibrate obligations so they are enforceable, measurable and operationally realistic.
Strategic analysis: strengths, weaknesses and risks of Google’s pivot
Strengths of Google’s approach:
- Leverages the Commission’s power: The DMA process offers a more powerful, systemic enforcement toolbox than a single Article 102 complaint could deliver. Redirecting the dispute to an institutional forum raises the odds of broad remedies.
- Avoids parallel proceedings: Withdrawing the complaint reduces the risk of fragmented rulings and duplicative evidence requests that could produce inconsistent outcomes.
- Political optics: It reframes Google as a champion of systemic reform rather than a single‑company litigant — a posture that can resonate with policymakers and public procurement officials.
Weaknesses and risks:
- Ceding control of timing and scope: Brussels controls the investigation’s timetable and priorities; Google is now a participant, not the agenda‑setter.
- Protracted uncertainty: DMA probes can take 12–18 months, leaving enterprise customers and rivals in a long period of regulatory uncertainty that can freeze procurement decisions.
- Public scrutiny of Google’s own cloud strategy: As Google pushes the DMA framing, regulators and rivals may scrutinise Google’s own packaging and market behaviour.
What enterprises and IT leaders should do now
For IT and procurement teams, this regulatory pivot is practical and immediate — not merely academic. An actionable checklist:
- Audit license exposure: Map where Windows Server, SQL Server and other vendor licences run, and quantify contractual exit costs and clauses that affect portability.
- Negotiate visibility: Demand clearer egress pricing, exit penalties and portability terms in new cloud agreements.
- Design for portability: Prioritise containerisation, infrastructure‑as‑code, and automation that reduce friction across clouds.
- Architect defensively: Test disaster recovery and failover across multiple clouds where feasible; avoid one‑time engineering patterns that create untested single‑vendor dependencies.
- Use compliance and procurement levers: Insert contractual SLAs and audit rights to obtain telemetry or billing evidence that will be valuable if regulatory scrutiny deepens.
- Monitor procurement policy: Follow public procurement guidance in the EU and member states; some public buyers may begin to require portable, open standards for critical workloads.
These steps balance short‑term operational continuity with longer‑term strategic optionality. Enterprises that prepare now will be in a better position to exploit any regulatory improvements in portability and transparency that emerge from Brussels’ probes.
Likely timelines and milestones to watch
- Evidence requests and information gathering — expected immediately after the DMA market investigations were opened; regulators will issue formal information requests to major providers and customers.
- Company‑level assessments (Azure, AWS) — Brussels indicated roughly a 12‑month window to assess gatekeeper designation for the targeted providers.
- Horizontal sectoral report — a broader market review could take 18 months and may recommend DMA adjustments or sector‑specific obligations.
- Interim remedies or sector guidance — regulators may issue interim guidance or soft remedies before final determinations to address acute harms.
- Litigation and appeals — any designation or binding obligation will likely be litigated, extending the effective timeline for final outcomes.
Broader implications: competition, sovereignty and AI
Two structural trends make this fight consequential beyond immediate licensing questions:
- AI infrastructure demand: Hyperscalers’ cloud platforms are the backbone for enterprise AI workloads. Any regulatory order affecting portability, API access or data flows will shape not only cloud competition but the economics of training and serving large AI models.
- Digital sovereignty and EU industrial strategy: The EU views cloud portability and interoperability as part of strategic digital sovereignty. Remedies that improve portability could bolster European cloud alternatives and reshape procurement for public sector AI and critical infrastructure projects.
The stakes extend well beyond commercial rivalry: the Commission’s outcomes will influence where workloads sit, which vendors win enterprise and public contracts, and how resilient supply chains for AI compute become over the next decade.
Conclusion
Google’s withdrawal of its EU antitrust complaint against Microsoft is a deliberate, strategic pivot — a hand‑off to Brussels’ DMA machinery that elevates the dispute from a single complaint to a sectoral, regulatory showdown. That move increases the likelihood of systemic remedies but also ushers in prolonged uncertainty for enterprises, vendors and investors alike. Regulators now have a unique opportunity — and a heavy responsibility — to craft technically precise, proportionate rules that increase contestability without undermining the security, performance and investment incentives that underpin modern cloud and AI infrastructure. For IT leaders, the right response is pragmatic: quantify licence and exit exposure, demand contractual clarity, and design systems for portability today so they remain resilient whatever Brussels ultimately decides.
Source: SiliconANGLE
Google drops EU antitrust complaint against Microsoft amid cloud probe - SiliconANGLE