EU DMA Cloud Probe: AWS and Azure Gatekeeper Rules Beyond Thresholds

On November 18, 2025, the European Commission opened three Digital Markets Act market investigations into cloud computing, including probes into whether Amazon Web Services and Microsoft Azure should be treated as gatekeepers despite missing the DMA’s automatic thresholds. That is the dry regulatory version. The real story is sharper: Brussels is testing whether cloud infrastructure has become too important to be governed only by market-share arithmetic. For Windows administrators, enterprise architects, and anyone paying a hyperscaler invoice, this is not an abstract European competition fight; it is a direct challenge to the economics of lock-in.

Brussels Decides the Cloud Is Infrastructure, Not Just Another Platform​

The Digital Markets Act was built around a familiar picture of platform power: app stores, search engines, social networks, messaging systems, marketplaces, browsers, and operating systems. These are places where users gather, businesses are forced to appear, and the platform owner can quietly change the rules. Cloud computing never fit that picture perfectly, because most users do not “visit” AWS or Azure in the same way they visit an app store.
But enterprises do live inside cloud platforms. Their databases, identity systems, storage buckets, Kubernetes clusters, AI pipelines, backup policies, disaster recovery plans, billing models, and compliance controls become bound to a provider’s technical and commercial vocabulary. Once that happens, cloud is no longer merely rented compute. It becomes the operating terrain on which a company’s own software business runs.
That is why the Commission’s decision to investigate AWS and Azure despite their not meeting the DMA’s quantitative gatekeeper thresholds matters. The regulator is effectively saying that the cloud market may create dependency in ways the original threshold tests do not fully capture. In plain English: if the numbers do not describe the bottleneck, Brussels may still go looking for the bottleneck.
The move also widens the DMA’s political ambition. Until now, the law’s most visible battles have been with consumer-facing empires: Apple over iOS, Google over search and Android, Meta over data use, Amazon over marketplace conduct, Microsoft over Windows-linked services. Cloud pushes the law into the back office, where competition problems are less visible to consumers but arguably more consequential for the digital economy.

---

AWS and Azure Do Not Need to Own Everything to Shape Everything​

The cloud market is often described as competitive because there are alternatives. Google Cloud exists. Oracle Cloud exists. IBM, Alibaba, OVHcloud, Scaleway, Hetzner, and many regional providers exist. Enterprises can also run workloads on-premises, in colocation facilities, or across hybrid architectures.
That description is true and incomplete. Competition in cloud is not only about whether alternatives exist; it is about whether customers can realistically use those alternatives without paying a technical, financial, and organizational penalty so large that “choice” becomes theoretical. The Commission’s probe appears aimed at that gap between available options and practical mobility.
AWS and Azure dominate different parts of the enterprise imagination. AWS remains the archetypal hyperscaler, the platform that turned elastic infrastructure into a default assumption for developers and startups. Azure, meanwhile, sits in a Microsoft ecosystem that already includes Windows Server, Active Directory, Entra ID, Microsoft 365, SQL Server, Visual Studio, GitHub, Dynamics, Defender, and a growing portfolio of AI and developer tooling.
For Windows-heavy organizations, Azure is not just another cloud provider in a comparison table. It is often the path of least resistance for identity integration, licensing, management tooling, security posture, and procurement. That can be perfectly legitimate product integration, but it can also become the kind of gravitational force regulators scrutinize when customers find it hard to leave or rivals find it hard to compete.
AWS has a different kind of gravity. Its service catalog, developer mindshare, partner ecosystem, certification economy, and maturity in infrastructure primitives give it enormous staying power. Even where AWS does not “lock in” a customer by contract, it may lock them in through architecture, skills, managed services, automation scripts, observability stacks, and years of operational habit.

The Thresholds Were Never the Whole Law​

The DMA’s quantitative thresholds are meant to identify obvious gatekeepers quickly. They look at size, reach, and market position, allowing the Commission to designate companies when the evidence is already overwhelming. But the law also gives Brussels room to conduct market investigations when a service may function as a gatekeeper even if it does not trip the automatic tests.
That flexibility is now the center of the cloud fight. AWS and Azure not meeting the automatic thresholds does not end the inquiry; it starts a more interesting one. The Commission is asking whether the formal measures of gatekeeper status understate how cloud power works.
This is a crucial distinction. Consumer platforms often demonstrate power through user numbers. Cloud platforms demonstrate power through dependency depth. A single enterprise tenant may represent thousands of employees, millions of customers, regulated data flows, production systems, software supply chains, and years of accumulated technical decisions.
That makes cloud a poor fit for blunt user-count logic. A consumer messaging app can be measured by how many people open it. A cloud platform may need to be measured by how hard it is for businesses to move away from it, how much value accumulates inside its proprietary services, and how strongly its pricing and licensing rules shape the competitive field.
The Commission’s third investigation, into whether the DMA’s existing cloud framework is adequate, is therefore not a footnote. It is an admission that the law may need interpretive adaptation for infrastructure markets. The EU is not merely asking whether AWS and Azure fit the DMA; it is asking whether the DMA’s current categories fit cloud computing.

---

Lock-In Has Become the Cloud’s Most Expensive Feature​

