Google has formally withdrawn its antitrust complaint against Microsoft’s cloud licensing practices in the European Union, citing the European Commission’s recent launch of broader market investigations into cloud computing under the Digital Markets Act (DMA). The move shifts Google’s fight from a single case lodged last year to a regulatory process that could address systemic, sector‑wide issues—potentially forcing remedies that are more structural and faster to implement than traditional antitrust rulings.
Background
The original complaint and the cloud war
In September 2024 Google Cloud filed an antitrust complaint with the European Commission alleging that Microsoft used licensing terms and commercial mechanics to “lock” enterprise customers into its Azure platform, raising switching costs and disadvantaging competing cloud providers. Google argued that restrictive license surcharges and discriminatory contractual terms penalized customers that ran Microsoft workloads outside Azure, raising costs cumulatively into the hundreds of millions annually for European customers. Those allegations landed in a turbulent regulatory environment where multiple actors—national regulators, trade bodies and rival hyperscalers—have pressed Brussels for action. A separate complaint from the industry group CISPE and other national inquiries have already focused attention on licensing, portability, and interoperability in cloud markets. Microsoft meanwhile negotiated a settlement with CISPE in 2024 that resolved that organisation’s claims and included commitments about new licensing options and product releases for European hosters.
The European Commission’s new approach: DMA market investigations
On 18 November 2025 the European Commission opened three DMA‑based market investigations into cloud computing services. Two target whether Amazon Web Services (AWS) and Microsoft Azure function as “gatekeepers” for cloud computing under the DMA’s framework; the third is a sectoral study to test whether the DMA’s toolkit can be applied to cloud services and to identify the practices that restrict contestability and fairness. The Commission explicitly flagged issues such as interoperability barriers, conditioned access to business user data, tying and bundling, and imbalanced contractual terms as topics for fact‑finding. The DMA path gives Brussels ex‑ante powers that differ materially from conventional competition enforcement: gatekeeper designation can trigger non‑discrimination requirements, mandated interoperability, stronger portability obligations, and faster remedies. The Commission has statutory targets for market investigations and “endeavours” to complete such processes within about 12 months, meaning the probe could produce meaningful regulatory steps long before a drawn‑out antitrust court fight concludes.
What happened: Google’s withdrawal and official accounts
Google’s public explanation frames the withdrawal as pragmatic: the complaint—filed to “give voice” to customers and partners concerned about restrictive licensing—has been withdrawn because the Commission’s DMA investigations will “assess problematic practices affecting the cloud sector under a separate process,” making a single complainant’s case redundant or less strategically useful. Google also stressed it will continue to engage with policymakers and regulators in the EU and the UK in pursuit of increased openness and customer choice. Microsoft has consistently defended its commercial practices and points to the CISPE settlement and other industry engagements as evidence that many concerns were already addressed through negotiation and product roadmaps. Microsoft’s public posture has been that the cloud market remains competitive and that tailored settlements resolved many complainants’ issues—positioning the company to argue that additional enforcement is unnecessary or disproportionate.
Why Google withdrew: strategic calculus and evidence amplification
Channeling leverage into a broader forum
Withdrawing a complaint does not equate to abandoning the underlying allegations. Instead, Google’s move is best read as a deliberate reallocation of political and evidentiary capital from a single antitrust filing to the Commission’s DMA process—where remedies can be applied systemically across the cloud sector and to multiple providers simultaneously. Under the DMA, regulators can require behavioural or structural fixes that apply to entire product classes; that scale makes the DMA an inherently more attractive enforcement route for companies seeking durable, sector‑wide change.
Avoiding fragmented or duplicative proceedings
Parallel or overlapping legal tracks risk inconsistent remedies. By stepping back from a stand‑alone complaint, Google reduces the chance of procedural duplication or divergent outcomes that could blunt the Commission’s ability to extract uniform remedies. A single DMA market investigation can integrate evidence from multiple complainants, industry witnesses and internal telemetry in one consolidated record—something a case‑by‑case approach cannot.
Tactical evidence collection and political optics
The DMA empowers Brussels to issue broad information requests—contracts, telemetry, invoices, technical documentation—and to convene technical fact‑finding with market participants. That kind of discovery is well suited to the cloud context where claims turn on detailed contract mechanics (licence triggers, pricing differentials) and technical interoperability (APIs, control‑plane access). Google can now rely on the Commission’s compulsory powers to surface the corroborating materials that are often out of reach for private litigants.
Immediate market context: market shares and positioning
Market share numbers for cloud infrastructure continue to show sharp concentration at the top: AWS leads globally with roughly a 30% share, Microsoft Azure is estimated around 20%, while Google Cloud sits in the low teens. Those figures vary by geography and by whether the measure is revenue, infrastructure spend or specific service slices, but they illustrate the dominance of the “big three” hyperscalers and explain why Brussels sees the cloud sector as a strategic chokepoint for AI and digital sovereignty. These shares underpin Brussels’ logic: even if AWS and Azure do not meet the DMA’s quantitative gatekeeper thresholds, their de facto control over enterprise cloud infrastructure in certain markets could justify designation under the DMA via a market investigation. The Commission’s November 18 announcement explicitly covers exactly that scenario.
What the DMA probe can do that antitrust complaints cannot
- Apply ex‑ante rules: The DMA can impose forward‑looking obligations to prevent anti‑competitive conduct before it hardens into entrenched lock‑in.
- Mandate interoperability: Brussels can require technical interoperability and non‑discriminatory access to critical interfaces, which are central to cloud portability.
- Force broad remedies: The Commission can require changes that apply to entire product lines or service classes, rather than narrow case‑by‑case relief.
- Impose heavy sanctions: Violations of DMA obligations carry fines of up to 10% (or more for repeat breaches) of global turnover and the potential for structural remedies in the most severe cases.
These powers change the enforcement calculus: companies facing the DMA are subject to standardised obligations with clear timelines for compliance, and non‑compliance risks immediate and substantial penalties.
Implications for Microsoft, AWS and the broader industry
For Microsoft
If Microsoft Azure is found to act as a DMA “gatekeeper” for cloud services, Microsoft could face:
- Non‑discrimination obligations preventing preferential bundling of Microsoft software with Azure.
- Mandated interoperability and data‑portability rules to ease migration.
- Forced transparency around pricing and licensing mechanics.
- Possible restrictions on tying or contractual practices that raise switching costs.
Such remedies would materially change how Microsoft bundles Windows Server, SQL Server and Office with cloud provisioning and could require product redesigns or new licensing models. Microsoft’s prior settlement with CISPE and its rollouts for European hosters may blunt certain claims, but the DMA probe’s sectoral scope and sanction tools make outcomes far from certain.
For AWS
AWS faces parallel scrutiny. The DMA market investigation into AWS follows similar logic: market power in cloud infrastructure creates incentives and opportunities to entrench position via technical or contractual design. AWS will therefore be required to explain design decisions, pricing differentials and interoperability practices. A determination that AWS is a gatekeeper would expose it to a similar suite of obligations and enforcement risks.
For Google Cloud and other rivals
Google’s withdrawal suggests a bet that EU regulators can deliver broader remedies faster than individual litigation. If regulators impose interoperability rules and ban discriminatory license conditions, smaller cloud providers and specialist European hosters could see a more level playing field. That could accelerate competition, cut migration costs and lower the friction for enterprises to run Microsoft workloads on non‑Azure platforms—potentially a commercial win for Google Cloud if the remedies are meaningful and enforceable.
What it means for enterprise customers and public sector buyers
Enterprises trapped by license terms or worried about vendor lock‑in stand to gain the most if Brussels extracts concrete interoperability and portability commitments. Practical outcomes that matter to customers include:
- Easier licence portability for Windows Server, SQL Server and other Microsoft stack components.
- Lower or eliminated “penalty” surcharges for running Microsoft software outside Azure.
- Clearer contracts and greater transparency around price triggers and egress charges.
- Technical standards or APIs that make migration less risky and painful.
However, customers should temper optimism: DMA investigations and subsequent remedies still take time, and companies may need to engage with new compliance regimes and reporting obligations that change commercial workflows. The net effect for customers will depend heavily on the specificity and enforceability of the Commission’s findings.
Legal, commercial and political risks
1. Regulatory complexity and implementation friction
Applying DMA obligations to contractual and technical features of enterprise cloud stacks is legally and technically complex. Regulators will need deep technical evidence and credible benchmarks to craft workable remedies; vague or overly prescriptive orders risk unintended side effects that harm interoperability or security. The Commission has acknowledged this complexity by launching a thematic study alongside company probes, but the risk of imperfect remedies is real.
2. Divergent national stances and geopolitics
EU cloud policy is intertwined with broader digital‑sovereignty debates. Some member states prioritise openness and competition, while others stress local data control and industrial policy. Remedies that tilt market access toward either outcome could create political friction and prompt parallel national measures. That complexity raises the chance of appeals and prolonged legal challenges.
3. Litigation, reprisals and global domino effects
A harsh DMA outcome could trigger multijurisdictional litigation and even reciprocal regulatory scrutiny in other markets. It could also prompt hyperscalers to recalibrate product strategies and pricing globally, with potential knock‑on effects for customers outside the EU. Conversely, a weak remedy risks entrenching incumbents and leaving structural issues unresolved.
4. Unverifiable or disputed facts
Several claims in the public debate—such as precise licensing “penalty” amounts, the exact financial harm to customers, or the true extent of self‑preferencing—are contested and often based on trade group studies or company submissions. Regulators will need to validate those assertions with primary documents and independent technical audits. Where public claims lack corroborating documentary evidence, treat them as allegations pending formal evidentiary testing.
Timeline and procedural outlook
The Commission’s DMA press release signals an accelerated fact‑finding clock: market investigations under the DMA are expected to target preliminary findings within months and aim to conclude within roughly 12 months, although precise timing depends on the volume of evidence and the need for technical hearings. If preliminary findings point to gatekeeper designation, the Commission can impose specific obligations and begin monitoring compliance with statutory reporting duties. Meanwhile, companies can expect exhaustive information requests and must prepare for on‑site or technical audits. Steps to watch next:
- Commission information requests to Microsoft and AWS and responses from those firms.
- Third‑party submissions from cloud customers, hosters and independent experts.
- Technical hearings or workshops to calibrate interoperability remedies.
- Any preliminary findings indicating gatekeeper status or recommended remedial packages.
What to watch: key scenarios and business outcomes
- Scenario A — DMA finds gatekeeper status and mandates interoperability: this would likely force licensing parity, ban discriminatory packaging and reduce switching costs materially; a structural shift in cloud competition could follow.
- Scenario B — Commission identifies problematic practices but stops short of gatekeeper designation, instead recommending targeted obligations or guidance: this would yield more modest but still meaningful changes to contracts and APIs.
- Scenario C — Commission declines to act substantively after investigation: regulatory inaction would keep current industry dynamics intact and leave competitors to pursue litigation or market remedies.
Each scenario has distinct commercial consequences for Microsoft, AWS, Google Cloud and EU hosters. The most disruptive outcomes are only possible if the Commission deploys the full scope of the DMA’s remedial powers.
Bottom line: a strategic pivot with high stakes
Google’s withdrawal of its EU complaint is not capitulation—it is a strategic pivot. By choosing to concentrate pressure on the Commission’s DMA probes rather than pressuring through a single antitrust complaint, Google and its allies are betting that Brussels can deliver cross‑cutting remedies more quickly and effectively than piecemeal litigation. That bet elevates the stake of the Commission’s market investigations: a decisive DMA intervention could reshape cloud market mechanics across Europe and set a precedent for global cloud competition policy. At the same time, the legal and technical complexity of imposing DMA remedies on enterprise cloud stacks means the path forward will be contested, evidence‑heavy and politically charged. Enterprises, public sector buyers and smaller cloud providers should follow the process closely: outcomes could lower switching costs and boost competition—or, if remedies are poorly calibrated, create new compliance burdens without solving the underlying market frictions.
Conclusion
This episode is a milestone in the ongoing “cloud wars.” Google’s withdrawal of its complaint reframes the debate from a bilateral dispute with Microsoft into a sector‑wide regulatory engagement with Brussels—one that will test the Digital Markets Act’s reach into enterprise infrastructure and determine whether Europe can effectively police cloud competition at scale. The Commission’s investigations will demand deep technical evidence, rapid procedural work and robust legal analysis. For the cloud market’s many stakeholders, the coming months will be decisive: the DMA has the power to deliver systemic remedies, but the quality and enforceability of those remedies will determine whether customers see real relief or simply another round of regulatory theater.
Source: ET Telecom
Google ditches EU antitrust complaint about Microsoft cloud amid EU probe