The EU Just Aimed Its Gatekeeper Rules at AWS and Azure for the First Time, and It Used AI to Do It

The European Union’s most powerful competition instrument, the Digital Markets Act, was written to discipline consumer platforms: app stores, search, social networks, messaging. On June 25 the European Commission pointed it, for the first time, at cloud infrastructure, reaching a preliminary position, in two market investigations it had opened in November 2025, that Amazon Web Services and Microsoft Azure should be designated as gatekeepers. Two things make this more than a routine regulatory escalation. The first is that the Commission did it without either company meeting the DMA’s quantitative size thresholds, the user-count and revenue triggers that have defined every previous designation, relying instead on a qualitative judgment, a first in the law’s history. The second is the reason it gave: artificial intelligence. The Commission’s stated logic is that AI has made cloud lock-in worse, that control over compute and foundation models lets the largest clouds foreclose European AI startups, and that AI capability is now a decisive factor in how cloud is procured. For every European host, reseller, and sovereign-cloud operator that competes against the two dominant hyperscalers, this is the most consequential regulatory development of the year, because the remedies that follow a gatekeeper designation are precisely the ones that would loosen the lock-in they have been losing customers to.

Key facts, EU DMA gatekeeper findings on AWS and Azure (European Commission, June 25, 2026)

• The action: on June 25 the Commission reached a preliminary position, in two market investigations it opened on 18 November 2025, that AWS and Microsoft Azure should be designated DMA gatekeepers, the first time cloud infrastructure has been brought into the regime
• The precedent: the preliminary position rests on a qualitative finding rather than the DMA’s quantitative thresholds, which AWS and Azure do not meet, the first time the Commission has taken this route to a gatekeeper designation
• AI is the stated rationale: the Commission found that AI tools and partnerships have become a decisive factor in cloud procurement and that AWS and Azure retain a large share of the AI-driven demand within their own ecosystems; EVP Henna Virkkunen, responsible for Tech Sovereignty, said “cloud services have become a cornerstone of Europe’s economy – and a prerequisite for AI”
• The market position: the Commission calls AWS and Azure the largest and second-largest cloud services in the EU and notes more than half of EU businesses rely on cloud; its press release gives no percentages, while secondary analyses of its assessment put the two firms’ combined EU share above 70 percent (AWS roughly 35 to 40 percent, Azure 30 to 35 percent)
• The timeline: AWS and Azure have until September 2026 to submit written representations and request a hearing; because a DMA market investigation must conclude within 12 months of opening, the Commission must decide by November 2026 (a final decision is expected around late October), after which a designated gatekeeper gets six months to comply
• It does not stand alone: the move sits alongside the EU Cloud and AI Development Act and the Data Act’s switching and egress provisions, all pointing at the same target: cloud lock-in

Why “Qualitative Grounds” Is the Real Headline

The DMA was built to be mechanical. A company that crosses defined thresholds, a certain market capitalization, a certain number of monthly users in the EU, operating a “core platform service,” is presumed a gatekeeper and designated, which is how Apple, Google, Meta, Amazon’s marketplace, Microsoft, ByteDance, and Booking were brought in. Cloud infrastructure does not fit those triggers cleanly, because the customers are businesses rather than the tens of millions of consumer end-users the thresholds count. Rather than conclude that cloud therefore falls outside the regime, the Commission has done something more aggressive: it has invoked the DMA’s provision for designating a company that has “an entrenched and durable position” on qualitative evidence even without the quantitative triggers, and applied it to cloud for the first time. That is the precedent that matters beyond AWS and Azure. It signals that the Commission will not let the consumer-shaped thresholds shield business-infrastructure dominance, and it opens the door to the same reasoning being applied to other concentrated infrastructure layers. The hosting industry should read it as the EU declaring that cloud lock-in is a competition problem of the same order as app-store lock-in, and that it will find a legal route to treat it as one.