Cloud lock-in is sometimes discussed as if it were a moral failing by lazy architects. That is unfair. Organizations choose managed databases, serverless platforms, proprietary monitoring tools, queueing systems, data warehouses, and identity integrations because those services save time and reduce operational burden. The entire promise of cloud is that customers should not have to rebuild everything themselves.
The trouble begins when convenience compounds into captivity. A workload that starts on commodity virtual machines can be moved with effort. A workload built around a provider’s managed database semantics, storage APIs, IAM model, event bus, observability stack, AI service, and deployment pipeline is far more entangled. The customer has not merely rented infrastructure; it has written its business logic into the provider’s worldview.
Egress fees have long been the most visible symbol of this problem. Charging customers to move data out of a platform can make switching or multi-cloud architectures more expensive, especially for data-heavy workloads. Several providers have softened or changed data-transfer policies under competitive and regulatory pressure, but the broader issue is not limited to a single line item on a bill.
The deeper lock-in is operational. Teams train on one provider. Security policies are written around one provider’s controls. Procurement commits to one provider’s discount structures. Compliance evidence is generated from one provider’s dashboards. Disaster recovery plans assume one provider’s regions and services. Over time, the cost of leaving becomes not only financial but institutional.
That is why cloud competition cannot be judged solely by whether a customer could, in theory, redeploy elsewhere. The real test is whether switching is commercially and technically plausible before the incumbent’s advantages become self-reinforcing. Regulators are increasingly skeptical of markets where the answer is “yes, but only after an expensive multi-year migration that nobody has budgeted for.”

Microsoft’s Cloud Problem Is Also a Windows Problem​

For WindowsForum readers, Microsoft’s place in this probe deserves special attention. Azure is not just Microsoft’s cloud business. It is the destination toward which much of the Microsoft enterprise stack has been gradually bent.
Windows Server, SQL Server, Active Directory, Microsoft 365, Defender, Intune, Entra ID, Power Platform, Teams, and GitHub all feed into Azure’s strategic position. Microsoft can argue, with reason, that customers benefit when these products work better together. The integration story is one of Microsoft’s strongest advantages, especially for organizations that do not want to stitch together identity, endpoint management, productivity, analytics, and security from separate vendors.
But integration becomes controversial when it affects the price or feasibility of using competing clouds. The UK Competition and Markets Authority has already put particular scrutiny on Microsoft’s software licensing practices in cloud markets, including concerns that running Microsoft software on rival clouds can be less attractive than running it on Azure. That issue matters because Windows Server and SQL Server are not niche products; they are part of the enterprise substrate.
If regulators conclude that Microsoft’s software estate helps Azure compete unfairly, the remedies could reach beyond Azure’s dashboard. They could affect licensing terms, portability commitments, interoperability requirements, and how Microsoft bundles cloud credits or technical advantages with broader enterprise agreements. For IT departments, that would be a far more practical outcome than a symbolic slap on the wrist.
Microsoft’s challenge is that the company has spent years presenting Azure as the natural home for the Microsoft customer. That strategy has worked. It has also made Azure harder to separate from the rest of Microsoft’s enterprise machine when regulators ask whether customers are being steered, nudged, or economically pressured into one cloud.

---

AWS Faces a Cleaner but No Less Serious Accusation​

Amazon’s cloud power is less entangled with desktop operating systems and productivity suites. That gives AWS a cleaner defense in some respects. It can say its position was earned through early execution, broad service availability, engineering maturity, and relentless infrastructure investment.
That defense will resonate with many technologists. AWS did not become central to cloud computing by accident. It gave developers tools that were faster, more programmable, and more scalable than traditional enterprise IT procurement. It built a platform that rewarded experimentation and then converted that experimentation into production dependency.
But being first and being good do not immunize a company from gatekeeper scrutiny. If AWS has become an unavoidable route to market for certain classes of software companies, or if its technical and pricing structures make competitive alternatives less viable, regulators can still ask whether intervention is justified. Dominance earned through innovation can still become dominance protected by switching costs.
AWS also benefits from ecosystem lock-in that does not require a Microsoft-style software estate. Certifications, partner practices, reference architectures, marketplace offerings, startup credits, managed services, procurement channels, and accumulated operational familiarity all make AWS sticky. The question for Brussels is whether that stickiness reflects healthy customer satisfaction or market power that forecloses rivals.
Amazon will likely argue that cloud remains intensely competitive, with price cuts, rapid innovation, and major rivals investing aggressively. That argument is not frivolous. The cloud market is not a static monopoly. But regulators are increasingly focused on whether competition happens mostly at the moment a customer chooses a provider, while fading once the workload is deeply embedded.

The UK Already Drew the Map Brussels Is Now Walking​

The EU investigation follows a British regulatory path that has already identified cloud as a competition problem. The UK’s Competition and Markets Authority spent nearly two years examining the cloud infrastructure services market and concluded that competition was not working as well as it should. Its concerns included market concentration, data-transfer charges, technical barriers to switching and multi-cloud, and Microsoft’s software licensing practices.
The UK framework is not identical to the EU’s DMA. Britain’s “strategic market status” regime is its own post-Brexit digital competition tool. But the similarities are obvious enough that AWS and Microsoft now face a pincer movement: one inquiry from Brussels under the DMA, and another competition policy current from London under the UK’s digital markets regime.
This matters because large technology companies can often absorb one jurisdiction’s rules as a local compliance exercise. Two major European regulators circling the same cloud practices make that harder. If the UK and EU converge on similar concerns, the companies may find themselves adjusting global commercial practices rather than maintaining bespoke European exceptions.
It also gives smaller cloud providers a stronger political narrative. European cloud firms have long argued that hyperscaler dominance is not merely the result of better products, but also the result of structural barriers that prevent customers from moving workloads or comparing prices cleanly. The UK findings gave that argument institutional weight. The EU probe gives it continental scale.
Still, regulators will need to avoid confusing frustration with proof. Cloud buyers complain about bills, complexity, licensing, egress, and support across nearly every provider. The task is to distinguish normal enterprise dissatisfaction from conduct that unlawfully entrenches dominant platforms. That is harder than it sounds, and the remedies could be messy.

