EU DMA Probes Cloud Giants as Google Withdraws Microsoft Complaint

Alphabet’s Google has quietly withdrawn its formal complaint against Microsoft over Azure cloud practices in the European Union, a strategic retreat that follows the European Commission’s decision to open a broader market inquiry into cloud computing under the Digital Markets Act (DMA). This move shifts the battleground from a company‑to‑company antitrust complaint to the EU’s institutional arena, where regulators may now consider designating cloud platforms like Microsoft Azure and Amazon Web Services (AWS) as DMA “gatekeepers,” triggering a suite of prescriptive obligations and potentially far‑reaching remedies.

Background​

What Google filed, and when​

Google filed the public complaint with the European Commission in late 2024, formalizing concerns it had aired about licensing and contractual terms that it said made it difficult for customers to switch away from Microsoft Azure. The original Google Cloud blog post that accompanied the complaint laid out specific customer grievances and framed the filing as an effort to ensure choice, interoperability, and openness in European cloud markets.

What changed: EU’s market investigations under the DMA​

On 18 November 2025 the European Commission launched three market investigations under the Digital Markets Act targeting the cloud sector: two focused on whether AWS and Azure should be designated as DMA gatekeepers, and a third aimed at testing whether the DMA’s existing toolkit is effective in addressing cloud‑specific competition issues such as interoperability, conditioned access to data, tying and bundling, and imbalanced contractual terms. The Commission’s market investigations give Brussels the authority to examine structural features of cloud markets and to consider ex ante regulatory remedies if gatekeeper status is found to be warranted.

Google’s withdrawal and public explanation​

Google’s head of government affairs and public policy for Google Cloud Europe, Giorgia Abeltino, appended an editorial note to Google’s original blog post announcing the withdrawal, saying the company was withdrawing its complaint “in light of the recent announcement that the EC will assess problematic practices affecting the cloud sector under a separate process.” Abeltino reaffirmed Google’s intention to continue working with policymakers and regulators to advocate for choice and openness.

---

How we got here: timeline and key facts​

• September 25, 2024 — Google published the blog post that constituted its formal complaint about Microsoft licensing and cloud practices.
• November 18, 2025 — European Commission announced market investigations under the DMA into cloud computing services, explicitly flagging AWS and Azure for potential gatekeeper designation and opening a sector‑wide review.
• November 28, 2025 — Media outlets reported that Google withdrew its original complaint following the Commission’s announcement; Google confirmed the withdrawal with an editorial note on the original blog post.

These are the publicly confirmed milestones; as with many regulatory matters, there will be parallel informal engagement between stakeholders and the Commission that may not be in the public record.

---

Market context: who controls the cloud and why it matters​

Understanding the commercial stakes is essential: the cloud market is dominated by a small number of hyperscalers whose platform choices, contract terms, and integrations shape enterprise architecture and vendor lock‑in dynamics.

• Market share snapshots vary by methodology. Canalys and several industry trackers place AWS as the leader with roughly 30% market share, Microsoft Azure as a strong number two around 20%, and Google Cloud smaller but growing in the low‑teens (roughly 11–13%). Those figures are widely used by regulators and journalists to describe the market.
• Other research firms measure IaaS and public cloud differently. For example, Gartner’s 2024 IaaS market share table reports higher concentration for AWS (nearly 38% in some datasets) and a somewhat different percentage for Google—reflecting different baskets of services, geographic weighting, and revenue definitions. This methodological variation is important when regulators or litigants rely on market‑share thresholds or competitive benchmarks.

Why it matters for end users: these platforms do more than rent compute. They bundle management tooling, developer ecosystems, AI services, identity and security primitives, and enterprise licensing schemes. When a provider controls multiple layers of this stack, switching costs can rise sharply. That is the precise competitive problem officials aim to diagnose and, if necessary, regulate.

---

Legal and regulatory mechanics: the DMA and market investigations​

What the DMA does and why the Commission used it here​

The Digital Markets Act is a proactive regulatory instrument that identifies “core platform services” and designates certain providers as gatekeepers when they meet size and market‑control thresholds. Gatekeeper designation brings a prescriptive list of “dos and don’ts” covering areas such as self‑preferencing, interoperability obligations, data combination bans, and restrictions on using business customer data to compete with those customers. While the DMA’s thresholds are quantitative, the Commission also has the flexibility to perform market investigations and designate a service on an individualized basis if the evidence shows it functions as an important gateway for business users. That is the route the Commission has chosen for the cloud sector.

What market investigations can do​

Market investigations are fact‑gathering procedures that allow the Commission to:

• Collect contractual and commercial evidence from market participants.
• Test whether structural features (e.g., network effects, interoperability barriers, bundling) reinforce incumbents’ positions.
• Consider whether the DMA’s existing obligations are sufficient or need specification for cloud scenarios.
• Conclude whether to designate specific cloud services as gatekeepers even if those services do not meet the DMA’s standard quantitative thresholds.