Using AI as the connective tissue is what makes the argument land. The Commission’s case is not simply that AWS and Azure are large; it is that AI has deepened the dependency, because the compute, the managed AI services, and the foundation-model partnerships that European businesses increasingly need are concentrated on the same two platforms, so a company that adopts AI is pulled further into a cloud it already struggles to leave. Virkkunen’s framing, cloud as “a prerequisite for AI,” turns the AI boom from a reason to defer regulation into a reason to accelerate it. For an industry that has spent the year selling agentic infrastructure and AI-ready hosting, the regulatory subtext is sharp: the same AI dependency the market treats as a growth story, the Commission treats as a lock-in mechanism to be remedied.

What Gatekeeper Obligations Would Actually Change

A final designation, which the Commission must make by November 2026 to stay within the twelve-month limit on the investigations it opened in November 2025, triggers a defined set of obligations, and in the cloud context they map almost exactly onto the friction points that keep customers stuck. Gatekeepers must allow business users genuine interoperability and data portability, must not impose unfair conditions that lock customers in, and must not preference their own services in ways that foreclose competitors. Translated to cloud, that points toward the live grievances of the European hosting market: punitive data-egress fees that make leaving expensive, technical and contractual friction that makes migration slow, and the bundling of AI and managed services in ways that deepen dependence. The EU Data Act already began legislating switching and egress relief, and the Cloud and AI Development Act is moving to restrict hyperscaler access to sensitive-sector workloads; a DMA gatekeeper designation would add the regime with the sharpest enforcement teeth, backed by fines of up to 10 percent of global turnover, aimed at the two specific companies that dominate the market. The combination is what makes this more than symbolic. Three separate EU instruments are now converging on cloud lock-in, and the DMA is the one that names defendants and sets deadlines.

The Opening, and the Caution, for European Hosts

For European hosts, resellers, and sovereign-cloud operators, the strategic reading is that the structural advantage they have been unable to win on price or scale may be handed to them on switching cost. The entire competitive difficulty of competing with AWS and Azure is that customers cannot easily leave; remedies that force genuine portability, cap egress fees, and require interoperability attack that difficulty directly, and they attack it only on the two designated incumbents, not on the challengers. A host positioned as the destination for workloads leaving a newly-regulated hyperscaler, with migration tooling ready and a sovereignty story aligned to the CADA direction, is positioned for exactly the market the Commission is trying to create. This publication has documented the narrow window European hosts have to capture the sovereign-cloud mandate; the DMA findings widen it, because they target the lock-in rather than merely subsidizing the alternative.

The caution is in the timeline and the contingency. These are preliminary findings, not a final designation. AWS and Azure have until September to contest them, the Commission must decide by late 2026, and a designated gatekeeper then gets six months to comply, which puts real remedies into 2027 at the earliest, and Amazon has pushed back, warning that the move could deter European investment, the standard and not entirely empty argument that aggressive regulation raises the cost of building in Europe. The honest framing for a hosting boardroom is therefore neither to treat the lock-in as broken nor to dismiss the finding as posturing. It is to recognize that the EU has, for the first time, established that it will regulate cloud infrastructure as a gatekeeper market and has chosen AI dependence as the lever, that three instruments are now converging on the switching costs that protect the incumbents, and that the providers who build the migration path and the sovereignty posture now will be the ones ready when the remedies land. The designation is preliminary. The direction is not.

Methodology and Attribution

The preliminary position, its June 25, 2026 date, the qualitative basis rather than the DMA’s quantitative thresholds, the AI rationale, and the exact Virkkunen quotation and title are drawn from the European Commission’s own published announcement, verified June 26, 2026. The Commission opened the two underlying market investigations on 18 November 2025, and the DMA’s twelve-month limit on such investigations puts the final decision in late 2026, expected around late October rather than in 2027. The Commission’s press release describes AWS and Azure only as the largest and second-largest cloud services in the EU and gives no percentages; the combined-share-above-70-percent and 35-to-40 and 30-to-35 figures are from secondary reporting of its assessment and are attributed as such. Amazon’s warning that the move could deter European investment is from press coverage of its response. The gatekeeper-obligation descriptions are from the DMA’s published provisions; their specific application to cloud is the Commission’s stated direction and this publication’s analysis, not a list of finalized remedies, which would follow a final designation. The connection to the Cloud and AI Development Act and the Data Act draws on this publication’s prior reporting.