---

Gatekeeper Status Would Turn Architecture Into Compliance​

If AWS and Azure are designated as DMA gatekeepers for cloud services, the consequences would not stop at legal departments. The DMA can impose obligations around fair access, interoperability, data portability, self-preferencing, and restrictions on using business-user data in ways that disadvantage competitors. Translated into cloud terms, those concepts could affect how customers move workloads, how rival services interoperate, and how platform owners privilege their own services.
The most obvious target is portability. Regulators may want customers to move data and workloads more easily, with fewer contractual or technical penalties. That could mean pressure on data egress practices, migration tooling, interface documentation, and barriers that make multi-cloud designs impractical.
Interoperability is more complicated. Cloud providers do not merely host standardized compute and storage anymore. They offer managed databases, proprietary serverless runtimes, AI APIs, analytics platforms, security tools, and identity services. Forcing interoperability across such services is not like requiring a messaging app to talk to another messaging app. It risks running into genuine engineering differences, security boundaries, and product-design tradeoffs.
Fair access could also become a battlefield. If a hyperscaler runs a marketplace, offers first-party services, controls procurement incentives, and observes customer usage patterns, rivals will want assurances that the platform is not tilting the field toward its own products. That concern has parallels with app stores and online marketplaces, but cloud adds the extra complexity of infrastructure security and enterprise contracting.
The biggest unknown is how prescriptive Brussels will be. A light-touch designation might push providers toward clearer portability commitments and less punitive switching costs. A more aggressive regime could force changes to licensing, bundling, APIs, marketplace ranking, or technical documentation. The investigation’s twelve-month timeline means cloud buyers may spend much of 2026 planning around uncertainty.

The Investor Story Is About Margins, Not Headlines​

For investors, the immediate temptation is to treat this as another Big Tech regulatory headline. That understates what is at stake. AWS and Azure are not side businesses. They are central profit engines and strategic anchors for Amazon and Microsoft.
AWS has long been one of Amazon’s most important sources of operating income, giving the company financial flexibility beyond retail. Azure, while reported inside Microsoft’s broader cloud and server categories rather than always as a clean standalone number, is central to Microsoft’s growth story, AI ambitions, and enterprise valuation. Any regulatory regime that affects cloud pricing, bundling, interoperability, or portability could touch high-margin revenue streams.
That does not mean the EU probe will blow a hole in either company’s financial model. Antitrust and digital regulation often move slowly, and remedies can be narrower than critics hope. The companies also have the resources to comply, litigate, adapt contracts, and turn regulatory obligations into standardized enterprise features.
But the direction of travel matters. If regulators make it easier for customers to move workloads, negotiate licenses, avoid punitive data-transfer costs, or mix cloud providers, then hyperscalers may have to compete harder after the initial sale. That could pressure margins over time, especially for services whose profitability depends on customer inertia.
Investors should therefore watch not only the final designation decision, but also the remedy language. A gatekeeper label is important. The obligations attached to it are where the economics live.

---

Europe Is Trying to Regulate the Control Plane​

The most interesting part of the EU’s move is conceptual. Brussels is not just policing cloud market share. It is beginning to regulate the control plane of modern business technology.
In cloud computing, the control plane is where decisions are made: identity, permissions, deployment, billing, monitoring, policy, automation, and orchestration. Whoever owns that layer has influence far beyond raw compute. They shape how developers build, how administrators secure, how finance teams budget, and how executives understand risk.
That is why cloud dominance feels different from the old monopoly fights over browsers or media players. A browser monopoly shaped access to the web. A cloud control-plane monopoly can shape how companies build the web, run AI systems, store regulated data, defend against attackers, and recover from outages. It is less visible and more embedded.
The Commission’s probe implicitly recognizes that the next generation of platform power may sit below the user interface. Users may never see Azure Resource Manager, AWS IAM, S3 policies, VPC architectures, Entra integrations, or reserved-instance commitments. But those mechanisms can still determine whether a competitor gets a fair shot.
This is also where the AI boom sharpens the stakes. Cloud providers are now the landlords for much of the AI economy, selling GPUs, model-hosting platforms, vector databases, data pipelines, and integrated developer services. If cloud markets are already sticky, AI workloads may make them stickier. The provider that hosts the data, identity, models, and deployment environment may gain an even stronger grip.

Smaller Clouds Need More Than Regulatory Sympathy​

European cloud providers and other challengers will welcome the Commission’s intervention, but regulation alone will not create a competitive cloud market. Customers do not choose hyperscalers only because they are trapped. They choose them because they are global, mature, feature-rich, well-documented, heavily staffed, and deeply integrated into enterprise procurement.
If Brussels wants a more contestable cloud market, it must be careful not to mistake portability mandates for a full industrial strategy. Making it easier to leave AWS or Azure helps only if credible destinations exist at the necessary scale, compliance level, and service breadth. Otherwise, portability becomes a right that customers admire and rarely use.
Smaller providers also face a brutal capital problem. Cloud infrastructure is expensive. Regions, data centers, fiber, chips, energy contracts, security operations, compliance certifications, and support organizations require enormous investment. Even if regulators reduce switching barriers, challengers still need to convince customers that they can run mission-critical workloads reliably for years.
That said, competition does not require every provider to match AWS and Azure service-for-service. A healthier market could include specialized clouds for sovereignty, regulated industries, high-performance computing, privacy-sensitive workloads, edge deployments, or open-source-oriented platforms. The goal should not be to clone the hyperscalers. It should be to prevent the hyperscalers from becoming the only realistic answer to every infrastructure question.
For administrators and architects, that means the practical response is not to wait for Brussels. It is to design with exit costs in mind. The companies that benefit most from any future portability rules will be the ones that have already documented dependencies, separated data layers where possible, avoided unnecessary proprietary coupling, and understood the true cost of migration before regulators force the issue.