If a gatekeeper designation follows, the Commission can require behavioral remedies and demand compliance with DMA obligations. Non‑compliance can lead to substantial fines (up to double‑digit percentages of global turnover) and, in extreme cases, structural remedies. The investigations are expected to take about a year, though exact timing will depend on the complexity of the evidence and stakeholder cooperation.

---

Strategic reading: why Google withdrew its complaint​

Google’s decision to withdraw its complaint is a tactical recalibration with multiple plausible motives.

• Regulatory leverage: A Commission‑led market investigation has broader institutional scope and the potential to produce ex‑ante rules that apply to all market players, rather than a bilateral enforcement action tied to a single company. In that light, channeling concerns into the EC’s DMA process could secure a more systemic and durable remedy for the cloud industry. Google’s public statement frames the withdrawal as an endorsement of the Commission’s new inquiry.
• Resource allocation and optics: Pursuing a formal antitrust case can be resource‑intensive and adversarial, with uncertain timelines and remedies. Converting the dispute into regulatory input to a Commission investigation may be a more effective use of corporate advocacy resources and avoid a protracted legal showdown that could burn political capital.
• Coalition building: By withdrawing a head‑to‑head complaint, Google may be signaling willingness to work within a multilateral regulatory process that includes smaller cloud providers, customers, and policymakers. That can allow Google to shape the investigation’s terms and evidence collection while avoiding the perception of pursuing narrow commercial advantage through litigation.

These are plausible strategic motivations grounded in how enforcement and policymaking typically unfold; however, internal corporate motives are not fully public and cannot be verified beyond Google’s public statements. That uncertainty should be treated with caution. Any interpretation of motive remains an inference unless confirmed by Google’s internal communications or direct statements from senior executives.

---

What could the Commission do — and what would it mean for Azure and AWS​

If the Commission concludes that AWS or Azure (or both) qualify as gatekeepers for cloud computing services, the immediate implications could include:

• Mandatory interoperability requirements: Gatekeepers may be required to enable standardized APIs, interfaces, or data portability mechanisms that make it easier for customers to multi‑home or migrate workloads. This could reduce technical switching costs and force more open integration of management and identity services.
• Bans on self‑preferencing and bundling: Cloud providers could face obligations not to bundle proprietary services in ways that unfairly advantage their own offerings over third‑party equivalents (e.g., tying a specific cloud identity service or database to platform hosting in an exclusionary way).
• Limits on data use: Rules could bar combining personal or business data from different core services to train models or offer competing services, or at least require explicit business customer consent or transparent, fair terms.
• Contractual fairness: The Commission could scrutinize and require the reworking of common contractual terms seen as imbalanced, such as clauses that restrict portability, impose most‑favoured‑nation terms, or create economic penalties for switching.

These are high‑level possibilities; exact remedies would depend on the investigation’s findings. Remedies could be behavioral (changes to conduct and contracts) or, in extreme scenarios, structural (divestitures), although the latter is less common and usually reserved for the most entrenched abuses.

---

Practical consequences for enterprises, developers, and partners​

Enterprises and developers should watch this process for concrete outcomes that will affect procurement, architecture, and vendor strategy.

• For procurement teams, formal DMA obligations could translate into clearer interoperability guarantees and more standardized outbound data and workload portability, making multi‑cloud strategies easier to execute.
• For developers, access to standardized APIs and less restrictive platform integrations could reduce vendor lock‑in and simplify toolchain portability.
• For ISVs and managed service providers, new rules may open opportunities to offer cross‑platform services without being disadvantaged by gatekeeper‑owned marketplaces or bundled tooling.
• For Microsoft and AWS, compliance costs could rise, both in engineering and legal teams, as platform interfaces are opened and contractual terms adjusted.

However, the timeline for these changes is measured in quarters to years. Even if DMA obligations were imposed, implementation and compliance verification require time and technical standard‑setting, which may yield incremental rather than immediate change.

---

Risks and unintended consequences​

The Commission’s intervention and Google’s withdrawal do not come without risks and complexities.

• Regulatory overreach vs. underreach: The DMA is a blunt instrument in some respects—its “dos and don’ts” are broad. Imposing rules designed for social networks or search engines onto complex cloud stacks could produce mismatched obligations that disrupt innovation or raise compliance overheads without materially improving competition. At the same time, insufficient remedies could leave the fundamental switching costs in place. The Commission’s success will hinge on technical nuance and sector knowledge.
• Perverse incentives: Ex ante obligations risk freezing certain engineering practices or creating perverse incentives to route around compliance in ways that harm security or performance (for example, if “openness” requirements encourage fragile interoperability layers). Policymakers will need to balance competition goals with operational realities such as latency, regional control, and security architectures.
• Fragmentation: Overly prescriptive remedies could lead to fragmentation of cloud standards across jurisdictions as other regulators adopt divergent approaches, increasing complexity for global customers and cloud vendors.
• Political dynamics: Cloud regulation is geopolitical as well as economic. European efforts to regulate hyperscalers interact with US trade policy, national cloud strategies, and security considerations (data residency, sovereign clouds). That complexity makes predictable outcomes more difficult to forecast.

