Alphabet’s Google has formally withdrawn its formal complaint to the European Commission alleging that Microsoft’s cloud licensing and commercial practices lock customers into Azure — a move that comes after Brussels opened a sweeping set of market investigations into the cloud sector that could see Microsoft’s Azure and Amazon Web Services treated as regulated “gatekeepers” under the EU Digital Markets Act.
Google’s withdrawal is both tactical and symbolic: the company told regulators and customers it will no longer pursue the standalone antitrust complaint it filed last year because the European Commission has launched a broader, DMA‑linked process to examine potentially problematic practices across the cloud market. That EU process assesses whether the structure and commercial features of today’s cloud industry strengthen incumbent hyperscalers — notably AWS and Azure — and whether the Digital Markets Act (DMA) or other competition tools should be adapted to address cloud‑specific issues. This development ties together four pieces of an unfolding digital policy story in Europe:
The Commission’s choice to use the DMA framework — while novel for cloud services — is defensible because the DMA is designed to stop entrenched platform behavior before it ossifies. The danger, however, is twofold: (1) that EU rules become over‑prescriptive and raise the cost of capital for infrastructure; and (2) that regulatory actions fail to keep pace with the rapid technical change of AI and cloud engineering, inadvertently locking in today’s market leaders under new compliance burdens.
Practical remedies that would strike a useful balance include narrowly targeted obligations on contractual fairness (greater transparency and portability in license terms), clearer rules on egress and pricing transparency, and time‑limited interoperability measures focused on data portability and principled API escape hatches — all designed to lower switching friction while preserving incentives for massive infrastructure investment.
The next 12 months of the Commission’s investigations will be decisive. Companies, trade associations, and national authorities will supply the evidence; Brussels will weigh systemic risks against the innovation imperative; and users — enterprise IT organizations and developers — will watch to see whether Europe’s regulatory experiment produces more choice and lower lock‑in, or whether it raises the compliance costs of the infrastructures that now power modern businesses.
The outcome will reshape not only commercial cloud contracts but also the regulatory template for dealing with the infrastructural layer beneath AI — making this probe one of the most consequential tech policy developments for Europe’s digital economy in the coming year.
Source: The Hindu Google ditches EU antitrust complaint about Microsoft cloud amid EU probe
Overview
Google’s withdrawal is both tactical and symbolic: the company told regulators and customers it will no longer pursue the standalone antitrust complaint it filed last year because the European Commission has launched a broader, DMA‑linked process to examine potentially problematic practices across the cloud market. That EU process assesses whether the structure and commercial features of today’s cloud industry strengthen incumbent hyperscalers — notably AWS and Azure — and whether the Digital Markets Act (DMA) or other competition tools should be adapted to address cloud‑specific issues. This development ties together four pieces of an unfolding digital policy story in Europe:- A detailed public complaint by Google about Microsoft’s licensing terms and pricing practices that Google says penalize customers who choose rival clouds.
- A formal EU market investigation into cloud services under the DMA framework, opened by the Commission in mid‑November 2025.
- Public statements and pushback from the hyperscalers defending cloud competitiveness.
- Google’s calculated decision to fold its specific complaint into the Commission’s broader inquiry — an overture to regulators that lets Brussels take the lead while Google continues public advocacy.
Background: Google’s complaint and the licensing dispute
What Google alleged
In a widely publicized blog post and a formal complaint to the European Commission, Google Cloud accused Microsoft of anti‑competitive licensing practices that, according to Google, make it materially more expensive for enterprises to run Windows Server and related workloads on rival clouds. Google’s argument focused on contractual terms and price structures that allegedly favor Azure and disincentivize customers and managed service providers from migrating or running dual‑cloud deployments. Google also framed those licensing policies as a systemic problem with cross‑border economic implications, arguing they harm competition, reduce customer choice, and ultimately raise costs for European businesses. The company quantified the alleged economic harm in public materials, though such macroeconomic estimates are inherently contestable and stem from Google’s policy advocacy rather than independent econometric verification. Those aggregate economic projections should be treated as Google’s policy claims, not established fact.Timeline and public messaging
Google first made its public complaint and related blog posts in late 2024 and refreshed the message across 2025, continuing to press regulators in the EU and the UK. On November 28, 2025, Google posted an editorial note to its original blog entry stating it was withdrawing the formal complaint in light of the Commission’s decision to launch targeted market investigations into the cloud sector. Giorgia Abeltino, Google Cloud’s head of government affairs and public policy for Europe, signed the editor’s note.The European Commission’s probe: scope, timeline, and legal context
What Brussels announced
On November 18, 2025, the European Commission opened three market investigations under the Digital Markets Act framework: two investigations, focused on Microsoft Azure and Amazon Web Services respectively, are designed to determine whether those cloud services act as important gateways — a status that could lead to gatekeeper designation; the third investigation examines whether the DMA’s existing obligations are fit for purpose in addressing cloud‑specific competitive frictions such as interoperability barriers, conditioned access to data, tying and bundling, and contractual imbalances. The Commission aims to complete the investigations within roughly 12 months.Why the DMA matters here
The DMA creates a menu of ex ante obligations and prohibitions for designated gatekeepers (large digital platforms deemed to have systemic importance). If a cloud service is designated as a gatekeeper for cloud computing, that service would face mandated behavioral rules intended to guarantee openness, non‑discrimination, and interoperability — measures that could directly touch on the practices Google complained about. Importantly, the Commission is explicitly exploring whether cloud services can be treated like traditional core platform services even when the providers do not meet standard DMA thresholds. That legal and policy question is central: the DMA was not originally drafted with cloud‑infrastructure services at the forefront, so Brussels is now assessing whether delegated acts or interpretative steps are needed.Market structure: who dominates and why it matters
Independent market research confirms that the cloud infrastructure market is heavily concentrated. Q3 2025 data from Synergy Research Group and corroborating industry reporting show the three hyperscalers — Amazon Web Services (AWS), Microsoft Azure, and Google Cloud — together control roughly two‑thirds of enterprise spending on cloud infrastructure. Recent quarterly snapshots put AWS around 29–30% market share, Microsoft Azure at roughly 20%, and Google Cloud at about 12–13%. Those shares vary slightly quarter to quarter but illustrate a persistent three‑player dynamic. Why this concentration matters:- Scale advantages feed faster infrastructure investment and better price economics for the largest providers, reinforcing network effects.
- Customers face switching costs, varied licensing regimes, and contractual complexity when migrating workloads between hyperscalers. These frictions create potential for vendor lock‑in even without legal monopolization.
- Rapid AI demand is amplifying the incumbents’ power: hyperscalers invest at scale in GPUs, custom chips, and global data centers — resources newcomers find costly to match. That dynamic increases the regulatory stakes because cloud is now the substrate for AI services and national digital sovereignty goals.
Why Google withdrew the complaint: a strategic reading
Avoid duplicative processes and seek a comprehensive remedy
Google’s public explanation is straightforward: the company withdrew its specific complaint because the European Commission has initiated a broader process that will assess problematic cloud practices across the sector. By folding its case into a regulatory market investigation rather than pursuing a stand‑alone complaint, Google effectively bets on a systemic fix rather than a narrow remedy. That makes strategic sense: a DMA‑style remedy or a sector‑wide delegated act could change commercial incentives across several providers, whereas an individual antitrust case risks producing micro‑level remedies that fail to reshape industry architecture.Regulatory signalling and optics
Withdrawing the complaint also signals to Brussels and to public audiences that Google backs the EU’s initiative and prefers regulatory leadership — an approach that amplifies Google’s policy arguments while avoiding the optics of adversarial litigation at the same time the Commission is taking action. It positions Google as a collaborator in policy development rather than a lone complainant hoping for a piecemeal victory.Risk management and evidence consolidation
Antitrust decisions depend on detailed evidence. A broader market investigation allows the Commission to gather cross‑market data, supplier and customer testimony, and comparative contractual terms across many vendors — a richer evidentiary base than a single party complaint can provide. Google likely calculated that its arguments would be better served inside a full sectoral inquiry that could lead to structural or regulatory remedies. This is a tactical shift rather than an admission of error.Reactions from the industry and regulators
Microsoft and AWS responses
Both Microsoft and Amazon publicly insisted the cloud market remains competitive and warned against heavy‑handed regulation that might slow innovation or raise costs for European businesses. Microsoft said it stood ready to contribute to the probe and emphasized the vitality and choice present in cloud services; AWS similarly argued the sector is dynamic and that designating cloud providers as gatekeepers carries risks to innovation. Those statements mirror the standard industry framing that ex ante regulation can unintentionally curb investment incentives in capital‑intensive infrastructure.Other regulators and competition authorities
The UK Competition and Markets Authority (CMA) has separately signalled concern about the market power of AWS and Microsoft in cloud and AI, and the CMA’s provisional findings have highlighted issues such as sustained returns above cost of capital and structural investment dynamics that could foreclose competition. These national probes — together with the EU’s DMA investigations — create a multi‑jurisdictional regulatory pressure cooker for hyperscalers. National findings and provisional remedies differ in scope and standard from EU DMA designation procedures; coordination across authorities will be consequential.What the Commission could do: scenarios and timelines
Scenario A — Designate AWS and/or Azure as DMA gatekeepers
If the Commission concludes AWS and/or Azure operate as important gateways, it could designate their cloud services as gatekeepers. Designation would bring mandatory obligations — for example, non‑discriminatory treatment of third‑party services, limits on tying and preferential self‑preference, and improved interoperability. Under current Commission statements, the investigations are expected to wrap up in about 12 months; if designation follows, the firms would then have a limited period (the DMA anticipates implementation windows) to bring their practices into compliance.Scenario B — Targeted, sector‑specific rules or delegated acts
Even without formal gatekeeper designation, the Commission could use the third investigation (assessing whether the DMA needs updates for cloud) to propose delegated acts or updated guidance that impose cloud‑specific obligations — for instance on egress fees, license portability, or API interoperability. This path would aim to capture cloud‑specific frictions while avoiding the political and legal friction of a full gatekeeper designation. The Commission’s third probe can also lead to proposing amendments to how the DMA is applied to infrastructure services.Scenario C — Competition enforcement actions and negotiated remedies
Concurrently, the Commission could rely on classical competition law if it finds anticompetitive tying, abuse of dominance, or unfair contractual practices in specific cases. Those enforcement actions can produce targeted injunctions or commitments but may be slower and more case‑specific than a DMA approach. Google’s withdrawal arguably steers the conversation toward the DMA pathway rather than isolated antitrust litigation.Technical and commercial issues at stake
Vendor lock‑in and license portability
At the heart of Google’s complaint are licensing rules that allegedly make it costly to run Windows Server on non‑Azure clouds. This includes license transferability, penalties, and contractual constraints on managed service providers. The Commission’s market investigation explicitly lists such issues — conditioned access to data, tying/bundling, and interoperability challenges — as topics for inquiry. Whether such contractual terms amount to anticompetitive conduct under EU law depends on detailed market definition and proof of foreclosure.Egress fees, interoperability, and technical standards
Customers often face network egress fees, proprietary APIs, and integration work that make multi‑cloud strategies expensive. The DMA and other regulatory tools could target these practices by compelling clearer portability rules, or requiring standardized interfaces where technically feasible. However, imposing standards raises difficult technical questions: who defines the standard, how to preserve innovation, and how to avoid imposing inefficient uniformity. Those tradeoffs are front and center in the Commission’s analysis.AI, capacity constraints, and investment incentives
Generative AI workloads are intensifying demand for specialized infrastructure (GPUs, low‑latency networking, custom silicon). Market dynamics from 2025 show hyperscalers expanding capex aggressively, but there have also been capacity strain episodes (notably AWS’s summer 2025 AI capacity bottlenecks) that pushed some customers to rivals. Regulators must weigh whether ex ante obligations could disincentivize the large capital investments required to serve AI workloads at scale. This tension between competition policy and infrastructure investment underpins much of the hyperscaler debate.Strengths and weaknesses of the Commission’s approach
Notable strengths
- The Commission’s DMA pathway enables broad remedies that can alter market architecture and prevent repeat patterns of anti‑competitive conduct across the sector rather than leaving fixes to narrow court orders. That systemic lens matches how cloud services operate — as layers of infrastructure and platform functions whose cross‑cutting practices affect many customers.
- A consolidated market investigation can collect cross‑market data, harmonize rules across EU member states, and coordinate with other regulators (e.g., UK CMA), increasing the likelihood of effective, cross‑border enforcement.
Potential risks and weaknesses
- Over‑broad regulation risks: Imposing DMA‑style obligations on capital‑intensive cloud infrastructure might inadvertently increase compliance costs and slow investment cycles for providers, with knock‑on effects on prices and service innovation for European businesses. Several industry and policy analysts have warned about the potential for regulatory overreach. Policymakers must calibrate rules to avoid chilling infrastructure investment.
- Technical complexity and standardization hazards: Mandating interoperability or interfaces could lock in today’s technical approaches and reduce the flexibility vendors need to innovate, particularly for AI optimizations that depend on tight hardware‑software co‑design. Any interoperability requirements must be carefully bounded and technolog y‑neutral.
- Enforcement and litigation risk: Gatekeeper designations and novel delegated acts are likely to prompt high‑stakes litigation from large tech firms, potentially delaying the remedies and producing mixed legal outcomes under EU administrative law or international trade pressures.
What to watch next: calendar and indicators
- European Commission interim updates and stakeholder consultations over the next 12 months. The Commission has signalled an aim to wrap the Azure/AWS investigations within approximately one year.
- Any draft delegated acts or white papers that propose DMA modifications specific to cloud services; these would indicate Brussels’ appetite for structural rules beyond case‑by‑case remedies.
- Parallel findings from the UK CMA and other national authorities; coordinated pressure across jurisdictions increases the chance of meaningful remedies.
- Evidence and testimony on license portability costs, egress fee practices, and contract clauses submitted during the Commission’s information‑gathering phase — these inputs will shape the degree of regulatory intervention.
- Hyperscaler investment trajectories and capacity announcements, particularly around AI hardware; a sustained investment surge could blunt arguments that remedies are needed to reduce barriers to entry.
Final analysis: a pragmatic balance between competition and infrastructure
Google’s decision to withdraw its individual complaint and place its policy case inside the Commission’s broader DMA inquiries is a pragmatic recalibration. It recognizes that cloud competition is not purely a matter of isolated contract terms but a systemic ecosystem problem: infrastructure scale, specialized AI hardware, commercial licensing, and network effects combine to create industry‑wide dynamics that are difficult to fix with one litigant’s complaint.The Commission’s choice to use the DMA framework — while novel for cloud services — is defensible because the DMA is designed to stop entrenched platform behavior before it ossifies. The danger, however, is twofold: (1) that EU rules become over‑prescriptive and raise the cost of capital for infrastructure; and (2) that regulatory actions fail to keep pace with the rapid technical change of AI and cloud engineering, inadvertently locking in today’s market leaders under new compliance burdens.
Practical remedies that would strike a useful balance include narrowly targeted obligations on contractual fairness (greater transparency and portability in license terms), clearer rules on egress and pricing transparency, and time‑limited interoperability measures focused on data portability and principled API escape hatches — all designed to lower switching friction while preserving incentives for massive infrastructure investment.
The next 12 months of the Commission’s investigations will be decisive. Companies, trade associations, and national authorities will supply the evidence; Brussels will weigh systemic risks against the innovation imperative; and users — enterprise IT organizations and developers — will watch to see whether Europe’s regulatory experiment produces more choice and lower lock‑in, or whether it raises the compliance costs of the infrastructures that now power modern businesses.
The outcome will reshape not only commercial cloud contracts but also the regulatory template for dealing with the infrastructural layer beneath AI — making this probe one of the most consequential tech policy developments for Europe’s digital economy in the coming year.
Source: The Hindu Google ditches EU antitrust complaint about Microsoft cloud amid EU probe