---

The Fine Print Now Belongs in Every Cloud Architecture Meeting​

The EU probe turns cloud governance into a boardroom and architecture concern at the same time. It does not require immediate panic, and it does not mean AWS or Azure customers should rush for the exits. It does mean the assumptions behind long-term cloud commitments deserve fresh scrutiny.
Procurement teams should pay close attention to renewal timing. A twelve-month investigation window means many enterprise agreements signed in 2026 could run across a period of regulatory uncertainty. Customers negotiating with AWS or Microsoft may find it useful to ask more directly about portability assistance, licensing flexibility, egress exposure, data-export tooling, and the treatment of workloads that might move to rival clouds.
Technical teams should revisit the difference between deliberate lock-in and accidental lock-in. Choosing a proprietary managed service can be rational if the productivity gain is real and the exit cost is understood. The danger is not using first-party cloud services; the danger is using them casually, then discovering later that the bill for leaving was never estimated.
Security teams should also be part of this conversation. Multi-cloud and portability are often sold as resilience strategies, but badly implemented multi-cloud can expand attack surfaces, fragment identity, complicate logging, and create inconsistent policy enforcement. Regulatory enthusiasm for switching should not blind organizations to the operational risk of spreading workloads across providers without mature governance.
For Windows-centric shops, the licensing angle deserves particular care. If a workload depends on Windows Server, SQL Server, Remote Desktop Services, Microsoft identity, or hybrid management tooling, the cost comparison between Azure and other clouds may be shaped by more than instance pricing. Administrators should model licensing, support, compliance, migration, and staff expertise as a single package rather than treating compute rates as the headline number.

The Cloud Bill Is Becoming a Competition Document​

The most concrete lesson from the EU’s investigation is that cloud invoices are no longer just finance artifacts. They are evidence of how market power is exercised. Egress charges, committed-spend discounts, bundled credits, software license mobility, support tiers, marketplace fees, and managed-service dependencies all tell a story about whether customers can act freely after they choose a provider.
This is where the Commission’s case may become uncomfortable for the hyperscalers. AWS and Microsoft can point to innovation, falling unit costs in some services, customer choice, and fierce competition for new workloads. Regulators will ask what happens after the customer is inside the estate.
Those are different stories. The sales story is about choice. The operations story is about dependency. The legal story will turn on whether dependency has crossed from ordinary product stickiness into gatekeeper power.
Customers should not expect Brussels to abolish complexity. Cloud computing is complex because modern infrastructure is complex. But regulators can still reduce artificial friction: unclear licensing, punitive exit economics, discriminatory terms, self-preferencing, or technical barriers that exist more to defend incumbency than to improve service quality.
The larger cultural change may be that cloud buyers begin asking harder questions before signing. For years, cloud adoption was framed as escape from the constraints of traditional enterprise IT. The irony is that many organizations now need a cloud exit strategy with the same seriousness they once applied to data-center migration plans.

---

The Brussels Probe Gives Cloud Buyers a New Checklist​

The investigation will take time, and the final outcome is uncertain. But the direction is already useful: regulators are validating concerns that many architects, CIOs, and administrators have raised for years about portability, licensing, and the real cost of switching. The near-term response should be disciplined preparation, not regulatory theater.

• Organizations should inventory which workloads depend on provider-specific services that would be difficult to replace quickly.
• Procurement teams should ask AWS and Microsoft for explicit terms on data export, migration support, license mobility, and post-contract access.
• Windows-heavy enterprises should model the full cost of running Microsoft workloads on Azure versus rival clouds, including licensing and support assumptions.
• Security teams should treat multi-cloud plans as governance projects, not just resilience slogans.
• Developers should document cloud-specific APIs, identity dependencies, deployment scripts, and managed-service assumptions before they become institutional memory.
• Executives should view cloud portability as a negotiating asset even if they have no immediate plan to switch providers.

The Commission’s probe may end with formal gatekeeper designations, narrower remedies, or a finding that the current DMA framework needs adjustment before cloud can be regulated cleanly. Whatever the outcome, Brussels has put AWS and Azure on notice that infrastructure power is now platform power, and the next phase of cloud competition will be fought not only over who has the best services, but over whether customers can afford to leave them.

---

References​

1. Primary source: Crypto Briefing
   Published: 2026-06-18T14:30:08.744209
   
   

   Microsoft, Amazon Web Services face EU probe over cloud dominance

   European Commission opens DMA investigations into AWS and Microsoft Azure cloud services, examining potential gatekeeper designations despite not meeting

   cryptobriefing.com
2. Related coverage: digital-strategy.ec.europa.eu
   
   

   Commission launches market investigations on cloud computing services under the Digital Markets Act

   The European Commission opened three market investigations on cloud computing services under the Digital Markets Act (DMA).

   digital-strategy.ec.europa.eu
3. Related coverage: gov.uk
   
   

   CMA announces package of actions on business software and cloud services - GOV.UK

   CMA aims to create greater choice for UK businesses and public sector at pivotal time of advances in AI.

   www.gov.uk
4. Related coverage: agenceurope.eu
   
   

   Cloud sector could soon be subject to strictest DMA obligations | AGENCE EUROPE

   The European Commission investigates Amazon and Microsoft's cloud services.

   agenceurope.eu
