Google Cloud has formally withdrawn the antitrust complaint it lodged with the European Commission in September 2024 over Microsoft’s cloud licensing practices, a tactical retreat that coincides with the Commission’s own decision to open market investigations into cloud computing services — including probes that could bring Microsoft and Amazon Web Services (AWS) under the Digital Markets Act (DMA) umbrella.
Background
For more than a year the cloud licensing fight has been one of the most visible flashpoints in hyperscaler competition. Google Cloud’s original complaint accused Microsoft of using licensing rules to make running Microsoft software — notably Windows Server and SQL Server — on rival clouds prohibitively expensive, effectively steering customers toward Azure and raising the risk of supplier lock‑in. That complaint, filed publicly on 25 September 2024, put commercial and regulatory pressure on Microsoft and drew on research suggesting European organisations pay unusually high extra fees when they run Microsoft software outside Azure. The European Commission’s decision to launch market investigations under the DMA on 18 November 2025 elevated the debate from discrete antitrust complaints to a broader policy question about whether cloud platforms should be treated as “gatekeepers” because of their strategic role in digital markets. The Commission said it will examine whether AWS and Microsoft act as important gateways and whether the DMA’s obligations are fit for the cloud sector. That escalation is the proximate reason Google withdrew its separate complaint on 28 November 2025 — Google said the EC’s new process would cover the same problematic practices.
Why the complaint matters: the mechanics of the dispute
At the heart of Google’s argument is a commercial asymmetry in licensing and product support:
- Microsoft’s marketing and pricing material highlights big cost advantages for customers that run Windows Server and SQL Server on Azure, through programs such as the Azure Hybrid Benefit. Microsoft itself publishes comparisons that say other clouds can be “up to five times more expensive” for those workloads.
- Google and other rivals say Microsoft’s contractual changes since 2019 stripped or limited the right to “bring your own license” (BYOL) in cloud contexts or imposed steep penalties, fees or repurchase requirements for running Microsoft software on non‑Azure clouds. Google framed the gap as a “400% price markup” in its blog and complaint — a figure that maps directly to Microsoft’s claim that non‑Azure deployment can be up to five times costlier.
- Independent analyses commissioned by cloud trade groups (notably CISPE) have attempted to quantify the aggregate cost to European businesses, estimating at least €1 billion a year in additional licensing expense for specific products and extrapolating much larger systemic effects. These numbers have been widely cited by cloud rivals and regulators.
These contractual and price differences translate into practical switching costs for enterprise IT: higher run costs, different patching and extended support regimes, and potential limits on moving virtual machine images or receiving parity-level security updates when using non‑Azure infrastructure.
Timeline — key milestones
- September 25, 2024 — Google Cloud files an antitrust complaint with the European Commission alleging Microsoft’s cloud licensing harms competition and customers. Amit Zavery (then VP/GM, head of platform at Google Cloud) and Tara Brady published the blog post that accompanied the complaint.
- July 2024 — Microsoft reached a settlement with some European cloud providers represented by CISPE, which led to a withdrawal of a separate complaint from that group. Google did not join the settlement, signalling it believed the concessions were insufficient.
- January–July 2025 — The UK Competition and Markets Authority (CMA) published provisional findings and then concluded its cloud market probe, flagging problems including egress fees, interoperability limits, and Microsoft’s licensing practices. The CMA’s work intensified regulatory focus on the sector.
- November 18, 2025 — The European Commission opens three DMA market investigations: two to assess whether AWS and Microsoft should be designated “gatekeepers” for cloud computing services, plus a horizontal probe into DMA fit-for-purpose questions in the cloud market.
- November 28, 2025 — Google Cloud withdraws its EC complaint, citing the Commission’s new DMA‑based market investigations and restating its earlier arguments.
What the EC probe will (and won’t) examine
The Commission’s market investigations are framed in DMA vocabulary but are unusually wide:
- Two investigations will assess whether AWS and Microsoft should be named gatekeepers for cloud computing services, despite cloud platforms often failing standard DMA thresholds based on consumer user counts. The Commission will instead look at market structure, business user dependence, and the extent to which cloud services act as gateways for other digital services.
- A third, horizontal probe will examine whether DMA obligations are adequate for cloud markets, and whether practices such as limited interoperability, conditioned access to business user data, tying and bundling, and contractual terms create systemic barriers.
If Microsoft and Amazon are designated as gatekeepers for cloud services, they would face ex‑ante obligations under the DMA designed to prevent self‑preferencing and other foreclosure mechanisms. Non‑compliance with DMA obligations already carries heavy penalties — up to 10% of worldwide revenue for a first breach and up to 20% for repeat violations — plus other corrective measures and potential structural remedies. These figures are explicit in EU enforcement practice and legislation.
Cross‑checking the big claims
Several load‑bearing assertions have driven headlines and policy debate; each merits checks against multiple sources.
- Claim: Microsoft’s policies impose a “400%” or “5x” premium on customers who move Microsoft workloads to rival clouds. This language originates in Google’s complaint and mirrors Microsoft’s own sales messaging comparing Azure’s pricing and benefits (e.g., Azure Hybrid Benefit). Microsoft’s public pages say other clouds can be “up to five times” more expensive for some Windows and SQL Server scenarios — a statement that Google and others point to when describing the gap. The number is thus traceable both to Google’s complaint and Microsoft’s materials, although how that figure translates to any individual customer depends on licensing terms, Software Assurance status, region, and product mix.
- Claim: Restrictive licensing costs European businesses “at least €1bn a year”. That estimate comes from a CISPE‑commissioned analysis by Professor Frédéric Jenny cited in trade coverage and in Google’s complaint. The figure specifically compared licensing for a small set of products and scenarios and extrapolated a sectoral impact; it is not a comprehensive audit of all enterprise licensing across Europe. Policymakers and journalists have treated the estimate as an indicator rather than a final accounting. Readers should treat the €1bn assertion as a reasoned estimate rather than a definitive ledger entry.
- Claim: Microsoft withholds parity of security patches or limits updates for workloads running off Azure. Google’s complaint raised concerns about support and security parity; some reporting references anecdotal customer complaints. Microsoft disputes the characterization and points to program rules such as Azure Hybrid Benefit and Extended Security Updates on Azure as advantages rather than conditional penalties for other clouds. The existence of isolated support restrictions is plausible and in some cases documented, but the scale and systemic intent behind such practices remain contested and partly factual and partly interpretive. This is one claim to watch closely as regulators gather documentary evidence.
Where claims depend on contractual nuance, supplied documentation, or internal negotiations, the public record is often asymmetric: cloud vendors and trade bodies produce analyses that support their positions, and firm‑level commercial contracts are rarely public. That is precisely why regulators empowered with discovery and formal information‑gathering powers are critical here.
What this means for Microsoft, Google, AWS, and enterprise customers
For Microsoft
- Elevated regulatory risk: DMA‑based market investigations carry the potential for designation as a gatekeeper for cloud computing — an outcome that would impose significant operational constraints and reporting requirements on Azure if confirmed. The possibility of heavy fines and mandatory behavioural remedies is now tangible.
- Reputational pressure: Repeated scrutiny across the EU and UK — and the steady drumbeat of formal complaints — could erode enterprise trust where organisations view vendor neutrality as essential for cloud strategy.
- Business calculus: Microsoft’s pricing and incentives for Azure have undoubtedly helped Azure win share, but the company now faces the tradeoff between protecting channel economics and avoiding regulatory entanglement that could limit commercial flexibility.
For Google Cloud and AWS
- Regulatory leverage without litigation cost: By withdrawing an active EC complaint after the Commission launched its own probe, Google has effectively ceded enforcement primacy to the regulator while preserving its substantive case. That’s a pragmatic, lower‑cost path to the same investigatory outcome. Reuters and other outlets read Google’s withdrawal as a tactical shift into regulatory coordination.
- Competitive positioning: The probes create a window of opportunity for rivals to underscore openness and neutrality in their messaging and to court customers who prioritise multi‑cloud resilience.
For enterprise customers
- Potential win on choice and cost: If the Commission or national regulators find that certain licensing conditions materially foreclose competition, remedies could open up BYOL portability, reduce repurchase penalties, or force parity in extended support — all of which would lower costs and friction for multicloud architectures.
- Short‑term uncertainty: The evidence‑gathering phase can be long and disruptive. Customers negotiating renewals or shaping cloud roadmaps should plan for multiple scenarios — from status quo to legally mandated pricing parity.
- Procurement and compliance challenges: A regulator’s finding could trigger shifts in public procurement policy, contractual language revisions, and a surge in vendor audits as customers test new portability options.
Strengths of Google’s approach — and its limits
- Strengths
- The withdrawal of its formal complaint does not mean retreat on the argument: Google’s blog and public record preserve a clear, documented claim that regulators can investigate. By anchoring its narrative in Microsoft’s own public pages, Google made a traceable, repeatable claim that is difficult for Microsoft to ignore.
- Channeling the matter into a DMA‑led probe leverages a high‑impact regulatory mechanism that can issue systemic remedies, rather than a binary antitrust case that might take years to litigate in court.
- Limits and risks
- Google is a direct competitor to Microsoft in the cloud; its motives will be judged through that lens. Regulators will therefore be careful to separate competitive positioning from consumer harm. The CMA and EC will need documentary proof of anticompetitive intent or effect beyond marketing copy.
- Trade groups and independent researchers use modelling to estimate aggregate harm; those models depend on assumptions about licence mixes, Software Assurance, and workload profiles. Regulators will validate those assumptions against raw contracts and invoices — which means some headline figures may not survive forensic scrutiny.
Regulatory strategy and what to expect next
The Commission’s DMA investigations typically include:
- Formal information requests to cloud providers, ISVs, large customers, and channel partners.
- Confidential document review, including licence terms, internal pricing comparisons, and partner communications.
- Public consultations or targeted hearings with industry stakeholders.
The EC has set variable timelines in similar probes but aims to produce final reports within defined windows; in this case the Commission said a final report across these investigations is expected within 12 to 18 months. If it designates a service as a gatekeeper, there will be subsequent compliance timelines and potential remedies to negotiate. Regulators in the UK and elsewhere are running parallel processes. The UK CMA’s provisional findings and its referral mechanics under the Digital Markets, Competition and Consumers (DMCC) framework mean actions are likely to play out across multiple jurisdictions simultaneously, increasing complexity for the companies involved.
Practical implications for IT leaders and procurement teams
Enterprises should adopt a cautious, evidence‑based posture while regulators adjudicate:
- Document existing entitlements: Catalogue licences, Software Assurance status, support entitlements, and any vendor communications that discuss portability or pricing differences.
- Stress‑test cloud migration plans: Run cost models for staying on current vendors vs. moving to Azure vs. multi‑cloud splits, and explicitly model the “repurchase” or “premium” scenarios that Microsoft and others describe.
- Include regulatory triggers in contracts: For renewals, consider clauses that allow for re‑negotiation or exit rights if regulator findings materially change the commercial landscape.
- Short‑term procurement: Where possible, seek price clarity and time‑limited concessions that reduce switching risk during the regulatory period.
- Advocate and engage: Participate in industry consultations and provide anonymised billing evidence to regulators if comfortable — real‑world invoices and contracts help regulators cut through marketing claims and modelling assumptions.
These steps don’t assume any particular outcome of the investigations; they simply reduce uncertainty and preserve options.
Risks and unintended consequences
- Over‑engineering compliance: If the DMA leads to heavy‑handed remedies, cloud platforms may respond by simplifying offerings or shifting costs in other ways (for example, changes to commercial discounts, reserved‑instance mechanics, or support packaging) that could create new complexity for customers.
- Fragmentation vs resilience: Remedies that simply lower the cost of multicloud could accelerate multi‑vendor deployments (a resilience benefit) but also increase integration and operational tax for customers that must manage more heterogeneous stacks. Enterprises must balance cost, resilience, and complexity.
- Regulatory overreach: There is an explicit tension in the DMA between curbing anticompetitive conduct and preserving incentives for cloud providers to invest in innovation and capacity. Remedies must be carefully tailored; too broad an injunction risks chilling product development or raising costs across the board.
What to watch next — checkpoints and milestones
- Information requests and targeted hearings: Expect regulators to issue formal document demands within the first three months of the investigation announcement. These will reveal much about the evidence base and the Commission’s lines of inquiry.
- CMA and other national regulators’ coordination: Parallel findings in the UK, France, Germany, or other markets could compound pressure and shorten the time to remedies. The CMA’s earlier work already sets a baseline for concerns in the region.
- Designation decision and possible DMA obligations: If the EC determines that AWS or Microsoft (or both) should be designated as gatekeepers for cloud services, expect a defined list of do’s and don’ts, compliance timelines, and a watchdoging mechanism. The consequences could materially reshape commercial negotiations for cloud contracts.
- Litigation and appeals: Any formal DMA designation or antitrust remedies will be litigable. Expect prolonged legal exchanges around the proper scope of DMA authority and the contours of cloud markets.
Conclusion
Google Cloud’s withdrawal of its formal complaint does not end the debate over cloud licensing practices — it reframes it. By stepping back, Google has handed the baton to the European Commission and other regulators, who now have the investigative powers to test claims, force document production, and, if warranted, impose systemic remedies under the Digital Markets Act and related competition law. For enterprises, the immediate implication is simpler to state than the eventual outcome: expect continued regulatory turbulence, maintain meticulous licence and billing records, and design cloud strategies that preserve choice while managing complexity.
Regulators will now have the facts and the forum to settle whether the gap between Microsoft’s commercial messaging and the practice experienced by customers represents lawful product differentiation or structural foreclosure that requires intervention. The answer will shape not only the cost of migration and multicloud operations, but also the legal architecture that governs how hyperscalers compete for the next decade of enterprise computing.
Source: Computer Weekly
Google Cloud withdraws complaint with European Commission over Microsoft’s cloud licensing tactics | Computer Weekly