These risks argue for careful, technical engagement from industry players and civil society, as well as for the Commission to rely on robust empirical evidence rather than analogies to other digital markets.

---

What this means for Microsoft and the Azure ecosystem​

Microsoft now faces a regulatory moment that touches on core business models for Azure and its integration with Windows Server, SQL Server, enterprise licensing, and developer tooling.

• For enterprises that rely on deep Microsoft integrations (Windows Server, Active Directory, SQL Server, .NET ecosystems), the central question is whether the Commission will require loosening of ties between these platform assets and Azure that materially affect value‑added services. Any remedy must weigh migration costs and security considerations.
• For Microsoft’s commercial strategy, a DMA designation could require product changes and contractual amendments. These would impose near‑term compliance costs but could also open Microsoft to new market opportunities if its cloud services become easier to interoperate with third‑party offerings.
• For channel partners and ISVs that build on Microsoft ecosystems, clearer interoperability rules could remove some friction when building cross‑cloud solutions—potentially expanding addressable markets while increasing competition.

Microsoft will likely engage robustly with the Commission to shape the technical contours of any remedies, arguing for practical, security‑sensitive implementation paths.

---

Evaluation: strengths of the Commission’s approach and remaining questions​

Strengths:

• The Commission’s sector‑wide approach acknowledges that cloud competition issues are systemic rather than strictly bilateral, and it leverages the DMA’s ex ante toolkit to address structural incentives. A market investigation can examine technical architectures, contractual ecosystems, and industry practices in aggregate.
• By moving to a Commission‑led study, evidence gathering will be broader and more inclusive of customers, competitors, and intermediaries, increasing the chance of calibrated, durable remedies.

Open questions and caveats:

• Technical nuance: Can the Commission translate cloud architectural realities into actionable DMA obligations without harming engineering flexibility and security? The answer is not yet evident and will depend on the quality of expert input and technical analysis during the investigations.
• Metrics and market definition: Different market trackers yield different market‑share snapshots. Regulators must be explicit about the product market definitions they use— IaaS vs. PaaS, global vs. EU regional footprints, and revenue vs. installed base—because these choices materially affect whether a provider is deemed to hold a gatekeeper role.
• Timeline and enforcement: Investigations projected to take about a year will produce findings, but many remedies, guidance, and standards will take longer to operationalize. The interim period will be critical for contractual practices and commercial deals that are already in motion.

These observations underline that while the Commission’s move is consequential, the precise legal and technical outcomes are uncertain and will require iterative policymaking and engagement.

---

What to watch next (practical checklist)​

• Commission notices and questionnaires: Watch for formal market investigation notices and stakeholder questionnaires that identify which contractual clauses and technical interfaces the Commission wants to examine. Responding to these will be how industry shapes the factual record.
• Industry coalition responses: Expect letters and joint submissions from cloud providers, enterprise customers, trade associations, and smaller cloud players; these will reveal core industry priorities and points of contention.
• Technical workshops and standards: Look for Commission‑led workshops or requests to technical standards organizations to define interoperable interfaces or portability formats; standards work will be critical to any practical remedy.
• Interim guidance from the Commission: The Commission may issue interpretive guidance on how DMA provisions apply to cloud services; such guidance can materially affect compliance strategies.

---

Bottom line​

Google’s withdrawal of its complaint against Microsoft is less a retreat than a strategic repositioning: by stepping out of a bilateral complaint and into a Commission‑led, sector‑wide process, Google is betting on systemic remedies under the Digital Markets Act to address the core business practices it flagged. The European Commission’s market investigations create a new legal and policy framework that could reshape how cloud platforms interoperate, how customers switch, and how hyperscalers leverage their ecosystems. Yet the path from investigation to effective, technically sound remedies is long and uncertain, and outcomes will hinge on careful definitions, rigorous technical evidence, and finely tuned regulatory design.
Enterprises, partners, and developers should track the Commission’s evidence requests and technical discussions closely: the decisions made during the next year will determine whether cloud competition becomes more open and interoperable—or whether regulatory complexity introduces new frictions that slow innovation.

---

Conclusion
The dispute has moved from a company‑filed complaint to a public policy process with broader ambitions. That shift raises the stakes for every player in the cloud ecosystem: hyperscalers will face deeper institutional scrutiny; enterprise buyers may eventually gain stronger portability and contract protections; and regulators will be tested on their ability to convert high‑level competition objectives into technically feasible, proportionate rules. The coming year of market investigations will be decisive for Europe’s cloud landscape and will likely set precedents that ripple through cloud governance and platform regulation worldwide.

---

Source: PYMNTS.com Google Withdraws EU Antitrust Complaint Against Microsoft | PYMNTS.com