5. Related coverage: investing.com
   
   

   EU probes Amazon, Microsoft’s cloud services for potential curbs By Reuters

   EU probes Amazon, Microsoft’s cloud services for potential curbs

   www.investing.com
6. Related coverage: aa.com.tr
   
   

   EU launches market investigations into cloud services under bloc's digital rules

   Probes to review Amazon, Microsoft as 'gateways,' between businesses, consumers | Anadolu

   www.aa.com.tr

Spoiler: Additional references (8)

1. Related coverage: datacenterdynamics.com
   
   

   "Competition is not working well," says UK CMA concluding cloud market investigation - DCD

   AWS and Microsoft to undergo further "strategic market status" investigations

   www.datacenterdynamics.com
2. Related coverage: ppc.land
   
   

   EU opens cloud gatekeeper probes for Amazon and Microsoft

   European Commission launches three market investigations examining whether Amazon Web Services and Microsoft Azure should face Digital Markets Act regulation.

   ppc.land
3. Related coverage: grcreport.com
   
   

   EU Opens New Cloud Investigations Under the Digital Markets Act

   Nov 20, 2025 - Compliance & Ethics - The European Commission is taking a look at the foundations of Europe’s cloud computing market, opening three new investigations that could reshape how major providers operate across the EU.

   www.grcreport.com
4. Related coverage: cincodias.elpais.com
   
   

   Bruselas investiga el control de acceso de Amazon y Microsoft a sus servicios en la nube | Empresas | Cinco Días

   La Comisión Europa estudia si las dos tecnológicas deben someterse a las reglas más estrictas de la ley europea de mercados digitales

   cincodias.elpais.com
5. Related coverage: tomshardware.com
   
   

   Microsoft facing $2.8 billion UK lawsuit for overcharging 60,000 businesses using Microsoft Server on other clouds — Azure users allegedly received lower wholesale pricing | Tom's Hardware

   Is the company charging a premium for users not on Azure?

   www.tomshardware.com
6. Related coverage: techradar.com
   
   

   UK looks to stop "harmful" cloud domination by AWS, Microsoft - but the tech giants are hitting back | TechRadar

   Microsoft and AWS hit back at CMA decision

   www.techradar.com
7. Related coverage: windowscentral.com
   
   

   UK CMA questions cloud market as Azure revenue grows | Windows Central

   This fiscal year, Azure and other Microsoft cloud services earned $75 billion in revenue.

   www.windowscentral.com
8. Related coverage: itpro.com
   
   

   ‘Misses the mark’: Microsoft, AWS hit out at CMA cloud competition report | IT Pro

   The CMA claims Microsoft and AWS are harming competition – the duo strongly disagree

   www.itpro.com

 

[ChatGPT]

The European Commission is reportedly preparing preliminary findings as soon as the week of June 22, 2026, that Amazon Web Services and Microsoft Azure likely qualify as cloud “gatekeepers” under the Digital Markets Act, setting up possible new EU restrictions by year’s end. This is not just another Brussels-versus-Big-Tech skirmish. It is the moment the DMA’s logic moves from app stores, messaging, search, and marketplaces into the infrastructure layer beneath almost every modern software business. If the Commission follows through, cloud lock-in will stop being a customer grievance and become a formal competition problem.

Brussels Moves the DMA Down the Stack​

The Digital Markets Act was sold to the public as a way to curb the most visible choke points in digital life: phones, browsers, search engines, social networks, app stores, advertising systems, and marketplaces. That made political sense. Voters understand why a default browser matters, why an app store commission stings, and why a messaging platform can become a private toll road.
Cloud computing is harder to dramatize, but it may be more consequential. AWS and Azure are not merely storefronts for compute cycles; they are vast, integrated ecosystems of databases, identity tools, analytics platforms, storage layers, development pipelines, security products, and AI services. Once a company builds deeply around those primitives, switching becomes less like changing suppliers and more like rewriting the plumbing of the business.
That is why the Commission’s reported preliminary view matters. The question is not whether AWS and Azure are large; everyone in enterprise IT already knows that. The question is whether their position makes them gateways between businesses and users even when cloud services do not fit the DMA’s more consumer-facing thresholds as neatly as a social network or mobile operating system.
The EU began that inquiry in November 2025, opening market investigations into AWS and Azure while also asking whether the DMA’s existing framework is sufficient for cloud services. That third question is the tell. Brussels is not merely asking whether two companies should be added to a list. It is testing whether the law can regulate the infrastructure market without being forced to rewrite itself first.

Cloud Lock-In Becomes a Regulatory Theory​

For years, cloud lock-in has been discussed as a practical nuisance, a procurement complaint, or a line item in an architecture review. Engineers know the mechanics well. A team starts with commodity compute, adds a managed database, wires in identity, moves logs into a native analytics tool, builds automation around provider-specific APIs, and eventually discovers that the “cloud” it bought is really a development platform with gravitational pull.
That gravitational pull is not inherently abusive. Managed services are useful precisely because they abstract away complexity. Azure SQL Database, AWS Lambda, Amazon S3, Azure Active Directory integrations, native Kubernetes services, managed AI platforms, and provider-specific observability stacks all exist because customers want higher-level tools, not just rented servers.
The competition concern begins when convenience turns into dependency. If the cost of moving data, licenses, workloads, security policies, or identity integrations becomes prohibitive, the customer’s theoretical freedom to switch loses practical meaning. A CIO can issue an RFP every three years, but that does not help much if the application estate has quietly become inseparable from one hyperscaler’s assumptions.
The DMA gives regulators a vocabulary for this problem. Gatekeeper status is not a moral judgment; it is a legal designation for firms that control important access points in digital markets. In cloud, the access point is less visible than a search box or an app store, but it may be more durable. Once infrastructure decisions become software architecture decisions, the customer relationship becomes sticky in a way ordinary contract law struggles to address.

AWS and Azure Are Not the Same Target​

It is tempting to describe this as a symmetrical case against “the two biggest clouds,” but AWS and Azure present different regulatory stories. AWS is the original hyperscale cloud colossus, the provider that turned elastic infrastructure into a mainstream enterprise operating model. Its power comes from breadth, maturity, ecosystem depth, and the fact that countless startups and enterprises built on its services before “multi-cloud” became a boardroom phrase.
Azure’s power is different. Microsoft’s cloud advantage is inseparable from its enterprise software estate: Windows Server, Active Directory, Entra ID, Microsoft 365, Teams, SQL Server, Visual Studio, GitHub, Dynamics, Defender, and a licensing universe that has shaped corporate IT for decades. Azure is not merely a cloud provider competing for workloads; it is the cloud extension of Microsoft’s existing enterprise relationship.
That distinction matters because cloud competition is not just a market-share contest. It is a question of leverage across layers. AWS can bind customers through service depth and operational familiarity. Microsoft can bind them through identity, licensing, productivity software, developer tooling, and security bundling. Both routes can produce customer dependence, but the mechanisms are not identical.
For WindowsForum readers, Azure’s case is especially important. The Windows ecosystem has always lived at the intersection of platform convenience and platform dependency. The move from on-prem Windows domains to hybrid identity, Microsoft 365 administration, Intune, Defender, and Azure-connected services has given IT teams powerful tools. It has also made the boundary between “Microsoft customer” and “Azure-dependent organization” harder to draw.

The DMA Was Always Headed for Infrastructure​

The Commission’s April review of the DMA signaled that cloud and AI would become priority areas. That was not regulatory mission creep so much as an admission that digital markets have shifted. The next gatekeeper may not be the company that controls the app icon on a phone; it may be the company that controls the model endpoint, the identity layer, the vector database, or the managed runtime.
This is where cloud and AI converge. Generative AI has made infrastructure choices more strategic, not less. Training, fine-tuning, retrieval systems, inference deployment, data governance, and model monitoring all lean heavily on cloud platforms. A company that standardizes on a hyperscaler’s AI stack may soon find that its data architecture, compliance posture, developer workflow, and application roadmap are all tied to that provider’s AI services.
The Commission appears to understand that the AI market cannot be analyzed apart from the cloud market. AI systems need compute, storage, networking, security controls, model catalogs, orchestration services, and developer access. If those are controlled by a handful of vertically integrated cloud platforms, then AI competition may be shaped before end users ever see a chatbot, assistant, or enterprise copilot.
That is why the cloud investigation has implications beyond hosting bills. A DMA designation for AWS and Azure would tell the market that infrastructure can be a gatekeeping layer in its own right. It would also warn the AI industry that regulators are watching not only consumer-facing models but the platforms that make those models commercially deployable.

Interoperability Is the Word That Will Do the Most Work​

If AWS and Azure are ultimately designated as gatekeepers for cloud services, the debate will quickly turn to interoperability. That sounds benign, even boring. In practice, it is where the hardest fights will happen.
Interoperability in cloud can mean many things. It could mean clearer data portability. It could mean limits on technical or commercial barriers to migration. It could mean fairer access to APIs, more transparent pricing, or less punitive treatment of customers that mix cloud providers. It could mean restrictions on self-preferencing, especially when a platform’s own services are advantaged over rivals in procurement, integration, performance, or licensing.
But cloud interoperability is not as simple as making two messaging apps talk to each other. Cloud platforms differ in architecture, service semantics, security models, operational assumptions, and failure modes. A database service on AWS is not automatically equivalent to a database service on Azure. A serverless function, identity policy, logging pipeline, or AI deployment workflow may behave differently even when the marketing nouns sound similar.
That complexity will be central to the hyperscalers’ defense. Amazon and Microsoft can argue, with some justification, that deep integration is not a trick but the product. Customers pay for managed services because they want the provider to make opinionated choices. Regulators, meanwhile, will argue that integration stops being benign when it forecloses realistic alternatives.
The difficult regulatory task is to separate genuine technical differentiation from avoidable friction. Nobody should want a DMA that freezes cloud design into lowest-common-denominator plumbing. But neither should customers accept a world where every managed convenience becomes another rivet in a cage.

The Licensing Question Is Microsoft’s Special Exposure​

Microsoft’s cloud position carries a particular vulnerability: licensing. For years, rivals and customers have complained that Microsoft’s software licensing terms can make it cheaper or easier to run Microsoft workloads on Azure than on competing clouds. Google’s 2024 complaint to the Commission focused on this broad concern, and although Google later withdrew that complaint after the EU opened its DMA cloud investigations, the underlying issue did not disappear.
Licensing is where old platform power can become new cloud power. A customer that already depends on Windows Server, SQL Server, Microsoft 365, and identity services may evaluate Azure through a different economic lens than it uses for AWS, Google Cloud, Oracle Cloud, or a European provider. Discounts, bundles, hybrid-use rights, support models, and compliance integrations can all tilt the playing field without ever looking like a crude refusal to deal.
This is why Azure’s DMA exposure is not merely about Azure. It is about Microsoft’s ability to connect its enterprise stack into a cloud adoption funnel. The company can argue that customers benefit from integrated licensing and unified administration. Competitors can argue that the same integration raises rivals’ costs and makes switching less plausible.
For administrators, the tension is familiar. Microsoft’s integrated stack can reduce operational pain. A single identity fabric, security dashboard, endpoint-management plane, and productivity suite can be a gift to understaffed IT departments. The regulatory question is whether those conveniences remain a choice when the alternatives are commercially or technically disadvantaged by the same vendor’s control of adjacent layers.

AWS Faces the Purity Problem of Being First and Biggest​

AWS does not have Microsoft’s Windows and Office inheritance, but it has a different problem: it defined much of the modern cloud market. Its APIs, service categories, architectural patterns, and operational vocabulary became defaults for a generation of engineers. In many organizations, AWS is not just a vendor; it is the assumed environment in which cloud-native work happens.
That creates a subtler kind of gatekeeping. A startup choosing AWS may do so because talent is easier to hire, documentation is abundant, third-party tools are mature, and investors trust the platform. An enterprise may stay because its operational runbooks, security approvals, disaster-recovery plans, and developer skills all assume AWS primitives. None of that requires coercion to create market power.
The Commission’s challenge will be to prove that this power creates unfairness or limits contestability in ways the DMA can address. Being successful is not illegal. Offering excellent managed services is not illegal. Building an ecosystem that customers like is not illegal.
But competition law has always cared about what happens after success hardens into control. If customers cannot credibly leave, if rivals cannot compete on equal terms because the incumbent’s ecosystem blocks practical entry, or if platform operators can favor their own higher-margin services at the expense of alternatives, then size becomes more than a reward. It becomes a lever.

Europe’s Cloud Sovereignty Debate Gets a Legal Engine​

The AWS-Azure probe also lands inside Europe’s broader debate over digital sovereignty. European governments and companies have long worried that critical infrastructure depends heavily on US hyperscalers. Those concerns intensified as cloud became inseparable from public services, defense-adjacent workloads, health systems, financial infrastructure, and AI development.
The DMA is not a sovereignty law in the narrow sense. It does not exist to punish American companies for being American, and its gatekeeper list already includes companies across different services rather than one nationality. But in practical politics, cloud competition and sovereignty now overlap. A more contestable cloud market could make room for European providers, sector-specific clouds, sovereign-cloud offerings, and multi-cloud architectures that reduce strategic dependence.
This does not mean European providers will suddenly match AWS or Azure across every service category. Hyperscale cloud is capital-intensive, technically brutal, and operationally unforgiving. The gap between “we should have European alternatives” and “European alternatives can satisfy all enterprise requirements at comparable cost and scale” remains large.
Still, regulation can change the terms of competition at the margins that matter. If data portability improves, if egress fees and licensing constraints become less punitive, if public-sector procurement becomes less tilted toward incumbents, or if interoperability obligations reduce migration risk, smaller providers gain oxygen. That may not dethrone the hyperscalers, but it could prevent them from becoming the only realistic substrate for Europe’s digital economy.

The United States Should Read This as a Market Signal, Not Just a Trade Fight​

From Washington, it will be easy to cast the EU’s move as another attack on American technology champions. That reading is politically convenient and partially understandable. The targets are AWS and Azure, two crown jewels of US enterprise technology, and the DMA has already produced high-profile clashes with Apple, Meta, Google, Amazon, and Microsoft.
But US businesses should resist the instinct to treat every European enforcement action as anti-American theater. Many of the frustrations behind the cloud probe are shared by American customers. CIOs in Chicago, Atlanta, and Dallas worry about the same migration costs, licensing traps, data-egress bills, and vendor concentration risks as their counterparts in Paris, Berlin, and Amsterdam.
The difference is that Europe has a regulatory instrument designed specifically for gatekeeping platforms. The United States has antitrust law, procurement pressure, agency investigations, and congressional anger, but it lacks a DMA-style rulebook for digital infrastructure. That makes Brussels the venue where cloud market structure is most likely to be tested first.
If the EU imposes meaningful obligations, global customers may benefit indirectly. Hyperscalers do not like maintaining radically different product and contracting practices across major markets unless they must. A rule written for Europe can become a de facto global baseline when operational simplicity, customer pressure, and reputational risk line up behind it.

The Compliance Burden Will Be Real, but So Will the Customer Leverage​

AWS and Microsoft will likely warn that DMA obligations could slow innovation, complicate security, and force platforms to expose interfaces in ways that make systems less reliable. Those concerns should not be dismissed out of hand. Cloud services are not static products; they are continuously evolving systems where a bad rule can create perverse incentives.
Yet customers should also recognize the negotiating leverage that comes from regulatory scrutiny. Even before final decisions, hyperscalers may become more careful about contractual restrictions, migration tooling, partner access, and the optics of bundling. A market investigation changes the room in which enterprise deals are negotiated.
For large customers, this is a moment to revisit assumptions. If your architecture review says “multi-cloud” but your identity, data, logging, deployment, and AI workflows all depend on one provider’s native services, you are not multi-cloud in any meaningful operational sense. If your exit plan has not been tested, it is not an exit plan. If your licensing model makes a rival cloud economically irrational, that is not a neutral technical choice.
For smaller customers, the immediate effect may be less visible. Most businesses will not rewrite applications because the Commission issues preliminary findings. But over time, the obligations attached to gatekeeper status can shape product defaults, contract language, and migration economics. The point of the DMA is not to make every customer switch. It is to make switching credible enough that staying becomes a choice rather than a sentence.

The Fine Print Will Decide Whether This Is a Turning Point​

The DMA’s promise is clear, but its cloud application will depend on details that are easy to underestimate. A designation alone does not solve lock-in. The important question is what obligations follow, how they are interpreted, and whether enforcement is fast enough to matter in markets that move faster than litigation.
If the Commission focuses too narrowly on formal portability, hyperscalers may comply in ways that look adequate on paper but do little to reduce real-world switching costs. Exporting data is not the same as moving workloads. Publishing APIs is not the same as making third-party services viable. Allowing customers to leave is not the same as making the cost of leaving commercially tolerable.
If the Commission goes too broad, it risks mandating interoperability without understanding operational complexity. That could create compliance theater, security ambiguity, or lowest-common-denominator services that help lawyers more than customers. The best outcome is a regime that targets avoidable barriers while preserving room for genuine platform innovation.
The preliminary nature of the reported findings matters here. A final decision is expected by the end of 2026, but timing can change, and the companies will have opportunities to contest the analysis. The real fight will not be over whether cloud is important. It will be over whether the Commission can define gatekeeping conduct in cloud precisely enough to survive legal, technical, and political pressure.

Windows Shops Should Treat This as an Architecture Warning​

For Windows-heavy organizations, the Azure angle should prompt a sober inventory. Microsoft’s cloud story is deeply compelling: Entra ID for identity, Intune for device management, Defender for security, Microsoft 365 for productivity, Azure for infrastructure, GitHub for development, and Copilot-branded AI across the stack. The administrative appeal is obvious.
But the same coherence that makes the Microsoft stack attractive can also reduce strategic optionality. A business that authenticates through Microsoft, manages endpoints through Microsoft, stores documents in Microsoft 365, routes security telemetry into Microsoft tools, and builds AI workflows against Microsoft cloud services may still technically be free to choose another cloud. In practice, every adjacent dependency raises the cost of doing so.
That does not mean administrators should flee Azure or reject integration. It means they should price dependency honestly. Vendor concentration can be rational, especially when staffing is limited and the integrated platform is demonstrably better. The mistake is pretending that convenience has no strategic cost.
The DMA investigation gives IT leaders a useful frame for internal discussions. If regulators are asking whether Azure functions as a gatekeeper, boards and CIOs should ask the same question at the organizational level. Where are the exits? Which workloads are portable? Which licenses assume Azure? Which security controls would break in a migration? Which AI projects are binding the company to a platform faster than procurement can track?

The Cloud Fight Has Finally Reached the Procurement Desk​

The practical lesson is not that AWS and Azure are suddenly unsafe choices. They remain the dominant platforms because they solve real problems at enormous scale. The lesson is that cloud strategy can no longer be separated from competition policy, regulatory risk, and exit economics.
Enterprise customers should not wait for Brussels to finish its process before improving their posture. The smartest response is to treat regulatory scrutiny as confirmation of risks that good architects already understood. Cloud dependency is manageable when it is visible, measured, and intentionally accepted. It becomes dangerous when it hides behind convenience.

• The Commission is reportedly preparing preliminary findings that AWS and Azure likely meet the DMA’s gatekeeper standard for cloud services.
• A final decision could arrive by the end of 2026, although the timetable may shift as Amazon and Microsoft respond.
• The investigation turns cloud lock-in from a customer pain point into a formal competition issue under EU law.
• Microsoft’s exposure is tied not only to Azure itself but also to licensing, identity, productivity software, security tools, and its broader enterprise stack.
• AWS faces a different challenge rooted in ecosystem depth, service breadth, and the inertia that comes from defining the modern cloud model.
• IT leaders should use the investigation as a prompt to test exit plans, review licensing dependencies, and distinguish real portability from slide-deck multi-cloud.

The EU’s cloud push will not make AWS or Azure disappear, and it will not magically create a perfectly open infrastructure market. But it may force the industry to admit that the most powerful digital gatekeepers are no longer always the ones users tap on a phone screen. Increasingly, they are the platforms buried beneath the application, the identity layer, the data pipeline, and the AI service — and Brussels has now signaled that those layers are fair game.

---

References​

1. Primary source: Silicon UK
   Published: Fri, 19 Jun 2026 06:30:43 GMT
   
   

   EU Set To Place Azure, AWS In DMA Crosshairs | Silicon UK Tech

   European Commission reportedly find Microsoft's Azure, Amazon Web Services probably meet DMA gatekeeper threshold All IT news on Silicon.co.uk

   www.silicon.co.uk
2. Related coverage: digital-markets-act.ec.europa.eu
   
   

   Commission launches market investigations on cloud computing services under the Digital Markets Act

   The Commission opened three market investigations on cloud computing services under the Digital Markets Act (DMA). Two market investigations will assess whether Amazon and Microsoft should be designated as gatekeepers for their cloud computing services, Amazon Web Services and Microsoft Azure...

   digital-markets-act.ec.europa.eu
3. Related coverage: europeaninterest.eu
   
   

   EU investigates Amazon and Microsoft cloud businesses under the Digital Market Act

   The cloud services offered by Amazon and Microsoft are currently under investigation by European Union regulators, who are considering whether these platforms should be classified as “gatekeepers” under the EU’s Digital Markets Act (DMA). The European Commission announced on...

   www.europeaninterest.eu
4. Related coverage: investing.com
   
   

   EU probes Amazon, Microsoft’s cloud services for potential curbs By Reuters

   EU probes Amazon, Microsoft’s cloud services for potential curbs

   www.investing.com
5. Related coverage: ppc.land
   
   

   EU opens cloud gatekeeper probes for Amazon and Microsoft

   European Commission launches three market investigations examining whether Amazon Web Services and Microsoft Azure should face Digital Markets Act regulation.

   ppc.land
6. Related coverage: itpro.com
   
   

   Google drops cloud complaint against Microsoft | IT Pro

   Anticompetitive concerns aren't gone, but Google is leaving the battle to the EC instead

   www.itpro.com