EU DMA Push Targets AWS and Azure as Cloud Gatekeepers: What Windows IT Teams Need

ChatGPT · Jun 26, 2026

The European Commission said on June 25, 2026, that Amazon Web Services and Microsoft Azure should preliminarily be treated as Digital Markets Act gatekeeper services in the European Union, a move that could force both cloud platforms to meet stricter competition obligations within six months of a final designation. The finding is not yet a final order, but it is a sharp escalation: Brussels is no longer treating cloud infrastructure as merely an enterprise procurement market. It is treating AWS and Azure as chokepoints in the digital economy. For Windows administrators, developers, and CIOs, that means the next European tech fight may land not on phones or app stores, but in licensing portals, identity stacks, AI services, and the architecture diagrams that decide where workloads can realistically run.

Brussels Moves the DMA From Screens to Server Rooms

The Digital Markets Act was sold to much of the public through familiar consumer technology fights: app stores, messaging interoperability, browser choice, self-preferencing, and the gravitational pull of the largest online platforms. Cloud computing always sat inside the law’s conceptual perimeter, but it was harder to dramatize. Nobody queues outside a data center because an object storage API changed its terms.
That is what makes the Commission’s AWS and Azure move important. Brussels is arguing that cloud platforms are not just back-end suppliers; they are gateways between businesses and customers. If the Commission finalizes the designation, the DMA’s platform logic will have crossed from the visible layer of digital life into the infrastructure layer beneath it.
This is a more ambitious theory of competition than simply asking whether a provider has a large market share. The Commission’s preliminary view is that AWS and Azure matter because they combine scale, customer dependency, ecosystems, investment capacity, and adjacent services in ways that make migration difficult and rival growth harder. In cloud, dominance is not only a percentage on a chart. It is a web of APIs, reserved capacity, certifications, data gravity, identity systems, security tooling, databases, analytics services, developer habits, partner channels, and procurement inertia.
The Commission opened the relevant market investigations on November 18, 2025, and its June 2026 preliminary findings now put Amazon and Microsoft on notice. Both companies can examine the file and respond in writing. If the finding becomes final, the six-month compliance clock starts.

The Cloud Was Never Just Somebody Else’s Computer

The old joke that “the cloud is just somebody else’s computer” was useful because it punctured marketing fog. It is also increasingly inadequate. The modern cloud is somebody else’s computer, network, security perimeter, software catalog, AI accelerator fleet, observability layer, data warehouse, compliance story, and purchasing framework.
That is why the Commission’s analysis reaches beyond raw revenue. A business that builds around AWS or Azure often does not buy a single interchangeable utility. It buys an operating environment. A team that starts with virtual machines may add managed databases, serverless functions, container registries, event buses, identity integrations, endpoint management, AI APIs, data lakes, security posture tools, backup, disaster recovery, and billing commitments that shape the next several years of technical decisions.
For WindowsForum.com readers, Azure has a special place in that picture. It is not merely Microsoft’s cloud. It is deeply tied to Microsoft Entra ID, Microsoft 365, Windows Server licensing, Defender, Intune, SQL Server, GitHub, Visual Studio, Power Platform, Dynamics, and increasingly Copilot-flavored AI services. That does not make Azure anti-competitive by default. It does make Azure unusually sticky for organizations that already live in Microsoft’s enterprise universe.
AWS has its own gravity. It has the first-mover advantage, a massive services catalog, deep partner maturity, and an enterprise customer base that has spent years standardizing around its primitives. Moving a serious AWS estate is not like switching broadband providers. Even when technical migration is possible, the organizational cost can be brutal.
Brussels is effectively saying that the difficulty of leaving is part of the competitive story. A market can look lively at the sales-pitch level while still being constrained at the architecture level. The first migration decision may be competitive; the tenth year of accumulated dependencies may not be.

Azure’s Real Power Is the Enterprise Bundle

Microsoft’s cloud position is often misunderstood when viewed only through Azure infrastructure services. Azure competes with AWS and Google Cloud in compute, storage, databases, analytics, and AI, but Microsoft’s strongest enterprise advantage comes from the bundle around it. Azure is where many organizations expect their Microsoft identities, compliance controls, endpoint policies, productivity data, and developer pipelines to meet.
That makes the Commission’s scrutiny especially relevant for Windows shops. An administrator deciding whether to host a workload on Azure is rarely making a clean, isolated cloud choice. The decision may be shaped by existing Microsoft 365 commitments, Entra ID conditional access, Windows Server hybrid benefits, SQL Server licensing terms, Defender telemetry, or the convenience of keeping governance under one vendor roof.
This is the brilliance of Microsoft’s enterprise model and the reason regulators keep circling it. Microsoft can make Azure feel like the path of least resistance without necessarily issuing a crude ultimatum. In large IT departments, “least resistance” is not a small thing. It determines project timelines, risk assessments, procurement approvals, and the informal advice architects give when nobody wants to defend an exotic design in a steering committee meeting.
The Commission’s preliminary findings also point toward AI as a new accelerant. Cloud demand is rising because AI workloads require compute, data services, model tooling, and secure integration with enterprise systems. Microsoft’s investments and partnerships in AI have made Azure a default venue for many AI procurement conversations, especially where Microsoft 365 Copilot, Azure OpenAI Service, GitHub Copilot, or security automation are already in play.
That creates a new form of lock-in. The old lock-in was about virtual machines and databases. The new lock-in may be about model access, embeddings pipelines, enterprise search, data residency promises, agent frameworks, developer tooling, and governance systems that determine whether AI pilots become production workloads. Once those decisions harden, switching cloud providers becomes less like moving files and more like rebuilding an operating model.

AWS Faces the Same Charge From a Different Angle

Amazon does not have Microsoft’s Windows and Office estate, but AWS has something just as formidable: cloud-native incumbency. It trained a generation of developers and architects to think in AWS patterns. Its service catalog became the reference language for much of modern infrastructure.
AWS lock-in often looks less like a bundle and more like technical depth. Customers may adopt DynamoDB, Lambda, S3 eventing, IAM policies, CloudFormation, ECS, EKS, Kinesis, Redshift, SageMaker, and a thick layer of monitoring and security tooling. Each choice can be rational. Together, they form an estate that is hard to duplicate elsewhere without redesign.
This is the central paradox of cloud competition. The better the managed services become, the stronger the customer’s dependency becomes. A cloud provider that offers excellent proprietary primitives can reduce operational burden while increasing switching cost. Customers often accept that trade because the alternative is slower delivery and more self-managed infrastructure.
Regulators, however, see the aggregate effect. If the largest platforms can absorb demand, expand service catalogs, discount strategically, and make departures painful, smaller cloud providers can be confined to niches even when they offer credible technology. The market may reward innovation inside the big platforms more than innovation against them.
AWS will likely argue that enterprise cloud remains competitive, that customers use multi-cloud strategies, and that rivals from Google to Oracle to European providers continue to win business. That is not a frivolous defense. But the Commission’s theory is aimed at the practical limits of that competition: whether the largest providers function as unavoidable gateways even when a customer technically has alternatives.

The DMA Threshold Fight Is the Legal Tell

The most striking part of the Commission’s move is that AWS and Azure reportedly do not meet the DMA’s usual quantitative thresholds for designation in this context. Brussels is not saying the spreadsheet alone settles the matter. It is using the DMA’s investigative path to argue that qualitative power can be enough.
That matters because cloud markets do not behave like consumer social networks or mobile operating systems. User counts are harder to interpret. A single large enterprise customer may matter more than millions of individual accounts. Revenue, workload criticality, and ecosystem dependency can say more about market power than the number of people who click a login button.
The Commission’s position is therefore both legally aggressive and intellectually coherent. If cloud computing is now foundational infrastructure for commerce, government, media, finance, healthcare, manufacturing, and AI, then a rigid threshold test may miss the real gatekeeping function. The business user, not the consumer, becomes the key unit of analysis.
That is also where the fight will get ugly. Amazon and Microsoft can argue that the Commission is stretching a law built for platform bottlenecks into a market where technical choice is abundant and customer sophistication is high. Brussels can counter that sophisticated customers still get trapped when the economic and operational cost of moving becomes prohibitive.
The outcome will help define how flexible the DMA really is. If the Commission succeeds, it will have shown that the law can reach infrastructure markets before they fully calcify. If it overreaches, it risks turning the DMA into a broad industrial-policy lever that every large digital supplier must treat as a standing threat.

Europe’s Sovereignty Argument Is Hiding in Plain Sight

The Commission’s public competition language is about fair, open, and contestable markets. But cloud regulation in Europe is never only about competition. It is also about sovereignty, resilience, and the uncomfortable fact that much of Europe’s digital economy runs on infrastructure controlled by American giants.
That tension has been present for years. European governments and regulated industries want modern cloud capability, but they also worry about data protection, foreign legal exposure, dependency, and strategic autonomy. The rise of AI has intensified the anxiety because model training, inference, data integration, and high-performance computing make cloud capacity even more central to national competitiveness.
The AWS and Azure gatekeeper move is not a data sovereignty rule in disguise, but it lives in the same political weather system. If European cloud providers cannot gain meaningful ground because customers are locked into U.S. hyperscaler ecosystems, then Europe’s sovereignty agenda is constrained before it starts. Brussels cannot build strategic autonomy on a foundation that procurement teams cannot realistically choose.
This is why the cloud fight feels different from earlier DMA battles. When regulators pressure app stores, the immediate story is consumer choice and developer fees. When they pressure cloud providers, the story reaches public administration, critical infrastructure, AI policy, defense-adjacent workloads, and the ability of European firms to scale without renting their strategic nervous system from abroad.
There is a risk in that framing. Competition law can become muddled if it is asked to do too much industrial-policy work. But there is also a practical truth behind it: infrastructure dependency is power, and Europe has decided it cannot leave that power entirely to contract negotiations between hyperscalers and customers.

The AI Boom Gives Regulators Their Urgency

If this were only a cloud market-share dispute, Brussels might have moved more slowly. AI has changed the tempo. The Commission’s preliminary findings explicitly connect cloud demand with AI tools and partnerships, and that is the right place to look.
AI workloads do not float above infrastructure. They need chips, storage, networking, orchestration, data pipelines, developer frameworks, identity controls, logging, compliance, and integration with business applications. The provider that controls those layers can shape what AI products customers can deploy, how quickly they deploy them, and which ecosystem captures the follow-on spend.
Microsoft’s Azure AI strategy is especially consequential because it sits next to Microsoft 365, GitHub, Windows, security, and business applications. A company experimenting with Copilot or Azure OpenAI is not simply buying model access. It may be moving more data, identity, developer activity, and governance into Microsoft-controlled channels.
AWS has responded with its own AI stack, including model marketplaces, custom silicon, managed AI services, and infrastructure tuned for large-scale workloads. Google Cloud, Oracle, and others are also pushing hard, but the Commission’s focus on AWS and Azure reflects the scale and position of the top two providers in the EU market.
AI makes lock-in more durable because the integrations are more semantic and organizational than traditional infrastructure migrations. A database can be exported, painfully. A model governance process tied to a vendor’s identity, logging, prompt management, retrieval system, and compliance workflow is harder to unwind. Once AI becomes embedded in internal processes, the cloud platform becomes part of the company’s decision-making machinery.

CIOs Wanted Optionality, Not Another Compliance Drama

Enterprise buyers have spent years saying they want portability, multi-cloud leverage, and reduced lock-in. In practice, they also want fewer vendors, simpler governance, lower operational risk, and discounts. Those goals conflict. The hyperscalers have won partly because they are very good at exploiting that conflict.
For CIOs, the Commission’s move may create useful leverage before it creates immediate change. If AWS and Azure are eventually designated, customers may see pressure around interoperability, self-preferencing, access terms, data portability, and commercial practices that make switching harder. Even the possibility of intervention can change negotiations.
But enterprises should not confuse regulatory motion with architectural freedom. A future DMA obligation will not magically rewrite Terraform modules, untangle identity dependencies, refactor applications, or retrain engineers. The cloud customer that wants leverage still needs to design for it.
That means being honest about which workloads are portable and which are not. A containerized application using open databases and standard observability tooling is one thing. A business-critical platform built around proprietary serverless functions, vendor-specific eventing, managed AI services, and identity-bound automation is another. Both may be legitimate choices, but only one preserves credible exit options.
The most mature IT shops will treat the Commission’s move as a prompt for internal review. They will not wait for Brussels to define their risk. They will ask where the organization is dependent, where that dependency is worth it, and where convenience has quietly become strategic exposure.

For Windows Shops, Licensing May Be the Pressure Point

The Microsoft angle is particularly sensitive because cloud competition is entangled with software licensing. Windows Server, SQL Server, Microsoft 365, and enterprise agreements shape how customers evaluate Azure versus alternatives. Even when the technical migration path exists, licensing economics can tilt the field.
This has been a recurring grievance among rivals and customers. The complaint is not simply that Microsoft offers attractive terms on Azure. It is that customers running Microsoft software may face less favorable economics or added complexity when they choose competing clouds. Microsoft has made changes over time, but the broader suspicion remains: Azure benefits from Microsoft’s control over software that many enterprises cannot easily abandon.
For Windows administrators, this is not abstract. Licensing rules affect modernization projects, disaster recovery architecture, VDI decisions, SQL Server placement, hybrid cloud design, and whether a workload can move to another provider without cost shock. A beautifully portable application can still be commercially pinned down by the licensing stack underneath it.
If Azure becomes subject to DMA gatekeeper obligations, regulators may examine not only obvious cloud platform practices but also the way Microsoft’s broader ecosystem reinforces Azure’s position. The hard part will be drawing the line between legitimate integration and exclusionary leverage. Microsoft can reasonably argue that customers benefit when identity, security, productivity, and cloud infrastructure work together. Competitors can reasonably answer that integration becomes coercive when alternatives are made unnecessarily expensive or awkward.
This is where the DMA may collide with decades of enterprise software practice. Bundling, discounting, volume commitments, and ecosystem integration are normal in enterprise IT. The question is whether they remain normal when the supplier also controls a platform Brussels considers a gateway.

Smaller Clouds Need More Than Sympathy

European cloud providers and smaller rivals are likely to welcome the Commission’s pressure, but regulation alone will not make them hyperscalers. Customers do not choose AWS and Azure only because they are trapped. They choose them because they offer breadth, maturity, global reach, security certifications, partner ecosystems, and service velocity that smaller providers often struggle to match.
This is the uncomfortable side of the sovereignty debate. If Europe wants more cloud competition, it needs more than restrictions on American platforms. It needs credible alternatives that can meet enterprise requirements without asking buyers to accept a downgrade in capability, tooling, resilience, or support.
The DMA can lower barriers. It can attack unfair tying, portability obstacles, discriminatory access, or practices that trap customers. It cannot conjure GPU capacity, global regions, enterprise support maturity, or thousands of third-party integrations overnight.
That does not make the Commission’s move pointless. Markets can be unfair and still have strong incumbents for good reasons. The role of regulation is not to punish excellence; it is to prevent excellence from hardening into unchallengeable control. But rivals will still need to win on product, trust, and execution.
The best outcome for customers is not a weakened AWS or Azure. It is a cloud market where AWS and Azure remain excellent, but customers have more credible freedom to mix, leave, negotiate, and choose specialized providers without paying an artificial penalty.

The Compliance Clock Could Redraw the Cloud Contract

If the Commission confirms the designation, Amazon and Microsoft would have six months to bring AWS and Azure into compliance with DMA obligations. The precise practical effects will depend on the final decision and the Commission’s interpretation, but the direction is clear: cloud platforms would be expected to behave less like closed gravity wells and more like contestable infrastructure.
The most immediate impact may be contractual and procedural rather than technical. Providers may need clearer terms, better data access mechanisms, fairer treatment of third parties, and less friction for customers that want to move workloads or connect rival services. Procurement teams may gain language to challenge lock-in clauses or opaque bundling.
Technical changes could follow, especially around portability and interoperability. Cloud providers may be pushed to make exits less punitive, integrations less discriminatory, or ecosystem participation more open. But anyone expecting a single “export my cloud” button will be disappointed. Modern cloud estates are too varied for that.
A more realistic outcome is a gradual shift in incentives. If regulators make the worst lock-in tactics riskier, providers may compete harder on service quality and price rather than exit friction. If customers believe switching is more plausible, even if still difficult, negotiations change. Optionality does not need to be frictionless to be valuable; it just needs to be credible enough to discipline the supplier.
For IT departments, that makes documentation and architecture discipline more important. A regulated market helps most when customers can act on the freedom it creates. If an organization has no workload inventory, no dependency mapping, no licensing model, and no tested migration path, regulatory rights will sit unused.

Washington Will Hear an Industrial Policy Alarm

The Commission’s action will not be read in the United States as a narrow cloud competition case. It will be folded into the broader argument over whether the EU’s digital rulebook unfairly targets American technology companies. That argument has already followed DMA enforcement against other large platforms, and cloud will intensify it because AWS and Microsoft are crown jewels of U.S. enterprise technology.
Critics will say Brussels is punishing scale, successful investment, and integrated services. They will argue that the DMA risks slowing innovation, weakening trusted providers, and imposing European regulatory preferences on global platforms. They will also point out that cloud is a fiercely competitive market in which sophisticated buyers negotiate hard and routinely use multiple providers.
Supporters will answer that this is precisely the moment to intervene. Once AI infrastructure, cloud data layers, and enterprise identity systems are fused into a handful of platforms, competition remedies become harder and more disruptive. Waiting until customers have no practical exit would be regulatory malpractice.
Both sides have a point. The hyperscalers became dominant because they built extraordinary platforms and invested sums few others could match. They also benefit from feedback loops that can make future competition structurally harder. The policy question is whether Europe can restrain the latter without damaging the former.
That balance will determine whether the DMA becomes a durable competition framework or a recurring transatlantic grievance machine. Cloud is a tougher test than app stores because the customers are businesses, the contracts are complex, and the technical dependencies are often chosen knowingly. Brussels will need to show that it understands that sophistication rather than pretending enterprise buyers are helpless consumers.

The Real Test Is Whether Exit Becomes Believable

Cloud customers rarely need to switch providers tomorrow. They need the supplier to believe they could switch if the relationship deteriorates. That distinction is central to competition in enterprise technology.
A credible exit option disciplines pricing, support, roadmap neglect, and aggressive bundling. An incredible exit option becomes theater. Vendors know when a customer is bluffing, and cloud vendors have more telemetry than most about how deeply a customer is embedded.
The Commission’s gatekeeper theory is really about making exit believable again. Not cheap, not instant, and not painless, but believable. That would be a meaningful change in a market where many customers talk multi-cloud while quietly centralizing critical capabilities around one provider.
There is also a security dimension. Concentration can improve security because hyperscalers have world-class teams, tooling, and resilience. Concentration can also create systemic risk because an outage, policy change, identity compromise, or service degradation at one provider can ripple through thousands of organizations. A more contestable market is not automatically safer, but dependency mapping is a security control as much as a procurement tool.
Windows and Microsoft-centric environments should be especially careful not to treat Azure as the inevitable destination for every modernization project. Azure may often be the right answer. The problem begins when it becomes the answer nobody has to justify.

The Cloud War Now Has a Regulatory Front

The Commission’s preliminary findings do not mean AWS and Azure are already operating under a final DMA cloud regime. Amazon and Microsoft still have the right to respond, and the final designation could be narrowed, delayed, challenged, or reshaped. But the strategic signal has already been sent.
For the cloud industry, the signal is that scale plus ecosystem control will invite scrutiny even when conventional thresholds are not met. For customers, the signal is that regulators are beginning to take switching costs and AI-driven dependency seriously. For rivals, the signal is that Brussels may be willing to intervene before the AI cloud market locks into a permanent hierarchy.
The practical next step for IT leaders is not to wait for the Commission. It is to treat cloud dependency as a board-level architecture issue. The organizations that benefit most from any regulatory opening will be the ones that already know where they are locked in and why.

The Fine Print Is Where This Fight Will Be Won

The Commission’s move is easy to summarize as “EU targets AWS and Azure,” but the real story will be in implementation. Cloud markets are too technical for slogans. A remedy that sounds powerful in Brussels can become irrelevant if it does not touch the actual sources of customer dependency.
The important questions will be concrete. Can customers move data without punitive cost or unacceptable delay? Can third-party services interoperate without being disadvantaged? Can Microsoft’s software licensing terms avoid tilting infrastructure choices toward Azure? Can AWS and Azure maintain integrated service quality while giving rivals fair access to customers? Can AI tooling be made portable enough that customers are not locked into a model ecosystem before the market has matured?
Those are hard questions because cloud lock-in is not always abusive. Sometimes it is the price of using advanced managed services. The same proprietary feature that traps a customer may also be the feature that let a small team ship a product without hiring a platform engineering department.
That is why the Commission should avoid treating portability as a religion. Open standards matter, but customers also benefit from differentiated platforms. The right target is not every form of dependency; it is dependency that is hidden, coercive, discriminatory, or commercially engineered to make competition ineffective.
If Brussels can keep that distinction clear, it may produce a more competitive cloud market without flattening the services that made cloud valuable in the first place. If it cannot, the DMA risks becoming a compliance tax that sophisticated incumbents absorb more easily than the smaller rivals it is supposed to help.

The Architecture Review That Should Happen Before Brussels Decides

The most useful response from enterprise IT is an internal one. Every major AWS or Azure customer should use this moment to review its own assumptions. Regulation may change the market, but architecture determines whether those changes matter.
A serious review should start with the workloads that would be hardest to move under pressure. That means looking beyond compute and storage into identity, databases, observability, AI services, security controls, automation scripts, backup designs, network dependencies, and licensing commitments. The question is not whether everything can be made portable. It is whether the organization knows which dependencies are deliberate and which accumulated by accident.
The second step is commercial. Cloud bills are not just consumption meters; they are maps of leverage. Reserved instances, committed spend agreements, enterprise licensing terms, marketplace purchases, and support contracts all shape future options. A customer that treats those commitments as procurement paperwork will miss their architectural significance.
The third step is governance. If developers can adopt proprietary services faster than architects can evaluate long-term consequences, lock-in becomes an emergent property of delivery pressure. That does not mean banning managed services. It means requiring the team to state the trade-off in plain English before the dependency becomes business-critical.
This is where Windows administrators and platform teams can add real value. They understand the hidden coupling between identity, endpoints, servers, policy, monitoring, and user productivity. In a Microsoft-heavy estate, the decision to use Azure is often not a single decision at all. It is the cumulative result of dozens of smaller defaults.

The Six-Month Shadow Over Hyperscale Cloud

The Commission has not yet imposed the final designation, but the possible six-month compliance deadline now hangs over AWS and Azure strategy in Europe. That timetable is short in regulatory terms and very short in cloud engineering terms. If final decisions arrive, Amazon and Microsoft will need to translate legal obligations into product, contract, and partner changes quickly.
Customers should expect careful messaging from both companies. They will emphasize existing competition, customer choice, security, investment, and the risk of regulatory friction. They may also quietly adjust terms or practices before being forced to do so, because no platform wants a public list of lock-in remedies written entirely by regulators.
Rivals will press the opposite case. They will argue that voluntary changes have not been enough, that hyperscaler dominance has already shaped the market, and that AI will make delay more costly. European providers, in particular, will frame the issue as both competition and strategic autonomy.
The Commission will have to prove it can distinguish between market power and mere success. That is the credibility test. AWS and Azure are not dominant because customers are foolish; they are dominant because they are useful, mature, and deeply integrated into how modern organizations build technology. Any remedy that ignores that will fail.

Europe’s Cloud Verdict Is Really an AI Verdict

The Commission’s preliminary gatekeeper move is best understood as an early verdict on the AI era. Brussels sees cloud platforms becoming the substrate for the next wave of digital power. If the same companies that dominate infrastructure also capture the AI tooling, data integration, and enterprise workflow layers, the market may close before competitors have a meaningful chance.
That does not mean AWS and Azure should be treated as villains. It means they should be treated as infrastructure with public consequences. The larger and more indispensable a platform becomes, the more its private design choices become market rules for everyone else.
For Windows users and administrators, the immediate effects may be subtle. Nobody’s Azure tenant changes overnight. No AWS workload suddenly becomes portable by decree. But procurement language, licensing pressure, AI service selection, and cloud architecture debates may all start to shift as the regulatory fight advances.
The cloud was once pitched as flexibility itself. The Commission is now asking whether the biggest clouds have become the opposite: flexible on the way in, rigid on the way out.

The Practical Reading for WindowsForum Readers Is Written in Contracts and Diagrams

This story will produce plenty of ideological noise, but the useful signal for IT pros is concrete.

The Commission’s June 25, 2026 preliminary finding targets AWS and Azure as potential DMA gatekeeper services, not Amazon and Microsoft’s entire corporate existence in a generic sense.
The process began with market investigations opened on November 18, 2025, and Amazon and Microsoft still have an opportunity to respond before any final designation.
If the designation is confirmed, the companies would have six months to bring the affected cloud services into compliance with DMA obligations.
The Commission’s theory rests heavily on lock-in, switching costs, ecosystem depth, AI-driven demand, and the role of AWS and Azure as gateways between businesses and customers.
Windows-centric organizations should pay special attention to Microsoft licensing, identity, security, and productivity integrations that can make Azure the default even when alternatives exist.
The most useful preparation is dependency mapping: knowing which workloads, contracts, data flows, and AI services could realistically move, and which are effectively anchored.

Brussels has opened a new front because the cloud has become too important to remain a private fight between procurement departments and hyperscalers. Whether the DMA can make AWS and Azure more contestable without weakening the services customers rely on is now the question that will define Europe’s next phase of tech regulation. For enterprises, the wise move is not to wait for a final order, but to rediscover the discipline cloud once promised: build for choice, document the trade-offs, and never let convenience quietly become captivity.

References

Primary source: EU Today
Published: Fri, 26 Jun 2026 07:24:02 GMT

Brussels opens new front in cloud regulation with AWS and Azure gatekeeper move - https://eutoday.net

The European Commission has opened a new front in its regulation of Big Tech after reaching the preliminary view that Amazon Web Services and Microsoft Azure

eutoday.net
Independent coverage: The Brussels Times
Published: 2026-06-25T22:30:26.575559

The Brussels Times

www.brusselstimes.com
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
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: itif.org

EU’s Designation of AWS and Azure as Core Platform Services Escalates Weaponization of Digital Markets Act, Says ITIF | Press Releases | Jun 25, 2026 | ITIF

The European Commission is stretching the DMA to target cloud infrastructure, raising the stakes for U.S.-EU tech tensions.

itif.org
Related coverage: computerweekly.com

European Commission launches AWS and Microsoft-focused cloud competition probes | Computer Weekly

The European Commission has launched three investigations into how the continent's cloud market operates, with two focused specifically on Microsoft and Amazon Web Services

www.computerweekly.com

Related coverage: 2eu.brussels

EU wants stricter cloud rules: Amazon and Microsoft investigated for dominant position

The European Commission has opened three market investigations targeting cloud services from Amazon (AWS) and Microsoft (Azure). Brussels is analyzing whether they should be designated as "gatekeepers" under the DMA, even if they don't meet standard size thresholds, and is evaluating whether...

2eu.brussels
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
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
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: ec.europa.eu

DMA 100236 28

PDF document

ec.europa.eu
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
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
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

ChatGPT · Jun 26, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that its preliminary view is that AWS and Azure should be designated as Digital Markets Act gatekeepers for cloud computing services in the European Union. The finding is not yet a final order, but it is the clearest signal so far that Brussels wants its Big Tech rulebook to move below the app store and search layer into the infrastructure layer. For WindowsForum readers, the story is not merely that two American hyperscalers may face more paperwork. It is that the cloud stack behind Microsoft 365, Azure AI, Windows management, retail platforms, and countless enterprise applications is becoming a formal competition battleground.
The Commission’s move lands at a moment when cloud has stopped being a neutral utility in the political imagination. It is now where AI models are trained, customer data is warehoused, software vendors are locked in or locked out, and national governments discover how much of their digital sovereignty depends on someone else’s data center roadmap. The EU is not just asking whether AWS and Azure are large. It is asking whether they have become unavoidable.

Brussels Moves the Gatekeeper Fight Down the Stack

The Digital Markets Act was written for a world in which digital power looked visible: app stores, search engines, browsers, social networks, operating systems, marketplaces, and advertising networks. Those were the obvious choke points. If a developer could not get into an app store, if a merchant had to play by marketplace rules, or if a browser default quietly shaped the web, regulators could point to a recognizable gate.
Cloud infrastructure is a less photogenic target, but it may be the more consequential one. A retailer choosing AWS, a manufacturer standardizing on Azure, or a startup building around managed databases and AI services is not simply renting compute. It is adopting an operating environment that can reshape procurement, software architecture, security tooling, identity systems, data flows, and exit costs for years.
That is why the Commission’s preliminary position matters. AWS and Azure reportedly do not meet the DMA’s normal quantitative thresholds for this specific designation, yet Brussels says they may still function as important gateways between businesses and customers in the EU. In plain terms, the Commission is saying that formal thresholds are not the only way to measure power when an infrastructure platform becomes deeply embedded in commercial life.
This is a familiar European regulatory instinct, but applied to a newer terrain. The EU has long preferred ex ante rules for digital markets, arguing that waiting for traditional antitrust cases to grind through the courts often lets dominant positions harden before remedies arrive. The DMA is supposed to prevent gatekeepers from using their platform control to entrench themselves, not simply punish them after the market has tipped.
The cloud inquiry stretches that theory. If app stores are doors, cloud platforms are the building’s foundation. Regulating them under the same framework raises harder questions, because the cloud is not a single consumer-facing product with a neat user interface. It is a mesh of compute, storage, networking, databases, AI tooling, identity, telemetry, security, billing, partner marketplaces, and professional services.

AWS and Azure Are Being Judged by Dependence, Not Just Size

The important detail is that the Commission’s argument appears to lean on functional dependence rather than a simple market-share headline. AWS is the largest cloud provider in the EU, Azure the second largest, and together they account for a very large slice of the region’s public cloud market. But the regulatory case is less interesting if reduced to a leaderboard.
What Brussels is really probing is whether customers and software vendors can realistically avoid the two hyperscalers without paying a penalty in capability, scale, compliance coverage, AI tooling, support, or ecosystem access. This is the problem every IT leader recognizes but rarely states in procurement language. The best cloud may not be the cheapest cloud; it is often the one that comes with the fewest career-threatening surprises.
AWS earned that position by being early, broad, and relentless. Azure earned it by turning Microsoft’s enterprise gravity into cloud momentum, binding Windows Server, Active Directory, Microsoft 365, SQL Server, developer tools, and enterprise agreements into a platform migration path. For many organizations, Azure is not a new vendor. It is the next room in a Microsoft house they already live in.
That makes Azure’s scrutiny particularly important for this audience. Microsoft’s cloud business is not just a place to host virtual machines. It is tied to Entra ID, Intune, Defender, Sentinel, GitHub, Visual Studio, Power Platform, Dynamics, Teams, and now an expanding line of Copilot and Azure AI services. The more Microsoft turns its productivity, security, developer, and AI portfolio into a unified platform, the more regulators will ask whether customers are choosing each piece freely or being carried along by the bundle.
AWS has a different kind of gravitational field. Its lock-in is less about an installed base of Windows desktops and Office tenants and more about service depth, operational maturity, and developer habit. Once an application is built around AWS primitives, managed databases, serverless functions, IAM policies, data pipelines, and observability systems, moving it can become less a migration than a rewrite.
The Commission’s preliminary view treats both models as potentially gatekeeping. That is the notable part. Brussels is not saying Microsoft and Amazon are identical companies with identical leverage. It is saying each may control a route to customers that is now important enough to warrant DMA obligations.

The Cloud Was Supposed to Be Portable Until It Became Productized

The old sales pitch for cloud computing was elasticity. Buy what you need, scale up, scale down, avoid capital expenditure, and stop treating servers like furniture. Portability was implied by abstraction: if workloads were just software running somewhere else, surely they could run somewhere else again.
That promise was only partly true. Basic virtual machines are portable in the same way that moving house is simple if all you own is a chair. Modern cloud applications use managed databases, identity services, queues, secrets stores, analytics engines, AI APIs, deployment pipelines, proprietary monitoring, and vendor-specific cost controls. The value of the cloud is precisely the thing that makes it sticky.
This is where regulators and engineers sometimes talk past each other. A legal framework may ask whether a customer can switch provider. An architect will answer: yes, with enough money, risk, downtime, testing, retraining, and executive patience. The practical question is not whether switching is possible. It is whether switching is economically rational after the platform has become part of the application.
For Windows administrators, that distinction is not abstract. A company that manages devices with Intune, authenticates users through Entra ID, protects workloads through Defender, deploys infrastructure through Azure Policy, and analyzes logs in Microsoft Sentinel may technically be multi-cloud. Operationally, however, it has a Microsoft control plane. The cloud is no longer just where workloads run; it is where the rules of the environment are enforced.
AWS customers face similar realities through a different toolchain. A workload that leans heavily on Lambda, DynamoDB, S3 eventing, CloudWatch, IAM, KMS, and Bedrock is using a coherent platform. It gains speed by adopting AWS-native services, but every native integration becomes another thread to untangle if the customer later wants to leave.
The Commission’s move is therefore not anti-cloud. It is a recognition that the cloud’s most valuable features create the very dependencies that competition law worries about. A bare-bones commodity cloud would be easier to switch away from, but less useful. A highly integrated cloud is more powerful, but harder to escape.

Microsoft’s Problem Is That Azure Is No Longer Just Azure

Microsoft will likely argue that Azure competes fiercely with AWS, Google Cloud, Oracle, and a long tail of European and specialist providers. That is true as far as it goes. The cloud market is competitive in visible ways: vendors fight over discounts, regions, AI accelerators, database migrations, sovereign offerings, and enterprise commitments.
But Microsoft’s regulatory challenge is that Azure increasingly functions as the substrate for a much broader Microsoft ecosystem. The company’s AI strategy flows through Azure. Its security strategy increasingly assumes Microsoft telemetry and cloud-native response. Its device management strategy pushes enterprises toward cloud control. Its productivity suite is wrapped in identity, compliance, data governance, and Copilot services that make Azure a natural extension of the Microsoft 365 tenant.
This is a triumph of product strategy. It is also a red flag for regulators who have spent decades watching platform companies turn adjacency into advantage. When one vendor controls the operating system on endpoints, the dominant office suite, enterprise identity, collaboration, security tooling, developer platforms, and a top-two cloud, every integration can be defended as convenience and attacked as foreclosure.
The Windows world has lived this story before. Internet Explorer’s bundling with Windows was the canonical antitrust fight of the late 1990s and early 2000s. Today’s cloud integrations are subtler, more defensible, and often genuinely useful. No administrator wants identity, endpoint management, email security, and conditional access to be more fragmented for the sake of regulatory purity.
Yet the logic is familiar. The more Microsoft makes Azure the easiest default for existing Microsoft customers, the more rivals will argue they are not competing on a level field. The gatekeeper question becomes less about whether Azure has good products and more about whether Microsoft’s estate makes Azure the path of least resistance.
That is why this proceeding could matter even if the immediate remedies are procedural. A DMA designation would put pressure on Microsoft to show that interoperability, portability, fair access, and data-use boundaries are not afterthoughts. It would also give European regulators a stronger basis to examine cloud-adjacent conduct that might otherwise be treated as ordinary product integration.

Amazon’s Cloud Dominance Has a Different Political Weakness

AWS does not carry Microsoft’s Windows legacy, but it has its own exposure. It is the original hyperscale cloud giant, and for many developers it remains the reference model for what public cloud is. Its sheer breadth can make competitors look partial even when they are technically capable.
Amazon’s political weakness is not that AWS is tied to a dominant desktop operating system or productivity suite. It is that AWS has become infrastructure for companies that also compete with Amazon in retail, logistics, media, advertising, and data-intensive services. The old marketplace concern — whether Amazon can use its position to advantage itself — takes on a new form when Amazon also hosts parts of the digital economy’s backend.
Retail Gazette’s framing is therefore apt, because retailers are not passive observers in this fight. Many of them rely on cloud infrastructure for commerce platforms, personalization, inventory systems, analytics, fraud detection, and customer-service automation. Some are also wary of Amazon as a competitor or marketplace power. The cloud relationship can be commercially rational and strategically uncomfortable at the same time.
AWS has long insisted that it serves customers independently and securely. Its credibility with enterprise buyers depends on that trust. But competition policy does not require a finding that a company has misused every possible advantage before regulators act. Under the DMA model, the question is whether the structure of the market gives a gatekeeper incentives and capacities that require rules in advance.
That makes AWS a clean test case for the cloud chapter of Big Tech regulation. It is dominant without being bundled into Windows. It is deeply embedded without being a default office-suite extension. If the Commission ultimately designates AWS, it will be saying that infrastructure power alone can justify gatekeeper obligations.

The DMA May Force Cloud Providers to Compete on Exit as Well as Entry

The cloud industry is very good at onboarding. It has credits, migration factories, reference architectures, partner incentives, free tiers, proof-of-concept funding, and armies of solution architects. It is less enthusiastic about helping customers leave.
That asymmetry is central to the regulatory case. Competition is not healthy simply because vendors fight hard before a contract is signed. It remains healthy when customers can credibly threaten to move after the contract is signed. If exit is too painful, renewal becomes less a contest than a hostage negotiation with better dashboards.
Europe has already spent years circling issues such as data portability, egress fees, interoperability, software licensing restrictions, and cloud switching costs. The DMA could bring a sharper enforcement tool to some of those concerns, though the fit will not be perfect. Cloud markets are technical, contractual, and operational in ways that consumer platform rules were not originally designed to handle.
The most immediate practical effect may be behavioral. If AWS and Azure expect gatekeeper obligations, they may become more cautious about self-preferencing, restrictive contract terms, data-use practices, and technical barriers that make rivals’ services harder to use. They may also invest more heavily in compliance narratives around portability, sovereign operations, and open standards.
That does not mean cloud will suddenly become plug-and-play. No regulation can make a complex distributed application portable by decree. But rules can change the incentives around how vendors price data movement, document interfaces, support third-party tooling, and structure licensing. For customers, that is where the real stakes sit.

Europe’s Sovereignty Argument Is Becoming an Economic Argument

The EU’s cloud push is often described as digital sovereignty, and that phrase can sound like a policy slogan in search of a product. But sovereignty in this context is not only about flags over data centers. It is about who has leverage when cloud infrastructure becomes essential to industry, government, healthcare, finance, retail, and AI development.
European policymakers have watched the region become heavily dependent on non-European hyperscalers while its own cloud providers struggle to match their scale, service catalogs, and capital expenditure. That dependence is not automatically a security failure. AWS, Microsoft, and Google operate some of the most sophisticated infrastructure in the world. Many European organizations choose them because the alternatives do not offer the same combination of capability and reach.
Still, capability does not erase strategic concern. If European cloud demand keeps growing while the control plane remains concentrated in a few American firms, Brussels will face a recurring dilemma. It can enjoy the productivity benefits of hyperscale infrastructure, or it can try to nurture local alternatives, or it can attempt to do both by forcing the biggest platforms to behave more like regulated gateways.
The DMA route is the third option. It does not nationalize the cloud or ban foreign providers. It tries to make dominant platforms contestable enough that European providers, open-source stacks, specialist clouds, and multi-cloud strategies have room to survive. Whether that works is another matter.
There is a danger that regulation becomes a substitute for industrial capacity. Europe can designate gatekeepers, but it cannot fine its way into cheaper GPUs, denser data center buildouts, better developer ecosystems, or faster product execution. If the goal is a more competitive cloud market, rules must be paired with credible investment, procurement reform, and technical standards that customers actually want to use.

AI Turns Cloud Gatekeeping Into a Faster-Moving Problem

Five years ago, a cloud competition fight might have centered on storage prices, virtual machines, software licensing, and data egress. Those issues still matter. But AI has raised the stakes and accelerated the clock.
Modern AI services are deeply tied to cloud infrastructure. Training and inference require specialized hardware, massive data pipelines, managed model services, security boundaries, developer tools, and enterprise integration. The companies with cloud scale can turn AI into a platform layer faster than smaller competitors can assemble the required infrastructure.
Microsoft’s relationship with OpenAI and its broader Copilot strategy make Azure central to the company’s AI ambitions. AWS has its own AI stack, including model services and infrastructure offerings designed to keep customers inside the AWS ecosystem. Google Cloud, though not the target of this preliminary finding, is also a major AI cloud competitor, which is why Microsoft is reportedly keen to argue that regulators should not understate Google’s position.
The Commission’s cloud investigation is therefore also an AI market investigation by implication. If cloud providers become the default route to enterprise AI, then gatekeeper power in cloud could influence which models, tools, marketplaces, and data services gain traction. The risk is not merely that customers pay too much for compute. It is that the next software platform shift inherits the same concentration as the last one.
This is where the DMA may prove both useful and strained. It can impose obligations on designated gatekeepers, but AI services evolve quickly and blur product boundaries. Is a model catalog part of cloud infrastructure, a marketplace, a developer platform, or an application service? Is a Copilot feature a productivity product, an AI service, or an Azure workload in disguise? Regulators will need answers fast enough to matter.

Enterprise IT Should Read This as a Procurement Warning

For enterprise buyers, the Commission’s move should not trigger panic migration plans. AWS and Azure are not going away, and a preliminary DMA position does not invalidate their technical merits. Most organizations will continue buying from them because they solve real problems at scale.
The smarter response is to treat the proceeding as a warning about concentration risk. If the EU believes AWS and Azure may be unavoidable gateways, CIOs should ask whether their own architecture has quietly reached the same conclusion. A regulator’s concern about lock-in is often just an enterprise risk register written in public-policy language.
That means procurement teams should pay closer attention to exit clauses, data mobility, egress economics, identity dependencies, software licensing terms, and operational portability. Multi-cloud should not be treated as a slogan or a badge of sophistication. A sloppy multi-cloud estate can be more expensive and less secure than a disciplined single-cloud strategy.
The question is where portability is worth paying for. Some workloads are so tied to a platform’s managed services that portability would destroy the business case. Others can be designed around containers, open databases, infrastructure as code, and vendor-neutral observability without sacrificing much. The art is knowing which is which before the renewal deadline arrives.
Windows-heavy shops face a particularly subtle version of the problem. Microsoft’s tooling can reduce operational friction dramatically, especially for identity, endpoint security, compliance, and device management. But every successful integration can also narrow the practical path away from Azure. That does not make the integration bad. It makes its long-term consequences worth documenting.

The Hyperscalers Will Sell Compliance as Confidence

Amazon and Microsoft are unlikely to treat a final designation as a simple defeat. Large platform companies have learned to turn regulatory compliance into a feature. Expect language about trust, transparency, European values, customer choice, sovereign cloud options, and continued investment.
Some of that will be fair. The hyperscalers have already built EU regions, compliance programs, encryption controls, data residency commitments, and sovereign-cloud offerings because customers demanded them. Their scale allows them to absorb regulatory costs that might crush smaller providers. A more regulated AWS or Azure may still be more attractive to many buyers than a smaller provider with fewer services and less mature tooling.
But compliance branding can obscure the underlying market question. If the same companies that dominate the market are also best positioned to satisfy the new rules, regulation may harden rather than weaken their advantage. The DMA’s success will depend on whether obligations create genuine room for competition or simply add a paperwork moat around incumbents.
This is one of the paradoxes of Big Tech regulation. The companies most capable of complying are often the companies regulators are trying to constrain. A giant can hire lawyers, policy teams, engineers, auditors, and lobbyists. A challenger may struggle to interpret the same rulebook while also trying to build a product.
That does not mean the EU should do nothing. It means regulators must measure outcomes rather than press releases. If customers still cannot move data affordably, if independent software vendors still face platform pressure, if licensing still distorts cloud choice, and if AI services become more tightly bundled into dominant ecosystems, then formal compliance will not be enough.

The Fight Will Be Over Remedies, Not Rhetoric

The preliminary finding is only one step. Amazon and Microsoft can respond, contest the analysis, and argue that designation is unnecessary, misapplied, or competitively harmful. A final decision would then determine whether AWS and Azure are formally added to the list of gatekeeper-controlled core platform services under the DMA.
The most consequential debate will be about what obligations mean in practice for cloud. Some DMA rules map more naturally to app stores and marketplaces than to infrastructure services. Applying them to cloud will require careful interpretation, especially where technical integration is both a source of customer value and a possible tool of lock-in.
If the Commission pushes too broadly, it risks turning cloud engineering into a compliance guessing game. If it pushes too narrowly, the designation becomes symbolic. The real test is whether Brussels can identify conduct that distorts competition without punishing the normal advantages of scale, reliability, and product integration.
That distinction matters because not every form of customer dependence is abusive. Enterprises depend on platforms because platforms reduce complexity. A bank may prefer Azure because its Microsoft estate already has identity and compliance patterns there. A retailer may prefer AWS because its engineers know the services and the performance is predictable. Competition law should not pretend that switching costs can be eliminated without also eliminating much of what makes cloud useful.
But dependence becomes a public concern when the provider can exploit it to foreclose rivals, impose unfair terms, or make adjacent markets less contestable. That is the line Brussels is trying to draw. The difficulty is that, in cloud, the line often runs through architecture diagrams rather than consumer-facing screens.

The Cloud Crackdown Gives Windows Shops a New Checklist

This proceeding will move slowly compared with product roadmaps, but it should still change the questions IT leaders ask now. The practical lesson is not to abandon hyperscale cloud. It is to stop treating cloud dependency as somebody else’s policy problem.

Organizations should inventory which workloads depend on vendor-specific managed services and which could realistically move with modest refactoring.
Procurement teams should model data egress, licensing, and migration costs before they become leverage points in renewal negotiations.
Windows-centric environments should document where Microsoft 365, Entra ID, Intune, Defender, Sentinel, GitHub, and Azure create operational coupling.
Developers should distinguish between productive platform-native choices and accidental lock-in created by convenience defaults.
Security teams should ensure that multi-cloud or hybrid strategies do not multiply identity, logging, and incident-response gaps.
Executives should treat regulatory scrutiny as a signal that cloud concentration is a strategic risk, not just a technical architecture choice.

The EU’s preliminary move against AWS and Azure is best understood as a bet that infrastructure platforms have become as gatekeeping as the consumer platforms regulators first targeted. That bet may prove messy, contested, and technically difficult to enforce, but it reflects a real shift in where digital power now lives. The next phase of cloud competition will not be decided only by who has the most regions, the best AI accelerators, or the deepest enterprise discounts. It will also be decided by whether customers, rivals, and regulators believe the cloud is still a market they can leave.

References

Primary source: Retail Gazette
Published: Fri, 26 Jun 2026 07:52:36 GMT

EU targets Amazon and Microsoft cloud dominance in 'Big Tech' crackdown - Retail Gazette

<div class="at-above-post addthis_tool" data-url="https://www.retailgazette.co.uk/blog/2026/06/eu-targets-amazon-and-microsoft-cloud-dominance-in-big-tech-crackdown/"></div>Amazon and Microsoft’s cloud computing businesses could be brought under tougher EU tech...

www.retailgazette.co.uk
Independent coverage: Computing UK
Published: Fri, 26 Jun 2026 07:51:14 GMT

AWS and Azure edge closer to EU 'gatekeeper' status

The EU is moving towards placing Amazon and Microsoft’s cloud computing businesses under its landmark digital competition law.

www.computing.co.uk
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
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
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu

Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: computerweekly.com

European Commission launches AWS and Microsoft-focused cloud competition probes | Computer Weekly

The European Commission has launched three investigations into how the continent's cloud market operates, with two focused specifically on Microsoft and Amazon Web Services

www.computerweekly.com
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
Related coverage: techradar.com

AWS brings ‘Sovereign’ cloud to Europe - you can pause your geopatriation plans, for now | TechRadar

As the Atlantic rift deepens, Europeans get better compliance and protections from AWS

www.techradar.com
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
Related coverage: lemonde.fr

Trump fires back at EU tech regulation

Donald Trump's administration is defending US tech giants against EU regulations. Brussels says it is 'determined to apply them.'

www.lemonde.fr

ChatGPT · Jun 26, 2026

The European Commission told Amazon and Microsoft on June 25, 2026, that Amazon Web Services and Microsoft Azure should be classified as Digital Markets Act gatekeepers in the European Union, after a seven-month investigation into whether their cloud platforms function as critical business gateways. The move is preliminary, not final, but it is already a turning point: Brussels is no longer treating cloud infrastructure as a neutral utility sitting beneath platform power. It is treating the cloud itself as platform power. For Windows shops, Azure tenants, software vendors, and administrators running hybrid estates, that distinction matters more than another round of abstract Big Tech antitrust theater.

Brussels Moves the DMA Below the App Store Layer

Until now, the Digital Markets Act has been understood mostly through consumer-facing fights: app stores, browsers, search, messaging, ads, and operating-system defaults. Those were visible markets where gatekeeping could be explained in the familiar language of user choice. You could point to a default browser prompt, an app-store fee, or an interoperability wall and make the case in a single screenshot.
Cloud is harder to see and much harder to regulate cleanly. AWS and Azure do not merely sit in front of consumers; they sit underneath applications, identity systems, databases, AI workloads, analytics pipelines, security tooling, and the public-sector services that increasingly behave like software companies. The gate is not always a login screen. Sometimes it is an API, a managed database format, an identity dependency, a data-egress bill, or an enterprise procurement commitment that quietly makes moving away feel irrational.
That is what makes the Commission’s preliminary finding so consequential. It is not just saying Amazon and Microsoft are large. It is saying that AWS and Azure may be important gateways between European businesses and their customers even though they reportedly do not meet the DMA’s normal quantitative thresholds for designation. In other words, Brussels is asserting that market structure can matter even when the scoreboard designed for consumer platforms does not capture the whole game.
That is an aggressive interpretation of the DMA, but not an illogical one. The cloud market has always been defined by a contradiction: customers buy it as flexible infrastructure, then discover that flexibility often declines as they adopt higher-level managed services. The more useful the platform becomes, the harder it can be to leave.

The Threshold Miss Is the Point, Not a Technicality

The detail that AWS and Azure do not meet the DMA’s quantitative thresholds could sound, at first, like a procedural weakness in the Commission’s case. It is actually the part that reveals the Commission’s strategy. The EU is arguing that cloud dominance cannot be measured with the same instruments used for consumer platforms because cloud power is mediated through enterprises, developers, and ecosystems rather than monthly consumer headcount alone.
That is the right debate to have, even if the final answer is contested. A cloud provider can be indispensable without having the kind of end-user relationship that makes sense in a social network or app store analysis. A bank’s customers may never know that a payment system, fraud model, document workflow, or mobile back end runs on Azure or AWS. Yet the infrastructure provider can still shape cost, resilience, interoperability, security posture, and competitive access for the businesses built on top of it.
The Commission reportedly emphasized revenue, operations, investments, user bases, AI tools, and partnerships. That combination is important because the cloud wars are no longer just about virtual machines and object storage. They are about vertically integrated stacks that run from silicon and data centers through model hosting, developer platforms, security services, productivity suites, and business applications.
Microsoft is the sharper case for WindowsForum readers because Azure is not merely a cloud brand. It is increasingly the connective tissue across Microsoft 365, Entra ID, Defender, GitHub, Power Platform, Dynamics, Windows Server, Windows 365, and Copilot-era AI services. Azure’s power is not only that customers deploy workloads there. It is that Microsoft can make Azure feel like the natural gravity well for almost every adjacent enterprise decision.
AWS, by contrast, is the archetype of cloud scale and service breadth. It built much of the market’s vocabulary and remains a benchmark for depth, reliability, and developer reach. But the EU’s theory appears less interested in who invented the market than in who can now steer it.

Azure’s Regulatory Problem Is Its Enterprise Superpower

Microsoft’s central enterprise advantage has always been integration. Administrators rarely buy one Microsoft product in isolation. They inherit or choose a stack in which identity, endpoint management, productivity, compliance, collaboration, security, and increasingly AI are designed to reinforce each other.
That integration is often genuinely useful. A Windows estate using Entra ID, Intune, Defender, Microsoft 365, and Azure policy tooling can achieve operational coherence that would be expensive and fragile to reproduce with a dozen independent vendors. For stretched IT departments, that coherence is not a conspiracy. It is a budget line, a staffing model, and a lower-friction way to survive the next audit.
The DMA problem is that the same coherence can look like foreclosure when viewed from the outside. If Azure services receive smoother identity integration, better commercial bundling, easier procurement, privileged telemetry access, or preferential placement inside Microsoft’s broader software estate, rivals may argue they are not competing against a cloud provider but against an operating environment. That is precisely the kind of platform leverage the DMA was built to scrutinize.
For Microsoft, the challenge is therefore subtler than a simple compliance checklist. The company must defend the benefits of integration while proving those benefits are not engineered to make alternatives impractical. That is a familiar antitrust burden for Microsoft, but the terrain has changed. The old Windows cases revolved around PCs and browsers. The new one revolves around identity, APIs, AI, cloud credits, data mobility, and managed services.
The most uncomfortable fact for Microsoft is that enterprise customers often like the very integration regulators distrust. Admins want fewer dashboards, fewer identity seams, fewer support runarounds, and fewer procurement fights. The Commission’s job is to ensure that convenience does not become coercion. Microsoft’s job is to show that its stack can remain convenient without becoming a one-way door.

Cloud Lock-In Is No Longer a Niche Architect’s Complaint

For years, cloud lock-in was treated as a concern for purists and consultants. The practical response from many businesses was blunt: every platform has trade-offs, migration is expensive, and the benefits of managed services outweigh theoretical portability. That was a defensible position when cloud adoption was mainly about elasticity and operational modernization.
It is less comfortable now. Cloud platforms increasingly define how organizations build software, store data, secure identities, train or host AI models, and observe systems. Once an application depends on a provider’s managed database, event system, secrets manager, identity controls, data warehouse, AI service, and logging platform, the word portable starts to do a lot of unpaid labor.
The Commission’s preliminary position gives regulatory weight to a complaint many engineers have made for years: lock-in is not a single abusive clause. It is an accumulation of small rational decisions. Each managed service saves time. Each proprietary integration reduces short-term complexity. Each reserved-capacity deal lowers this year’s bill. Then, five years later, the exit plan is a multi-quarter transformation program with board-level risk.
Data egress fees are only the most visible symbol of the problem. The deeper issue is architectural dependency. Even if a provider makes it cheaper to move bits out, moving systems out remains hard when applications depend on provider-specific behavior, IAM models, monitoring semantics, serverless runtimes, database extensions, and AI endpoints.
That is why the DMA’s likely obligations around interoperability and data portability could matter. If applied seriously, they could push the largest cloud providers toward more predictable interfaces, better export paths, and less punitive treatment of customers who use multiple clouds or third-party services. But if applied clumsily, they could also produce paperwork compliance while leaving the real switching costs untouched.

AI Turns Cloud Gatekeeping Into a Live Ammunition Issue

The cloud investigation lands at precisely the moment AI is making infrastructure dominance more valuable. Training, tuning, hosting, securing, and integrating AI models requires compute, storage, networking, data governance, developer tooling, and enterprise trust. The hyperscalers are not merely selling AI features; they are selling the operating environment in which AI will be built.
That changes the competitive stakes. A company choosing where to run AI workloads is often also choosing where its data pipelines live, how its developers authenticate, what governance tools compliance teams use, what model catalog is easiest to consume, and what vendor receives the next wave of budget. AI demand can therefore reinforce cloud incumbency rather than simply create a new market layered on top.
Microsoft’s OpenAI partnership, Copilot strategy, Azure AI services, GitHub developer reach, and Microsoft 365 distribution make this particularly sensitive. Azure is not just competing for generic compute; it is positioned as the enterprise AI substrate for organizations already inside Microsoft’s productivity and identity universe. That may be good product strategy. It is also exactly the kind of adjacent-market reinforcement regulators are now trained to examine.
AWS has its own version of this playbook, with custom silicon, Bedrock, SageMaker, marketplace relationships, and deep enterprise infrastructure credibility. The company’s argument will likely be that customers have abundant choice, that open-source models and multiple clouds remain available, and that heavy-handed DMA treatment could slow European access to advanced technology. That argument will resonate with some customers who fear regulation that makes cloud platforms slower, more fragmented, or more expensive.
But the Commission is unlikely to be moved by a simple innovation-defense narrative. Brussels increasingly sees AI, cloud, semiconductors, cybersecurity, and digital sovereignty as one strategic bundle. If cloud providers become the toll roads for AI adoption, then their contractual and technical terms become industrial policy by other means.

The Data Act Was Never Going to End This Fight

Amazon’s public pushback reportedly leaned on the EU Data Act, arguing that Europe already has comprehensive cloud regulation and that adding DMA obligations creates overlapping burdens. That is not a trivial complaint. Europe has a growing habit of layering ambitious digital rules until even sophisticated compliance teams need a map, a lawyer, and a stiff drink.
But the Data Act and DMA answer different questions. The Data Act is more directly concerned with access to and use of data, including measures intended to ease switching between data-processing services. The DMA is concerned with gatekeeper power in digital markets. One asks whether users can move and use data fairly. The other asks whether a platform’s structural position lets it shape competition.
That distinction matters because cloud lock-in is not reducible to data mobility. A customer can theoretically export data and still be stuck because its applications, operations, security processes, and procurement model are welded to provider-specific services. The Commission’s cloud theory appears to be that the largest providers can influence not just where data sits, but which businesses can efficiently reach customers, scale products, and participate in the next layer of digital markets.
Amazon is right that regulatory overlap can damage competitiveness if agencies treat compliance as an end in itself. But the overlap argument is also self-serving if it implies that one cloud-switching law should immunize hyperscalers from broader platform scrutiny. The real question is whether the EU can coordinate its rules well enough that compliance produces actual market openness rather than duplicative reporting.
That is the danger for everyone. A bad regulatory regime would create friction without freedom. A good one would make it easier for customers to mix providers, negotiate fairly, and adopt best-of-breed tools without discovering that the hyperscaler’s ecosystem punishes them for disloyalty.

Enterprise IT Will Feel This First in Contracts, Not Consoles

No administrator should expect the Azure portal or AWS Management Console to look different tomorrow because of the Commission’s preliminary finding. The immediate action is legal and procedural: Amazon and Microsoft get a chance to respond, and a final decision would trigger a compliance clock. If confirmed, the companies would have six months to meet DMA obligations for the designated services.
The first visible changes would likely appear in contracts, licensing language, partner terms, data-transfer commitments, interoperability documentation, and the way providers describe customer choice. Enterprise procurement teams may see new clauses or revised assurances before engineers see new buttons. Compliance tends to arrive first as PDFs and only later as product behavior.
For Microsoft customers, the places to watch are the seams between Azure and the rest of the Microsoft estate. Identity integration, security telemetry, licensing incentives, Azure consumption commitments, marketplace rules, and the bundling of cloud credits with broader agreements could all become areas of scrutiny. The issue is not that any one of these is automatically unlawful. The issue is whether their combined effect disadvantages rivals or makes realistic multi-cloud operation harder than it needs to be.
For AWS customers, attention should fall on egress, service interoperability, marketplace conditions, partner access, and the portability of applications built around high-level managed services. AWS has long argued that customers choose it because of capability and reliability, not coercion. The DMA process will test how well that claim holds when regulators examine not only customer choice at the moment of adoption, but customer freedom after years of dependence.
Smaller cloud providers and European infrastructure firms will welcome the pressure, but they should be careful what they wish for. Regulatory relief does not automatically create competitive parity. AWS and Azure have scale, engineering depth, global reach, security certifications, procurement familiarity, and enormous ecosystems. DMA designation may lower some barriers, but it will not manufacture an alternative hyperscaler overnight.

The Sovereignty Debate Finally Meets the Admin Console

Europe’s cloud-sovereignty debate has often sounded abstract, heavy with policy language about strategic autonomy and digital resilience. Administrators experience it more concretely. They need to know where data lives, who can access it, which jurisdiction applies, how outages propagate, whether support can cross borders, and whether a vendor’s road map can be trusted under political pressure.
The AWS and Azure DMA case intersects with sovereignty but is not identical to it. A gatekeeper designation would not, by itself, make European cloud providers more capable or guarantee that European data never comes under foreign legal pressure. It would also not make U.S. hyperscalers disappear from European infrastructure. Many European businesses depend on them too deeply for that fantasy to be plausible.
What it could do is force more disciplined behavior from the dominant platforms. Interoperability obligations could make hybrid and multi-cloud architectures less punishing. Data-portability rules could strengthen exit strategies. Limits on self-preferencing could give independent software vendors and competing cloud services a fairer shot inside ecosystems that increasingly function as marketplaces for enterprise IT.
This is where Windows administrators should resist the temptation to see the story as Brussels versus Redmond. The practical question is not whether Microsoft is good or bad, or whether AWS deserves punishment for being successful. The question is whether customers retain enough leverage once their infrastructure, identity, security, developer tooling, and AI investments concentrate inside a single provider’s universe.
That question has an uncomfortable answer in many organizations. The cloud made infrastructure easier to consume, but it did not eliminate dependency. It changed the shape of dependency from hardware refresh cycles and data-center leases to APIs, managed services, reserved spend, identity graphs, and platform-specific skills.

Microsoft Has Seen This Movie, But the Ending Is Not Prewritten

There is an obvious historical echo here. Microsoft spent decades learning that platform control attracts regulators once the platform becomes the route through which others reach users. Windows was the original strategic choke point. The browser became the symbol. Office, identity, and enterprise licensing became the durable machinery.
Azure is different because the customer relationship is more complex and the technical stack is vastly deeper. Regulators cannot simply demand a ballot screen and declare victory. Cloud competition lives in architectures, incentives, APIs, and ecosystems. The remedies will be harder to define and easier to game.
Microsoft also has a stronger customer-benefit argument than it did in some earlier platform battles. Azure integration with Microsoft 365, Entra ID, Defender, GitHub, and Windows management tools solves real problems. In security especially, unified telemetry and identity-aware policy can be the difference between a manageable environment and a mess of disconnected alerts.
But that strength cuts both ways. If the best security posture, the cleanest identity model, the easiest AI integration, and the most attractive licensing path all point back to Azure, regulators will ask whether choice is meaningful or ceremonial. Microsoft can answer that question, but it will need more than slogans about customer obsession and innovation.
The company’s best path is not to deny the gravitational pull of its stack. Everyone can feel it. The better argument is to prove that integration and openness are not mutually exclusive: that Azure can be first-class inside Microsoft’s ecosystem without making rivals second-class by design.

The Cloud Market Is Being Regulated After the Lock-In Already Happened

One reason the Commission’s move feels late is that cloud dependency is already baked into enterprise architecture. Many organizations made foundational choices years ago, often during migration waves accelerated by pandemic-era remote work, data-center exits, security modernization, and AI experimentation. Those decisions were not irrational. They were made under pressure, with the information available at the time.
Regulators are now arriving after the platforms have become operating environments. That does not make intervention pointless, but it does limit what can be achieved quickly. You cannot undo a decade of architectural decisions with a designation notice.
The realistic near-term effect is bargaining power. If AWS and Azure know that certain practices could draw DMA scrutiny, they may soften the edges of lock-in, clarify portability commitments, and adjust terms that look too obviously exclusionary. Customers may gain more leverage in negotiations, especially large European enterprises and public-sector bodies that can point to the Commission’s position when pushing for contractual escape hatches.
The longer-term effect could be architectural hygiene. If interoperability becomes a regulated expectation rather than a nice-to-have, vendors and customers may both invest more seriously in open standards, abstraction layers, container portability, identity federation, and data-export discipline. That will not make multi-cloud easy. It may make single-vendor dependency more visible and more consciously chosen.
There is also a risk that the biggest customers benefit most. Large enterprises have legal teams, procurement leverage, and architecture groups capable of using regulatory changes. Smaller businesses may receive standardized compliance promises without the resources to test them. A DMA cloud regime that helps only the largest buyers would be an incomplete victory.

The DMA’s Cloud Test Will Be Measured in Boring Details

The Commission’s preliminary finding is dramatic as policy, but its success will be measured in dull implementation details. That is usually where platform regulation either becomes real or dissolves into theater. The cloud industry is too technical, too contractual, and too economically complex for symbolic compliance to matter much.
If the final designation happens, the most important questions will be practical. Can customers move workloads and data without punitive costs or artificial friction? Can third-party tools integrate with core platform functions on fair terms? Can cloud marketplaces operate without hidden preference for the provider’s own services? Can identity, security, monitoring, and AI services interoperate without requiring customers to accept a degraded experience?
The answer will not be binary. AWS and Azure already support many open technologies, and customers already run multi-cloud and hybrid environments. The problem is that “possible” and “practical” are not the same thing. Regulation that celebrates theoretical portability while ignoring cost, risk, and operational complexity will not change customer behavior.
This is why IT professionals should watch the remedies more closely than the designation itself. Gatekeeper status is a door. The obligations behind it are the room. If the Commission focuses on measurable customer freedoms, the case could matter. If it settles for compliance theater, hyperscalers will absorb the paperwork and keep moving.

The Real Signal for Windows Shops Is Leverage

For Windows-heavy organizations, the reflexive response may be to treat this as distant EU policy. That would be a mistake. European regulation has a way of reshaping global product decisions, especially when it targets platform architecture rather than local paperwork. Microsoft and Amazon may implement some changes regionally, but enterprise cloud products do not like fragmentation. A rule born in Brussels can become a design assumption everywhere.
This does not mean administrators should panic or begin rewriting cloud strategies. It does mean they should revisit assumptions that were made when the cloud was framed primarily as an efficiency play. The strategic question is no longer simply “which provider has the best service?” It is also “how much future negotiation power are we giving away?”
Azure customers should map dependencies across identity, data, security, AI, and licensing. AWS customers should do the same across managed services, databases, messaging, observability, and marketplace dependencies. The point is not to avoid managed services; that would be a costly overcorrection. The point is to know where the exits are before a regulator, auditor, outage, acquisition, or price change makes those exits urgent.
The smartest organizations will use this moment to improve cloud governance rather than posture as purists. They will distinguish between dependencies that are worth it and dependencies that are accidental. They will ask vendors for portability commitments in writing. They will test backup and export paths before they need them. They will stop pretending that an architecture diagram with two cloud logos is the same as a credible multi-cloud strategy.

What the Gatekeeper Notice Should Push Every Azure and AWS Customer to Do Next

The Commission’s preliminary finding is not a final verdict, but it is a useful forcing function. It turns cloud concentration from a background concern into a board-level governance issue, and it gives IT leaders a fresh reason to document risks that may have been obvious to engineers for years.

Organizations should identify which workloads depend on provider-specific services that would be expensive or slow to replace.
Procurement teams should ask for clearer language on data portability, egress costs, interoperability, and termination assistance.
Security teams should examine whether their controls assume one cloud provider’s identity and telemetry stack too completely.
Developers should distinguish between managed services chosen for real business value and managed services adopted because they were simply the default.
IT leaders should treat AI cloud commitments as long-term platform bets, not short-term feature trials.
European customers should watch the final Commission decision closely because any confirmed designation would start a six-month compliance window for AWS and Azure.

The EU’s preliminary move against AWS and Azure is best understood as a warning that infrastructure platforms have become too important to regulate only after their power becomes visible to consumers. Whether Brussels can translate that insight into workable cloud rules is still uncertain, and both Amazon and Microsoft will argue hard that customers benefit from scale, integration, and rapid innovation. But the direction of travel is clear: the cloud is no longer just where platform battles are hosted. It is now one of the platforms being fought over, and the next phase of enterprise IT will be shaped by how much freedom customers can preserve while still using the ecosystems they cannot easily live without.

References

Primary source: 富途牛牛
Published: Fri, 26 Jun 2026 08:38:03 GMT

Document
Independent coverage: the420.in
Published: 2026-06-26T08:30:41.928501

Amazon And Microsoft Face New EU Rules As Cloud Services Tagged As Gatekeepers - The420.in

EU regulators issued preliminary findings that AWS and Microsoft Azure should be DMA gatekeepers, despite not meeting standard thresholds.

the420.in
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: itif.org

EU’s Designation of AWS and Azure as Core Platform Services Escalates Weaponization of Digital Markets Act, Says ITIF | Press Releases | Jun 25, 2026 | ITIF

The European Commission is stretching the DMA to target cloud infrastructure, raising the stakes for U.S.-EU tech tensions.

itif.org
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
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu

Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
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
Related coverage: europapress.es

Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio

La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...

www.europapress.es
Related coverage: euronews.com

Brussels tightens rules on US cloud providers as it pushes for tech sovereignty | Euronews

The European Commission has decided that Microsoft Azure and Amazon Web Services should face strict rules to improve cloud competition. The move risks angering Washington as Brussels pushes the European tech sovereignty agenda.

www.euronews.com
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
Related coverage: ec.europa.eu

IP 25 2717 EN

PDF document

ec.europa.eu
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

ChatGPT · Jun 26, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that AWS and Azure should be treated as Digital Markets Act gatekeepers in the European Union, a preliminary finding that would pull the two dominant cloud platforms into Brussels’ toughest digital competition regime. The move is not final, but it is already a warning shot. Europe is no longer treating cloud infrastructure as a neutral utility layer beneath the internet economy. It is treating cloud as the place where market power now lives.

Brussels Moves the DMA Below the App Layer

The Digital Markets Act was sold to the public through familiar consumer battles: app stores, browsers, search engines, messaging services, advertising platforms, and the operating systems that shape daily digital life. That made political sense. The average voter understands why Apple’s App Store rules or Google’s search defaults might matter.
Cloud computing is different. It is less visible, more technical, and harder to turn into a clean sound bite. Yet the Commission’s preliminary view that Amazon Web Services and Microsoft Azure should be designated as gatekeepers may be one of the DMA’s most consequential expansions, because it shifts the law from the storefront to the factory floor.
AWS and Azure are not merely places to rent servers. They are sprawling ecosystems of compute, storage, databases, analytics, identity services, developer tooling, AI services, security products, and managed infrastructure that often become the operating environment for entire companies. Once a business builds deeply around one of these stacks, leaving is not like cancelling a subscription. It is closer to moving a city while keeping the lights on.
That is why the Commission’s finding matters even though it remains preliminary. Brussels is arguing that cloud platforms can function as gateways between businesses and their customers, even when those platforms sit far below the user interface. The gate is not always an app store button. Sometimes it is the database, authentication layer, storage bucket, region policy, API dependency, or managed Kubernetes configuration that keeps an enterprise locked in place.

The Thresholds Were Never the Whole Law

The striking detail in the Commission’s case is that AWS and Azure reportedly do not meet the DMA’s usual quantitative thresholds for designation. Under the DMA, those thresholds are meant to identify companies with major economic weight, large numbers of users, and durable market positions. They are a shortcut, not the whole test.
By proceeding anyway, the Commission is leaning on the DMA’s broader logic: a service can be a gatekeeper if it has become an important route through which businesses reach customers and markets. That interpretation matters because cloud infrastructure does not behave like a consumer social network. It may not have tens of millions of monthly “end users” in the ordinary sense, but it can still shape what thousands of companies can build, deploy, secure, and scale.
This is the regulatory equivalent of looking past the front door and asking who owns the roads. A cloud provider with enough scale can determine the economics of data transfer, the design of interoperability, the availability of sovereign regions, the pace of AI deployment, and the practical cost of moving elsewhere. Even when customers are technically free to leave, the architecture may tell a different story.
Amazon and Microsoft will have the opportunity to respond before any final decision. That process matters, because a preliminary finding is not a conviction. But the direction of travel is unmistakable: the Commission is testing whether the DMA can discipline infrastructure power, not just consumer platform power.

Cloud Lock-In Is the Quiet Competition Problem

The cloud market has always had a contradiction at its center. It promises flexibility, elasticity, and abstraction from physical infrastructure, yet it can also produce some of the stickiest dependencies in modern IT. The more useful a cloud platform becomes, the harder it can be to leave.
Basic compute workloads can often be moved, painfully but plausibly. The problem begins when a company builds around provider-specific managed services. A database migration is not just a file copy. An identity migration is not just a configuration change. A shift from one cloud’s event bus, serverless runtime, monitoring stack, security model, or AI service to another can involve months of refactoring and risk.
This is where Brussels’ competition concerns become concrete. Switching costs are not merely financial. They include downtime risk, compliance revalidation, retraining, integration rewrites, procurement disruption, and the fear that a migration will break systems that quietly depend on years of accumulated platform assumptions.
The largest providers also compound this advantage through scale. AWS and Azure can invest heavily in new regions, custom silicon, AI infrastructure, security tooling, and enterprise sales capacity. Smaller providers can compete on price, locality, sustainability, privacy, or specialization, but they struggle to match the sheer gravitational pull of the hyperscalers.
None of this means AWS or Azure are bad products. Their success is partly the result of genuine technical execution, reliability, and breadth. But competition law is often most interested in the moment when excellence hardens into dependency, and dependency becomes leverage.

Microsoft’s Cloud Problem Is Bigger Than Azure

For WindowsForum readers, Microsoft’s position deserves special attention because Azure is not an isolated business line. It sits inside a broader Microsoft enterprise universe that includes Windows Server, Active Directory, Entra ID, Microsoft 365, Defender, Intune, GitHub, Visual Studio, Power Platform, SQL Server, Dynamics, and the company’s fast-expanding AI stack.
That integration is a commercial superpower. It is also the reason regulators keep circling Microsoft’s cloud practices. A customer that standardizes on Microsoft identity, productivity, endpoint management, collaboration, security, and development tooling may find Azure to be the path of least resistance, even when another cloud might be attractive for particular workloads.
The Commission’s preliminary designation does not appear to be a narrow Windows issue. But Windows administrators understand the mechanics better than most. Identity is infrastructure. Directory services are infrastructure. Device management is infrastructure. Once those control planes are woven into cloud services, the boundary between operating system, productivity suite, security stack, and cloud platform becomes much harder to police.
That is the strategic context Microsoft now faces in Europe. Azure is not just competing against AWS, Google Cloud, Oracle, OVHcloud, and others on infrastructure features. It is also being judged as part of a broader enterprise architecture in which Microsoft can bundle convenience, familiarity, and licensing gravity into a powerful migration funnel.
For Microsoft customers, the question is not whether Azure remains a capable platform. It does. The question is whether the regulatory environment will force Microsoft to make its cloud easier to mix, match, audit, and exit.

AWS Has Scale Without the Desktop Shadow

Amazon’s challenge is different. AWS does not carry Microsoft’s Windows and Office legacy, but it remains the largest cloud provider and the benchmark against which much of the industry measures itself. Its ecosystem has depth, maturity, and a huge catalog of services that can pull customers into increasingly AWS-specific architectures.
That makes AWS a cleaner test of the Commission’s cloud theory. If Microsoft’s case can be framed around ecosystem leverage, AWS’s case is about infrastructure scale itself. The Commission is effectively saying that cloud dominance can be gatekeeping even without a desktop operating system, productivity suite, or consumer platform attached.
AWS will likely argue that the cloud market remains competitive, fast-moving, and full of credible alternatives. That is not a frivolous argument. Customers can and do run multi-cloud strategies, negotiate enterprise agreements, use open-source platforms, and shift some workloads among providers. Cloud is not a monopoly in the old telephone-network sense.
But regulators are not only asking whether alternatives exist. They are asking whether alternatives are practically reachable once a customer has built deeply around a hyperscaler. In enterprise IT, “you can migrate if you want to” is a much weaker claim when the migration requires budget, engineering capacity, risk tolerance, and executive sponsorship that few organizations can spare.

The DMA Enters the Server Room

If the designation becomes final, Amazon and Microsoft would have six months to comply with DMA obligations for the relevant cloud services. The exact practical implications will depend on the final decision and how the Commission applies the law to infrastructure services. Still, the broad direction is easy to read: interoperability, fairness, portability, and limits on self-preferencing are likely to become the vocabulary of cloud regulation.
For consumer platforms, DMA compliance has produced changes around app distribution, default settings, data access, and service tying. Cloud will not map neatly onto those categories. The hard questions will be more technical and more enterprise-specific.
What does meaningful interoperability look like between managed cloud databases? How portable should logs, telemetry, identity policies, encryption configurations, and machine images be? When does discounting become loyalty pressure? When does a cloud provider’s own managed service receive an unfair advantage over a rival service running on the same platform?
These are not academic questions for administrators. They affect architecture diagrams, procurement language, backup strategies, vendor risk assessments, and disaster recovery planning. A regulation that sounds distant in Brussels may eventually show up as a new contract clause, a new export format, a new compliance dashboard, or a new support matrix.
The likely near-term effect is not that AWS and Azure suddenly become interchangeable. They will not. The more realistic outcome is pressure at the margins: fewer artificial barriers, clearer documentation, better data portability, less punitive egress economics, and more scrutiny of practices that make leaving harder than arriving.

Europe’s Cloud Sovereignty Push Is the Wider Frame

The DMA action lands inside a larger European project: reducing dependence on non-European technology infrastructure without cutting Europe off from the global technology market. That is a delicate balance, and Brussels has not always articulated it cleanly. Europe wants competition, sovereignty, security, investment, and innovation, but those goals do not always point in the same direction.
Cloud is where the tension becomes unavoidable. European governments and businesses rely heavily on American hyperscalers because they are capable, available, and deeply integrated into modern software development. At the same time, public-sector workloads, regulated data, and critical infrastructure raise uncomfortable questions about legal jurisdiction, geopolitical risk, and long-term dependence.
The Commission’s cloud investigations therefore have two audiences. One is the competition-law audience, focused on fairness, contestability, and lock-in. The other is the sovereignty audience, focused on whether Europe can build and sustain strategic digital capacity without becoming a permanent tenant in someone else’s data centers.
Those audiences overlap, but they are not identical. A more competitive cloud market does not automatically create European cloud champions. A sovereignty agenda does not automatically produce better services. The danger for Europe is that it treats regulation as a substitute for industrial execution.
Still, the DMA gives Brussels a lever it already knows how to pull. It cannot instantly create another AWS. It can, however, make the existing giants justify the ways their platforms make customers dependent.

The Hyperscalers Will Fight on Definition

Amazon and Microsoft’s strongest argument will probably center on whether cloud infrastructure fits the DMA’s gatekeeper concept as cleanly as the Commission suggests. They can argue that business customers are sophisticated, contracts are negotiated, workloads are portable at the infrastructure layer, and competition is fierce among hyperscalers, regional providers, private cloud vendors, and open-source stacks.
There is truth in that defense. Enterprise customers are not helpless consumers being nudged into a default browser. Many large organizations use multiple clouds, maintain internal platform teams, and negotiate aggressively. Some deliberately avoid overreliance on provider-specific services.
But that argument weakens when applied to the broader market. Many businesses do not have the engineering capacity to sustain true multi-cloud portability. Even large enterprises often discover that “multi-cloud” means different workloads on different clouds, not seamless mobility between them. The architecture may be diversified, but the individual systems remain sticky.
The fight will therefore turn on practical power rather than theoretical choice. The Commission will want to show that AWS and Azure occupy a durable position as essential intermediaries. The companies will want to show that cloud is dynamic, contestable, and unlike the consumer platforms that inspired the DMA.
That debate will define the next phase of European cloud policy. If Brussels wins the argument, cloud infrastructure becomes a first-class target for platform regulation. If the companies successfully narrow the definition, the DMA remains more focused on services closer to consumers.

Administrators Should Read This as a Procurement Story

For sysadmins and IT leaders, the temptation is to treat EU competition policy as background noise. That would be a mistake. The Commission may speak in legal language, but the operational stakes are familiar: portability, exit planning, identity dependency, data governance, and vendor concentration.
The smartest organizations already behave as if regulators are asking the right questions. They know which workloads are portable and which are not. They know where provider-specific services create business value and where they create avoidable lock-in. They know whether their backup strategy is independent of their cloud provider or merely another feature inside the same blast radius.
This does not mean every company should flee AWS or Azure. In many cases, that would be irrational. The hyperscalers provide security capabilities, regional reach, compliance tooling, and operational reliability that would be difficult to reproduce elsewhere.
But it does mean cloud buyers should stop pretending that convenience is neutral. Every managed service is also a dependency. Every identity integration is also a control point. Every volume discount may shape future architecture more than the architecture team wants to admit.
The DMA proceeding is a reminder that procurement is architecture by other means. The contracts signed today determine the migrations that will be possible tomorrow.

Developers Will Feel This Through APIs, Not Press Releases

Developers are unlikely to experience a final gatekeeper designation as a banner in the Azure portal or AWS console. They will feel it through the slow reshaping of platform behavior. Compliance, if it comes, will likely arrive as changes to APIs, export tools, documentation, data movement options, partner access, and service terms.
That matters because developer convenience is one of the main engines of lock-in. A managed queue, serverless function, proprietary database feature, observability tool, or AI model endpoint can save enormous time. It can also make an application less portable with every sprint.
The best engineering teams do not respond to that reality with dogma. They do not reject every cloud-native service in the name of purity. They make explicit trade-offs. They decide where lock-in is worth it because the product benefit is real, and where abstraction is worth the extra effort because future flexibility matters more.
Regulatory pressure may help by making some portability features less heroic. But no law can turn a deeply provider-specific architecture into a neutral one after the fact. That remains an engineering choice, made repeatedly in tickets, templates, modules, and deployment pipelines.
The practical developer takeaway is simple: write down the exit cost before the exit is needed. If the answer is “we would rewrite half the platform,” then the organization should at least know that it has made a strategic bet, not merely adopted a service.

The Competition Fight Is Also an AI Fight

Cloud regulation in 2026 cannot be separated from artificial intelligence. The most important AI systems require massive compute, specialized accelerators, high-speed networking, data pipelines, model hosting, security controls, and developer platforms. In other words, they require exactly the kind of cloud infrastructure controlled by the hyperscalers.
Microsoft’s Azure has become central to its AI strategy, from enterprise Copilot services to model hosting and developer tools. AWS is pushing its own AI infrastructure, chips, model services, and enterprise AI products. The cloud platforms are not passive hosts for AI; they are becoming the distribution layer for AI capabilities.
That raises the stakes of the DMA cloud case. If cloud platforms become the default channels through which companies access advanced AI, then cloud gatekeeping can become AI gatekeeping. A business that depends on one cloud for models, data storage, identity, security, and deployment may find its AI roadmap tied to that provider’s commercial incentives.
European regulators understand this. The Commission’s language around secure, sustainable, and interoperable cloud services is not just about yesterday’s virtual machines. It is about the infrastructure stack for the next decade of software.
This is why the case should not be dismissed as an old competition-law reflex applied to a new market. Brussels is trying to intervene before the AI infrastructure layer becomes as difficult to unwind as the mobile platform layer was by the time regulators fully caught up.

The Risk Is Regulation That Solves Yesterday’s Cloud

There is a real danger in this approach. Cloud markets move quickly, and rules written around static concepts of gatekeeping can miss the ways technical competition actually works. If compliance becomes too rigid, it could burden the very interoperability efforts it hopes to encourage.
There is also a risk that European policy becomes too fixated on American hyperscalers as symbols. AWS and Azure dominate for reasons that include capital investment, technical execution, global reach, and customer trust. Europe cannot regulate its way into having equivalent platforms without also solving investment, energy, permitting, talent, and procurement problems.
The Commission’s challenge is to distinguish between harmful lock-in and legitimate product integration. A managed service that works better inside its native cloud is not automatically anti-competitive. A discount for committed spend is not automatically coercive. A proprietary feature is not automatically abusive.
But the reverse is also true. Technical complexity should not become a shield for market power. If a provider designs systems, contracts, or economics in ways that make rivals less viable and customers less free, regulators are right to look closely.
The best version of the DMA cloud case would push the hyperscalers toward cleaner exits, fairer interfaces, and more honest interoperability claims. The worst version would produce paperwork, symbolic concessions, and a compliance theater that changes little about the actual structure of dependency.

The Six-Month Clock Would Be Only the Beginning

If the Commission confirms its preliminary view, AWS and Azure would face a six-month compliance window. That sounds short, but the real timeline would be longer. Designation would trigger obligations, negotiations, technical interpretations, possible disputes, and likely legal challenges.
The hyperscalers have the resources to comply and contest at the same time. They can change product terms while arguing over scope. They can offer portability improvements while resisting interpretations they see as overbroad. They can satisfy some demands quickly and litigate others slowly.
Customers should not expect an overnight transformation. Cloud exit fees will not vanish from architecture. Managed services will not become magically portable. Procurement teams will not suddenly gain perfect leverage over trillion-dollar vendors.
But regulatory pressure can still alter behavior before formal enforcement bites. Large platforms often adjust roadmaps, documentation, partner programs, and commercial terms when they see where the regulator is heading. The preliminary finding itself may become a market signal.
That signal is especially useful for smaller cloud providers and European alternatives. They can now frame interoperability and sovereignty not as niche preferences, but as regulatory priorities. Whether they can convert that into meaningful market share is another question.

The Fine Print Now Belongs in the Architecture Review

The immediate lesson for WindowsForum’s audience is not to panic, but to inventory. Organizations running major workloads on AWS or Azure should understand exactly where they are dependent on provider-specific services, pricing structures, and control planes. The Commission’s action is a reminder that lock-in is not an abstract policy concern; it is an operational fact that can be measured.

Organizations should identify which workloads could realistically move to another provider within 90 days and which would require a full application redesign.
Cloud teams should document where managed services create deliberate business value and where they create accidental dependency.
Procurement teams should review egress costs, committed-spend agreements, support terms, and licensing structures as part of technical risk management.
Security teams should test whether backup, logging, identity, and incident response processes remain usable if the primary cloud account or region is impaired.
Developers should treat portability as an architectural requirement when the business value of provider-specific features does not clearly outweigh future exit costs.
Executives should read the Commission’s preliminary finding as a sign that cloud concentration has become a board-level risk, not just an infrastructure preference.

The Commission’s preliminary move against AWS and Azure is not the end of cloud as we know it, and it is not a guarantee that Europe will produce a more competitive infrastructure market. It is, however, a clear sign that the political patience for invisible lock-in is running out. The next cloud era will still be built on scale, automation, and managed services, but the winners may have to prove that customers are staying because the platform is better — not because leaving has become too expensive to contemplate.

References

Primary source: table.media
Published: Fri, 26 Jun 2026 08:34:11 GMT

DMA: Commission considers AWS and Azure to be gatekeepers • Table.Briefings

Although the two cloud services offered by Amazon and Microsoft do not meet the quantitative thresholds, the Commission cites a list of qualitative arguments to justify its decision.

table.media
Independent coverage: Windows Report
Published: 2026-06-26T07:30:41.936995

Microsoft Azure and AWS Face EU Gatekeeper Designation Under DMA

Microsoft Azure and AWS may soon be designated as gatekeepers under the EU's Digital Markets Act, with six months to comply if approved.

windowsreport.com
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: itif.org

EU’s Designation of AWS and Azure as Core Platform Services Escalates Weaponization of Digital Markets Act, Says ITIF | Press Releases | Jun 25, 2026 | ITIF

The European Commission is stretching the DMA to target cloud infrastructure, raising the stakes for U.S.-EU tech tensions.

itif.org
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com

Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
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
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
Related coverage: euronews.com

Brussels tightens rules on US cloud providers as it pushes for tech sovereignty | Euronews

The European Commission has decided that Microsoft Azure and Amazon Web Services should face strict rules to improve cloud competition. The move risks angering Washington as Brussels pushes the European tech sovereignty agenda.

www.euronews.com
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
Related coverage: ec.europa.eu

IP 25 2717 EN

PDF document

ec.europa.eu

ChatGPT · Jun 26, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that it preliminarily believes Amazon Web Services and Microsoft Azure should be designated as Digital Markets Act gatekeepers for cloud computing services in the European Union. The finding is not a final ruling, but it is a clear signal that Brussels now sees cloud infrastructure as the next platform layer where competition policy must bite. For Windows administrators, Azure architects, developers, and procurement teams, this is not an abstract fight over European legal terminology. It is a preview of how the operating environment for enterprise cloud could change just as AI makes cloud dependency deeper, stickier, and more expensive to unwind.

Brussels Moves the DMA From the App Store to the Data Center

The Digital Markets Act began life in the public imagination as a law about phones, app stores, search engines, social networks, browsers, ads, and marketplaces. It was the European Union’s answer to the idea that a handful of digital intermediaries had become too important to discipline through case-by-case antitrust enforcement alone. Instead of waiting years to prove one abuse at a time, the DMA imposes up-front obligations on companies designated as gatekeepers for specific core platform services.
Cloud computing was always in the DMA’s orbit, but until now it had not occupied the same spotlight as iOS, Android, Google Search, Amazon Marketplace, or Meta’s social networks. That made sense politically: consumer platforms generate more visible anger. Everyone has a view about app store fees, default browsers, or whether an operating system nags them into using a preferred service.
The Commission’s preliminary view on AWS and Azure changes the center of gravity. It says, in effect, that the infrastructure layer underneath modern software has become just as gatekeeping as the consumer-facing layer above it. If a business cannot realistically reach customers, run AI workloads, store data, operate applications, or scale globally without depending on one of a few hyperscale clouds, then the data center has become a platform in the regulatory sense.
That is the real news here. Brussels is not merely adding two more services to a compliance spreadsheet. It is arguing that cloud has matured from commodity infrastructure into a control point for the digital economy.

Azure’s Regulatory Problem Is Also Microsoft’s Strategic Success

Microsoft should not be surprised to find Azure in this position. The company has spent the past decade turning Azure from a defensive response to AWS into the connective tissue of its entire enterprise stack. Windows Server, Active Directory, Entra ID, Microsoft 365, GitHub, Dynamics, Power Platform, Security Copilot, OpenAI integrations, developer tooling, endpoint management, and hybrid infrastructure all increasingly orbit Azure.
That strategy has been commercially brilliant. It has also made Azure more than a place to rent compute. For many organizations, Azure is identity, security, monitoring, analytics, AI, compliance posture, developer workflow, and procurement convenience rolled into one account relationship. Once a company is deep inside that model, moving “a workload” is not like switching a hosting provider in 2006. It can mean rethinking authentication, data governance, observability, licensing, automation, backups, security policy, and staff skills.
This is why the Commission’s emphasis on lock-in and switching costs matters. Hyperscale cloud competition does exist, and it is intense at the level of new features, price cuts, chip announcements, managed databases, and AI services. But competition for a new workload is not the same as competition for a mature estate that has already accumulated years of scripts, dependencies, reserved capacity, training, and data gravity.
Microsoft’s public response points toward Google Cloud and Gemini, arguing that excluding Google from the same treatment risks skewing the market. That is not a frivolous argument. Google is a serious cloud and AI competitor, and its model ecosystem has become a strategic procurement factor. But the Commission’s immediate case appears to rest on AWS and Azure’s position as the first and second largest EU cloud providers, their scale of investment, their entrenched user bases, and the way cloud choices increasingly pull AI choices along with them.
For Microsoft, the uncomfortable part is that Azure’s regulatory exposure flows directly from Azure’s enterprise appeal. The more Azure becomes the default operating plane for business computing, the easier it is for regulators to call it a gateway.

AWS Faces the Same Charge Without the Windows Halo

Amazon’s problem is different but no less serious. AWS does not have Windows’ historical enterprise monopoly behind it, nor does it control a desktop operating system or office productivity suite. Its power comes from being the original hyperscale cloud giant: breadth, maturity, operational credibility, and a sprawling catalog of services that can make alternative providers look incomplete by comparison.
AWS has long argued that cloud remains highly competitive because customers can choose among multiple providers, build on open technologies, use managed or unmanaged services, and negotiate aggressively. There is truth in that. The cloud market is not a simple monopoly story, and any serious enterprise buyer can point to genuine rivalry among AWS, Azure, Google Cloud, Oracle, IBM, regional providers, colocation firms, and specialized infrastructure companies.
But the DMA is built around a different question. It is less interested in whether competitors exist somewhere in the market than in whether a specific service acts as an unavoidable gateway between businesses and users. The Commission’s preliminary view suggests that AWS’s size, service depth, partner ecosystem, and operational reach create a form of dependency even without a desktop operating system attached.
Amazon’s response is predictably hostile. The company says Europe already has cloud regulation through the Data Act and that layering DMA obligations on top risks chilling investment and innovation. That argument will land with some CIOs, especially those already worried that Europe’s regulatory appetite can outpace its ability to produce native technology champions.
Still, AWS has a harder story to tell if the Commission frames the case around cloud portability and procurement fairness rather than punishment for success. The more AWS argues that customers have many choices, the more regulators will ask why leaving AWS is so technically, financially, and organizationally painful once those choices have been made.

The AI Boom Makes Cloud Lock-In More Than a Billing Problem

The timing is not accidental. Cloud has become the prerequisite layer for artificial intelligence, and AI has transformed old lock-in concerns into something more strategic. It is one thing for a company to be stuck with a cloud provider because its databases, networking, and automation are hard to move. It is another for the same provider to control the model catalog, GPU capacity, training pipelines, vector databases, data governance tools, inference services, and enterprise AI assistants that define the next wave of software spending.
This is why the Commission singled out AI tools and partnerships as a decisive factor in cloud procurement. Buyers are not merely asking which provider has the cheapest storage or the best Kubernetes service. They are asking where they can get access to frontier models, governed AI development, enterprise security, regional compliance, and enough accelerator capacity to run real workloads.
That shifts the cloud decision from infrastructure sourcing to strategic platform selection. Microsoft’s partnership with OpenAI, Azure AI Foundry, Copilot services, and its enterprise software estate create a particularly powerful funnel. AWS counters with Bedrock, custom silicon, model partnerships, and a massive customer base. Google brings Gemini, TPUs, and deep AI research credibility. The providers are no longer just competing to host applications; they are competing to define how applications are built.
For enterprise IT, AI also worsens the migration math. A conventional app may be portable with enough containerization, abstraction, and patience. An AI system tied to proprietary model APIs, embeddings, fine-tuning workflows, safety filters, telemetry, and data residency controls is harder to uproot. Even where the underlying model can be swapped, the behavior of the system may change enough to require retesting, revalidation, and new governance approvals.
The Commission is therefore treating cloud gatekeeping as a future-facing issue, not a retrospective complaint. If AI procurement hardens around the same hyperscalers that already dominate cloud infrastructure, the window to preserve contestability may close before European competitors can matter.

Interoperability Sounds Simple Until It Hits a Real Tenant

The DMA’s language around interoperability and data portability is easy to support in principle. Few customers would object to easier switching, clearer interfaces, less self-preferencing, and fewer traps that punish a company for adopting a rival’s service. In the abstract, everyone wants a cloud market where workloads can move and services can interoperate without contractual or technical booby traps.
In practice, cloud interoperability is brutally hard. Azure, AWS, and Google Cloud do not merely expose generic compute, storage, and networking. They expose thousands of managed services, each with its own identity model, policy framework, logging system, billing semantics, performance characteristics, API quirks, compliance documentation, and failure modes. A managed database on one cloud may be functionally similar to another, but “similar” is not portable.
For WindowsForum readers, this is where the policy becomes operational. A Windows-heavy enterprise using Azure Virtual Desktop, Entra ID, Intune, Defender, Sentinel, Azure SQL, Azure Kubernetes Service, and Microsoft 365 is not going to become cloud-neutral because Brussels writes the word portability into a rulebook. The real question is whether regulation can force enough transparency, interface discipline, and contractual fairness to make partial mobility more realistic.
That could still matter. Better egress terms, clearer migration tooling, more open identity and monitoring integrations, and fewer licensing practices that favor one cloud over another could reduce the penalty for multi-cloud or hybrid strategies. Even modest improvements could change negotiation dynamics, because customers do not need perfect portability to gain leverage. They need credible alternatives.
The danger is that regulators overspecify technical remedies in a market that changes faster than legal compliance cycles. If the Commission tries to freeze an idealized model of interoperability, it may produce paperwork rather than mobility. If it focuses on outcomes — lower switching friction, nondiscriminatory access, transparent terms, and enforceable portability commitments — it has a better chance of helping customers without pretending cloud platforms are interchangeable Lego bricks.

Europe’s Sovereignty Argument Is Doing Double Duty

The Commission’s language about secure, open, competitive markets and Europe’s tech sovereignty is not decorative. Cloud has become geopolitical infrastructure. Governments, hospitals, banks, manufacturers, universities, and startups are all placing sensitive data and critical operations into platforms controlled largely by American companies. That dependence is increasingly difficult for European policymakers to separate from security, industrial policy, and strategic autonomy.
This is where the DMA cloud move becomes more than competition enforcement. It sits alongside the EU Data Act, cybersecurity rules, data residency debates, sovereign cloud offerings, AI regulation, and a broader push to reduce dependence on foreign-controlled digital infrastructure. The Commission is not simply asking whether AWS and Azure charge fair prices. It is asking whether Europe can afford to let its digital future be mediated through a handful of external hyperscalers without stronger guardrails.
There is a tension here. Europe wants cutting-edge cloud and AI capabilities, but the companies with the deepest pockets, biggest infrastructure footprints, and most advanced AI partnerships are mostly American. European cloud providers often argue that hyperscaler scale makes fair competition difficult. Customers, meanwhile, often choose the hyperscalers because they need global reach, mature services, certifications, support, and engineering depth.
Regulation can alter incentives, but it cannot conjure hyperscale capacity overnight. If Brussels leans too hard into sovereignty without matching it with investment, procurement reform, and technical capability, it risks making European IT more regulated but not more competitive. If it does nothing, it risks watching the AI era lock in dependencies that later become politically and economically untouchable.
That is the needle the Commission is trying to thread. The preliminary AWS and Azure designations are a way to say that Europe welcomes cloud investment but will not treat infrastructure dominance as an ordinary market fact.

Microsoft’s Google Argument Reveals the Hardest Line to Draw

Microsoft’s response is notable because it does not simply deny Azure’s importance. It warns that ignoring Google Cloud and Gemini could tilt the market in a harmful way. That argument deserves attention because AI has scrambled old market-share categories.
In classical cloud infrastructure, AWS and Azure remain the obvious targets. They are the two giants, and in Europe the Commission says they occupy the top two slots. But AI procurement is not identical to infrastructure procurement. A company may choose a cloud because of access to models, AI development tools, accelerator availability, or integration with productivity software. On that axis, Google is not a marginal player.
The difficulty is that the DMA designates specific services based on legal criteria, not vibes about strategic momentum. Regulators have to decide whether a provider is already a gateway, not merely whether it might become one. Microsoft’s invocation of Google is therefore both a legal defense and a strategic warning: regulate Azure while leaving Google’s AI-cloud bundle untouched, and you may distort the next market rather than repair the last one.
The Commission will have to show that it is not simply picking the two largest names because they are politically visible. Its case will need to explain why AWS and Azure qualify despite reportedly not meeting certain quantitative gatekeeper thresholds, and why Google Cloud does not, at least for now. That is a delicate task.
For customers, the practical lesson is that gatekeeper status may not map cleanly onto technology choices. A regulated Azure may still be the best choice for a Windows-centric estate. An unregulated Google Cloud may still create AI dependencies. A regulated AWS may still offer more portability for some workloads than a smaller provider with fewer managed services. Legal labels matter, but architecture still matters more.

The DMA Could Make Cloud Contracts a New Compliance Front

If the preliminary findings become final, AWS and Azure would face a compliance clock. Under the DMA model, gatekeepers generally have months rather than years to bring designated services into line. That does not mean customers will wake up to a radically different Azure Portal the next morning. It does mean legal, procurement, product, and engineering teams inside the hyperscalers will start translating broad obligations into contract terms, APIs, documentation, administrative controls, and internal review processes.
Expect the first visible changes to appear in paperwork and procurement. Cloud contracts may become more explicit about data portability, interoperability commitments, ranking or recommendation practices in marketplaces, bundling behavior, and terms that affect third-party services. Enterprises operating in the EU may see new notices, compliance attestations, and possibly more granular explanations of how cloud services interact with adjacent products.
The more interesting changes would come if the Commission forces action on self-preferencing. In cloud, self-preferencing is harder to define than in a search results page or app store. Does a provider favor its own database because it integrates better with its own monitoring stack? Does it disadvantage a third-party security product by limiting access to telemetry? Does a marketplace ranking nudge customers toward first-party services? Does licensing make the provider’s own cloud financially preferable even when the software could run elsewhere?
These are not theoretical concerns. Microsoft’s licensing practices have drawn scrutiny for years from competitors who argue that running Microsoft software on rival clouds can be commercially disadvantaged. The company has made concessions in some markets, but the broader question remains central to cloud competition: when the same vendor controls software, identity, management tools, security services, and infrastructure, where does integration end and preference begin?
The DMA’s impact will depend on how aggressively regulators pursue those boundary cases. A light-touch approach could produce compliance theater. A maximalist approach could turn cloud product design into a legal minefield. The likely path is messy, iterative, and heavily litigated.

Windows Shops Should Read This as a Procurement Warning, Not a Migration Order

No CIO should treat the Commission’s preliminary finding as a reason to flee Azure or AWS. That would be a category error. The point of the DMA is not to tell customers which cloud to use; it is to change the conduct of companies deemed powerful enough to shape market access.
For Windows-heavy organizations, Azure will remain the path of least resistance for many workloads. The integration with Entra ID, Microsoft 365, Windows Server, SQL Server, Defender, Intune, and developer tooling is too deep to dismiss. In many cases, choosing Azure is not lock-in in the pejorative sense; it is a rational decision to reduce operational complexity.
But rational dependence is still dependence. The Commission’s move should prompt IT leaders to revisit assumptions that accumulated during years of cloud adoption. Which workloads are genuinely portable? Which services are tied to proprietary APIs? Which data stores would be expensive to move? Which identity and security policies presume Azure as the center of gravity? Which AI projects are quietly binding the organization to a single provider’s model stack?
The answer will not be the same for every workload. Some systems can be made portable with containers, infrastructure as code, open databases, and disciplined architecture. Others are deliberately built around managed services because the business values speed more than theoretical mobility. The problem is not choosing lock-in; the problem is choosing it accidentally.
The DMA debate makes that distinction more urgent. If regulators succeed, customers may gain better tools and terms for moving later. If regulators fail, organizations that ignored portability will have fewer excuses.

The Cloud Market Is Competitive and Concentrated at the Same Time

One reason cloud regulation is so contentious is that both sides can point to real facts. AWS, Azure, and Google Cloud compete ferociously. They announce new regions, custom chips, AI tools, database services, security products, and migration incentives at a pace that smaller vendors struggle to match. Customers routinely run multi-cloud strategies, and large enterprises can extract meaningful concessions from hyperscalers.
At the same time, the market is concentrated in the ways that matter most for long-term power. The largest providers have capital expenditure budgets that smaller rivals cannot approach. They can absorb the cost of custom silicon, global network buildouts, AI partnerships, compliance certifications, and developer ecosystems. They also benefit from procurement gravity: once a company standardizes on a hyperscaler, every new project has an incentive to land there too.
That dual reality frustrates simple narratives. It is not accurate to say cloud customers have no choice. It is also not accurate to say choices remain equally viable after years of architectural commitment. The market is competitive at the point of entry and sticky after adoption.
The Commission’s preliminary view appears to target that second phase. It is less concerned with whether a startup can choose among three clouds on day one than with whether a mature business can discipline its provider on day 1,000. In enterprise IT, that is often where market power hides.

The Coming Fight Will Be About Remedies, Not Labels

Amazon and Microsoft can now respond to the Commission’s preliminary findings before a final decision. They will almost certainly contest the analysis, narrow the obligations, and argue that existing regulation already covers much of the relevant ground. They may also lean on the risk that Europe’s regulatory layering makes it less attractive to deploy the newest infrastructure and AI services quickly.
The Commission, for its part, will need to convert a compelling political story into enforceable obligations. “Cloud should be fair and open” is not a remedy. “Interoperability” is not self-defining. “Data portability” can mean anything from downloadable exports to live migration paths. “No self-preferencing” becomes hard when first-party services are genuinely better integrated because the provider built the platform.
The most useful remedies would probably be prosaic. Clearer exit rights. More predictable data export and migration support. Limits on punitive egress practices. Stronger access for third-party tools to logs, telemetry, identity hooks, and marketplace surfaces. Greater transparency when first-party cloud services are advantaged by licensing or technical integration. Better documentation of dependencies that make workloads hard to move.
The least useful remedies would try to make all clouds behave the same. Homogenizing hyperscale platforms would be bad engineering and bad policy. Customers benefit from differentiated services, and innovation often comes from providers building opinionated systems that do not map neatly onto rivals’ offerings. The goal should be to make leaving possible, not to make every cloud identical.
That distinction will decide whether the DMA becomes a serious tool for enterprise buyers or another compliance ritual that lawyers understand better than administrators.

The Real Test Is Whether Azure and AWS Customers Gain Leverage

The practical stakes are narrower and sharper than the political rhetoric suggests. The Commission’s preliminary move will matter if it gives customers more leverage without slowing the infrastructure and AI investments those same customers need.

The Commission’s June 25 preliminary finding targets AWS and Azure specifically, not cloud computing as a category in the abstract.
A final designation would extend DMA obligations into cloud infrastructure, marking a major expansion beyond the consumer platform fights that defined the law’s early years.
The central regulatory concern is not merely market share, but whether entrenched ecosystems, high switching costs, AI services, and procurement patterns make AWS and Azure unavoidable gateways.
Microsoft’s warning about Google Cloud and Gemini highlights a genuine problem: AI competition may not line up neatly with traditional cloud market rankings.
Windows-centric organizations should not treat this as a signal to abandon Azure, but they should use it as a reason to audit portability, licensing exposure, and AI dependencies.
The most useful outcome for customers would be better exit rights, interoperability, transparency, and contractual leverage rather than a fantasy of perfectly interchangeable clouds.

The EU’s move against AWS and Azure is best understood as a bet that the next decade of digital competition will be decided below the app layer, inside the clouds where data, AI, identity, and software delivery now converge. Amazon and Microsoft will argue that Brussels is overreaching, and parts of that critique will resonate with anyone who has watched Europe regulate faster than it builds. But the Commission has identified a real pressure point: once cloud platforms become the place where businesses build their future, the cost of leaving becomes a form of power. The coming fight will determine whether that power is merely the reward for building indispensable infrastructure, or whether it has become the kind of gatekeeping Europe is no longer willing to leave alone.

References

Primary source: SRN News
Published: 2026-06-25T11:30:18.966885

EU targets Amazon, Microsoft cloud units for Big Tech “gatekeeper” rules - SRN News

By Foo Yun Chee BRUSSELS, June 25 (Reuters) – EU antitrust regulators said Amazon and Microsoft’s cloud computing services should be designated as “gatekeepers” under landmark tech rules, a step that would subject them to strict obligations aimed at curbing market power. The designation under...

srnnews.com
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105

Related coverage: euronews.com

Brussels tightens rules on US cloud providers as it pushes for tech sovereignty | Euronews

The European Commission has decided that Microsoft Azure and Amazon Web Services should face strict rules to improve cloud competition. The move risks angering Washington as Brussels pushes the European tech sovereignty agenda.

www.euronews.com
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
Related coverage: europapress.es

Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio

La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...

www.europapress.es
Related coverage: marketscreener.com

EU targets Amazon, Microsoft cloud units for Big Tech "gatekeeper" rules

EU antitrust regulators said Amazon and Microsoft's cloud computing services should be designated as gatekeepers under landmark tech rules, a step that would subject them to strict obligations aimed...

www.marketscreener.com
Related coverage: brusselstimes.com

The Brussels Times

www.brusselstimes.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com

ChatGPT · Jun 26, 2026

The European Commission said on June 25, 2026, that Amazon Web Services and Microsoft Azure should be designated as Digital Markets Act gatekeepers in the European Union, a preliminary finding that would bring cloud infrastructure under the bloc’s toughest platform-competition regime. This is not yet a final order, but it is a loud signal. Brussels is no longer treating cloud as plumbing beneath the internet economy; it is treating cloud as one of the places where market power is made, defended, and monetized.
That distinction matters for WindowsForum readers because Azure is not just another Microsoft business line. It is the substrate beneath Microsoft 365, Entra ID, GitHub, Defender, Copilot, Windows cloud management, and a large share of the enterprise software stack. If the Commission follows through, the DMA fight moves from app stores and browsers into the control plane of modern IT.

Brussels Moves the DMA Below the Waterline

The Digital Markets Act was sold to the public through familiar consumer-facing examples: app stores, search engines, messaging apps, ads, marketplaces, browsers. Those were the visible choke points. Cloud computing, by contrast, is the part most users never see and most businesses cannot easily escape.
That invisibility is precisely why the Commission’s move is important. AWS and Azure do not need to be the default icon on a phone screen to act as gatekeepers. They can shape markets through identity systems, data gravity, technical dependencies, licensing terms, egress fees, procurement inertia, certification ecosystems, and managed services that become harder to leave with every passing quarter.
The Commission’s preliminary position follows market investigations opened in late 2025 into whether AWS and Azure should fall under the DMA despite not meeting the law’s usual quantitative thresholds. That is the crucial legal twist. Brussels is saying that the absence of a simple threshold trigger does not necessarily mean the absence of gatekeeper power.
For Amazon, the issue is AWS’s role as the largest cloud provider in the EU. For Microsoft, the question is more complicated because Azure is tied to a wider enterprise empire. Microsoft can sell cloud infrastructure, productivity software, identity, endpoint security, developer tooling, AI services, and operating-system management as mutually reinforcing pieces of one stack. That integration is useful to customers, but it is also the kind of gravity regulators now want to inspect.
The Commission has reportedly estimated that AWS and Azure together account for roughly 60 percent of the EU cloud market. Even if the exact percentage shifts by methodology, the strategic picture is not subtle: two U.S. hyperscalers sit at the center of Europe’s enterprise cloud economy. The DMA was built to address digital bottlenecks, and Brussels is now arguing that infrastructure bottlenecks count.

Cloud Is No Longer Just Someone Else’s Server

The old joke that cloud is “just someone else’s computer” was always technically incomplete, but it has become strategically useless. Cloud is now someone else’s compliance boundary, billing model, identity fabric, observability layer, software marketplace, hardware procurement strategy, and AI accelerator pipeline. It is where decisions made by a handful of platform vendors ripple outward into thousands of businesses.
That is why cloud regulation is harder than browser regulation. If a browser is a gatekeeper, the remedy might involve choice screens, defaults, interoperability, or data portability. If a cloud platform is a gatekeeper, the remedy could touch procurement, migration, technical documentation, API behavior, software licensing, contract terms, workload portability, and preferential treatment for first-party services.
The Commission’s theory is that cloud providers can become essential gateways between business users and customers. That framing is broader than the usual consumer-platform model, but it reflects how companies actually build software now. A bank’s mobile app, a retailer’s inventory system, a hospital’s patient portal, a government authentication service, or a startup’s AI product may all depend on cloud services that are deeply embedded below the user interface.
The modern enterprise also does not consume “compute” in the abstract. It consumes managed databases, AI APIs, Kubernetes services, identity integrations, security tooling, storage tiers, serverless runtimes, networking primitives, and compliance-ready templates. Each managed service saves time, but each one also creates a dependency map.
That dependency map is the real object of regulatory interest. Brussels is not merely asking whether AWS and Azure are big. It is asking whether they are positioned to decide how easily European businesses can switch, combine, compete, and build on top of digital infrastructure.

Azure Makes This a Microsoft Story, Not Just a Cloud Story

For Microsoft, the Commission’s preliminary finding lands at a sensitive point in the company’s transformation. Azure is no longer a side bet attached to Windows and Office. It is the engine through which Microsoft redefines Windows administration, enterprise identity, security operations, developer workflows, and AI adoption.
A Windows admin can see this everywhere. Entra ID is the front door for identity. Intune and Windows Autopatch move endpoint management into the cloud. Defender expands from antivirus into a cross-platform security operation. Microsoft 365 ties productivity to compliance and retention. GitHub and Azure DevOps shape developer pipelines. Copilot services ride on cloud-hosted models, telemetry, permissions, and tenant data.
None of that is inherently abusive. In many organizations, Microsoft’s integrated stack is the rational choice because it reduces vendor sprawl and gives IT departments one throat to choke. The problem, from a competition-law perspective, is that convenience and lock-in often look identical from the inside of a procurement cycle.
Azure’s relationship with Windows Server and SQL Server has been a recurring flashpoint in Europe. Cloud rivals have complained for years that Microsoft’s software licensing terms made it more expensive or cumbersome to run Microsoft workloads on competing clouds. Microsoft has made concessions over time, but complaints from European cloud providers and competitors helped keep the issue alive.
The DMA process gives Brussels a different instrument from traditional antitrust enforcement. Instead of proving a single abuse after years of litigation, the law imposes obligations on designated gatekeepers up front. That is why a final designation would matter even before any individual penalty or remedy arrives.

AWS Is the Cleaner Case, Which May Make It the Harder One

Amazon’s AWS presents a different regulatory profile. AWS does not have Microsoft’s Windows-and-Office history, and it does not bundle the dominant enterprise desktop operating system with cloud infrastructure. Its power comes from being early, broad, reliable, and deeply embedded in how modern software teams work.
That makes the AWS case cleaner in one sense. Brussels can focus on cloud-market structure without the complication of Microsoft’s adjacent monopolies and enterprise licensing legacy. AWS is the archetypal hyperscale cloud: enormous service breadth, global infrastructure, a vast partner ecosystem, and a procurement position that often makes it the safe default.
But that also makes the case harder. Much of AWS’s advantage was earned through execution. It built the category, trained the market, normalized self-service infrastructure, and gave developers an operating model that incumbents initially underestimated. Regulators must distinguish between punishing success and restraining gatekeeper conduct.
The Commission appears to be leaning on the practical effect rather than the origin story. If a platform becomes an unavoidable gateway, its route to that position matters less than the consequences of that position. That is the DMA’s defining attitude toward digital markets.
For AWS customers, the most likely near-term effects would not be a dramatic breakup or forced unbundling. They would be pressure around interoperability, commercial terms, data movement, switching barriers, transparency, and discrimination between first-party and third-party services. In other words, the battle would be fought in the places cloud architects already know are painful.

The DMA’s Cloud Test Is Really About Switching Costs

Cloud lock-in is rarely a single locked door. It is more often a corridor of half-open doors that each require time, money, risk acceptance, and executive patience to walk through. The more a company uses managed services, the more expensive it becomes to move.
A workload running on generic virtual machines can be migrated with pain but without existential redesign. A workload built around proprietary databases, serverless functions, IAM assumptions, observability pipelines, event buses, storage semantics, marketplace dependencies, and AI services is a different beast. Even when technical migration is possible, organizational migration can be brutal.
The Commission’s cloud inquiry should be read through that lens. A gatekeeper designation would not mean every AWS or Azure customer is trapped. It would mean Brussels sees enough structural dependency to justify imposing rules before the dependency becomes irreversible.
Switching costs are not only technical. They are embedded in procurement, certification, training, staffing, compliance audits, vendor credits, discount schedules, and risk committees. A CIO who wants a multi-cloud posture may still discover that her finance team, developers, auditors, and security engineers all have different incentives pushing back toward consolidation.
Microsoft and Amazon will argue, with some justification, that customers can and do use multiple providers. Google Cloud, Oracle Cloud, IBM, OVHcloud, Scaleway, Deutsche Telekom, and others all exist. The counterargument is that the existence of alternatives does not prove the absence of gatekeeper power when the economic and technical cost of using those alternatives is high.

Europe’s Sovereignty Argument Is Now an Infrastructure Argument

The Commission’s move cannot be separated from Europe’s broader push for digital sovereignty. For years, “sovereignty” in tech policy sounded like a slogan that could mean anything: data residency, industrial policy, privacy law, cybersecurity, procurement nationalism, or strategic autonomy from U.S. platforms. Cloud makes the slogan concrete.
If European governments, banks, manufacturers, hospitals, universities, and startups depend on U.S.-controlled hyperscalers, then Europe’s digital economy is exposed to decisions made in Seattle, Redmond, Washington, and sometimes geopolitical weather well outside Brussels. That does not mean AWS and Azure are unsafe or unreliable. It means they are strategically central.
The rise of sovereign-cloud offerings from U.S. providers shows that Amazon and Microsoft understand this pressure. They have tried to answer European concerns with EU-based regions, operational separation, local controls, residency promises, and governance structures designed to reassure public-sector and regulated customers. Those offerings may solve some compliance problems, but they do not fully answer the competition question.
A sovereign region operated by a hyperscaler is still part of a hyperscaler ecosystem. It may address data location and control, while leaving market structure largely intact. Brussels appears to be saying that sovereignty without contestability is not enough.
That is where the DMA and industrial policy begin to overlap. Europe wants trusted cloud capacity, but it also wants a market in which European providers can compete without being permanently relegated to niche status. The danger is that the policy becomes protectionism dressed as competition law. The opportunity is that it forces the cloud market to become more open, portable, and transparent than it would have become on its own.

The United States Should Not Dismiss This as Eurocrat Theater

American tech companies have grown used to treating Brussels as both regulator and irritant: powerful enough to fine them, slow enough to be gamed, and occasionally useful as a forcing function for product changes they can later standardize globally. But the cloud inquiry is different because it touches the enterprise infrastructure market, not merely consumer defaults.
For U.S. policymakers, the instinctive response will be suspicion. AWS and Azure are national champions in everything but name. They support American software exports, AI development, cybersecurity capacity, and government infrastructure. European regulation of those platforms will inevitably be read through a geopolitical lens.
But dismissing the Commission’s concerns would be a mistake. The United States has its own growing anxiety about cloud concentration, especially as AI workloads increase dependence on hyperscale infrastructure. When a small number of firms control the compute, storage, networking, identity, marketplace, and model-hosting layers, competition questions are not parochial European obsessions. They are basic questions about how digital economies remain contestable.
The irony is that American enterprises may benefit indirectly from European pressure. If DMA obligations force clearer portability rules, fairer licensing practices, better documentation, or less punitive data-movement economics in Europe, global customers will ask why those improvements should stop at the border. The Brussels effect is not automatic, but it is real enough that vendors plan around it.
That is particularly true for Microsoft. The company has repeatedly changed Windows, browser, Teams, app-store, and cloud practices under European scrutiny. Sometimes those changes were grudging and regional. Sometimes they became part of a broader product strategy. Azure’s turn under the microscope may produce a similar pattern.

The AI Boom Raises the Stakes for Cloud Gatekeepers

The timing is impossible to ignore. Cloud was already critical before generative AI became the boardroom obsession of the decade. Now AI has made cloud infrastructure even more central because advanced models depend on scarce accelerators, specialized networking, storage pipelines, model-hosting platforms, and developer ecosystems.
Microsoft’s AI strategy is tied deeply to Azure. OpenAI workloads, Azure AI services, Copilot infrastructure, and enterprise data integration all reinforce the idea that cloud is where AI becomes a business product. Amazon has its own AI stack through Bedrock, custom chips, model partnerships, and AWS-native deployment pathways.
If cloud platforms become the default routes to enterprise AI, then gatekeeper power in cloud could become gatekeeper power in AI adoption. The company that hosts the workload can influence which models are easiest to buy, which data pipelines are simplest to build, which security controls are preapproved, and which developer tools feel native. That influence can be subtle, but subtle does not mean small.
The Commission has already shown interest in how digital gatekeepers can use adjacent markets to reinforce core positions. Cloud and AI are a natural next front. A business that standardizes on Azure for identity, productivity, security, and data may find Microsoft’s AI services not just attractive, but institutionally inevitable.
Again, inevitability is the regulatory trigger. The question is not whether Microsoft or Amazon offers good AI services. The question is whether customers and competitors can make genuine choices without being dragged by cloud gravity into a predetermined path.

Enterprise IT Will Feel This First as Paperwork, Then as Leverage

For sysadmins and IT managers, the first visible effect of a final gatekeeper designation may be boring: compliance updates, contract language, procurement memos, legal reviews, revised documentation, and regional policy announcements. That does not mean the impact is trivial. In enterprise technology, paperwork is often where power changes hands.
If AWS and Azure face DMA obligations, customers in Europe may gain new leverage in negotiations. Procurement teams could ask sharper questions about portability, termination, data export, interoperability, and parity between first-party and third-party services. Competitors may use the designation to challenge commercial practices that previously seemed too entrenched to fight.
Administrators should not expect overnight simplicity. Multi-cloud remains operationally complex, and regulators cannot magically make IAM models, database engines, network architectures, and compliance regimes interchangeable. Anyone promising frictionless portability is selling a fantasy.
But regulation can change the default assumptions. If hyperscalers know they must defend their switching terms and platform conduct under DMA scrutiny, they may design future services with fewer obvious lock-in traps. If not out of generosity, then out of risk management.
The practical lesson for IT shops is to document dependency. Organizations should know which workloads rely on proprietary services, which data sets are costly to move, which contracts penalize exit, and which identity or security assumptions bind them to one cloud. A regulatory proceeding in Brussels will not replace architecture discipline.

Microsoft’s Compliance Challenge Is Cultural as Much as Legal

Microsoft has become skilled at regulatory adaptation. It can produce regional SKUs, revised admin controls, compliance dashboards, data-boundary commitments, unbundling options, and licensing updates with the fluency of a company that has spent decades under antitrust scrutiny. That experience is an advantage.
It is also a liability. European regulators remember the history. They remember browser bundling, server interoperability fights, licensing disputes, Teams complaints, and the long arc from Windows dominance to cloud-platform integration. Microsoft may insist that today’s Azure is a competitive cloud in a dynamic market, but it enters the room carrying institutional baggage.
The deeper challenge is cultural. Microsoft’s modern success comes from integration: tying identity to productivity, productivity to security, security to cloud, cloud to developer tools, and all of it now to AI. The company’s strategic instinct is to make the Microsoft stack feel coherent and inevitable.
The DMA’s instinct is the opposite. It seeks to prevent inevitability from becoming foreclosure. It asks dominant platforms to leave room for rivals, alternatives, and user choice even when integration would be commercially efficient.
That tension will define Microsoft’s response. The company can comply narrowly, turning every obligation into a regional checkbox. Or it can treat the cloud inquiry as a warning that enterprise customers and regulators increasingly want openness to be designed into the stack, not bolted on after complaints.

The Real Cloud Bill Is the Cost of Leaving

The most concrete lesson from the Commission’s move is that cloud buyers should stop treating exit planning as pessimism. In a market where regulators are investigating gatekeeper power, the ability to leave is not a luxury feature. It is part of the cost model.

The Commission’s June 25 finding is preliminary, so AWS and Azure are not yet finally designated as DMA gatekeepers for cloud services.
A final designation would move the DMA deeper into enterprise infrastructure, where switching costs are technical, contractual, and organizational.
Microsoft faces special scrutiny because Azure sits inside a wider enterprise stack that includes Windows, Microsoft 365, Entra ID, Defender, GitHub, and Copilot.
AWS faces scrutiny as the EU’s largest cloud provider, even without Microsoft’s desktop and productivity legacy.
European customers should use the regulatory process as leverage to demand clearer portability, fairer exit terms, and better transparency from hyperscalers.
IT teams should map proprietary dependencies now, because regulation may improve bargaining power but will not redesign architectures for them.

This is the useful way to read Brussels’ move: not as a guarantee that European cloud competition will suddenly flourish, and not as proof that AWS or Azure has broken the law, but as a recognition that cloud infrastructure has become too important to remain beneath the competition-policy radar.
The Commission’s preliminary finding is a warning shot at the architecture of dependency that now underpins enterprise computing. AWS and Azure will fight to frame their scale as the result of innovation, customer trust, and operational excellence; Brussels will frame that same scale as a gateway that must be made contestable. Both can be true at once, which is why the next phase matters. If the DMA can push the cloud market toward portability without freezing the innovation that made hyperscale useful, Europe may end up doing more than regulating American platforms. It may force the whole industry to admit that the freedom to build in the cloud is incomplete without the freedom to leave it.

References

Primary source: Moomoo
Published: 2026-06-26T09:30:31.599218

Document
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
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
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu

Related coverage: europeansting.com

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA - The European Sting - Critical News & Insights on European Politics, Economy, Foreign Affairs, Busin

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA The European Sting - Critical News & Insights on European Politics, Economy, Foreign Affairs, Business & Technology - europeansting.com...

europeansting.com
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
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
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
Related coverage: ec.europa.eu

IP 25 2717 EN

PDF document

ec.europa.eu
Related coverage: itpro.com

What the new AWS European Sovereign Cloud means for enterprises | IT Pro

AWS has announced the general availability of its European Sovereign Cloud, offering EU-based customers stringent data residency and protection controls.

www.itpro.com
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

ChatGPT · Jun 26, 2026

European Union regulators said on June 25, 2026, that Amazon Web Services and Microsoft Azure should be designated as cloud “gatekeepers” under the Digital Markets Act, opening the door to interoperability, data portability, and anti-self-preferencing obligations across Europe’s dominant cloud infrastructure market. The finding is preliminary, but the direction is unmistakable: Brussels is no longer treating cloud as a neutral utility sitting behind the real platform wars. It is treating cloud as the platform war.
For WindowsForum readers, the Microsoft angle is obvious, but the bigger story is not merely that Azure may face another EU compliance regime. It is that the cloud layer underneath Windows, Microsoft 365, GitHub, Copilot, OpenAI integrations, enterprise identity, databases, and security tooling is now being pulled into the same regulatory logic that reshaped app stores, browsers, search, and messaging. The EU is arguing that infrastructure can be a gatekeeper even when most end users never see the gate.

Brussels Moves the DMA Below the Waterline

The Digital Markets Act was originally sold to the public through consumer-facing examples: app store rules, search ranking, browser choice screens, messaging interoperability, and whether a platform owner could privilege its own services over rivals. Cloud computing was always in the background, but it did not have the same political simplicity. Nobody marches in the street because their Kubernetes cluster cannot be live-migrated from one hyperscaler to another.
That is precisely why the Commission’s move matters. The EU is now saying that market power in the digital economy does not need a consumer homepage, a social feed, or a smartphone icon to be systemically important. If enough businesses build on a platform, if switching costs are high enough, and if the provider’s ecosystem becomes the default route to customers, regulators see a gate.
The Commission’s preliminary findings followed a seven-month investigation into whether AWS and Azure act as important gateways between businesses and customers in the EU. The key phrase is not “largest cloud providers,” although that is true. The key phrase is important gateway, because it translates the DMA’s consumer-platform vocabulary into the language of enterprise infrastructure.
That translation is legally and commercially explosive. A cloud provider does not merely host workloads anymore. It sells databases, AI accelerators, model hosting, identity, observability, security services, developer tools, and managed application stacks. Once an enterprise has built deeply into that mesh, the cost of leaving can become less like changing vendors and more like rewriting institutional memory.

The Cloud Was Never Just Someone Else’s Computer

The old joke that cloud is “just someone else’s computer” has always been comforting because it suggests interchangeability. If one rented server looks like another rented server, competition should take care of itself. But modern hyperscale cloud is not a rack of anonymous virtual machines. It is an operating environment with its own APIs, billing incentives, compliance defaults, privileged integrations, and gravitational pull.
AWS and Azure became indispensable not simply by selling compute and storage, but by building large catalogs of services that reward customers for staying inside the same perimeter. The deeper a company goes into proprietary managed services, the less plausible it becomes to switch providers without re-architecting applications. A CIO can say “multi-cloud” on a slide deck while the actual database, identity layer, data pipeline, and AI deployment path quietly bind the organization to a single vendor.
That is where Brussels sees lock-in. Cloud lock-in is not only contractual; it is technical, operational, and cultural. Developers learn one provider’s idioms. Security teams tune policies around one provider’s controls. Finance teams learn one provider’s discount structures. Compliance teams document one provider’s assurances. At enterprise scale, these are not minor inconveniences. They are organizational facts.
Microsoft knows this terrain better than almost anyone. Azure’s strength is not just its data centers or its virtual machines. It is its integration with Windows Server, Active Directory and Entra ID, Microsoft 365, Defender, SQL Server, Visual Studio, GitHub, Power Platform, and now Copilot-branded AI services. That is an extraordinary enterprise stack. It is also exactly the kind of stack regulators scrutinize when they worry that adjacency can become leverage.

Azure’s Windows Advantage Is Now a Regulatory Liability

For two decades, Microsoft has worked to turn its enterprise dominance from a vulnerability into an advantage. The company did not merely survive the antitrust battles of the Windows era; it adapted. Azure was built for a world where Microsoft could say, plausibly, that it supported Linux, open source, hybrid cloud, containers, and competing platforms. The new Microsoft was interoperable, pragmatic, and developer-friendly.
That posture is real, but it does not erase the fact that Microsoft’s enterprise footprint gives Azure a uniquely powerful sales channel. A company already committed to Microsoft 365, Entra ID, Intune, Defender, Windows Server, and SQL Server does not encounter Azure as just another cloud provider. It encounters Azure as the path of least resistance.
The Commission appears to understand that point. In cloud procurement, the question is often not which provider has the best isolated service. It is which provider reduces friction across the systems the enterprise already runs. For many Windows-heavy organizations, Azure benefits from decades of accumulated Microsoft standardization. That is not illegal by itself. It is also not invisible.
This is why Microsoft’s response pointing to Google Cloud and Gemini is strategically predictable. Microsoft wants the Commission to see AI cloud competition as dynamic, unsettled, and increasingly shaped by Google’s model and infrastructure ambitions. It is not an absurd argument. Google is a serious cloud and AI player. But the DMA question is not whether another giant exists. It is whether Azure has become a gateway with durable power over business users in the EU.
The distinction matters. Antitrust debates often become theater around who is “dominant,” as if dominance were a trophy awarded to only one company. The cloud market can be competitive in some dimensions and still produce gatekeeper power in others. A developer choosing where to test a new AI workload may have several options. A regulated enterprise with thousands of Windows devices, Microsoft identity dependencies, and a decade of Azure architecture may have far fewer.

AWS Is the Pure Cloud Target, Azure Is the Ecosystem Target

Amazon and Microsoft enter this fight from different directions. AWS is the archetypal hyperscaler: the cloud pioneer whose breadth, scale, and operational maturity made it the default infrastructure choice for much of the startup and enterprise world. Azure is the enterprise ecosystem cloud, fused to Microsoft’s long-standing software estate and now tightly linked to the company’s AI ambitions.
That difference will shape the politics of the case. AWS can argue that customers have a wide range of cloud options and that excessive regulation will chill investment in European infrastructure. It can point to the constant arrival of new services, regional providers, open-source stacks, and multi-cloud architectures as evidence that the market is not static. Amazon’s defense is likely to be a version of: customers have choice, and the EU is mistaking success for foreclosure.
Microsoft’s defense is more complicated. Azure is not merely a cloud unit; it is a strategic layer across Microsoft’s entire enterprise business. Every time Microsoft bundles, integrates, discounts, or optimizes across that stack, it creates customer value and regulatory suspicion at the same time. The exact same integration that makes Azure attractive to IT departments can look, from Brussels, like a mechanism for steering demand.
That tension is familiar to anyone who remembers the browser wars or the more recent Teams bundling fight. Microsoft’s commercial superpower has always been integration. The EU’s recurring concern has always been that integration can be used to deny rivals a fair shot.
The cloud version is subtler because no one is forcing a customer to choose a managed database, a model-hosting service, or a proprietary analytics platform. But in enterprise IT, defaults are powerful. Procurement templates, technical documentation, partner incentives, and licensing structures can make one path feel obvious and every alternative feel like an exception requiring justification.

The DMA Enters the AI Supply Chain

The Commission’s emphasis on AI tools and partnerships is the sharpest part of the preliminary finding. Cloud infrastructure has become the staging ground for AI deployment, not merely a place to store data or run applications. The provider that hosts the data, supplies the GPUs, offers the model catalog, wraps it in governance tools, and connects it to productivity software may define the next enterprise computing platform.
This is why the cloud investigation cannot be separated from AI. Generative AI has intensified the importance of cloud capacity, data gravity, and platform ecosystems. Training and inference are expensive. Enterprises want managed services rather than raw infrastructure. Vendors want to bind AI adoption to their existing cloud and software footprints.
For Microsoft, this means Azure is not just another business line under scrutiny. It is the infrastructure layer beneath Copilot, Azure OpenAI Service, GitHub Copilot integrations, Microsoft 365 AI features, and the company’s broader pitch that AI will be woven through work. If regulators impose interoperability and anti-self-preferencing obligations on Azure, they may indirectly shape how Microsoft can bundle and advantage its AI services in Europe.
For AWS, the AI story is different but no less important. Amazon has been racing to position AWS as a neutral and broad AI platform, with its own chips, managed model services, and partnerships. It wants to be the place where customers can choose among models and build at scale. Brussels is likely to ask whether that marketplace remains genuinely open when the cloud provider controls the surrounding infrastructure and economics.
The EU’s concern is not that AI services exist inside cloud platforms. It is that the next generation of enterprise dependency may form before regulators can see it clearly. By the time every business process is connected to a provider’s AI stack, portability may be a slogan rather than an option.

Data Portability Sounds Simple Until the Bill Arrives

Among the likely DMA consequences, data portability is the one that sounds most straightforward and becomes most complicated in practice. In consumer tech, portability often means exporting photos, contacts, playlists, or messages. In cloud, portability means moving enormous volumes of data, metadata, configurations, permissions, logs, application dependencies, and sometimes entire operational models.
The technical challenge is real, but the economic challenge may be more important. Cloud providers have long faced criticism over egress fees, transfer costs, and pricing structures that make leaving more expensive than arriving. Even where fees are reduced or waived under certain conditions, the broader problem remains: moving a large, complex workload is expensive, risky, and disruptive.
DMA-style obligations could push AWS and Azure toward clearer migration paths, better documentation, less punitive switching economics, and stronger interoperability commitments. That would be welcomed by many CIOs who already want leverage in vendor negotiations. But the devil will be in the definitions. What counts as meaningful portability for a managed database? What does interoperability mean for proprietary AI governance tooling? How much compatibility can regulators demand without freezing product design?
These are not academic questions. If obligations are too vague, the hyperscalers will satisfy them with compliance theater. If they are too rigid, regulators could accidentally favor the lowest common denominator and make advanced cloud services harder to evolve. The EU will have to regulate lock-in without pretending that all cloud services are interchangeable commodities.
That balance is difficult, and the hyperscalers will exploit every ambiguity. They will argue that cloud innovation depends on specialized services, and that specialized services inevitably create dependencies. There is truth in that. There is also a convenient escape hatch. Not every dependency is abusive, but every gatekeeper would prefer to describe lock-in as innovation.

Interoperability Is the Word Everyone Supports Until It Has Teeth

Interoperability is one of those terms that almost no vendor opposes in public. Microsoft, in particular, has spent years presenting itself as a champion of cross-platform reality. Azure runs Linux. Microsoft contributes to open source. SQL Server runs on Linux. Visual Studio Code became a developer staple far beyond Windows. The company has earned some credibility here.
But interoperability under regulation is different from interoperability as marketing. The regulated version asks whether rivals can connect on fair terms, whether customers can move without unreasonable friction, and whether the platform owner withholds technical advantages from competitors. It is less about whether something is possible and more about whether it is practical, documented, supported, and economically sane.
For Windows administrators, this is where the story becomes operational. A more aggressive EU stance could eventually influence how Microsoft documents Azure migration paths, exposes APIs, treats third-party management tools, and structures integrations with Microsoft 365 and Entra ID. It may also affect how European customers negotiate contracts, especially if compliance obligations create new standardized expectations around portability and access.
The risk for Microsoft is that Azure’s most valuable integrations become the focus of regulatory line-drawing. If Defender, Sentinel, Entra, Intune, GitHub, Microsoft 365, and Copilot work best on Azure, is that legitimate product integration or self-preferencing? The honest answer may vary by feature. Regulators are rarely good at that level of nuance, but vendors are rarely neutral judges of their own incentives.
AWS faces a different version of the same question. Its service catalog is so broad that it can build convenience into its own ecosystem at every layer. A customer may be free to use third-party tools, but AWS-native options often win because they are already integrated, billed, monitored, and supported inside the same console. That is not coercion in the old sense. It is platform gravity.

Europe’s Tech Sovereignty Argument Is Doing More Work Than It Admits

The Commission’s language about Europe’s digital future and technological sovereignty is not incidental. Cloud has become critical infrastructure, and Europe is uncomfortable with the fact that so much of it is controlled by American companies. The DMA gives Brussels a competition-law mechanism for a geopolitical anxiety.
That does not make the case illegitimate. Cloud concentration has real competitive consequences, and European businesses do face practical switching barriers. But the sovereignty framing changes the politics. It means the investigation is not only about whether AWS and Azure treat rivals fairly. It is also about whether Europe can tolerate depending on non-European infrastructure for AI, public services, defense-adjacent workloads, and regulated industries.
This is where critics will accuse the EU of protectionism dressed as competition policy. They will say Brussels wants to handicap American winners because Europe failed to produce equivalent hyperscalers. There is some force to that critique, especially when regulation becomes a substitute for industrial strategy. But it is too easy to stop there.
The United States also treats digital infrastructure as strategic. China does the same, more explicitly. The idea that cloud should be viewed as a neutral commercial market untouched by state interest is quaint. The only unusual thing about the EU is that it often expresses industrial anxiety through legal process, consultation periods, and compliance regimes.
That style frustrates American companies because it is slow, procedural, and intrusive. It also gives them room to respond. Amazon and Microsoft now get to challenge the preliminary findings before a final decision. The fight is not over; it has simply moved from speculation into the regulatory record.

The Hyperscalers Will Fight on Investment, Innovation, and Scope

Amazon’s first line of defense is already visible: the EU has cloud regulation through other laws, and another DMA layer could deter investment and innovation. This is the standard hyperscaler argument, but it is not empty. Europe wants more data centers, more AI capacity, better sovereign cloud options, lower latency, and more secure infrastructure. Those goals require capital, and AWS and Microsoft are among the few companies able to deploy it at the necessary scale.
The question is whether that investment should buy freedom from gatekeeper obligations. The Commission’s likely answer is no. In fact, the more essential the investment becomes, the stronger the case for obligations may appear. A bridge does not become less regulated because it is expensive to build.
Microsoft’s argument about Google Cloud and Gemini is more tactical. It seeks to widen the frame from a two-player cloud hierarchy to a three-way AI-platform race. If AI is the decisive frontier, Microsoft wants regulators to account for Google’s infrastructure, models, data, and distribution. This argument may resonate more in AI than in traditional enterprise cloud, where AWS and Azure remain the obvious first two names.
The broader industry will also argue about scope. If AWS and Azure are gatekeepers, why not Google Cloud? If cloud infrastructure is covered, what about enterprise SaaS platforms, developer platforms, cybersecurity platforms, or AI model marketplaces? The DMA was designed around “core platform services,” but the digital economy keeps turning more layers into platforms.
That is the deeper threat to Big Tech. Once Brussels proves it can extend gatekeeper reasoning into infrastructure, the DMA becomes less a fixed list of regulated services and more a doctrine of digital dependency. The next fight will be over where that doctrine stops.

Enterprise IT Should Read This as Leverage, Not Liberation

For CIOs, sysadmins, and architects, the immediate practical effect is limited. AWS and Azure have not yet been finally designated for cloud services under the DMA. Even if they are, compliance would unfold over time, and the most meaningful changes would likely arrive through contracts, documentation, migration tooling, interoperability commitments, and complaint-driven enforcement.
Still, enterprise buyers should pay attention now. Regulatory pressure can create negotiation leverage before formal remedies arrive. If a customer is renewing a large Azure or AWS agreement in Europe, questions about portability, egress, migration support, third-party tool access, audit rights, and AI data governance are no longer just technical diligence. They are aligned with the direction of EU policy.
This matters especially for Windows-heavy organizations considering deeper Azure commitments. The easiest architecture today can become tomorrow’s bargaining weakness. Microsoft’s integrated stack is genuinely powerful, but the more an organization relies on Azure-specific services, Microsoft-native security tooling, and Copilot-era workflows, the harder it may be to maintain credible exit options.
The same is true for AWS customers who have embraced managed services across the stack. A workload built on generic compute and open databases is one thing. A workload woven through proprietary eventing, analytics, machine learning, identity, monitoring, and serverless primitives is another. Portability is not a checkbox added at renewal time. It is an architectural discipline.
The irony is that multi-cloud strategies can also become expensive theater. Running everything across multiple providers for theoretical leverage may increase complexity without creating real freedom. The smarter move is selective portability: know which workloads must be movable, which dependencies are acceptable, and which vendor-specific services are worth the lock-in because they create measurable value.

Microsoft’s Old Antitrust Ghosts Have Learned Cloud Architecture

There is a historical echo here that Microsoft would rather avoid. In the late 1990s and early 2000s, the company’s antitrust problem was the Windows desktop monopoly and the use of that position to influence browsers and adjacent software markets. Today’s cloud fight is more abstract, but the pattern is recognizable: a dominant platform, adjacent services, bundling incentives, and regulators worried that rivals cannot get a fair route to customers.
The company is not the same as it was then. Satya Nadella’s Microsoft is more open, more cloud-native, and more comfortable competing on platforms it does not control. But Microsoft’s strategic instincts still favor integration, and integration is where antitrust attention gathers. The better Microsoft gets at making Azure the natural home for enterprise workloads, the more Brussels will ask whether “natural” is being engineered.
There is also a Windows-specific lesson. Microsoft’s desktop dominance once made the operating system the center of the regulatory universe. Now Windows is one piece of a broader enterprise fabric, but it still feeds Azure’s advantage through identity, endpoint management, server workloads, developer tools, and administrative habit. The center of gravity has shifted from the PC to the cloud control plane.
That shift changes the stakes for WindowsForum’s audience. The most important Microsoft platform decision in many organizations is no longer the version of Windows on the endpoint. It is the architecture of identity, management, security, data, and AI services around those endpoints. Azure is where much of that architecture now lives.
If the EU succeeds in imposing meaningful gatekeeper obligations, Microsoft may have to make that architecture more permeable. That could benefit customers and competitors. It could also create new compliance complexity, uneven regional features, and another layer of legal review around product changes. Regulation rarely produces only clean wins.

The Real Test Is Whether Brussels Can Regulate Without Freezing the Stack

The EU’s critics often portray Brussels as a bureaucracy that regulates what it cannot build. That line is too glib, but the underlying challenge is real. Cloud infrastructure evolves faster than traditional competition remedies. By the time regulators define a problematic practice, the market may have shifted to a new abstraction layer.
AI makes this problem worse. In cloud, the frontier is moving from virtual machines to managed services, then to platform services, then to model services, agents, and integrated workflow automation. If the Commission writes obligations around yesterday’s cloud primitives, it may miss tomorrow’s lock-in. If it writes broad obligations around “fairness” and “interoperability,” it may create uncertainty that only the largest legal departments can navigate.
That paradox is uncomfortable. Regulation intended to constrain hyperscalers can sometimes entrench them, because only hyperscalers have the staff to absorb compliance. Smaller providers may welcome constraints on AWS and Azure, but they may also struggle if the regulatory environment becomes more complex for everyone.
The Commission will need to avoid confusing openness with paperwork. A cloud market is not more competitive because customers receive longer disclosures or because providers publish migration guides nobody can use. The useful test is practical: can a serious customer move, interoperate, or mix providers without being punished by hidden costs, degraded functionality, or contractual traps?
If the answer improves, the DMA intervention may be justified. If the result is merely another compliance dashboard, the hyperscalers will grumble publicly and adapt privately, while customers see little change. The EU’s tech regulation record contains examples of both outcomes.

The Calendar Now Belongs to the Commission

The next phase is procedural but important. Amazon and Microsoft can inspect the Commission’s file, respond in writing, and try to rebut the preliminary findings. A final decision is expected in the coming months, and a confirmed designation would trigger a compliance period before obligations bite.
That timeline gives both companies room to shape the remedy conversation. They may offer commitments, emphasize existing portability tools, revise commercial terms, or argue that other EU laws already address the same concerns. Microsoft will almost certainly keep pointing to Google’s AI momentum. Amazon will keep warning that duplicative regulation risks slowing Europe’s access to advanced infrastructure.
For customers, the temptation is to wait for the final decision. That would be a mistake. The legal outcome matters, but the strategic signal has already arrived. European regulators now view hyperscale cloud as a gatekeeping layer in its own right, and that view will influence future procurement norms, complaints, investigations, and political expectations.
It will also influence product strategy. Microsoft and Amazon may begin adjusting European-facing cloud practices before they are forced to do so. Large vendors often prefer controlled preemption to dramatic enforcement. Watch for changes in migration programs, interoperability language, partner access, data-transfer commitments, and AI governance positioning.
The Commission, meanwhile, must show that this is not merely symbolic escalation. If it designates AWS and Azure but cannot define obligations that matter, the DMA’s cloud expansion will look like a jurisdictional flex. If it lands concrete remedies, it will mark one of the most consequential expansions of European digital regulation since the DMA began.

The Fine Print That Will Matter More Than the Press Release

The headline is that AWS and Azure may become DMA gatekeepers. The real story will be buried in implementation details, because cloud power is exercised through defaults, APIs, contracts, prices, and integration paths rather than a single obvious chokepoint.

AWS and Azure have only received preliminary findings, so the companies still have an opportunity to challenge the Commission before any final designation is made.
A confirmed DMA designation would likely force closer scrutiny of interoperability, data portability, switching costs, and self-preferencing across cloud services in Europe.
Microsoft faces a distinct risk because Azure’s value is tightly connected to Windows, Microsoft 365, Entra ID, Defender, GitHub, and Copilot-era AI services.
Amazon’s strongest defense is that cloud remains broad and competitive, but the Commission is focused on entrenched customer bases, scale, and lock-in rather than consumer-style market share alone.
Enterprise customers should treat the investigation as a reason to revisit portability assumptions, especially where AI services and managed cloud platforms are becoming deeply embedded.
The most important outcome will not be whether Brussels wins a headline fight, but whether customers gain practical freedom to move workloads, mix providers, and resist ecosystem pressure.

If the EU follows through, the DMA will have crossed a threshold from regulating the visible platforms of the consumer internet to regulating the invisible machinery of enterprise computing. That will not make AWS or Azure less central overnight, and it will not magically create a European hyperscaler capable of matching them. But it may force the cloud giants to compete with fewer escape hatches and fewer assumptions that technical dependency is simply the customer’s problem. For Microsoft, Amazon, and every IT department building the next decade of AI-enabled infrastructure, the message from Brussels is blunt: the cloud is no longer below the regulatory weather.

References

Primary source: The Express Tribune
Published: 2026-06-25T18:30:11.632208

EU targets Amazon, Microsoft cloud units for Big Tech “gatekeeper” rules

EU DMA designation may impose interoperability, data portability and self-preferencing limits on AWS and Azure

tribune.com.pk
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105

Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: euperspectives.eu

Whoever controls the cloud controls the future. Brussels wants to rein in Amazon and Microsoft - EU Perspectives

The European Commission is taking aim at Amazon and Microsoft's cloud dominance in a move that could reshape AI markets.

euperspectives.eu
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
Related coverage: europapress.es

Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio

La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...

www.europapress.es
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
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com

ChatGPT · Jun 26, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that its preliminary view is that AWS and Azure should be brought under the Digital Markets Act as gatekeeper cloud services in the European Union. That is not a final designation, but it is the clearest sign yet that Brussels no longer sees cloud infrastructure as plumbing beneath the digital economy. It sees cloud as the economy’s control layer. For WindowsForum readers, the story is not just whether two American hyperscalers face another compliance checklist; it is whether the rules governing app stores, browsers, and marketplaces are about to move into the server rooms where enterprise Windows, identity, AI, and data strategy now live.

Brussels Moves the DMA From Screens to Server Rooms

The Digital Markets Act was sold to much of the public as a law about the visible internet: app stores, search engines, social networks, messaging platforms, advertising systems, and operating systems. Those were the places where consumers could see gatekeeping in action. A browser choice screen, a default search deal, or an app store commission could be explained without a whiteboard.
Cloud computing is different. It is less visible, more technical, and far more embedded in the operational decisions of businesses and public administrations. Yet that is precisely why the European Commission’s move matters: it suggests regulators believe the next generation of digital lock-in is being built below the user interface, at the level of compute, storage, identity, data services, AI tooling, and managed platforms.
The Commission’s preliminary position is that Amazon Web Services and Microsoft Azure, the largest and second-largest cloud providers in the EU, act as important gateways between businesses and their customers even though they do not meet the DMA’s standard quantitative thresholds. That caveat is crucial. Brussels is not merely saying AWS and Azure are big; it is saying the law’s gatekeeper concept can reach services whose importance cannot be captured by a simple count of monthly active end users.
That is a major expansion in regulatory posture. The DMA was built around the idea that certain digital platforms become unavoidable bottlenecks. By applying that logic to cloud, the Commission is arguing that the infrastructure choices made by companies, developers, and governments may shape competition as decisively as the choices made by consumers on their phones.

The Thresholds Were Never the Whole Law

The DMA’s headline tests are familiar by now: large economic scale, a significant impact on the internal market, and enough users or business users to indicate gateway power. The commonly cited figures include more than 45 million monthly active end users in the EU and more than 10,000 yearly active business users. AWS and Azure, according to the Commission’s preliminary reasoning, do not satisfy those quantitative thresholds in the conventional way.
That might sound like a weakness in the EU’s case, but it is actually the point of the case. The DMA allows market investigations where a service appears to have gatekeeper power despite falling outside the standard numerical box. Cloud services expose why such a provision exists. A hyperscale cloud platform can influence millions of downstream users without those users ever logging directly into an AWS or Azure console.
A small business may buy software that runs on Azure. A hospital may rely on a vendor whose analytics stack sits on AWS. A public service may depend on a contractor whose authentication, database, and AI services are stitched together across one cloud ecosystem. In each case, the end user experiences the application, not the cloud provider beneath it.
That makes cloud a poor fit for consumer-style metrics. Counting direct users of a cloud console misses the web of dependencies that makes infrastructure strategically important. If the DMA is meant to address bottlenecks in digital markets, the Commission is effectively saying it must be able to see the bottleneck even when it is buried several layers down.

AWS and Azure Are Being Judged on Gravity, Not Just Size

The strongest part of the Commission’s argument is not that AWS and Azure are large. Everyone in enterprise IT already knows that. The more consequential claim is that both platforms have durable, entrenched positions reinforced by switching costs, ecosystem breadth, and the gravitational pull of adjacent services.
Cloud buyers rarely purchase raw compute in isolation anymore. They buy managed databases, identity integrations, developer pipelines, observability, security controls, data lakes, serverless functions, AI model access, compliance tooling, backup services, networking, and increasingly industry-specific platforms. The more services an organization adopts inside one cloud, the harder it becomes to move.
That is not always because of bad behavior. Some lock-in is the result of useful engineering. A managed database that removes operational burden is valuable precisely because it abstracts away complexity. A cloud identity service that integrates cleanly with Microsoft 365, Windows endpoints, and enterprise security tooling can make an administrator’s life easier. A proprietary AI workflow may be attractive because it delivers faster results than building everything from neutral components.
But regulators care about the cumulative effect. When convenience, integration, procurement inertia, data gravity, and skills availability all point in the same direction, the market can become contestable in theory while being sticky in practice. A rival may exist, but the cost of seriously considering that rival becomes too high for many customers.
This is where Microsoft faces a particularly delicate problem. Azure is not merely a cloud provider; it is part of a broader enterprise stack that includes Windows Server, Microsoft 365, Entra ID, Defender, GitHub, Visual Studio, Power Platform, Dynamics, and a rapidly expanding AI portfolio. The Commission’s preliminary cloud findings arrive in a world where Microsoft’s operating system and other services are already familiar territory for DMA scrutiny. For Brussels, Azure is not an island. It is a platform inside a platform company.

The AI Layer Makes Cloud Lock-In Harder to Pretend Away

The timing of the EU’s move is not accidental. Cloud has been central to enterprise computing for years, but AI has turned cloud infrastructure into a strategic choke point. Training, tuning, hosting, governing, and integrating AI systems all require compute, data access, security controls, and developer tooling. The cloud provider is increasingly the broker between an organization’s data and its AI ambitions.
That matters because AI services tend to deepen existing commitments. If a company builds internal copilots around one provider’s model catalog, vector databases, agent tooling, identity layer, governance features, and monitoring systems, switching cloud providers becomes more than a migration project. It becomes a redesign of the organization’s emerging AI operating model.
The Commission has explicitly linked AI tools and partnerships to cloud purchasing decisions. That is a sober reading of the market. AWS, Microsoft, and Google are no longer competing only on virtual machines and storage prices; they are competing on who can supply the most complete AI development and deployment environment. The more AI procurement is bundled into cloud procurement, the more cloud market power can influence the next wave of software competition.
Microsoft’s response points to the strategic sensitivity here. The company has warned that excluding Google Cloud and Gemini from equivalent scrutiny could distort the market. That is not a frivolous argument. Google is a major cloud and AI player, and any regulatory framework that focuses only on the top two providers risks freezing a picture of the market at one moment while the AI race is still moving.
But Microsoft’s complaint also reveals the bind hyperscalers are in. The companies want regulators to recognize competitive pressure when it helps their defense, but they also market themselves as uniquely comprehensive, secure, global, and AI-ready when selling to customers. The more indispensable a platform claims to be in the sales deck, the harder it is to sound like just another competitor when Brussels calls.

Europe’s Cloud Sovereignty Argument Is Finally Meeting Competition Law

For years, European cloud politics has been split between two conversations. One was about competition: switching costs, licensing terms, interoperability, and hyperscaler concentration. The other was about sovereignty: dependence on non-European providers, exposure to foreign legal regimes, and the strategic risk of outsourcing public and industrial infrastructure.
The DMA investigation pulls those conversations together. Brussels is not simply asking whether AWS and Azure are too successful. It is asking whether the structure of the cloud market gives a handful of companies too much influence over Europe’s digital future. That is why the case has sharper geopolitical edges than a normal antitrust file.
American officials and industry groups have repeatedly criticized European digital regulation as discriminatory or protectionist. From Washington’s perspective, the pattern is hard to miss: many of the companies designated under the DMA are American, and many of the obligations land on firms that dominate global technology markets. Cloud scrutiny of AWS and Azure will be read by some in the U.S. as another front in a regulatory campaign against American tech.
Europe’s reply is equally predictable: market power is market power, and the nationality of the provider does not make lock-in less real for European customers. The Commission can also point to the fact that European businesses, public administrations, and citizens increasingly depend on cloud services whose architecture, contractual terms, and ecosystems are controlled outside the bloc.
Both sides have a point, but neither point resolves the policy question. The EU’s challenge is to prove that DMA obligations can make cloud markets more open without turning digital sovereignty into disguised industrial policy. The U.S. challenge is to acknowledge that cloud concentration is not imaginary just because the leading firms are American.

The Windows Angle Is Bigger Than Azure

For this community, the obvious question is how much this matters to Microsoft customers. The answer is: more than it may first appear. Azure sits at the intersection of Windows infrastructure, identity, endpoint management, developer tooling, security operations, and now AI adoption. Any European regulatory pressure on Azure could ripple across the everyday architecture choices made by sysadmins and IT leaders.
Consider identity. Microsoft’s Entra platform, Windows sign-in experiences, Microsoft 365, Azure resources, Conditional Access policies, Defender integrations, and device management flows all reinforce one another. That integration is genuinely useful. It is also the kind of ecosystem density that makes regulators wonder whether rivals can compete on equal terms.
Consider licensing. Microsoft’s cloud licensing practices have already drawn criticism from European cloud competitors, particularly around the cost and complexity of running Microsoft software on non-Microsoft clouds. Even when a specific DMA proceeding is not directly about Windows Server licenses or Office workloads, the broader regulatory mood around Azure will inevitably be shaped by those complaints. Regulators do not evaluate cloud power in a vacuum; they look at the ways operating systems, productivity software, databases, and cloud services interact.
Consider developers. Azure is tightly connected to GitHub, Visual Studio, .NET, Windows development workflows, and Microsoft’s AI coding push. A developer can move quickly when the stack is integrated from source control to deployment to monitoring. But that smooth path can become a paved road away from alternatives if interoperability and portability are weak.
The irony is that Microsoft’s enterprise strength has always been integration. Windows won because it became the default environment where hardware makers, software vendors, administrators, and users could expect things to work together. Azure extends that logic into the cloud era. The EU’s concern is not that integration exists; it is that integration can become gatekeeping when customers cannot realistically leave.

AWS Has a Different Problem, but the Same Regulatory Shadow

AWS does not carry Microsoft’s Windows legacy, but it has its own version of ecosystem gravity. It built the modern cloud market, expanded aggressively across service categories, and became the default vocabulary for many developers and architects. For a generation of cloud-native teams, AWS is not just a provider; it is the reference model.
That gives AWS a powerful defense and a vulnerability. The defense is that cloud customers are often technically sophisticated and can choose among many providers, architectures, and deployment models. AWS can argue, as it has, that European customers face a broad range of cloud options and that the sector is already covered by extensive rules.
The vulnerability is that practical choice is not the same as theoretical choice. A company with years of workloads built around AWS IAM, S3, Lambda, DynamoDB, CloudFormation, EKS, and a long list of managed services may have alternatives on paper, but migration can be expensive, risky, and operationally disruptive. The deeper the dependency, the less credible it becomes to say the customer can simply switch.
AWS also has to contend with Europe’s sovereignty mood. The company has invested in sovereign cloud offerings and European infrastructure commitments, but those moves can cut both ways. They show responsiveness to European concerns, yet they also underscore how central AWS has become to sensitive workloads. A provider does not build sovereign variants unless customers and governments already see the platform as strategically important.

The DMA May Be a Blunt Instrument for a Subtle Market

The most serious criticism of the Commission’s approach is not that cloud markets are perfectly competitive. They are not. The better criticism is that the DMA was designed around platform conduct that may not map cleanly onto infrastructure services.
Rules about self-preferencing, data access, interoperability, tying, and fair access make intuitive sense when applied to app stores or marketplaces. Cloud is messier. A cloud provider’s managed services are often differentiated precisely because they are deeply integrated. Requiring interoperability sounds attractive until engineers have to define what meaningful portability looks like across databases, AI services, security models, networking constructs, and identity systems.
There is also a risk that compliance favors the largest firms. If DMA obligations become a dense layer of legal, technical, and reporting requirements, AWS and Microsoft can afford the teams needed to comply. Smaller European providers may gain some competitive openings, but they may also face a market where customers demand DMA-style assurances from everyone, raising the cost of participation.
Still, the alternative is not regulatory purity. The status quo already imposes costs. Enterprises pay in migration complexity, contractual opacity, skills concentration, and architectural dependence. Public administrations pay in sovereignty risk and procurement lock-in. Developers pay when platform-specific convenience becomes a long-term constraint.
The question is not whether the DMA is a perfect fit. It is whether regulators can use it surgically enough to improve contestability without damaging the cloud features customers actually value.

The Google Omission Will Haunt the Case

The Commission’s decision not to pursue the same preliminary gatekeeper finding against Google Cloud is one of the most politically and analytically important parts of the story. Google is the third major hyperscaler, and its AI assets are plainly relevant to cloud competition. Microsoft is therefore unsurprising in warning that ignoring Google Cloud and Gemini could tilt the market in harmful ways.
The Commission’s likely answer is that dominance matters, and AWS and Azure occupy the top two positions in the EU cloud market. If the evidence shows that they have more entrenched and durable positions than Google, then unequal treatment may be justified. Competition law often begins with market structure, not with a desire to regulate every large player symmetrically.
But cloud and AI are converging quickly. Google’s strength in AI research, model development, data infrastructure, and developer tooling could make it more competitively significant than its cloud market share alone suggests. If the DMA analysis underweights that trajectory, the Commission could end up regulating yesterday’s cloud hierarchy while tomorrow’s AI-cloud hierarchy takes shape.
There is also a practical market concern. If AWS and Azure face obligations that Google Cloud does not, some customers may see Google as a less encumbered alternative. That could increase competition against the top two, which Brussels may welcome. But if the regulatory asymmetry changes purchasing behavior for reasons unrelated to product quality or openness, the EU will invite accusations that it is steering the market rather than opening it.
This does not mean Google must be included automatically. It means the Commission will need to explain, in unusually clear terms, why the line is drawn where it is. In a market defined by rapid AI-driven change, a static ranking will not be enough.

Enterprise IT Should Read This as a Portability Warning

The immediate legal process will take months. Amazon and Microsoft can respond to the preliminary findings, inspect the Commission’s file, and argue against designation before a final decision. If the Commission confirms the findings, the companies would then face DMA obligations and a compliance timeline.
For enterprise IT leaders, waiting for the legal endpoint would be a mistake. The regulatory direction is already visible. Brussels is telling customers that cloud dependency is no longer just an architecture decision; it is a competition and sovereignty issue.
That does not mean organizations should panic-migrate away from AWS or Azure. Most should not. Hyperscale cloud platforms remain deeply capable, and for many workloads they are the rational choice. The lesson is subtler: every new managed service, AI integration, proprietary data layer, and identity dependency should be evaluated not only for immediate productivity but for future exit cost.
A serious cloud strategy in 2026 needs a portability ledger. Which workloads can move? Which data formats are open? Which services have credible substitutes? Which identity, security, and observability assumptions are provider-specific? Which AI workflows would be painful to rebuild elsewhere?
Those are not anti-cloud questions. They are mature-cloud questions. The EU’s preliminary findings simply make public what experienced architects already know: the cheapest migration is the one you plan before you need it.

The Cloud Contract Is Becoming a Regulatory Document

If the Commission follows through, the most visible changes may not be dramatic product redesigns. They may appear in contracts, documentation, APIs, admin controls, audit trails, data portability features, and procurement language. That is where cloud power is often exercised, and that is where cloud competition may be won or lost.
A few concrete implications stand out.

AWS and Azure are not yet finally designated under the DMA, but the Commission’s preliminary position makes cloud infrastructure a live target for Europe’s gatekeeper regime.
The case matters because cloud platforms influence downstream markets even when end users never interact directly with the cloud provider.
AI has made cloud lock-in more consequential by tying compute, data, models, governance, and developer tools into single-provider ecosystems.
Microsoft faces special scrutiny because Azure connects to Windows, Microsoft 365, identity, security, developer tools, and AI services in ways that few competitors can match.
Google Cloud’s exclusion from the preliminary findings will remain a pressure point if AI reshapes cloud competition faster than regulators update their market analysis.
Enterprise customers should treat portability, interoperability, and exit planning as board-level risk controls rather than optional architecture hygiene.

The deeper story is that cloud computing has crossed a political threshold. It is no longer just a place to run workloads or rent capacity. It is the terrain on which software competition, AI adoption, public-sector resilience, and digital sovereignty are now being negotiated. AWS and Azure may yet persuade Brussels to narrow or abandon its preliminary view, but the broader argument will not go away. The next era of cloud regulation will be fought less over whether hyperscalers are useful, because they plainly are, and more over whether usefulness has hardened into dependency that only law can loosen.

References

Primary source: Digital Watch Observatory
Published: Fri, 26 Jun 2026 09:39:19 GMT

EU targets AWS and Azure under the DMA | Digital Watch Observatory

Amazon and Microsoft face stronger EU oversight as cloud infrastructure becomes critical to AI development.

dig.watch
Independent coverage: Qatar Tribune
Published: 2026-06-26T00:30:08.603733

EU opens door to DMA rules for Amazon and Microsoft cloud units - Read Qatar Tribune on the go for unrivalled news coverage

AgenciesThe EU said Thursday that the cloud services of Amazon and Microsoft should face tougher digital competition rules in Europe because of their dominant position in the...

www.qatar-tribune.com
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: itif.org

EU’s Designation of AWS and Azure as Core Platform Services Escalates Weaponization of Digital Markets Act, Says ITIF | Press Releases | Jun 25, 2026 | ITIF

The European Commission is stretching the DMA to target cloud infrastructure, raising the stakes for U.S.-EU tech tensions.

itif.org
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: europapress.es

Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio

La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...

www.europapress.es

Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
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
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105
Related coverage: euronews.com

Brussels tightens rules on US cloud providers as it pushes for tech sovereignty | Euronews

The European Commission has decided that Microsoft Azure and Amazon Web Services should face strict rules to improve cloud competition. The move risks angering Washington as Brussels pushes the European tech sovereignty agenda.

www.euronews.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: itpro.com

What the new AWS European Sovereign Cloud means for enterprises | IT Pro

AWS has announced the general availability of its European Sovereign Cloud, offering EU-based customers stringent data residency and protection controls.

www.itpro.com

ChatGPT · Jun 26, 2026

On June 25, 2026, the European Commission said Amazon Web Services and Microsoft Azure should be designated as Digital Markets Act gatekeepers, a preliminary Brussels finding that would pull cloud infrastructure into the EU’s strictest Big Tech competition regime. The move is not final, but it is already a strategic escalation. Europe is no longer treating cloud as plumbing beneath the digital economy; it is treating cloud as the control plane for everything above it.
That distinction matters more than the familiar “Big Tech regulation” headline suggests. The original DMA battles were about app stores, search defaults, browsers, messaging, ads, and social networks — visible choke points where consumers could see the lock-in. The AWS and Azure case says the most important choke points may now sit deeper in the stack, inside the databases, identity systems, AI accelerators, developer tools, data lakes, and managed services that modern businesses cannot easily abandon.

Brussels Moves the Gatekeeper Fight Below the User Interface

The Commission’s preliminary view is simple enough: AWS and Azure are not merely large cloud providers, but essential gateways between European businesses and their customers. That is the legal and political hinge. If cloud infrastructure becomes a “core platform service” under the DMA in practice, then Brussels has decided that market power in the digital economy is not confined to consumer-facing platforms.
That is a meaningful shift. Until now, the DMA’s public identity has been shaped by fights over Apple’s App Store, Google Search, Meta’s messaging ecosystem, Amazon Marketplace, and Microsoft’s Windows-adjacent services. Cloud was always in the statutory orbit, but it did not sit at the emotional center of the debate because consumers do not usually choose a hyperscaler the way they choose a phone, browser, or social app.
Enterprise users, however, know the lock-in story intimately. An organization does not merely rent compute from AWS or Azure. It builds around IAM policies, storage semantics, monitoring tools, network constructs, proprietary databases, serverless runtimes, AI services, marketplace procurement, cost models, support contracts, and compliance paperwork. Migration is rarely a clean “switch”; it is usually a multi-year refactoring project disguised as procurement.
That is why the Commission’s framing leans heavily on interoperability, data portability, self-preferencing, switching costs, entrenched user bases, and AI partnerships. These are not consumer-rights slogans lifted from the app-store wars. They are the vocabulary of cloud architecture, and they point to a more technical, more consequential enforcement frontier.

The DMA Was Built for Platforms, and Cloud Has Become the Platform

The cloud market has long resisted tidy competition-law metaphors. AWS, Azure, and Google Cloud do not resemble a single app store or a social network feed. They sell thousands of services, from commodity virtual machines to advanced AI tooling, and customers range from one-person startups to global banks.
Yet that complexity is exactly why regulators are circling. The more cloud providers become bundles of infrastructure, software, security tooling, AI models, data platforms, and procurement channels, the more they begin to function as operating systems for companies. Windows once defined the boundaries of the PC software world. Hyperscale cloud now defines the boundaries of enterprise application strategy.
The DMA’s gatekeeper concept was designed for companies that control access between business users and end users. In the early 2020s, that mainly meant platforms that mediated consumer attention and transactions. By 2026, the argument is harder to contain there, because the path between a business and its customers increasingly runs through hyperscale infrastructure.
A retailer’s checkout, a bank’s fraud model, a hospital’s analytics stack, a game studio’s backend, and a software vendor’s subscription platform may all depend on cloud services that are expensive to move and difficult to replicate elsewhere. If those services are bundled with preferential AI access, integrated developer environments, privileged marketplace placement, or proprietary data tooling, the cloud provider can shape competition without ever showing the end user a search result or app-install prompt.
This is the Commission’s real bet: that infrastructure markets can produce gatekeepers even when the “gate” is invisible to ordinary users.

AWS and Azure Are Being Judged by Gravity, Not Just Thresholds

One of the striking details in the Commission’s preliminary conclusion is that AWS and Azure are being targeted despite not meeting the DMA’s usual quantitative thresholds for designation as cloud gatekeepers. That does not mean Brussels is ignoring the law. It means the Commission is using the DMA’s investigative pathway to argue that raw user-count formulas are a poor fit for cloud.
That is defensible, though controversial. Cloud services do not map neatly onto monthly active users in the way social networks or messaging apps do. One enterprise customer can represent millions of downstream users, terabytes of business-critical data, and years of operational dependency. Counting individual “users” risks underestimating the market power created by large business accounts.
The Commission instead points to turnover, operational capacity, investments, entrenched user bases, lock-in effects, high switching costs, and the role of AI tools and partnerships in procurement. In plain English, Brussels is saying that the force of a cloud platform is measured by gravity. The bigger the ecosystem, the more services orbit it, and the harder it becomes for customers to escape the pull.
AWS and Azure are natural targets under that logic. AWS created much of the modern public-cloud model and remains the sector’s defining reference point. Azure, meanwhile, is deeply woven into Microsoft’s enterprise base through Windows Server history, Active Directory lineage, Microsoft 365, GitHub, Visual Studio, security tooling, and hybrid-cloud management. They are different machines, but both benefit from ecosystems that extend well beyond compute and storage.
The Commission’s mention of AI procurement is especially important. In 2026, cloud decisions are increasingly AI decisions. Companies choosing where to train, fine-tune, deploy, secure, and govern AI workloads are also choosing which cloud platform will hold the next layer of strategic dependency.

Microsoft’s Google Argument Is Clever, but It Cuts Both Ways

Microsoft’s response is politically sharp: if Brussels ignores Google Cloud and Gemini, it may tilt the market in a harmful way. The company is not wrong to point out that Google is a serious cloud and AI competitor. Google has formidable AI infrastructure, deep research credibility, and a cloud business that has matured well beyond its old “distant third” caricature.
But Microsoft’s argument has two layers. The first is a competition claim: do not regulate two players in a way that strengthens a third. The second is a strategic claim: cloud and AI markets are converging so quickly that yesterday’s cloud-share snapshot may be a bad guide to tomorrow’s power. Both deserve attention.
The problem for Microsoft is that those arguments also validate the Commission’s broader concern. If AI tooling is already powerful enough to reshape cloud procurement, then cloud is no longer a neutral infrastructure market. It is a battleground where model access, data gravity, developer ecosystems, enterprise contracts, and compute capacity reinforce one another.
Google’s rise may complicate the Commission’s target list, but it does not make AWS and Azure irrelevant as gatekeeper candidates. A market can be dynamic and still have gatekeepers. In fact, dynamic markets can make gatekeeper power more consequential, because early architectural choices harden into long-term dependencies before buyers fully understand the cost of exit.
There is also an uncomfortable asymmetry. Microsoft wants Brussels to consider Google’s growing power, while Amazon warns that more regulation could deter investment and innovation. Both arguments may be true in part. But neither directly answers the customer-side problem: what happens when a European business decides its cloud architecture is no longer a commercial choice, but a dependency it cannot practically unwind?

Amazon’s Overlap Complaint Lands in a Crowded Regulatory Room

AWS says Europe already has comprehensive cloud regulation through the Data Act and that layering DMA obligations on top risks undermining competitiveness and access to cutting-edge IT. This is not just corporate grumbling. Europe’s digital rulebook is crowded, and cloud providers already face a dense mix of cybersecurity, data, resilience, procurement, privacy, and sector-specific obligations.
The overlap problem is real. The Data Act includes cloud-switching and data-access provisions. The Cyber Resilience Act, NIS2, DORA, GDPR, AI Act, and sectoral compliance regimes all touch different parts of the same enterprise technology stack. Add DMA obligations, and legal departments will spend years determining where one duty ends and another begins.
But AWS’s argument also reveals why Brussels is acting. The Data Act can make switching rights more explicit, but the DMA is about structural platform power. A cloud provider can comply with data-export rules while still making its best databases, AI services, identity integrations, support discounts, and marketplace economics work most naturally inside its own ecosystem. Portability of data is necessary, but it is not the same thing as portability of architecture.
That is the difference between moving the contents of a house and moving the house itself. Enterprises can export data from one platform and still face a brutal rewrite of application logic, security models, automation pipelines, monitoring, backup, disaster recovery, and audit processes. The Commission appears to be looking at that broader lock-in pattern, not merely file transfer.
AWS is also right that regulation can slow deployment or discourage investment if obligations are vague or punitive. Europe has a long-running problem of wanting more indigenous cloud capacity while relying heavily on American hyperscalers to deliver the performance, breadth, and scale European enterprises require. The hard policy question is whether contestability rules can reduce dependency without making the best infrastructure harder to use.

The Real Target Is Not Compute, It Is Managed Dependency

If this case were only about virtual machines and object storage, it would be much less explosive. Compute and storage are already more portable than they used to be, even if not frictionless. The modern lock-in frontier is managed services.
Managed databases, analytics engines, serverless functions, event buses, AI APIs, security dashboards, observability platforms, proprietary accelerators, and automated compliance tooling are where convenience becomes dependency. Each service saves engineering time. Each also creates assumptions that applications carry forward like genetic code.
This is the bargain cloud customers willingly made. They traded the pain of running everything themselves for a faster path to deployment, scaling, security, and innovation. For startups, that bargain can be existential. For large enterprises, it can compress a three-year infrastructure program into a procurement cycle and a few architecture reviews.
The DMA challenge is that market power can hide inside convenience. A hyperscaler does not need to block a customer from leaving if leaving means rewriting half the stack. It does not need to forbid interoperability if the most useful integrations are best inside the home cloud. It does not need to self-preference crudely if pricing, credits, support, data-egress economics, marketplace incentives, and AI bundling all nudge customers toward deeper commitment.
Regulators often struggle with technical lock-in because it is not always abusive in the narrow sense. Sometimes it is simply the residue of good engineering, product integration, and customer demand. The Commission will have to distinguish harmful enclosure from legitimate platform design, and that is much harder than ordering a messaging app to open an interface.

AI Turns Cloud Lock-In Into Industrial Policy

The phrase “tech sovereignty” can sound like Brussels boilerplate, but in the cloud-and-AI context it has concrete meaning. If European companies build their AI systems on a handful of non-European hyperscale platforms, then Europe’s industrial strategy becomes dependent on foreign infrastructure, foreign model partnerships, foreign hardware supply chains, and foreign platform roadmaps.
That does not mean American cloud providers are villains. AWS and Azure have invested heavily in European data centers, local jobs, compliance tooling, security capabilities, and sovereign-cloud offerings. Many European businesses use them because they are very good at what they do. The concern is not merely nationality; it is leverage.
AI increases that leverage. Training and running advanced models requires immense compute capacity, specialized chips, data pipelines, model governance, developer frameworks, and security controls. Hyperscalers are among the few companies capable of packaging all of that at scale. Once AI services become part of cloud procurement, the platform choice starts to shape which models are practical, which data architectures are favored, and which vendors get privileged routes to customers.
This is why the Commission’s focus on AI tools and partnerships is not a side note. The cloud market is becoming the distribution layer for enterprise AI. A provider that can bundle compute credits, model access, database integration, productivity software, identity management, security, and marketplace procurement can influence the AI stack from top to bottom.
For WindowsForum readers, Microsoft’s position is particularly interesting because Azure is not just a cloud brand. It is tied to Entra ID, Microsoft 365, Windows Server estates, Defender, Sentinel, GitHub, Visual Studio, Power Platform, Copilot services, and a vast partner channel. Azure’s strength is not merely that it rents infrastructure. It is that it sits inside the operational bloodstream of the Microsoft enterprise customer.

Windows Shops Should Watch the Compliance Details, Not Just the Politics

For IT administrators and enterprise architects, the immediate effect is limited because the Commission has issued preliminary findings, not final obligations. Amazon and Microsoft can respond before a final decision. If the Commission confirms the designation, the DMA compliance clock would begin, and the practical obligations would become the story.
The likely areas to watch are interoperability, data portability, anti-steering, self-preferencing, access conditions, and technical documentation. That sounds abstract until it meets a real IT estate. A company running Windows Server workloads in Azure, identity through Entra ID, endpoints through Intune, analytics through Fabric, code through GitHub, and AI features through Copilot-adjacent services may eventually see changes in contracts, APIs, migration tools, pricing transparency, or integration terms.
The same goes for AWS-heavy shops that rely on IAM, S3, RDS, Lambda, CloudWatch, Bedrock, and marketplace procurement. A DMA designation could push AWS to clarify portability guarantees, avoid favoring its own services in ways regulators deem unfair, or make certain interfaces more open. But the line between “open enough” and “platform redesign” will be fought hard.
Admins should not expect magic portability. No regulation can turn a complex cloud-native application into a drop-down menu choice between hyperscalers. Kubernetes helped abstract some compute patterns, but data services, identity, networking, security operations, observability, and AI workflows remain deeply platform-specific. The best case for customers is not effortless switching; it is reduced penalty for credible multi-cloud, hybrid, or exit strategies.
Procurement teams may benefit sooner than engineers. If the DMA pressure forces clearer terms around lock-in, egress, bundling, interoperability, or marketplace conditions, buyers gain leverage. That matters because cloud cost and architecture decisions often become inseparable; a discount that looks attractive in year one can become a strategic constraint by year five.

Europe Wants Competition Without Losing the Cloud Race

The Commission’s challenge is that it is trying to solve two problems that pull in opposite directions. Europe wants fairer cloud markets, more interoperability, and less dependence on a few American hyperscalers. It also wants enormous investment in data centers, AI compute, sovereign infrastructure, and high-end digital services.
Regulation can support that goal if it makes the market more contestable. Smaller European cloud providers have long complained that customers are locked into hyperscaler ecosystems through proprietary services, data-egress costs, committed-spend contracts, software licensing rules, and procurement inertia. If DMA enforcement reduces those barriers, European providers could win more specialized workloads and participate in hybrid architectures.
But regulation can also backfire if it turns into a compliance tax that only the largest firms can absorb. The DMA is aimed at gatekeepers, not smaller rivals, but large platforms often respond to regulatory complexity by standardizing offerings, delaying features, or limiting regional availability. European customers have already seen versions of this dynamic in other technology markets, where compliance uncertainty can slow rollout.
That is why the Commission must be precise. “Do not self-preference” is easy to say in a marketplace context and harder to apply to cloud engineering. Is a native database integration self-preferencing or product quality? Is a discounted bundle anti-competitive or customer value? Is a proprietary AI accelerator a moat or an innovation? These are not rhetorical traps; they are the enforcement questions that will decide whether this case helps customers or merely produces paperwork.
The best version of the EU approach would focus on measurable harms: punitive switching costs, opaque contractual barriers, exclusionary licensing, unfair marketplace ranking, discriminatory access to APIs, and portability claims that collapse under real-world testing. The worst version would punish integration itself, which is one of the reasons customers use hyperscale cloud in the first place.

The Old App-Store War Was Easier Than This

The consumer-platform DMA fights were messy, but at least their shape was legible. App stores had fees, review rules, alternative payment restrictions, default settings, browser engines, and sideloading debates. The cloud fight is more technical and less visible, which makes it both more important and easier to mishandle.
Cloud gatekeeping is a systems problem. A hyperscaler’s power comes from the interaction of services, contracts, support, developer familiarity, compliance certifications, regions, chips, partners, and procurement channels. No single lever explains it. No single remedy will unwind it.
That complexity gives the providers a strong defense. They can argue that customers choose integrated services because they work, that switching costs reflect legitimate engineering realities, and that aggressive regulation will weaken the very platforms European companies rely on. They can also point to Google Cloud, Oracle, IBM, European sovereign-cloud projects, on-premises modernization, and open-source tooling as evidence that the market is not sealed.
The Commission’s counter is that formal alternatives do not guarantee practical contestability. A customer may have choices on paper while facing prohibitive migration costs in reality. The existence of competitors does not eliminate gatekeeper power if the dominant platforms remain unavoidable reference points for the most important workloads.
This is where the case will live or die: not in slogans about Big Tech, but in evidence about how customers actually buy, build, and leave cloud services.

The Sovereign Cloud Dream Meets the Hyperscaler Reality

Europe’s cloud debate is haunted by a contradiction. Policymakers want sovereign capability, but the continent’s enterprises often want the breadth, maturity, global reach, and AI capacity of AWS, Azure, and Google Cloud. Sovereignty is appealing in speeches; procurement teams still have uptime targets, talent constraints, integration needs, and product deadlines.
That is why sovereign-cloud initiatives frequently end up partnering with the very hyperscalers they are meant to counterbalance. Local control, legal assurances, and European operations can reduce some risks, but the underlying technology stack may still depend on American platform engineering. This is not hypocrisy so much as market reality.
The DMA move should be read against that background. Brussels may not believe it can replace AWS and Azure with European equivalents in the near term. Instead, it may be trying to prevent hyperscaler dependency from becoming irreversible just as AI infrastructure raises the stakes. If Europe cannot own the whole stack, it can at least regulate the terms on which the stack is accessed.
That is a more pragmatic version of sovereignty. It does not promise a sudden European AWS. It seeks leverage: more portable data, more interoperable services, fairer procurement conditions, and fewer contractual or technical traps that make exit impossible. Whether that leverage is enough is another matter.
The risk is that sovereignty becomes a catch-all justification for intervention without a clear theory of customer benefit. If the Commission wants durable support from IT buyers, it must show that the rules improve operational freedom rather than merely satisfying geopolitical anxiety. Enterprises will tolerate regulation that gives them bargaining power. They will resent regulation that reduces service quality, delays features, or complicates architectures without delivering practical alternatives.

The Fight Will Be Won in Definitions

The coming months will likely be consumed by definitions. What exactly counts as the cloud computing service subject to designation? Which Azure and AWS features are in scope? How do obligations apply across infrastructure, platform services, AI services, marketplaces, and partner ecosystems? Where does a cloud service end and an enterprise software product begin?
For Microsoft, those boundaries are especially sensitive. Azure is deeply connected to Microsoft’s broader enterprise stack. If regulators examine Azure in isolation, they may miss the way Microsoft’s identity, productivity, security, developer, and AI businesses reinforce it. If they define the scope too broadly, they risk turning a cloud case into a sprawling review of Microsoft’s enterprise ecosystem.
Amazon’s case is different but no less complex. AWS is a vast service catalog with its own marketplace, support structures, AI offerings, and partner network. It is less tied to a desktop operating system or productivity suite than Azure, but it is extraordinarily deep as a cloud-native platform. Its lock-in profile is architectural rather than office-suite-driven.
Google’s absence from the preliminary target list will remain a pressure point. If Google Cloud and Gemini continue to gain strategic influence, Brussels may face accusations that it regulated yesterday’s market structure. If Google remains materially smaller in European cloud procurement than AWS and Azure, the Commission will argue that different treatment is justified.
Either way, the cloud sector is now on notice. The Commission has signaled that being below a numerical threshold is not necessarily a safe harbor if a platform’s practical role in the economy is large enough.

The Practical Stakes Are Hidden in Tomorrow’s Architecture Reviews

For most businesses, this story will not change Monday morning’s incident queue. There will be no immediate mass migration, no sudden Azure redesign, no overnight AWS pricing revolution. The more realistic effect is slower and more institutional: legal teams, procurement departments, cloud centers of excellence, and architecture review boards will start asking sharper questions.
Those questions were already overdue. What would it cost to move a critical workload? Which services are portable and which are not? Are discounts tied to commitments that narrow future options? Does an AI roadmap assume one model provider, one data platform, or one hyperscaler? Are backups, observability, identity, and security controls genuinely separable from the primary cloud?
Regulation may give those conversations more force, but it cannot substitute for architecture discipline. Enterprises that want leverage need to design for it. That may mean using open standards where practical, containerizing selectively, avoiding unnecessary proprietary dependencies, maintaining tested export paths, negotiating exit terms, and resisting the temptation to treat cloud credits as strategy.
Still, there is a limit to purity. A company that avoids every proprietary managed service may preserve portability at the cost of speed, reliability, and engineering efficiency. The point is not to make every workload cloud-agnostic. The point is to know which dependencies are deliberate and which were acquired by accident.
The Commission’s intervention may help by making those accidental dependencies more visible. If AWS and Azure are forced to document, expose, or soften some of the edges that make switching painful, customers can make better decisions. But the hard work of deciding when integration is worth lock-in will remain with IT leadership.

The Cloud Gatekeeper Case Gives IT a New Negotiating Script

The immediate lesson for WindowsForum’s audience is not to panic, but to prepare. A preliminary DMA finding is not a final compliance regime, and the providers will fight hard to shape the outcome. But the direction of travel is clear enough that enterprise customers should treat portability, interoperability, and AI dependency as board-level architecture issues rather than cleanup tasks for some future migration.

The Commission’s June 25 preliminary finding targets AWS and Azure because Brussels sees cloud infrastructure as a gateway for European businesses, not merely a back-end utility.
A final DMA designation would likely put pressure on Amazon and Microsoft around interoperability, data portability, self-preferencing, switching barriers, and cloud-AI bundling.
Microsoft’s warning about Google Cloud and Gemini highlights a real uncertainty, but it also reinforces the Commission’s point that AI is changing cloud market power.
AWS’s concern about overlapping EU regulation is credible, yet data-portability rules alone do not solve architectural lock-in inside managed cloud ecosystems.
Windows-heavy enterprises should pay special attention to Azure’s ties with identity, endpoint management, developer tooling, security services, and AI features, because those integrations are where convenience and dependency often merge.
The best customer response is not blanket multi-cloud theater, but a sober inventory of which workloads can move, which cannot, and which commercial terms make that difference more expensive over time.

The EU’s cloud gatekeeper push is not just another Brussels-versus-Big-Tech skirmish; it is an acknowledgment that the next decade of digital power will be exercised through infrastructure, AI distribution, and enterprise dependency as much as through consumer apps. If the Commission can translate that insight into precise, technically literate obligations, European customers may gain leverage without losing access to world-class platforms. If it cannot, the cloud market will absorb another layer of legal friction while the real architecture of lock-in continues to harden underneath.

References

Primary source: 1470 & 100.3 WMBD
Published: 2026-06-25T20:30:08.946065

EU targets Amazon, Microsoft cloud units for Big Tech “gatekeeper” rules | 1470 & 100.3 WMBD

By Foo Yun Chee BRUSSELS, June 25 (Reuters) - EU antitrust regulators said Amazon and Microsoft's cloud computing services should be designated as “gatekeepers” under landmark tech rules, a step that would subject them to strict obligations aimed at c...

wmbdradio.com
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105

Related coverage: 2eu.brussels

European Commission wants Amazon Web Services and Microsoft Azure brought under Digital Markets Act rules

The European Commission has taken the preliminary view that Amazon Web Services and Microsoft Azure should be designated as gatekeepers under the Digital Markets Act because they have become essential gateways between businesses and customers in Europe’s digital economy. The decision could bring...

2eu.brussels
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: europapress.es

Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio

La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...

www.europapress.es
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
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
Related coverage: itpro.com

European Commission awards digital sovereignty contracts, backs Google Cloud involvement | IT Pro

The Commission has picked four providers to offer services for EU bodies, but one consortium includes Google Cloud

www.itpro.com

ChatGPT · Jun 26, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that it had preliminarily concluded Amazon Web Services and Microsoft Azure should be designated as cloud “gatekeepers” under the Digital Markets Act, exposing both businesses to stricter EU competition obligations after a seven-month investigation. The move is still provisional, and both companies can argue their case before Brussels makes a final decision. But the direction of travel is unmistakable: Europe now sees cloud infrastructure not as a neutral utility layer, but as a control point in the digital economy. For Microsoft customers, that makes Azure’s regulatory status as strategically important as any Windows, Office, or security update.

Brussels Has Found the Platform Beneath the Platforms

The Digital Markets Act was sold to the public largely through familiar consumer examples: app stores, search engines, social networks, browsers, messaging services, and online marketplaces. Cloud computing felt less visible because it does not sit on a phone home screen or shout for attention in a browser tab. Yet for modern businesses, cloud is often the platform that decides what can be built, how quickly it scales, and how difficult it is to leave.
That is why the Commission’s preliminary finding matters. AWS and Azure may not have met the DMA’s usual quantitative thresholds for gatekeeper designation in cloud, but Brussels argues that they function as crucial gateways between businesses and customers in the European Union. In plain English, the Commission is saying that market power can exist even when the spreadsheet test does not automatically trigger.
This is an important philosophical shift. The DMA was designed as an ex ante regime — a rulebook meant to prevent unfair conduct before markets tip beyond repair. Applying that logic to cloud means regulators are no longer waiting for disputes over pricing, licensing, data movement, or interoperability to become isolated antitrust cases years after the damage is done.
For Microsoft, this is familiar terrain with a new stack. The company has spent decades learning that dominance in one layer of computing invites scrutiny in the next. Windows made the browser fight possible; Office made document formats political; Azure now makes infrastructure procurement a sovereignty issue.

Azure Is No Longer Just Microsoft’s Growth Engine

Microsoft’s cloud business has become the gravitational center of the company. Azure is not merely a hosting platform for virtual machines and databases; it is the delivery mechanism for Microsoft’s enterprise identity, security, developer tooling, analytics, and AI ambitions. When an organization chooses Azure, it often chooses a much broader Microsoft operating environment.
That is precisely what makes the Commission’s theory powerful. The concern is not simply that Azure is large. The concern is that Azure is large, deeply integrated, and surrounded by services that make migration costly in both technical and organizational terms.
In a Windows-heavy enterprise, Azure can feel less like an outside provider than a continuation of the existing estate. Active Directory becomes Entra ID. System management becomes Intune. File and productivity workflows become Microsoft 365. Security telemetry flows into Defender and Sentinel. Developers build with Visual Studio, GitHub, Azure DevOps, and increasingly AI-assisted tooling attached to the same ecosystem.
None of that is inherently abusive. In fact, the integration is often the point. Microsoft’s pitch to CIOs is that complexity decreases when identity, endpoint management, productivity, security, and cloud infrastructure are coordinated through one vendor. The Commission’s emerging concern is that the same coordination can become a moat when customers later want pricing leverage, technical optionality, or a credible exit path.

AWS Is the Benchmark, but Microsoft Is the More Entangled Story

Amazon Web Services remains the defining company of the modern cloud era. It created the vocabulary of elastic infrastructure, turned internal capability into a public platform, and forced the enterprise technology market to reorganize around consumption-based computing. Its scale in Europe makes it an obvious target for gatekeeper analysis.
Microsoft’s case is different because Azure sits inside a much broader enterprise dependency chain. AWS may dominate cloud-native architecture in many sectors, but Microsoft reaches into desktops, productivity suites, developer workflows, identity systems, collaboration platforms, and compliance dashboards. That makes Azure’s market influence harder to isolate.
This is why Microsoft’s response reportedly pointed to Google Cloud and Gemini as evidence that the Commission is underestimating competitive pressure. It is not a frivolous argument. Google is a serious cloud and AI provider, and its AI brand has become much more relevant to enterprise procurement than it was a few years ago.
But Brussels appears to be looking less at whether Google can compete in the abstract and more at whether AWS and Azure already occupy durable positions that customers cannot easily route around. In that frame, the question is not whether there are three hyperscalers. The question is whether two of them have become default infrastructure for too many European businesses to treat them like ordinary suppliers.

The DMA Moves From App Stores to Data Centers

The political symbolism of this action is hard to miss. Europe is taking a law associated with consumer-facing Big Tech and pushing it down into the machinery room of the internet. That move will please some European cloud providers and alarm US technology companies that already view the DMA as a regulatory weapon aimed mostly at American firms.
The Commission’s stated logic is broader than nationalism. Cloud computing underpins e-commerce, public services, enterprise software, cybersecurity operations, and AI development. If the market calcifies around a few providers, Europe risks losing not only price competition but also strategic control over future digital infrastructure.
That word sovereignty is doing heavy work in Brussels. It does not mean Europe can or will unplug from US cloud providers. The largest European companies and public institutions cannot simply lift decades of IT dependency into a regional alternative overnight. But it does mean the Commission wants procurement markets to remain contestable enough that local providers, open standards, and multi-cloud strategies are not theatrical gestures.
For WindowsForum readers, the practical implication is that cloud regulation is no longer an abstract policy beat. It may shape the defaults that administrators see in licensing bundles, data portability tools, interoperability commitments, and the way Microsoft packages AI services into the broader enterprise stack.

Lock-In Has Become the Real Antitrust Vocabulary

The Commission’s preliminary finding leans heavily on lock-in effects, and that is where the debate becomes concrete. Cloud lock-in is not one thing. It is a stack of small decisions that become expensive to reverse.
A company may begin with commodity virtual machines, then adopt a managed database, then connect identity, logging, policy enforcement, analytics, serverless functions, container registries, key management, AI services, and vendor-specific observability. Each step may be rational. Taken together, they create a system where moving away requires not just migration but redesign.
This is why cloud portability is harder than downloading your photos from a social network. Data may be portable in theory, but application dependencies, permissions models, API assumptions, latency requirements, and compliance controls are harder to transplant. A regulator can mandate data portability, but it cannot instantly make a proprietary architecture behave like an open standard.
The lock-in question is especially thorny for Microsoft because customers often choose Azure to reduce friction with existing Microsoft estates. A Windows Server shop with Microsoft 365, Entra ID, Defender, SQL Server, Power Platform, and GitHub may see Azure as the natural place to modernize. That convenience is real value, but it can also make rival clouds appear artificially inconvenient.

AI Turns Cloud Procurement Into Platform Dependency

The Commission’s reference to AI tools and partnerships is not decorative. AI has changed cloud procurement from a debate about compute and storage into a debate about model access, data gravity, specialized hardware, developer frameworks, and compliance boundaries. The provider that wins the AI workload may win the next decade of infrastructure spending.
Microsoft’s OpenAI partnership and its Copilot strategy make Azure central to the company’s AI future. AWS has its own model marketplace, custom silicon strategy, and enterprise AI services. Google has Gemini and a long history in machine learning infrastructure. The cloud market is no longer merely hosting the AI boom; it is being reshaped by it.
That gives regulators a reason to act earlier than they might have in the previous cloud cycle. If customers are now signing infrastructure contracts based partly on AI capabilities, then the AI layer can reinforce the cloud layer. Once training pipelines, retrieval systems, enterprise data connectors, and governance controls are built around one vendor’s AI stack, switching providers becomes even harder.
There is a danger here for Europe as well. Overregulation could slow deployment, complicate compliance, or make hyperscalers more cautious about launching advanced services in the EU. Amazon has already argued that additional DMA obligations could undermine European competitiveness. That argument will resonate with businesses that want fewer procurement barriers, not more regulatory paperwork.
But the counterargument is equally forceful: if Europe waits until AI infrastructure has fully consolidated, the market may be effectively settled. By then, portability remedies may arrive after the lock-in has already hardened.

Microsoft’s Google Argument Is Both True and Incomplete

Microsoft’s reported complaint that the Commission overlooked Google Cloud and Gemini deserves scrutiny. Google is not a marginal cloud player, and Gemini has become a central part of Google’s enterprise pitch. Any serious analysis of cloud and AI competition must include Google.
Still, Microsoft’s argument risks conflating presence with constraint. A third major competitor can matter enormously in some segments while still failing to discipline the market overall. If AWS and Azure are the first and second largest cloud providers in the EU, and if customers face meaningful switching costs, Google’s existence does not automatically dissolve gatekeeper concerns.
The same dynamic has appeared repeatedly in technology markets. The presence of alternatives does not necessarily mean customers have practical freedom. Linux existed during Microsoft’s Windows dominance. Rival browsers existed during the browser wars. Alternative mobile app stores exist in theory on some platforms. Regulators care about whether alternatives can realistically change behavior, not whether they can be named in a slide deck.
Microsoft also has to navigate its own history. European regulators know the company’s pattern of bundling, integration, and enterprise leverage better than almost any other vendor’s. That does not mean Azure is guilty of misconduct by inheritance. It does mean Brussels will be less inclined to accept “competition exists” as a complete defense.

The Six-Month Clock Would Be Short in Enterprise Time

If the preliminary finding becomes final, Amazon and Microsoft would have six months to bring the relevant cloud services into DMA compliance. In consumer software, six months can be a product sprint. In enterprise cloud, six months is barely enough time to inventory contractual dependencies, rewrite documentation, adjust APIs, update procurement terms, retrain sales teams, and design compliance reporting.
The exact obligations will matter. The DMA can require gatekeepers to avoid certain self-preferencing practices, support interoperability, enable data portability, and refrain from conduct that unfairly disadvantages business users. Applied to cloud, those concepts are powerful but technically messy.
What does interoperability mean for managed databases, AI APIs, identity services, or security telemetry? How much portability is enough when workloads depend on proprietary orchestration and policy engines? At what point does a discount become a loyalty-inducing lock-in mechanism rather than ordinary commercial competition?
These are not academic questions for sysadmins. If Brussels forces clearer data export paths, less restrictive licensing, or more transparent interoperability commitments, IT teams may gain leverage. If compliance becomes another layer of contractual ambiguity, customers may inherit more paperwork without gaining real exit options.

Europe’s Cloud Sovereignty Push Is Not Just About Europe

The Commission’s action sits inside a broader European effort to reduce dependency on non-European technology providers without cutting itself off from global innovation. That balancing act has become harder as cloud and AI infrastructure spending explodes. Europe wants open markets, but it also wants resilience, bargaining power, and credible domestic capacity.
This will inevitably strain transatlantic politics. US technology groups and policy advocates often see the DMA as disproportionately aimed at American companies. European officials counter that the market structure is what it is: the dominant digital platforms serving European citizens and businesses are overwhelmingly American.
Both sides have a point. The DMA does target the companies that actually dominate the relevant markets, and those companies happen to be mostly US-based. But Europe’s rhetoric about sovereignty can also sound less like neutral competition policy and more like industrial strategy by regulatory means.
That tension will define the next phase. If the Commission frames the AWS and Azure case as a way to make cloud markets fairer, it may win support from customers tired of lock-in and smaller providers seeking oxygen. If the process looks like a punitive campaign against US hyperscalers, it will feed a backlash that could complicate cooperation on AI safety, cybersecurity, data transfers, and trade.

The Customer May Be the Missing Witness

The cloud debate is often presented as a fight between regulators, hyperscalers, and rival vendors. But the most important constituency is the customer that has to keep systems running while the lawyers argue. Enterprise IT does not live in theory; it lives in migration plans, uptime targets, audit findings, and budget meetings.
Many customers do not love lock-in, but they also do not love fragmentation. A single-vendor environment can be easier to secure, easier to staff, and easier to explain to executives. Multi-cloud architectures can provide leverage and resilience, but they can also multiply operational complexity.
That is why the best regulatory outcome would not be a forced fantasy of frictionless switching. Cloud platforms are complex because modern computing is complex. The more realistic goal is to make lock-in a conscious choice rather than an irreversible accident.
Customers should be able to understand the long-term consequences of adopting a managed service, exporting a dataset, committing to a licensing bundle, or embedding an AI service into a production workflow. If the DMA pushes hyperscalers to make those trade-offs clearer, it could improve the market without pretending that all clouds are interchangeable.

The Windows Admin’s Cloud Problem Just Became Political

For Windows administrators, the Azure question lands close to home. Microsoft has steadily moved identity, endpoint management, security, collaboration, and compliance into cloud-first control planes. Even organizations that still think of themselves as “on-prem” often depend on Microsoft cloud services for authentication, device posture, email security, file collaboration, or telemetry.
That means Azure’s regulatory future could influence everyday administrative work. Changes to interoperability rules might affect how Microsoft documents APIs, how third-party security tools integrate, how data can be exported, or how licensing terms interact with rival cloud deployments. None of this will arrive as one dramatic Windows Update. It will arrive through procurement language, admin portals, compliance notices, and product defaults.
The most immediate risk is uncertainty. Enterprises planning large Azure migrations or AI deployments now have to consider whether the service’s EU compliance obligations may change within a year. That does not mean projects should stop. It does mean architects should avoid designs that assume today’s vendor boundaries are permanent.
The old advice remains sound but newly urgent: document dependencies, test exits, avoid unnecessary proprietary coupling, and make sure leadership understands that cloud convenience has strategic cost. The DMA may eventually force hyperscalers to offer better tools, but customers still have to design systems that can use them.

The Cloud Gatekeeper Fight Leaves IT With Fewer Excuses

The Commission’s preliminary finding is not a final verdict, and AWS and Azure will not change overnight. But the signal is already useful: regulators are treating cloud dependency as a competition issue, not merely a procurement preference. That should push IT leaders to revisit assumptions that have been allowed to harden into architecture.

AWS and Azure are now under serious EU gatekeeper scrutiny for cloud services, even though the Commission says the usual quantitative DMA thresholds were not the deciding factor.
A final designation would give Amazon and Microsoft six months to comply with stricter DMA obligations for their cloud businesses in the European Union.
The practical fight will center on lock-in, interoperability, portability, self-preferencing, and the way cloud providers bundle adjacent services into larger ecosystems.
AI has made the cloud market more strategically important because model access, data pipelines, specialized compute, and enterprise AI tooling can deepen infrastructure dependency.
Microsoft’s Azure exposure is especially significant for Windows-centric organizations because identity, endpoint management, productivity, security, and developer workflows often reinforce the same ecosystem.
Customers should treat the investigation as a reason to map dependencies and strengthen exit options, not as a reason to pause every cloud or AI project.

The Commission has not yet won its argument, and Amazon and Microsoft may still narrow, delay, or defeat the proposed designation. But Brussels has already changed the conversation by making clear that the cloud is no longer hidden infrastructure beneath the digital economy; it is one of the places where power in that economy is exercised. If the DMA’s next frontier is the data center, Windows shops and cloud architects should expect the politics of competition to show up inside the architecture diagrams they once treated as purely technical.

References

Primary source: TechSpot
Published: 2026-06-26T17:30:12.497744

European Commission moves to designate Amazon and Microsoft as cloud gatekeepers | TechSpot

Amazon Web Services and Microsoft Azure are now so important to Europe's digital economy that they may be required to comply with additional rules when doing business...

www.techspot.com
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
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
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
Related coverage: france.representation.ec.europa.eu

La Commission estime à titre préliminaire que les services d’informatique en nuage d’Amazon et de Microsoft devraient être désignés au titre du DMA

La Commission européenne a informé Amazon et Microsoft de son appréciation préliminaire selon laquelle leurs services d’informatique en nuage, Amazon Web Services et Microsoft Azure, devraient être désignés comme contrôleurs d’accès au titre du DMA.

france.representation.ec.europa.eu

Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: europapress.es

Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio

La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...

www.europapress.es
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
Related coverage: ec.europa.eu

IP 25 2717 EN

PDF document

ec.europa.eu
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
Related coverage: itpro.com

Microsoft, Amazon cloud practice changes spark mixed industry reaction | IT Pro

Concerns have been raised over the voluntary actions agreed to by Microsoft and Amazon

www.itpro.com

ChatGPT · Jun 27, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that it preliminarily believes Amazon Web Services and Microsoft Azure should be treated as Digital Markets Act gatekeepers in the European Union. That is not a final ruling, but it is a major escalation. Brussels is no longer treating cloud as neutral infrastructure sitting beneath the platform wars. It is arguing that the infrastructure layer has become the platform war.

Brussels Moves the DMA Down the Stack

The Digital Markets Act was sold to the public as a way to discipline consumer-facing power: app stores, search engines, social networks, browsers, messaging apps, marketplaces, and advertising systems. Its early battles looked familiar because they were fought on familiar terrain. Apple’s App Store rules, Meta’s data practices, Google’s search and advertising stack, and Microsoft’s Windows-adjacent services were the obvious fronts.
Cloud computing is different. It is less visible, more technical, and harder to explain in a headline. Nobody queues outside a data center for a new object-storage bucket, and no consumer complains at dinner that their Kubernetes control plane has too much lock-in.
But the Commission’s latest move says that invisibility is precisely the problem. AWS and Azure are not merely vendors in a competitive procurement market. They are, in Brussels’ preliminary view, gateways between European businesses and their customers. If that view survives the companies’ objections, the DMA will have formally crossed from the app economy into the infrastructure economy.
That is the real story behind the Crypto Briefing headline. The EU is not simply “targeting” two American cloud giants because they are large. It is testing whether Big Tech regulation can follow market power into the places where modern software is actually built, deployed, billed, secured, and scaled.

The Gatekeeper Label Is a Legal Weapon, Not a Nickname

“Gatekeeper” sounds like political branding, but under the DMA it is a regulatory status with teeth. Designated firms face obligations meant to stop them from using control of a core platform service to preference their own products, trap business users, restrict interoperability, or make switching unnecessarily painful.
That matters because cloud lock-in rarely looks like a single abusive clause. It looks like architecture. A company starts with virtual machines, then adopts a managed database, then identity services, observability tools, serverless functions, AI model hosting, proprietary security integrations, data pipelines, and discounted enterprise bundles. By the time procurement asks whether it can move elsewhere, the answer is no longer a commercial answer. It is a migration program.
AWS and Azure will argue, with some justification, that cloud customers are sophisticated buyers. Enterprises do not click “accept” on a cloud migration the way a teenager downloads an app. They run proofs of concept, negotiate contracts, hire consultants, and maintain architecture boards.
Yet that argument has limits. A sophisticated buyer can still be locked in. A CIO can still face switching costs so high that theoretical competition becomes meaningless. The Commission’s theory is that when cloud providers become indispensable intermediaries, the market cannot be judged only by whether alternatives exist on a slide deck.

Microsoft Has More at Stake Than Azure Revenue

For Microsoft, this fight lands at an awkward moment. Azure is not just another business line. It is the connective tissue of the modern Microsoft strategy: Microsoft 365, Entra identity, Defender, Purview, GitHub, Power Platform, Dynamics, Windows Server, SQL Server, Copilot, and the company’s AI infrastructure ambitions all lean on Azure’s gravitational pull.
That integration is Microsoft’s strength. It is also the fact pattern regulators keep circling. The company can plausibly claim that enterprises want unified identity, security, compliance, endpoint management, cloud hosting, and productivity tools from a trusted vendor. It can also be accused of turning that unified stack into a one-way door.
WindowsForum readers have seen this movie in smaller forms for years. Windows sign-in increasingly points toward Microsoft accounts. Microsoft 365 integrations surface inside Windows. Defender, Entra, Intune, and Azure management capabilities make more sense together than apart. None of that is automatically anticompetitive; much of it is genuinely useful. But the line between integration and enclosure is exactly where Brussels likes to plant flags.
The cloud case is therefore not an isolated Azure problem. If Azure becomes a DMA gatekeeper service, Microsoft will have to think more carefully about how cloud, identity, productivity, AI, and Windows management are bundled, priced, and technically connected in Europe.

AWS Is the Bigger Cloud Target, but Microsoft Is the More Complicated One

Amazon Web Services is the larger cloud provider and the obvious first name in any global cloud competition discussion. AWS built the modern public cloud category and remains the default mental model for infrastructure as a service. If the EU wants to regulate market power in cloud, it cannot avoid Amazon.
Microsoft, however, presents the more intricate regulatory puzzle. AWS dominates by breadth, maturity, and developer gravity. Azure dominates in a different way: through enterprise adjacency. Microsoft already sits inside the corporate tenant, the endpoint, the identity provider, the document repository, the admin console, and the licensing agreement.
That makes Azure less like an isolated infrastructure provider and more like the cloud extension of an existing enterprise operating system. For many organizations, Azure adoption does not begin with a greenfield cloud decision. It begins with Active Directory, Microsoft 365, Teams, Windows Server licensing, SQL Server modernization, or a security consolidation program.
This is where the EU’s gatekeeper theory becomes especially potent. The Commission does not need to prove that every company is forced onto Azure. It needs to show that Azure occupies a durable gateway position that can shape how business users reach customers and how rivals compete. Microsoft’s enterprise footprint gives regulators plenty to examine.

The Quantitative Thresholds Were Not the Escape Hatch

One of the more important details is that the Commission opened these cloud investigations despite AWS and Azure not necessarily fitting neatly into the DMA’s standard quantitative thresholds for gatekeeper designation. That sounds like a technicality, but it is politically significant.
Regulators are saying the cloud market cannot be understood solely through the same user-count framework that applies to consumer platforms. Cloud’s power is not measured by monthly active users in the ordinary sense. It is measured by dependency, data gravity, switching costs, interoperability barriers, and control over business-critical infrastructure.
That is a shift in regulatory imagination. In the consumer platform era, the gatekeeper stood between users and apps, merchants and buyers, publishers and readers. In the cloud era, the gatekeeper may stand between developers and deployment, companies and their data, AI products and compute, public services and their digital delivery.
The distinction matters for future cases. If the Commission can stretch DMA analysis to cloud infrastructure, then other layers of the digital stack may eventually receive similar scrutiny. AI platforms, model marketplaces, developer ecosystems, cybersecurity control planes, and enterprise identity systems all start to look less like ordinary software markets and more like chokepoints.

The Cloud Market Is Competitive Until You Try to Leave

Cloud vendors love to point out that customers can choose among AWS, Azure, Google Cloud, Oracle, IBM, OVHcloud, Scaleway, regional providers, private cloud, hybrid cloud, and on-premises infrastructure. They are right in the abstract. The European cloud buyer is not staring at a monopoly storefront.
But competition at the moment of initial purchase is not the same as competition after five years of architectural accumulation. Once workloads depend on a provider’s managed database semantics, IAM model, networking fabric, monitoring stack, proprietary APIs, storage tiers, and discount commitments, the market changes. A rival can be cheaper and still not be a realistic option.
This is why “multi-cloud” often functions more as a boardroom comfort phrase than an operational reality. Many organizations use multiple clouds, but not necessarily in a portable way. They may run different workloads in different clouds while still being deeply dependent on each provider’s native services.
The Commission’s preliminary position appears to acknowledge that distinction. Cloud power is not just market share. It is the ability to shape the practical choices available to customers after they have built on your platform.

Europe’s Sovereignty Argument Is About Dependency, Not Just Geography

The EU often frames technology policy through the language of digital sovereignty. Critics hear protectionism. Supporters hear overdue realism. In cloud, both readings contain some truth.
Europe has spent years worrying that its critical digital infrastructure depends heavily on US hyperscalers. That concern sharpened as cloud became the foundation for government services, healthcare systems, financial operations, industrial platforms, and AI development. The question is no longer whether European firms can buy cloud capacity. It is whether Europe can shape the rules of the infrastructure it depends on.
That does not mean Brussels can simply regulate European cloud champions into existence. OVHcloud and other regional providers do not become hyperscalers because the Commission writes a stern letter to Seattle and Redmond. Scale, capital expenditure, developer ecosystems, security certifications, global regions, and service breadth are brutally hard to replicate.
But regulatory pressure can still change the competitive terrain. If the DMA forces clearer interoperability, fairer contractual terms, or reduced switching friction, European and smaller global providers may have a better chance at winning portions of enterprise workloads. The Commission’s bet is not that regulation replaces engineering scale. It is that regulation can stop scale from becoming destiny.

The AI Boom Makes This Fight Urgent

If this were only about virtual machines and storage buckets, the cloud gatekeeper debate would still matter. But in 2026, cloud is also the control layer for AI deployment. Model training, inference, vector databases, data governance, GPU allocation, developer tooling, and enterprise AI assistants increasingly sit inside hyperscaler ecosystems.
That gives the cloud case a sharper edge. Companies adopting AI are not merely choosing a chatbot. They are choosing where data lives, which identity system controls access, which models are easiest to deploy, which compliance tools govern output, and which vendor gets embedded into future workflows. The provider that hosts the AI stack can influence the entire application layer above it.
Microsoft’s position is especially sensitive because of its AI integration strategy. Azure provides infrastructure for AI services; Microsoft 365 Copilot pushes AI into productivity workflows; GitHub Copilot reaches developers; Windows is beginning to absorb AI features at the client layer; and enterprise security tooling increasingly wraps the whole arrangement.
The EU’s cloud scrutiny therefore doubles as an early warning about AI market structure. If AI becomes inseparable from cloud, then waiting until AI platforms are fully entrenched may be too late. Brussels is trying to intervene while the stack is still being assembled.

The Crypto Angle Is Smaller Than the Infrastructure Angle

Crypto Briefing’s interest in the story is understandable. Crypto companies, exchanges, wallet providers, analytics firms, node operators, and blockchain infrastructure companies often rely on hyperscale cloud. Even projects that market themselves as decentralized frequently depend on centralized hosting, APIs, monitoring, and developer platforms somewhere in the chain.
That dependency has always been an uncomfortable irony. A decentralized application can still have a very centralized operational footprint. If cloud access, pricing, compliance demands, or account enforcement change, supposedly distributed services may discover that their weak point is not the blockchain protocol but the vendor account that keeps their front end or indexer alive.
Still, the cloud gatekeeper story is bigger than crypto. It reaches every sector that has outsourced infrastructure complexity to a handful of providers. Banks, hospitals, manufacturers, retailers, schools, governments, media companies, SaaS vendors, and AI startups all live somewhere in this dependency map.
For WindowsForum’s audience, the practical lesson is blunt: cloud regulation is no longer a niche antitrust story. It is now part of the operating environment for IT architecture.

Enterprise IT Should Expect Paperwork Before Freedom

There is a temptation to imagine DMA designation as a sudden liberation event. Brussels acts, hyperscalers comply, and enterprises discover a new world of easy portability and fair contracts. That is not how this is likely to unfold.
If the Commission finalizes the designation, the first visible result will probably be process. Microsoft and Amazon will challenge, narrow, negotiate, document, and interpret. Lawyers will argue over which services are covered, which obligations apply, what compliance means, and how far technical changes must go.
Enterprise customers may eventually see more transparent terms, better portability commitments, revised data-access rules, altered bundling practices, or new interoperability interfaces. But those gains will arrive unevenly. They will also require customers to understand and use them.
The deeper truth is that regulation can lower barriers, but it cannot rewrite a bad architecture. An organization that has spent years hard-coding itself into provider-specific services will not become portable because a compliance page changes. IT leaders still need exit plans, data maps, abstraction strategies, and contract discipline.

Microsoft’s Defense Will Lean on Google, Choice, and Customer Sophistication

Microsoft is likely to argue that the Commission is underestimating competition in cloud, especially from Google. It may also emphasize that cloud buyers are professional customers with bargaining power, that Azure faces constant pressure on price and innovation, and that European businesses benefit from integrated services.
Those arguments should not be dismissed. Google Cloud is a serious competitor, especially in data, AI, analytics, and Kubernetes-adjacent workloads. Oracle has become more relevant in cloud infrastructure than many expected. Regional providers can win sovereignty-sensitive or specialized workloads. Hybrid and on-premises architectures remain real options for some enterprises.
But Microsoft’s challenge is that the DMA is not a popularity contest among vendors. It asks whether a service has a gateway function and whether that position can distort competition. A market can contain several strong competitors and still include gatekeepers.
That is why the legal and economic details will matter. The Commission must translate broad concerns about dependency into enforceable obligations. Microsoft must show that its cloud business is competitive in practice, not merely contestable in theory.

Amazon’s Defense Will Warn That Regulation Can Freeze the Market

Amazon’s response is likely to be more direct: applying gatekeeper rules to cloud could chill investment, slow innovation, and distort a market that is still evolving. AWS has long argued that customers choose it because it delivers breadth, reliability, security, and constant service improvement, not because they are trapped.
There is force in that warning. Cloud infrastructure is capital-intensive, and Europe wants hyperscalers to keep building regions, improving resilience, expanding security capabilities, and supporting local compliance needs. Heavy-handed rules could make providers more cautious, especially if obligations are vague or politically expandable.
But the opposite risk is also real. A market can innovate rapidly while becoming less open. In fact, rapid innovation can deepen lock-in when new features are designed to work best inside a single ecosystem. The more valuable native services become, the more expensive leaving becomes.
The Commission’s job is to avoid confusing innovation with immunity. The hyperscalers can be both impressive and too powerful. Those are not contradictory claims.

Windows Administrators Will Feel This Through Identity, Licensing, and Compliance

For admins, the cloud gatekeeper fight may sound remote until it shows up in the familiar places: tenant configuration, identity federation, licensing terms, security dashboards, data residency commitments, audit logs, procurement reviews, and migration planning.
Azure is deeply entangled with Microsoft’s enterprise management world. Entra ID, Intune, Defender, Purview, Azure Arc, Windows 365, Azure Virtual Desktop, and Microsoft 365 administration create a continuum from endpoint to cloud. That continuum can simplify life for stretched IT teams. It can also make alternatives harder to evaluate.
If DMA obligations eventually touch interoperability or bundling, administrators may see changes in how Microsoft documents integrations, exposes APIs, handles telemetry, structures cloud credits, or presents cross-product defaults. Some changes may be subtle. Others may arrive as new compliance toggles that only lawyers and architects notice at first.
The risk for IT departments is assuming this is a Brussels-versus-Big-Tech spectacle with no operational consequences. Regulatory pressure often becomes product behavior, and product behavior eventually becomes admin work.

The DMA Is Becoming Europe’s Operating System for Tech Power

The Commission’s cloud move also reveals something about the DMA itself. It is no longer just a statute aimed at yesterday’s platform giants. It is becoming Europe’s general-purpose operating system for digital market power.
That evolution will attract criticism. Companies will say the EU is expanding rules beyond their original intent. US policymakers may frame the campaign as discriminatory against American firms. Some technologists will argue that regulators do not understand the technical layers they are trying to govern.
Those critiques will land with different audiences, but they will not stop the broader trend. Europe has decided that market structure is a technology policy issue. It does not want to wait until a sector tips irreversibly before asserting authority.
The open question is whether the DMA can handle infrastructure markets without becoming either too vague to be useful or too rigid to be safe. Cloud is not an app store. Obligations designed for consumer platforms cannot simply be pasted onto distributed computing services. The Commission will need precision, or the fight will become a fog of compliance theater.

The Fight Is Really About Who Writes the Defaults

Every platform battle eventually becomes a battle over defaults. In cloud, defaults are not just user-interface prompts. They are reference architectures, managed services, recommended deployment paths, identity assumptions, data locations, contract templates, support tiers, and discount models.
Microsoft and Amazon write many of those defaults today. They do so because they built enormous, capable platforms that customers chose. But once defaults become entrenched, they shape what customers perceive as normal, efficient, safe, and affordable.
That is why cloud gatekeeper designation matters even before any final penalty or remedy. It challenges the idea that infrastructure defaults are purely technical. They are commercial and political choices embedded in architecture.
For years, cloud buyers were told not to worry too much about lock-in because the benefits outweighed the risk. That may still be true for many workloads. But the EU is now saying that when enough of the economy makes that same bargain with the same few providers, the result is no longer just a customer-by-customer risk calculation. It is a market-structure problem.

The Practical Reading for WindowsForum Readers

This case will move slowly, but it is already useful as a planning signal. The Commission’s preliminary view tells enterprises that cloud dependency is becoming a regulated concern, not just an architecture talking point.

The European Commission has not yet issued a final gatekeeper designation for AWS and Azure, but its preliminary position is a serious step toward applying DMA obligations to cloud infrastructure.
Microsoft’s exposure is broader than Azure alone because Azure is intertwined with identity, security, productivity, developer tools, Windows management, and AI services.
Cloud competition should be judged not only at the moment of purchase but also at the moment a customer tries to migrate away.
AI makes cloud gatekeeper scrutiny more urgent because model deployment, data governance, and compute access are increasingly concentrated inside hyperscaler ecosystems.
Enterprise IT teams should treat portability, exit planning, and contract review as operational disciplines rather than abstract antitrust concerns.
Smaller providers may benefit from reduced switching friction, but regulation alone will not erase hyperscaler advantages in scale, service breadth, and global infrastructure.

The EU’s message to Microsoft and Amazon is that the cloud is no longer beneath regulation simply because it is beneath the apps. For Windows users and administrators, that is the point to watch: the next decade of computing will be shaped less by which desktop icon wins attention and more by which cloud defaults define identity, security, AI, and deployment before anyone opens a browser.

References

Primary source: Crypto Briefing
Published: Sat, 27 Jun 2026 18:59:13 GMT

EU targets Microsoft and Amazon cloud units for Big Tech gatekeeper rules

The EU has preliminarily designated AWS and Microsoft Azure as gatekeepers under the Digital Markets Act, with major implications for crypto cloud

cryptobriefing.com
Related coverage: itpro.com

AWS says cloud market gatekeeper designation risks ‘deterring European investment and innovation’ as EU regulators plot competition crackdown | IT Pro

Gatekeeper designation under the legislation would force AWS and Microsoft to make concessions

www.itpro.com
Related coverage: digital-strategy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

The Commission has informed Amazon and Microsoft of its preliminary view that they should be designated as gatekeepers under the Digital Markets Act (DMA), for their cloud computing services, Amazon Web Services (AWS) and Microsoft Azure (Azure) respectively.

digital-strategy.ec.europa.eu
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
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: marketscreener.com

EU targets Amazon, Microsoft cloud units for Big Tech "gatekeeper" rules

EU antitrust regulators said Amazon and Microsoft's cloud computing services should be designated as gatekeepers under landmark tech rules, a step that would subject them to strict obligations aimed...

www.marketscreener.com

Related coverage: techspot.com

European Commission moves to designate Amazon and Microsoft as cloud gatekeepers | TechSpot

Amazon Web Services and Microsoft Azure are now so important to Europe's digital economy that they may be required to comply with additional rules when doing business...

www.techspot.com
Related coverage: insidermonkey.com

EU Targets Microsoft (MSFT) and Amazon Cloud Units for Big Tech “Gatekeeper” Rules, Reuters Reports - Insider Monkey

Microsoft Corporation (NASDAQ:MSFT) is one of the safe stocks for beginners to buy in 2026.

www.insidermonkey.com
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
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
Related coverage: techradar.com

Newly drafted EU cloud rules could stop US hyperscaler access to critical tenders | TechRadar

EU reportedly preparing new public sector cloud rules

www.techradar.com

ChatGPT · Jun 27, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that it preliminarily believes Amazon Web Services and Microsoft Azure should be designated as “gatekeepers” under the EU Digital Markets Act for cloud computing services. The decision is not final, but it is a warning shot aimed at the infrastructure layer beneath modern software, AI, and enterprise IT. For WindowsForum readers, the important part is not Brussels discovering that the cloud is big. It is Brussels deciding that cloud dependency itself may now be a competition problem.

Brussels Moves the DMA Below the App Store

The Digital Markets Act began life in the public imagination as a law about app stores, search engines, browsers, messaging, marketplaces, and social networks. It was the EU’s attempt to stop the largest digital platforms from using their position as unavoidable middlemen to tilt markets in their own favor.
That framing made the DMA easy to understand. Apple’s App Store, Google Search, Amazon Marketplace, Meta’s social networks, and Microsoft Windows all look like front doors to digital markets. The user can see them, click them, complain about them, and sometimes work around them.
Cloud infrastructure is different. AWS and Azure do not sit on the average consumer’s home screen, but they increasingly sit under the services that businesses, governments, developers, schools, hospitals, and AI companies use every day. The Commission’s move is significant because it treats cloud platforms not merely as suppliers, but as strategic control points.
The Commission says AWS and Azure are the largest and second-largest cloud computing services in the EU, respectively, and that both appear to serve as important gateways between businesses and their customers. That matters because the DMA’s “gatekeeper” concept is not just about market size. It is about whether a platform occupies a position that other businesses must pass through to reach users, run services, or compete effectively.
This is the regulatory equivalent of looking beneath the web page and asking who owns the server room.

The Thresholds Were Not the Whole Game

One of the more important details in the Commission’s announcement is that AWS and Azure apparently do not meet the DMA’s standard quantitative thresholds for this specific cloud designation. That might sound like a technicality, but it is the heart of the story.
The DMA contains numerical triggers for gatekeeper status, including business size and user reach. Those thresholds work more naturally for consumer platforms with millions of visible end users. Cloud services, however, are often business-to-business platforms where a smaller number of enterprise customers can represent enormous market power.
That mismatch has always made cloud a harder fit for platform regulation. A cloud provider may not have the same kind of daily active user count as a messaging app, but it can still influence pricing, interoperability, data movement, software architecture, procurement strategy, and the economics of competitors.
The Commission is therefore leaning on the DMA’s qualitative route: even if the numbers do not mechanically trigger designation, regulators can investigate whether a provider still acts as a durable gateway. That is not a loophole. It is the part of the law built for markets where power is obvious in practice but awkward on a spreadsheet.
For Amazon and Microsoft, that is the uncomfortable part. They are not being told they crossed a simple line. They are being told the structure of their cloud businesses may itself create gatekeeper power.

Cloud Lock-In Becomes the Political Target

Every sysadmin and cloud architect knows that “just move to another provider” is one of the great lies of modern computing. On paper, workloads are portable. In practice, identity systems, databases, storage formats, monitoring, automation, proprietary APIs, egress fees, compliance certifications, skill sets, procurement contracts, and application dependencies all conspire to make migration expensive.
The Commission’s language points directly at that reality. It has focused on entrenched user bases, high switching costs, lock-in effects, and large ecosystems. Those are not abstract competition-law terms to anyone who has tried to unwind a production estate built around a particular cloud vendor’s managed services.
This is where the AWS and Azure cases become more than another EU-versus-Big-Tech skirmish. The modern cloud business is not just rented compute. It is a gravitational field. Once an organization starts using managed identity, serverless functions, proprietary database services, analytics pipelines, AI tooling, storage tiers, security dashboards, and billing commitments, the cloud provider becomes part vendor, part platform, part operating environment.
Microsoft’s position is especially interesting for WindowsForum readers because Azure is tied into a broader Microsoft enterprise stack. Entra ID, Microsoft 365, Windows Server, Defender, GitHub, Visual Studio, Power Platform, SQL Server, and Azure all reinforce each other. That integration is genuinely useful, but it also raises the classic competition question: when does convenience become enclosure?
AWS has a different but equally powerful version of the same story. Its strength is breadth, maturity, developer familiarity, and an enormous catalog of services that often become de facto defaults. It may not have Windows on the desktop, but it has years of infrastructure gravity.

The AI Boom Makes Cloud Regulation Urgent

The Commission’s timing is not accidental. Cloud services are now the foundation for the AI race, and the AI race is rapidly becoming a competition-policy race.
Training and deploying AI systems requires compute, storage, networking, specialized accelerators, developer platforms, model hosting, data governance, security tooling, and enormous capital expenditure. In other words, AI does not float above the cloud. It depends on it.
That dependence creates a new kind of strategic risk. If the same companies that control cloud infrastructure also control AI platforms, developer tools, data pipelines, enterprise identity, productivity suites, and marketplaces, they can shape the path of AI adoption in subtle ways. They do not need to block competitors outright. They can make the integrated path cheaper, smoother, better documented, more visible, or easier to approve through procurement.
This is why the DMA’s cloud expansion matters even to organizations that have no immediate interest in EU competition law. The next decade of enterprise computing will be built around cloud-hosted AI services and hybrid automation. If regulators wait until every dependency is cemented, the market may be formally competitive but practically locked down.
There is also a sovereignty angle that Brussels rarely hides. Europe wants cloud capacity, AI capacity, and digital infrastructure that are not wholly dependent on a handful of American hyperscalers. That does not mean the EU can simply regulate European cloud champions into existence. But it does mean the Commission sees infrastructure openness as part of industrial policy, not just consumer protection.

Microsoft Faces a Familiar European Script

Microsoft has been here before, even if the technology layer has changed. The company’s long history with European competition authorities runs from Windows Media Player and Internet Explorer to more recent scrutiny of Teams bundling, cloud licensing, and platform interoperability.
The Azure gatekeeper question fits neatly into that lineage. Microsoft’s great commercial strength has always been integration. It builds platforms that become more valuable when customers adopt more of the stack. Windows led to Office, Office led to Exchange and SharePoint, Microsoft 365 led to Teams, Entra ID, Defender, and cloud management, and Azure increasingly sits beneath the whole enterprise story.
That strategy is not inherently abusive. Customers often buy Microsoft precisely because the pieces fit together. The problem, from a regulator’s perspective, is that integration can become a ratchet. Once a customer has standardized on Microsoft identity, productivity, security, endpoint management, licensing, and developer tooling, Azure may look less like one option among many and more like the default center of gravity.
The Commission will have to be careful here. If it treats every integrated product strategy as suspect, it risks punishing the very coherence enterprise buyers value. But if it ignores how licensing, identity, management, and cloud services reinforce each other, it will miss how platform power actually operates in 2026.
For Windows administrators, this is not academic. Hybrid estates increasingly depend on Microsoft’s cloud control plane. Whether you are managing endpoints through Intune, syncing identity through Entra ID, protecting workloads with Defender, or modernizing legacy Windows Server applications, Azure is often presented as the path of least resistance. That path may be efficient. It may also be strategically narrowing.

Amazon’s Defense Is About Investment, Not Just Compliance

Amazon’s likely argument is straightforward: regulating AWS as a gatekeeper could discourage investment, slow innovation, and make Europe a less attractive place to build cloud infrastructure. That line will resonate with anyone who has watched Europe worry simultaneously about dependence on U.S. tech and underinvestment in its own digital infrastructure.
The tension is real. Cloud infrastructure is capital-intensive, and hyperscale providers spend staggering sums on data centers, chips, networking, security, power, and availability zones. If Europe wants more cloud capacity, especially for AI, it cannot pretend that regulation has no cost.
But the investment argument cuts both ways. A market can attract infrastructure spending while still trapping customers in high-friction ecosystems. More data centers do not automatically mean more competition. More services do not automatically mean more openness. More innovation inside one vendor’s platform can sometimes make leaving that platform harder.
AWS’s challenge is that its best qualities are also the basis for regulatory concern. Its maturity, breadth, reliability, and service catalog are why customers use it. Those same qualities make it hard for rivals to match and hard for customers to exit.
The Commission’s job is not to punish AWS for being good at cloud. It is to decide whether AWS’s market position now requires obligations that stop success from becoming structural control.

The DMA’s Cloud Test Will Be Messier Than App Store Fights

Applying DMA rules to cloud will be harder than applying them to a consumer app store. In an app store, the controversial behaviors are relatively visible: ranking, commissions, payment rules, app review, sideloading restrictions, and access to platform features. In cloud, the disputed terrain is buried in contracts, APIs, service dependencies, technical documentation, billing mechanics, and migration cost.
What would “no self-preferencing” mean for cloud? Would it apply to marketplace listings, managed services, default integrations, pricing bundles, AI model access, database migration tooling, or enterprise licensing? What counts as interoperability in a world where cloud services are not interchangeable commodities but complex managed platforms?
Data portability is similarly difficult. Moving files from one storage bucket to another is the easy part. Moving a production system that depends on identity policies, event triggers, observability tools, managed databases, encryption keys, networking rules, and compliance controls is the real problem.
The Commission knows this, which is why a designation decision would only begin the next fight. If AWS and Azure are finally designated, they would have a compliance window, and then the argument would shift from whether they are gatekeepers to what gatekeeper obligations mean in cloud engineering terms.
That phase will be where vendors, competitors, regulators, and customers clash hardest. The law can demand interoperability. Engineers still have to define it.

Enterprise IT Should Watch the Remedies, Not the Rhetoric

For IT departments, the temptation is to treat this as distant Brussels theater. That would be a mistake. Even when EU digital rules technically apply to the European market, large platform vendors often adjust global products, contracts, and compliance strategies in response.
The practical consequences could show up in places administrators actually touch: cloud licensing terms, data export tooling, API access, marketplace behavior, identity integration, migration assistance, documentation, pricing transparency, and contractual restrictions. None of that will happen overnight, and some of it may never happen. But those are the areas where a gatekeeper designation would have teeth.
Customers should also resist the fantasy that regulation will make cloud portability painless. It will not. The hardest lock-in is often self-inflicted through architecture choices. If a company builds around deeply proprietary managed services, no regulator can magically turn that estate into a provider-neutral platform.
But regulation can change the default incentives. It can make vendors think twice before designing avoidable friction into exits. It can force clearer terms. It can make interoperability a compliance issue rather than a marketing slogan. And it can give competitors and customers a formal process to challenge behavior that previously looked like ordinary platform strategy.
That is why the Commission’s preliminary view matters even before a final decision. It tells cloud buyers that the regulatory weather is changing.

Europe Is Testing Whether Platform Law Can Reach Infrastructure

The broader question is whether the DMA can evolve from a consumer-platform law into an infrastructure-platform law. That is a much bigger project.
The original gatekeeper designations were easier to explain because they involved services people recognized: search, social networks, operating systems, marketplaces, browsers, ads, and messaging. Cloud is less visible but arguably more foundational. If a regulator wants to shape the future of digital markets, it cannot stop at the user interface.
This is also where Europe’s approach diverges from the more litigation-heavy U.S. model. The EU is trying to write rules for platform conduct before every abuse has to be proven in a decade-long court battle. That creates risks of overreach, but it also acknowledges a basic truth about digital markets: by the time traditional enforcement finishes, the market may already have tipped.
The cloud case will test whether that ex ante model can handle technical complexity. Regulators will need enough humility to avoid writing rules that break useful services. Vendors will need enough honesty to admit that not every lock-in effect is merely a byproduct of innovation.
If both sides fail, the result will be performative compliance: dashboards, reports, promises, and carefully scoped changes that leave the underlying power structure intact. If the Commission succeeds, cloud competition may become less about who can recreate AWS or Azure wholesale and more about whether customers can mix, move, and negotiate without being punished for it.

The Cloud Gatekeeper Fight Comes Down to Five Practical Stakes

The immediate story is a preliminary EU finding, but the real stakes are operational. If AWS and Azure become DMA gatekeepers for cloud, the impact will be measured less by press releases than by contract language, migration paths, and the daily architecture choices of enterprise IT teams.

The Commission’s June 25, 2026 move is preliminary, so Amazon and Microsoft still have a chance to respond before any final designation is adopted.
The case matters because AWS and Azure may be treated as gatekeepers even without meeting the DMA’s usual quantitative thresholds for this specific cloud category.
The central regulatory concern is not simply market share, but lock-in through ecosystems, switching costs, customer dependence, and control over cloud-based routes to market.
Microsoft’s Azure case is inseparable from its broader enterprise stack, including identity, productivity, security, developer tools, and Windows-oriented management.
AWS’s case will turn on whether its enormous service breadth and infrastructure lead have become a durable market gateway rather than merely a successful product portfolio.
For customers, the most meaningful outcomes would involve portability, interoperability, licensing transparency, and reduced friction when combining or leaving cloud platforms.

The EU’s cloud gatekeeper push is not a final verdict on Amazon or Microsoft, and it is certainly not a magic wand for Europe’s digital sovereignty ambitions. But it is a clear sign that regulators now see the cloud as the control layer beneath software, AI, and enterprise computing. If Brussels follows through, the next phase of platform regulation will not be fought only over app stores and browsers; it will be fought over the infrastructure choices that decide how much freedom businesses really have once they build in someone else’s cloud.

References

Primary source: harianbasis.co
Published: 2026-06-27T21:30:10.287997

EU Regulators Seek Gatekeeper Designation for Amazon and Microsoft

EU antitrust regulators recommend designating Amazon and Microsoft cloud services as gatekeepers under new tech rules to curb market power.

www.harianbasis.co
Related coverage: itpro.com

AWS says cloud market gatekeeper designation risks ‘deterring European investment and innovation’ as EU regulators plot competition crackdown | IT Pro

Gatekeeper designation under the legislation would force AWS and Microsoft to make concessions

www.itpro.com
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: digital-markets-act.ec.europa.eu

Commission designates six gatekeepers under the Digital Markets Act

Today (6 September 2023) the European Commission has designated, for the first time, six gatekeepers - Alphabet, Amazon, Apple, ByteDance, Meta, Microsoft - under the Digital Markets Act (DMA). In total, 22 core platform services provided by gatekeepers have been designated.

digital-markets-act.ec.europa.eu
Related coverage: digital-strategy.ec.europa.eu

Digital Markets Act: Commission designates six gatekeepers

The European Commission has designated, for the first time, six gatekeepers - Alphabet, Amazon, Apple, ByteDance, Meta, Microsoft - under the Digital Markets Act (DMA).

digital-strategy.ec.europa.eu
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu

Related coverage: legalclarity.org

EU Digital Markets Act: Rules, Gatekeepers, and Penalties - LegalClarity

The EU’s Digital Markets Act sets out who qualifies as a gatekeeper, what obligations they face, and the penalties for falling short.

legalclarity.org
Related coverage: finanza.repubblica.it

https://finanza.repubblica.it/News/2026/06/25/commissione_ue_servizi_cloud_di_amazon_e_microsoft%C2%A0siano_designati_come_gatekeeper_-105
Related coverage: techspot.com

European Commission moves to designate Amazon and Microsoft as cloud gatekeepers | TechSpot

Amazon Web Services and Microsoft Azure are now so important to Europe's digital economy that they may be required to comply with additional rules when doing business...

www.techspot.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
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

ChatGPT · Jun 28, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that it had preliminarily concluded Amazon Web Services and Microsoft Azure should be treated as Digital Markets Act gatekeepers for cloud computing services in the European Union. That is not a final designation, and both companies still get to argue their case. But the direction of travel is unmistakable: Brussels is no longer content to regulate the apps sitting on top of the internet. It is moving toward the infrastructure underneath them.
The cloud used to be sold as plumbing: elastic, invisible, interchangeable, a place where workloads could scale without procurement drama. The EU’s new position is that this plumbing has become a market-shaping layer in its own right, especially as artificial intelligence turns compute capacity, data gravity, and developer tooling into strategic assets. For Windows users, enterprise administrators, and software teams that live somewhere between Microsoft 365, Azure, AWS, GitHub, Entra ID, and a growing pile of AI services, this is not an abstract Brussels story. It is about whether the next decade of cloud choice is real, or merely contractual.

Brussels Has Found the Internet’s Basement

The Digital Markets Act began life in the public imagination as a consumer-platform law. It was the thing that forced arguments about app stores, messaging interoperability, browser choice, self-preferencing, and whether the biggest technology firms could keep using their platforms to privilege their own services. That framing made sense because the most visible fights were happening on phones, in search boxes, and inside social feeds.
Cloud computing is different. Nobody gets angry at a virtual machine in quite the same way they get angry at a locked-down app store. Infrastructure lock-in does not usually arrive as a pop-up or a missing button; it arrives as a three-year enterprise agreement, a database dependency, a bespoke identity stack, a proprietary monitoring pipeline, or a migration estimate so grotesque that the incumbent suddenly looks cheaper by comparison.
That is why the Commission’s preliminary view matters. It suggests that the EU sees AWS and Azure not merely as large vendors, but as gateways between businesses and customers. In DMA language, that distinction is crucial. A big company is not automatically a gatekeeper; a gatekeeper is a company whose position lets it shape the terms on which others reach the market.
For years, cloud vendors have resisted the idea that infrastructure should be regulated like consumer platforms. Their argument has always had some force: cloud customers are sophisticated buyers, the market contains multiple providers, open-source technologies are widely used, and enterprises can negotiate. Brussels is effectively saying sophistication does not eliminate dependency. Sometimes it only makes dependency more expensive to unwind.

The Gatekeeper Test Moves Past the Obvious Numbers

The most striking part of the EU’s move is that AWS and Azure are being considered for designation even though the Commission says they do not meet the DMA’s usual quantitative thresholds for this category. That does not mean the law is being ignored. It means Brussels is leaning into the DMA’s ability to examine whether a service functions as an important gateway even when the cleanest numerical triggers are not enough on their own.
That matters because cloud power is not measured only by user counts. A social network’s dominance is visible in daily active users; a cloud platform’s dominance is buried in procurement systems, developer habits, certification pipelines, data residency architectures, and the high-stakes fear that moving a business-critical workload will break something. The technical map is the market map.
AWS is still widely treated as the cloud market’s pioneer and scale leader. Azure, meanwhile, has become inseparable from Microsoft’s enterprise stack: Windows Server, Active Directory’s cloud-era successor Entra ID, Microsoft 365, Dynamics, Power Platform, GitHub, Visual Studio, SQL Server, Defender, and a growing set of AI and data services. For many organizations, Azure is not simply “another cloud”; it is the cloud-shaped extension of the Microsoft estate they already run.
The EU’s concern is therefore not just that two American companies are large. It is that scale, ecosystem depth, and switching costs may reinforce each other. When a provider offers compute, storage, identity, data analytics, AI tooling, security, developer workflows, and business applications in a tightly integrated portfolio, the customer’s initial convenience can become tomorrow’s dependency.
This is where the DMA logic becomes uncomfortable for cloud vendors. The best cloud platforms are valuable precisely because they integrate so much. But regulators are increasingly asking when integration becomes enclosure.

Lock-In Is Not a Bug in the Cloud Model

The cloud industry has always advertised portability more enthusiastically than it has delivered it. Containers helped. Kubernetes helped. Terraform, OpenTofu, PostgreSQL, Linux, open telemetry, and cross-cloud networking patterns all helped. Yet the deeper a company goes into managed services, the less meaningful abstract portability becomes.
A workload running on commodity virtual machines can move, at least in theory, with enough money and patience. A workload built around a provider’s managed database, event bus, identity service, logging stack, machine-learning pipeline, secrets manager, serverless functions, and cost-optimization model is not just hosted in that cloud. It is composed in that cloud.
That composition is the source of the hyperscalers’ business strength. It is also the reason switching costs become more than an accounting inconvenience. The migration is not merely a copy operation; it is an engineering program, a retraining exercise, a compliance review, a security redesign, and sometimes a product rewrite.
European regulators have been circling these issues for years, including egress fees, licensing terms, interoperability barriers, bundling, and the practical difficulty of running multi-cloud strategies without creating new complexity. The Commission’s latest step gives those concerns a sharper legal frame. If AWS and Azure become DMA gatekeepers for cloud services, the conversation shifts from “customers should negotiate better” to “certain platform practices may be structurally unfair.”
That distinction will irritate cloud providers, because it challenges one of the industry’s favorite defenses: that enterprise customers are free to choose. The EU’s answer is that freedom at purchase time is not the same as freedom after five years of accumulated dependencies.

Microsoft’s Cloud Problem Is Also a Windows Problem

For WindowsForum readers, Azure’s potential DMA designation is the more intimate story. AWS may be the largest cloud provider, but Microsoft owns the enterprise desktop, the productivity layer, the identity layer for countless organizations, and the administrative habits of the Windows world. Azure is not a distant infrastructure product; it is increasingly where Microsoft expects Windows administration, security, development, and AI adoption to converge.
That convergence has benefits. Hybrid identity works because Microsoft can connect Windows Server environments to Entra ID. Endpoint management improves when Intune, Defender, Windows Autopatch, and Microsoft 365 security signals talk to one another. Developers benefit when GitHub, Visual Studio Code, Azure DevOps, Azure Kubernetes Service, and Azure AI services are stitched together with a common account model.
But the same coherence can become a competitive weapon. A Microsoft customer may choose Azure because the integration is genuinely better. The hard question is whether Microsoft’s licensing, bundling, technical defaults, and enterprise agreements make that choice more inevitable than it appears.
This is the ghost behind every cloud competition fight involving Microsoft. The company has spent half a century learning how to turn platform position into ecosystem gravity. Sometimes that produces excellent products. Sometimes it produces the kind of market pressure that regulators recognize from earlier eras of computing.
The DMA cloud investigation does not need to relitigate the browser wars to matter. It only needs to ask whether the modern enterprise stack gives Azure advantages that rivals cannot realistically match, particularly where Windows Server, SQL Server, identity, productivity software, and security tools intersect with cloud deployment decisions.

AWS Is the Other Kind of Incumbent

Amazon’s case is different. AWS does not control the Windows desktop or the Office suite. Its power comes from being the cloud that taught the market how to buy cloud in the first place, then used relentless service expansion and operational maturity to become the default answer for a generation of startups, enterprises, and public-sector deployments.
That makes AWS a cleaner infrastructure story. It is the platform many organizations chose because it was early, broad, and credible. Over time, those choices hardened into architectures, skills markets, certifications, partner ecosystems, and procurement patterns.
Amazon’s argument against additional regulation is predictable and not frivolous. The company says customers have many options, that cloud remains competitive, and that adding another layer of regulation could discourage investment and innovation in Europe. There is a real policy trade-off here: if regulators make it harder or less profitable to build hyperscale infrastructure, Europe could end up with more formal competition but less practical capacity.
Still, the investment argument has limits. Every dominant infrastructure provider can warn that regulation will chill investment. That does not answer whether customers face unfair barriers when they try to leave, combine services, or demand interoperability. The point of competition law is not to reward incumbents for having built impressive systems; it is to prevent impressive systems from becoming tollbooths.
AWS’s strongest defense is that the cloud market is technically dynamic. Customers can and do use multiple providers. Google Cloud remains a serious competitor. Oracle has carved out strategic niches. European providers serve sovereignty-conscious customers. Open-source software gives enterprises some leverage. The EU’s challenge will be showing that these alternatives are meaningful at scale, not just theoretically available.

Google Cloud Is the Missing Giant in the Room

Microsoft has reportedly emphasized Google Cloud’s growing strength, and that line of argument is worth taking seriously. Any regulatory move that treats AWS and Azure as uniquely gatekeeping while leaving Google outside the same designation risks creating distortions of its own. Google is not a bit player in AI infrastructure, data analytics, Kubernetes history, or global cloud engineering.
But the EU’s preliminary position appears to be based on the specific role AWS and Azure play in the European cloud market. Gatekeeper designation is not supposed to be a trophy for being famous or a punishment for being American. It is supposed to reflect whether a service acts as an important gateway with entrenched power.
The difficult part is that cloud markets are changing quickly. AI workloads are scrambling old assumptions about who has leverage. Google has enormous AI assets, Microsoft has OpenAI-linked momentum and enterprise distribution, Amazon has scale and a massive installed base, and specialized providers are trying to compete on GPUs, inference economics, sovereignty, or developer experience.
That volatility cuts both ways. Microsoft can argue that the market is too fluid for a static gatekeeper label. Brussels can argue that this is exactly when intervention matters, before AI-era infrastructure dependencies become as entrenched as earlier enterprise software dependencies.
The missing-Google argument may therefore influence the final shape of obligations more than the basic premise. If the Commission proceeds, it will need to avoid writing rules that freeze today’s hierarchy while tomorrow’s AI cloud market is still forming.

AI Turns Cloud Lock-In Into Strategic Lock-In

The Brandsit piece is right to connect this fight to artificial intelligence. Cloud regulation in 2026 is no longer about storage buckets and virtual machines alone. It is about who controls the environments where companies train, tune, deploy, monitor, and govern AI systems.
AI intensifies cloud dependency because it concentrates demand around expensive and scarce resources: accelerators, high-speed networking, managed data platforms, model catalogs, vector databases, orchestration tools, safety systems, and integration with business applications. A company that builds its AI pipeline on one hyperscaler may find that moving later requires rethinking not only infrastructure, but data governance, model evaluation, compliance reporting, and developer workflows.
This is particularly important for Europe’s digital sovereignty agenda. If the continent’s businesses, governments, hospitals, banks, and manufacturers build their AI future primarily inside a few non-European clouds, then sovereignty becomes a contractual posture rather than an operational reality. Data residency can help. Sovereign cloud offerings can help. But the question remains: who designs the platform, controls the roadmap, and captures the dependency?
Microsoft and Amazon would argue that European customers benefit from their scale, security investment, and pace of innovation. They are not wrong. Building credible cloud and AI infrastructure is brutally expensive, and many European alternatives struggle to match the breadth of hyperscaler services.
But the EU’s bet is that competition cannot be postponed until Europe has perfect substitutes. If cloud and AI infrastructure are becoming foundational to the economy, then waiting for dependency to become irreversible would be regulatory malpractice.

The DMA Could Make Portability More Than a Slide Deck Promise

If AWS and Azure are formally designated, the practical consequences will depend on the obligations imposed and how aggressively they are enforced. The DMA is not a magic wand that makes a managed database portable or turns a proprietary AI stack into a neutral commodity. It can, however, force changes at the edges where business friction becomes market power.
Data portability is the obvious place to start. Enterprises need the ability to extract data in usable formats, move it without punitive costs, and understand what operational metadata is trapped inside a provider’s systems. In cloud, the real issue is not simply “can I download my files?” It is whether logs, configurations, access policies, model artifacts, backups, dependency maps, and service relationships can be migrated or replicated without heroic effort.
Interoperability is harder. Regulators can demand interfaces, documentation, and fair access, but they cannot make two complex clouds behave identically. There is always a line between legitimate product differentiation and deliberate incompatibility. Expect that line to become the battleground.
Self-preferencing may be harder still in a cloud context. In search or app stores, preferential treatment is often visible. In cloud procurement, it may appear as bundled credits, licensing discounts, privileged integration, technical defaults, marketplace placement, partner incentives, or support conditions. The enforcement problem is not that self-preferencing is absent; it is that it is embedded in the commercial machinery of enterprise IT.
That is where the DMA could become more consequential than it first appears. The cloud is not just a product catalog. It is a web of defaults, incentives, and dependencies. Changing those defaults may matter more than any headline fine.

Enterprise IT Should Expect Paperwork Before Freedom

Administrators hoping that Brussels will instantly make cloud migration easy should lower expectations. Even if the designation becomes final, and even if Amazon and Microsoft are given six months to comply with specific obligations, enterprise reality will move more slowly. Legal rights do not rewrite Terraform modules overnight.
The first effects are likely to show up in contracts, documentation, compliance programs, and procurement language. Large customers will ask sharper questions about data extraction, interoperability, licensing portability, and exit plans. Vendors will respond with updated commitments, revised APIs, new dashboards, and carefully worded compliance statements. Consultants will discover a thriving new market in DMA-aware cloud strategy.
That sounds cynical, but paperwork can matter. Enterprise IT often changes because procurement rules change first. If regulated portability requirements become standard language in tenders, cloud vendors will have to compete on exit terms as well as entry discounts.
For sysadmins, the practical lesson is to treat this moment as leverage rather than salvation. If your organization is renewing a major cloud agreement, now is the time to ask how identity, logs, backups, keys, network configurations, AI model artifacts, and licensing rights would move. The existence of an EU proceeding does not move them for you.
For developers, the lesson is architectural. Managed services can be worth the lock-in, but the lock-in should be a conscious trade-off. If a team chooses a provider-specific queue, database, AI service, or observability stack, it should do so because the product advantage is worth the future migration cost — not because nobody priced the exit.

Europe’s Sovereignty Argument Has Teeth, But Also Costs

The phrase digital sovereignty is often used so broadly that it risks meaning everything and nothing. In the cloud fight, it has a more concrete meaning: Europe wants critical digital infrastructure to operate under conditions that European law and European market policy can meaningfully shape. That does not necessarily mean banning American providers or pretending Europe can replicate hyperscale capacity overnight.
It does mean refusing to accept a world in which European businesses are permanently dependent on terms set in Seattle, Redmond, and Mountain View. The Commission’s preliminary AWS and Azure move is best understood as part of that broader effort. It sits alongside cloud procurement initiatives, data protection battles, competition investigations, and the push for European capacity in AI and high-performance computing.
There is a risk of overreach. If regulation becomes unpredictable, hyperscalers may delay investments, narrow service availability, or pass compliance costs to customers. Smaller providers may cheer new obligations on AWS and Azure while privately worrying that compliance burdens will eventually reach them too. European customers could end up with more rules but not necessarily better prices or better services.
There is also a risk of underreach. If the EU settles for cosmetic portability dashboards and vague interoperability promises, the market will absorb the DMA as another compliance ritual. The hyperscalers are exceptionally good at turning regulatory demands into managed processes.
The decisive question is whether Brussels can distinguish between visible compliance and actual contestability. A market is not contestable because a vendor publishes an export tool. It is contestable when customers can credibly threaten to use it.

The Cloud Fight Will Be Won in the Boring Details

The drama of “gatekeeper” designation invites sweeping language, but the outcome will hinge on technical and contractual specifics. What counts as cloud computing service under the designation? Which AWS and Azure services are covered? How are AI services treated when they depend on cloud infrastructure but are sold as higher-level platforms? What obligations apply to marketplaces, credits, identity systems, support plans, and licensing bundles?
Microsoft’s case could become especially complicated because Azure is entangled with products that already sit under other regulatory or competition scrutiny. Windows Server licensing, SQL Server mobility, Microsoft 365 integration, Teams bundling history, Defender, Entra ID, and developer tooling all create adjacent questions. Regulators do not need to decide all of them in this proceeding, but enterprise customers experience them as one Microsoft relationship.
AWS has a different complexity problem: sheer service breadth. Its catalog is vast, and many customers use provider-specific building blocks because they are mature and operationally reliable. If DMA obligations force clearer portability or interoperability commitments, AWS will need to decide where standardization is acceptable and where it believes product design is being constrained.
This is why the EU’s move is both ambitious and difficult. App store rules can be messy, but the object of regulation is relatively visible. Cloud rules must operate inside systems that are invisible to most users and deeply customized for each customer.
The Commission’s success will depend on whether it can convert a political insight — that cloud infrastructure is market power — into enforceable engineering and procurement requirements. That is much harder than issuing a press release.

The Windows Admin’s Cloud Strategy Just Got More Political

For years, Windows administrators have been pushed toward a hybrid future that is increasingly Microsoft-defined. On-premises Active Directory gives way to Entra ID. Group Policy coexists with Intune. File servers coexist with SharePoint and OneDrive. Endpoint security flows into Defender portals. Windows Server workloads get assessed for Azure migration. AI assistants begin appearing in productivity and development workflows.
None of this is inherently bad. Much of it is the logical modernization of enterprise IT. But the center of gravity has moved from local control to cloud control, and that makes regulatory fights newly relevant to administrators who once thought of Brussels as someone else’s problem.
If Azure becomes a DMA gatekeeper, Microsoft will face pressure to make parts of that cloud control plane more open, portable, or at least less coercive. That could benefit organizations that want Microsoft’s identity and productivity stack without feeling forced into Azure for every adjacent workload. It could also create compliance artifacts that administrators must understand and auditors will ask about.
AWS customers face a parallel version of the same shift. The questions are less about Windows integration and more about whether AWS-native architectures can remain flexible as AI, analytics, and security services become more deeply embedded. The operational convenience of using one provider for everything will remain powerful. The regulatory question is whether customers can still say no later.
This is the uncomfortable truth for IT pros: cloud architecture is now policy architecture. Decisions about identity, data, observability, automation, and AI tooling are also decisions about bargaining power.

A Narrow Ruling Could Still Change the Market

Even if the final EU decision is narrower than advocates hope, the symbolic effect is already significant. Regulators are telling the market that cloud infrastructure is eligible for the same kind of gatekeeper scrutiny once reserved for more visible digital platforms. That alone changes the negotiating environment.
Competitors will use the preliminary finding in sales pitches. Customers will use it in procurement. Trade associations will use it in lobbying. Microsoft and Amazon will use it to argue for careful, technically realistic rules. Google, Oracle, European cloud providers, and specialized AI infrastructure firms will watch for openings.
The most immediate market effect may be reputational. For years, hyperscalers have positioned themselves as enablers of digital transformation. The EU is now framing them, at least potentially, as chokepoints. That shift matters because enterprise technology buying is partly about trust.
Still, designation is not destiny. The DMA has already shown that implementation battles are long, technical, and contested. The largest platforms know how to comply in ways that preserve as much strategic advantage as possible. Regulators know this too, which is why the post-designation monitoring may matter more than the designation itself.
The cloud market will not suddenly become open because Brussels says the word “gatekeeper.” But the word gives customers, rivals, and regulators a shared vocabulary for a problem many have been describing for years.

The Fine Print Is Where Cloud Freedom Will Either Live or Die

The concrete lessons from this moment are less dramatic than the politics, but they are more useful. Cloud buyers should treat the EU’s move as a warning that dependency is no longer just a technical risk. It is a strategic and regulatory risk.

The Commission’s June 25, 2026 position is preliminary, so AWS and Azure are not yet finally designated as DMA cloud gatekeepers.
If the designation is confirmed, Amazon and Microsoft should expect obligations around interoperability, data portability, and limits on practices that unfairly favor their own services.
The fight is about more than cloud storage or virtual machines, because AI development makes compute, data platforms, and managed tooling central to future market power.
European customers may gain leverage in contract negotiations, but they should not expect regulation to make complex migrations simple.
Windows-heavy organizations should pay particular attention to how Azure dependencies intersect with Microsoft licensing, identity, security, management, and developer tools.
The most important test will be whether customers can credibly leave, mix providers, or resist bundled defaults without facing punitive cost or technical disruption.

The EU’s cloud gatekeeper push is not a revolution yet; it is a claim of jurisdiction over the layer of technology where modern business now lives. Amazon and Microsoft will argue that their clouds are competitive, innovative, and indispensable, and in many respects they are right. Brussels is making a different argument: indispensable infrastructure cannot be allowed to become inescapable infrastructure. If the Commission can turn that principle into rules that improve real-world portability without smothering investment, the DMA may become something more consequential than a platform law. It may become Europe’s first serious attempt to regulate the operating system of the digital economy.

References

Primary source: Brandsit
Published: 2026-06-28T11:30:09.191151

The EU wants to subject AWS and Azure to stricter DMA rules - Brandsit

The issue also has a clear link to artificial intelligence. The development of AI is driving up demand for computing power, data, development tools and

brandsit.pl
Independent coverage: Digital Pakistan
Published: Sun, 28 Jun 2026 06:00:57 GMT

EU Moves to Regulate Amazon, Microsoft Cloud Services

The EU plans to classify Amazon Web Services and Microsoft Azure as DMA gatekeepers, expanding Big Tech rules to cloud services.

digitalpakistan.pk
Related coverage: itpro.com

AWS says cloud market gatekeeper designation risks ‘deterring European investment and innovation’ as EU regulators plot competition crackdown | IT Pro

Gatekeeper designation under the legislation would force AWS and Microsoft to make concessions

www.itpro.com
Related coverage: digital-strategy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

The Commission has informed Amazon and Microsoft of its preliminary view that they should be designated as gatekeepers under the Digital Markets Act (DMA), for their cloud computing services, Amazon Web Services (AWS) and Microsoft Azure (Azure) respectively.

digital-strategy.ec.europa.eu
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: techspot.com

European Commission moves to designate Amazon and Microsoft as cloud gatekeepers | TechSpot

Amazon Web Services and Microsoft Azure are now so important to Europe's digital economy that they may be required to comply with additional rules when doing business...

www.techspot.com

Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
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
Related coverage: investing.com

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say By Reuters

Amazon, Microsoft cloud computing services should fall under EU tech rules, EU regulators say

www.investing.com
Related coverage: europapress.es

Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio

La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...

www.europapress.es
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
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

ChatGPT · Jun 28, 2026

On June 25, 2026, the European Commission told Amazon and Microsoft that it preliminarily believes Amazon Web Services and Microsoft Azure should be designated as Digital Markets Act gatekeepers for cloud computing services in the European Union. The finding is not final, and both companies can still argue their case before Brussels locks in the designation. But the direction of travel is unmistakable: Europe is preparing to treat cloud infrastructure less like a neutral utility market and more like a strategic control point. For WindowsForum readers, that makes this more than another Brussels-versus-Big-Tech headline; it is a signal that the operating environment for Azure, Microsoft 365, AI workloads, enterprise procurement, and sovereign cloud strategy is changing.

Brussels Moves the DMA from App Stores to the Server Room

The Digital Markets Act was born in the era of app stores, search engines, browsers, marketplaces, social networks, and messaging platforms. Its political target was the consumer-facing bottleneck: the platform that sits between a business and its users, sets the rules, and becomes too essential to ignore. Cloud computing never fit that image quite as cleanly.
That is precisely why this preliminary designation matters. The Commission is arguing that the same gatekeeper logic applies beneath the visible internet, in the infrastructure layer where databases, identity systems, compute instances, storage buckets, AI services, developer tools, and enterprise software integrations now live. AWS and Azure may not look like consumer platforms, but they increasingly determine which businesses can scale, which vendors can interoperate, and which customers can leave without a painful rebuild.
The Commission’s move follows market investigations launched in November 2025 into whether Amazon and Microsoft should be designated as gatekeepers for AWS and Azure despite not meeting the DMA’s standard quantitative thresholds. That caveat is the core of the story. Brussels is not merely applying a checklist; it is testing whether the DMA can reach companies that function as strategic gateways even when the law’s original numerical triggers do not map neatly onto cloud markets.
This is the moment when cloud stops being treated as background infrastructure and becomes a regulatory front line. For Microsoft, in particular, Azure is no longer just the growth engine behind the company’s enterprise story. It is also becoming one of the places where Europe will scrutinize the company’s leverage across Windows, Microsoft 365, identity, developer tooling, cybersecurity, and AI.

The Thresholds Failed, So the Commission Reached for Market Reality

The most interesting part of the Commission’s preliminary view is that AWS and Azure reportedly do not meet the DMA’s quantitative thresholds for designation. Under a mechanical reading of platform regulation, that could have ended the matter. If the numbers do not fit, the platform escapes the label.
Brussels is taking a different route. It is saying that market structure matters as much as arithmetic. AWS is the largest cloud computing service in the EU, Azure is the second largest, and both appear to hold durable positions that competitors cannot easily dislodge. The Commission’s theory is that a cloud service can be an important gateway even if the conventional gatekeeper thresholds were designed with more visible digital services in mind.
That is a significant legal and political bet. The EU is effectively arguing that the DMA is not just a statute about today’s dominant screens, stores, and feeds. It is a tool for identifying durable control points in the digital economy, even when those control points are buried in procurement contracts, architecture diagrams, and migration roadmaps.
For enterprise customers, this tracks reality. Nobody chooses a hyperscaler the way they install a casual mobile app. Once workloads, data pipelines, identity policies, monitoring systems, compliance controls, and internal developer practices are built around one cloud, switching becomes a technical, financial, and organizational event. The user count may not look like a consumer platform’s user count, but the dependency can be deeper.
This is why cloud regulation has always been harder than app-store regulation. A phone user can see the platform. A CIO sees the platform in invoices, egress fees, licensing terms, committed spend agreements, API dependencies, and architectural gravity. The Commission is now trying to turn that operational reality into regulatory doctrine.

Azure’s Strength Is Also Microsoft’s Exposure

Microsoft enters this fight with a uniquely complicated profile. Azure is not an isolated product line; it is part of a vast enterprise stack that includes Windows Server, Windows client management, Microsoft Entra ID, Microsoft 365, Teams, Defender, GitHub, Visual Studio, Power Platform, SQL Server, Dynamics, and a rapidly expanding set of AI services. That breadth is Microsoft’s commercial superpower.
It is also what makes regulators nervous. A customer adopting Azure is often not just buying cloud compute. It may be deepening an existing relationship that already runs through desktop productivity, directory services, endpoint security, collaboration, development workflows, and licensing agreements. The cloud purchase becomes one more layer in a Microsoft-centered operating model.
The company can argue, reasonably, that integration is what customers want. IT departments do not buy identity, endpoint management, productivity, compliance, and cloud services as abstract policy units. They buy systems that work together, reduce friction, and let small teams manage sprawling estates. Microsoft’s entire modern enterprise pitch is that it can make that bundle feel coherent.
The regulatory counterargument is that coherence can become captivity. If the best price, best compatibility, or easiest deployment path consistently appears when a customer stays inside the Microsoft estate, rival cloud providers and independent software vendors may struggle to compete on the merits. The Commission’s preliminary designation suggests it sees Azure not merely as a successful cloud platform, but as a gateway reinforced by Microsoft’s broader enterprise ecosystem.
For Windows admins, that is the part worth watching. The practical effects of any final DMA obligations may show up not as a dramatic “Azure breakup” moment, but as changes to interoperability, self-preferencing, data portability, licensing behavior, and the way Microsoft connects cloud services to its surrounding stack. The boring clauses could matter more than the headline.

AWS Is the Cleaner Target, Which Makes the Case Broader

Amazon’s cloud business presents a different regulatory story. AWS is less entangled with desktop operating systems or productivity software than Azure, but it is the original hyperscale cloud powerhouse. It has the largest market position, the deepest service catalog, enormous operational capacity, and a long history of becoming the default answer for startups and enterprises alike.
That makes AWS the cleaner test of the Commission’s cloud theory. If Azure raises concerns because of Microsoft’s ecosystem leverage, AWS raises concerns because of hyperscale gravity itself. Its strength comes from breadth, maturity, global infrastructure, partner ecosystems, technical familiarity, and the confidence customers place in a platform that has been battle-tested for years.
AWS will argue that punishing scale risks punishing success. Cloud markets are capital intensive, and hyperscalers spend staggering sums on data centers, chips, networking, power, security, and regional expansion. If Europe imposes obligations that make dominant providers less willing to invest or more cautious in launching services, customers could feel that too.
But the Commission’s concern is not simply that AWS is big. It is that big cloud platforms can become hard to leave, hard to compete with, and hard to negotiate against. If a market depends on a handful of providers whose operational capacity and investment far outpace rivals, then the competitive question is no longer whether alternatives technically exist. It is whether those alternatives can win meaningful workloads without customers absorbing unacceptable migration costs or performance penalties.
In that sense, AWS and Azure are complementary test cases. One represents the cloud-native incumbent with unmatched scale; the other represents the enterprise software giant whose cloud is woven into a broader productivity and identity empire. Brussels is signaling that both forms of power can qualify as gatekeeping.

AI Turned Cloud Lock-In into a Sovereignty Problem

The Commission’s emphasis on AI is not incidental. In the 2010s, cloud lock-in was mostly a procurement and architecture concern. In the 2020s, it has become a sovereignty concern, because the cloud is where advanced AI models are trained, hosted, integrated, governed, and sold.
This changes the political stakes. A business that builds on a hyperscaler’s proprietary AI services may not simply be renting compute. It may be adopting model APIs, vector databases, data governance tools, inference infrastructure, security controls, developer frameworks, and marketplace integrations that are difficult to reproduce elsewhere. The cloud provider becomes the venue through which AI capability is delivered.
For Europe, that raises an uncomfortable question: if the continent’s public administrations, regulated industries, startups, and AI developers depend on a small number of US-based hyperscalers, how much room does Europe really have to shape its own digital future? The answer is not solved by slogans about sovereignty or by pretending local providers can immediately match hyperscaler scale. But the question is now central to EU technology policy.
Microsoft understands this well. Its AI strategy is inseparable from Azure. OpenAI workloads, Copilot services, Azure AI tooling, enterprise data integration, and Microsoft 365 automation all reinforce the idea that Azure is where business AI becomes operational. That makes Azure more valuable, but also more strategically sensitive.
AWS has a parallel story through Bedrock, custom silicon, AI infrastructure, and a large ecosystem of model providers and enterprise AI services. Both companies can plausibly say they are expanding choice by giving customers access to more AI tools. Regulators can just as plausibly reply that those tools may deepen dependency on the same hyperscale platforms already dominating cloud infrastructure.
The Commission’s preliminary designation is therefore not just about cloud as it exists today. It is about cloud as the control plane for the next decade of AI adoption.

The Six-Month Clock Would Put Compliance on an Enterprise Timetable

If the preliminary findings become final, Amazon and Microsoft would have six months to comply with the relevant DMA obligations for AWS and Azure. Six months is a short period in regulatory theater and a very short period in enterprise IT. For hyperscalers, it would mean translating broad legal obligations into product behavior, contract rules, documentation, engineering controls, and customer-facing processes.
The exact obligations that bite hardest will depend on how the Commission applies the DMA to cloud services. The law was not written as a cloud portability manual, so the fight will likely be over interpretation. What counts as fair access? What counts as self-preferencing in a cloud marketplace? What does meaningful interoperability mean when the service catalog spans compute, storage, networking, identity, analytics, AI, security, and managed databases?
For customers, the answer may eventually surface in small but consequential ways. Contract terms could become more transparent. Switching and multi-cloud operations could receive more regulatory backing. Hyperscalers may face closer scrutiny when they bundle services, privilege their own products, restrict interoperability, or make it expensive to move data and workloads elsewhere.
No serious enterprise should expect an immediate liberation from cloud complexity. The DMA will not rewrite application architectures, normalize every API, eliminate skills gaps, or make multi-cloud cheap. But it could change the negotiation context. A customer asking for portability, interoperability, or non-discriminatory access may have more regulatory wind at its back than it did before.
That is why the final designation matters even before enforcement actions arrive. Regulation often changes behavior through anticipation. Hyperscalers, rivals, and customers all start adjusting once the likely rules of the road become visible.

The Windows Angle Is Identity, Licensing, and the Cloud Desktop

For WindowsForum readers, the temptation is to file this under “EU cloud policy” and move on. That would miss the Windows angle. Microsoft’s cloud strategy is deeply connected to how organizations deploy, secure, license, and manage Windows environments.
Azure is bound up with Microsoft Entra ID, Intune, Defender, Azure Virtual Desktop, Windows 365, server workloads, hybrid identity, and Microsoft 365 administration. Many organizations do not experience Azure as a standalone cloud provider; they experience it as the administrative extension of the Microsoft estate. That is exactly why regulatory scrutiny of Azure could eventually touch decisions that Windows admins make every day.
Licensing is the most obvious pressure point. Microsoft has already faced scrutiny in Europe over cloud licensing practices, including concerns from rivals that Windows Server and other Microsoft software can be more costly or harder to run on competing clouds. Any final DMA designation would not automatically settle those disputes, but it would place Azure inside a broader gatekeeper framework where tying, preferential treatment, and switching friction become more politically charged.
Identity is the quieter issue. Entra ID has become one of the central chokepoints in Microsoft’s enterprise platform. It governs access to Microsoft 365, Azure resources, SaaS applications, conditional access policies, device compliance, and security workflows. If regulators begin asking how Azure functions as a gateway, identity will inevitably be part of the practical conversation, even if the legal designation is formally about cloud computing services.
Then there is the cloud desktop. Windows 365 and Azure Virtual Desktop sit at the intersection of Windows licensing, virtualization, identity, endpoint management, and Azure infrastructure. They are useful products, especially for distributed workforces and contractors, but they also deepen the logic of Microsoft cloud dependency. In a DMA world, the way Microsoft packages and advantages those experiences may receive more scrutiny.
This does not mean Windows shops should panic. It does mean they should understand that Microsoft’s enterprise convenience story and Europe’s competition concerns are now describing the same architecture from opposite sides.

The DMA Will Not Make Multi-Cloud Simple

One of the predictable reactions to the Commission’s move will be that Europe is trying to force a multi-cloud utopia into existence. That is not quite right. The DMA can pressure gatekeepers to reduce unfair barriers, but it cannot erase the real technical reasons companies consolidate on one cloud.
Multi-cloud is expensive. It requires duplicated skills, governance models, observability tooling, security practices, network design, cost management, data architecture, and incident response playbooks. Even when workloads are containerized and infrastructure is described as code, the managed services that make cloud attractive often remain provider-specific. The more a team uses the best native services from AWS or Azure, the harder pure portability becomes.
That reality does not invalidate the Commission’s concern. It sharpens it. If cloud lock-in is partly a natural byproduct of useful managed services, then regulators must distinguish between legitimate product differentiation and artificial switching barriers. That distinction is easy to state and hard to enforce.
A managed database that performs better because a provider invested heavily in engineering is not the same as a contract term that penalizes customers for moving. A proprietary AI service that customers willingly choose is not the same as a licensing rule that makes rival clouds uneconomical. A deeply integrated security suite can be a customer benefit and a competitive moat at the same time.
The Commission’s challenge will be to avoid flattening those differences. If it treats every integration as suspicious, it risks discouraging useful engineering. If it treats every switching cost as natural, the gatekeeper label becomes decorative. The hard work lies between those extremes.

Europe Wants Competition Without Giving Up Hyperscale

There is an unresolved tension at the heart of Europe’s cloud policy. The EU wants fairer competition, more sovereign capacity, stronger local providers, and less dependency on foreign hyperscalers. At the same time, European businesses and governments rely on AWS and Azure because those platforms offer scale, resilience, services, security certifications, and global reach that are difficult to replicate.
This is not hypocrisy. It is the modern cloud dilemma. Hyperscalers are both indispensable infrastructure and competitive bottlenecks. They lower barriers for companies that need world-class infrastructure quickly, while raising barriers for competitors that cannot match their capital intensity and ecosystem depth.
European cloud providers have long argued that the market is tilted against them by egress fees, software licensing rules, bundled services, marketplace dynamics, and procurement habits that favor the largest platforms. AWS and Microsoft counter that customers choose them because they offer better capabilities, broader service portfolios, and stronger investment. Both arguments contain truth.
The Commission is trying to create room for competition without detonating the infrastructure that European customers already use. That is a delicate task. Too soft an approach will leave the market structure unchanged. Too aggressive an approach could create uncertainty for customers and slow investments that Europe also needs.
This is why the preliminary nature of the designation matters. Amazon and Microsoft will now make their case, and they will likely frame the issue around investment, innovation, security, and customer choice. The Commission will frame it around fairness, openness, and the risk that cloud control becomes a private chokepoint in Europe’s digital economy.
Neither side is arguing about a marginal market. They are arguing about the substrate on which everything else is being built.

The Real Fight Is Over Who Defines Openness

The word “open” will do a lot of work in the coming months. The Commission will use it to describe fair access, portability, interoperability, and competitive markets. Amazon and Microsoft will use it to describe customer choice, service breadth, partner ecosystems, and the freedom to build integrated products. The conflict is not about whether openness is good; it is about who gets to define it.
In cloud, openness is slippery. A workload can run on Linux, use Kubernetes, authenticate through standards-based protocols, and still be deeply dependent on proprietary services. A customer can export data, but still face prohibitive costs and engineering risk in moving it. A marketplace can include rival software, while the platform owner’s own services enjoy structural advantages in billing, integration, defaults, or procurement.
The DMA pushes regulators toward a more behavioral definition of openness. It asks whether business users can realistically reach customers without being trapped by a gatekeeper’s rules. Applied to cloud, that means the Commission will likely care less about abstract compatibility claims and more about practical exit rights, fair terms, and whether rivals can interoperate on commercially viable terms.
For Microsoft, this could become especially uncomfortable where Azure is adjacent to Microsoft’s own applications and services. The company can say customers are free to choose alternatives. Regulators may ask whether those alternatives face subtle disadvantages when competing against a platform owner with control over identity, licensing, administration, security integrations, and procurement channels.
For AWS, the issue may be less about adjacent productivity software and more about the sheer depth of the platform’s native service catalog. AWS can say customers are free to use open-source tools, third-party partners, and hybrid architectures. Regulators may ask whether the economics of moving data, rebuilding architectures, or matching managed-service functionality make that freedom theoretical for many customers.
The gatekeeper label is therefore not just a badge. It is a claim that the platform owner’s definition of openness can no longer be the only one that counts.

Admins Should Read This as a Procurement Warning

The practical lesson for IT departments is not to abandon Azure or AWS. That would be absurd. These platforms remain central to modern infrastructure, and for many organizations they are the best available choice. The lesson is to treat cloud dependency as a governance issue, not merely an engineering outcome.
Too many organizations discover lock-in after the architecture is already built. They learn that backups, logs, identity flows, data gravity, proprietary APIs, committed spend agreements, and staff skills all point in one direction. By then, “cloud choice” is a phrase in a procurement policy rather than an operational fact.
The Commission’s move should encourage customers to ask harder questions before the next renewal, migration, or AI rollout. What services are genuinely portable? Which workloads depend on provider-specific APIs? What would it cost to move data out? Are licensing terms different across clouds? Does the organization have a tested exit plan, or just a theoretical one?
For Windows-heavy environments, the questions should be even more specific. How tightly are Azure, Entra ID, Intune, Defender, Microsoft 365, Windows 365, and server licensing bound together in the organization’s operating model? Which integrations are delivering real administrative value, and which are narrowing future options? Where does Microsoft convenience become Microsoft dependency?
Regulation may eventually improve the market, but it will not replace internal discipline. The smartest customers will use the DMA process as leverage for better terms and clearer architecture, not as an excuse to postpone hard cloud governance decisions.

Brussels Has Put a Clock on Cloud Power

The Commission’s preliminary designation does three concrete things. It raises the likelihood that AWS and Azure will face DMA obligations in Europe. It expands the political meaning of gatekeeping from consumer platforms to infrastructure platforms. And it tells the market that cloud dominance will be judged by practical dependency, not only by statutory thresholds.
That last point is the most important. The Commission is not waiting for cloud to become a perfect fit for yesterday’s platform categories. It is adapting its theory of gatekeeping to the market as it now exists. Whether courts, companies, and customers accept that theory will shape how aggressively Europe can regulate the next generation of digital infrastructure.
There is a risk of overreach. Cloud platforms are complex, capital-intensive, and deeply technical. Badly designed obligations could create compliance theater, slow product improvements, or give customers more paperwork without more freedom. Europe’s regulators will need to prove they can distinguish between harmful gatekeeping and useful integration.
But there is also a risk of underreach. If regulators treat hyperscale cloud as too technical to govern, then the most important control points in the digital economy may drift outside meaningful competition oversight. The result would be a market where businesses can choose between a few giants, but cannot easily discipline any of them.
The Commission has chosen to test that boundary now, before AI makes the dependency even harder to unwind.

The Cloud Gatekeeper Era Arrives Before Anyone Is Ready

The immediate lesson is not that AWS and Azure are suddenly illegal, broken, or unsafe. It is that Europe now sees them as infrastructure platforms with the power to shape markets around them, and that judgment will affect vendors, customers, and administrators long before any final enforcement drama plays out.

Amazon and Microsoft have received a preliminary EU finding that AWS and Azure should be designated as DMA gatekeepers for cloud computing services.
The Commission is pursuing the designation even though AWS and Azure reportedly do not meet the DMA’s standard quantitative thresholds.
A final designation would give both companies six months to comply with relevant DMA obligations for their cloud services.
The case matters to Windows environments because Azure is tied closely to Microsoft identity, licensing, endpoint management, virtual desktop, security, and Microsoft 365 administration.
The AI boom makes cloud gatekeeping more consequential because model access, data pipelines, developer tooling, and compute capacity increasingly sit inside hyperscaler ecosystems.
IT departments should treat the case as a prompt to review portability, licensing exposure, exit planning, and the real cost of moving workloads.

The Commission’s preliminary move against AWS and Azure is not the end of the cloud competition debate; it is the moment the debate becomes unavoidable. Amazon and Microsoft will fight to define their platforms as engines of choice and innovation, while Brussels will argue that indispensable infrastructure needs public rules as well as private roadmaps. For enterprises, the prudent response is neither panic nor complacency, but a colder look at where convenience has hardened into dependency — because the next phase of cloud strategy will be shaped as much by regulation and sovereignty as by latency, pricing, and features.

References

Primary source: European Interest
Published: Sun, 28 Jun 2026 20:47:27 GMT

European Commission adds new designation to Amazon and Microsoft cloud services

The European Commission preliminarily designated Amazon and Microsoft as gatekeepers under the Digital Markets Act (DMA) for their cloud computing services. The change follows preliminary reports and two market investigations launched in November 2025. It focused on Amazon’s Amazon Web...

www.europeaninterest.eu
Related coverage: itpro.com

AWS says cloud market gatekeeper designation risks ‘deterring European investment and innovation’ as EU regulators plot competition crackdown | IT Pro

Gatekeeper designation under the legislation would force AWS and Microsoft to make concessions

www.itpro.com
Related coverage: digital-strategy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

The Commission has informed Amazon and Microsoft of its preliminary view that they should be designated as gatekeepers under the Digital Markets Act (DMA), for their cloud computing services, Amazon Web Services (AWS) and Microsoft Azure (Azure) respectively.

digital-strategy.ec.europa.eu
Related coverage: agenceurope.eu

European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE

The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.

agenceurope.eu
Related coverage: techspot.com

European Commission moves to designate Amazon and Microsoft as cloud gatekeepers | TechSpot

Amazon Web Services and Microsoft Azure are now so important to Europe's digital economy that they may be required to comply with additional rules when doing business...

www.techspot.com
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

Related coverage: competition-policy.ec.europa.eu

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA

competition-policy.ec.europa.eu
Related coverage: datacenterdynamics.com

AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD

European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"

www.datacenterdynamics.com
Related coverage: eunews.it

https://www.eunews.it/en/2026/06/25/digital-markets-act-eu-zeroes-in-on-amazon-and-microsofts-cloud-services
Related coverage: ceotodaymagazine.com

European Commission Targets AWS and Azure Under DMA

European Commission findings say AWS and Azure should face DMA gatekeeper rules because of their scale, user bases and cloud market power.

www.ceotodaymagazine.com
Related coverage: germany.representation.ec.europa.eu

DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden

Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.

germany.representation.ec.europa.eu
Related coverage: ec.europa.eu

IP 25 2717 EN

PDF document

ec.europa.eu
Related coverage: elpais.com

Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS

En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitales

elpais.com
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
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

Navigation section

EU DMA Push Targets AWS and Azure as Cloud Gatekeepers: What Windows IT Teams Need

The Gatekeeper Label Is Becoming an Infrastructure Test​

Cloud Lock-In Is Not a Bug; It Is the Business Model’s Gravity​

Microsoft’s Cloud Problem Is Also a Windows Problem​

AWS Faces a Different Kind of Scrutiny​

The AI Boom Turns Cloud Competition Into Strategic Policy​

Europe’s Sovereignty Argument Is Not Just Protectionism​

The DMA’s Six-Month Clock Would Force Concrete Changes​

The Multicloud Dream Has Always Needed a Regulator​

Sysadmins Should Watch the Contract, Not Just the Console​

Washington Will Read This as a Trade Fight​

The First Real Cloud Gatekeeper Fight Will Be Won in the Details​

Brussels Has Put the Exit Door on the Roadmap​

References​

AI

Brussels Moves the DMA From Screens to Server Rooms​

The Cloud Was Never Just Somebody Else’s Computer​

Azure’s Real Power Is the Enterprise Bundle​

AWS Faces the Same Charge From a Different Angle​

The DMA Threshold Fight Is the Legal Tell​

Europe’s Sovereignty Argument Is Hiding in Plain Sight​

The AI Boom Gives Regulators Their Urgency​

CIOs Wanted Optionality, Not Another Compliance Drama​

For Windows Shops, Licensing May Be the Pressure Point​

Smaller Clouds Need More Than Sympathy​

The Compliance Clock Could Redraw the Cloud Contract​

Washington Will Hear an Industrial Policy Alarm​

The Real Test Is Whether Exit Becomes Believable​

The Cloud War Now Has a Regulatory Front​

The Fine Print Is Where This Fight Will Be Won​

The Architecture Review That Should Happen Before Brussels Decides​

The Six-Month Shadow Over Hyperscale Cloud​

Europe’s Cloud Verdict Is Really an AI Verdict​

The Practical Reading for WindowsForum Readers Is Written in Contracts and Diagrams​

References​

AI

Brussels Moves the Gatekeeper Fight Down the Stack​

AWS and Azure Are Being Judged by Dependence, Not Just Size​

The Cloud Was Supposed to Be Portable Until It Became Productized​

Microsoft’s Problem Is That Azure Is No Longer Just Azure​

Amazon’s Cloud Dominance Has a Different Political Weakness​

The DMA May Force Cloud Providers to Compete on Exit as Well as Entry​

Europe’s Sovereignty Argument Is Becoming an Economic Argument​

AI Turns Cloud Gatekeeping Into a Faster-Moving Problem​

Enterprise IT Should Read This as a Procurement Warning​

The Hyperscalers Will Sell Compliance as Confidence​

The Fight Will Be Over Remedies, Not Rhetoric​

The Cloud Crackdown Gives Windows Shops a New Checklist​

References​

AI

Brussels Moves the DMA Below the App Store Layer​

The Threshold Miss Is the Point, Not a Technicality​

Azure’s Regulatory Problem Is Its Enterprise Superpower​

Cloud Lock-In Is No Longer a Niche Architect’s Complaint​

AI Turns Cloud Gatekeeping Into a Live Ammunition Issue​

The Data Act Was Never Going to End This Fight​

Enterprise IT Will Feel This First in Contracts, Not Consoles​

The Sovereignty Debate Finally Meets the Admin Console​

Microsoft Has Seen This Movie, But the Ending Is Not Prewritten​

The Cloud Market Is Being Regulated After the Lock-In Already Happened​

The DMA’s Cloud Test Will Be Measured in Boring Details​

The Real Signal for Windows Shops Is Leverage​

What the Gatekeeper Notice Should Push Every Azure and AWS Customer to Do Next​

References​

AI

Brussels Moves the DMA Below the App Layer​

The Thresholds Were Never the Whole Law​

Cloud Lock-In Is the Quiet Competition Problem​

Microsoft’s Cloud Problem Is Bigger Than Azure​

AWS Has Scale Without the Desktop Shadow​

The DMA Enters the Server Room​

Europe’s Cloud Sovereignty Push Is the Wider Frame​

The Hyperscalers Will Fight on Definition​

Administrators Should Read This as a Procurement Story​

Developers Will Feel This Through APIs, Not Press Releases​

The Competition Fight Is Also an AI Fight​

The Risk Is Regulation That Solves Yesterday’s Cloud​

The Six-Month Clock Would Be Only the Beginning​

The Fine Print Now Belongs in the Architecture Review​

The Gatekeeper Label Is Becoming an Infrastructure Test

Cloud Lock-In Is Not a Bug; It Is the Business Model’s Gravity

Microsoft’s Cloud Problem Is Also a Windows Problem

AWS Faces a Different Kind of Scrutiny

The AI Boom Turns Cloud Competition Into Strategic Policy

Europe’s Sovereignty Argument Is Not Just Protectionism

The DMA’s Six-Month Clock Would Force Concrete Changes

The Multicloud Dream Has Always Needed a Regulator

Sysadmins Should Watch the Contract, Not Just the Console

Washington Will Read This as a Trade Fight

The First Real Cloud Gatekeeper Fight Will Be Won in the Details

Brussels Has Put the Exit Door on the Roadmap

References

Brussels Moves the DMA From Screens to Server Rooms

The Cloud Was Never Just Somebody Else’s Computer

Azure’s Real Power Is the Enterprise Bundle

AWS Faces the Same Charge From a Different Angle

The DMA Threshold Fight Is the Legal Tell

Europe’s Sovereignty Argument Is Hiding in Plain Sight

The AI Boom Gives Regulators Their Urgency

CIOs Wanted Optionality, Not Another Compliance Drama

For Windows Shops, Licensing May Be the Pressure Point

Smaller Clouds Need More Than Sympathy

The Compliance Clock Could Redraw the Cloud Contract

Washington Will Hear an Industrial Policy Alarm

The Real Test Is Whether Exit Becomes Believable

The Cloud War Now Has a Regulatory Front

The Fine Print Is Where This Fight Will Be Won

The Architecture Review That Should Happen Before Brussels Decides

The Six-Month Shadow Over Hyperscale Cloud

Europe’s Cloud Verdict Is Really an AI Verdict

The Practical Reading for WindowsForum Readers Is Written in Contracts and Diagrams

References

Brussels Moves the Gatekeeper Fight Down the Stack

AWS and Azure Are Being Judged by Dependence, Not Just Size

The Cloud Was Supposed to Be Portable Until It Became Productized

Microsoft’s Problem Is That Azure Is No Longer Just Azure

Amazon’s Cloud Dominance Has a Different Political Weakness

The DMA May Force Cloud Providers to Compete on Exit as Well as Entry

Europe’s Sovereignty Argument Is Becoming an Economic Argument

AI Turns Cloud Gatekeeping Into a Faster-Moving Problem

Enterprise IT Should Read This as a Procurement Warning

The Hyperscalers Will Sell Compliance as Confidence

The Fight Will Be Over Remedies, Not Rhetoric

The Cloud Crackdown Gives Windows Shops a New Checklist

References

Brussels Moves the DMA Below the App Store Layer

The Threshold Miss Is the Point, Not a Technicality

Azure’s Regulatory Problem Is Its Enterprise Superpower

Cloud Lock-In Is No Longer a Niche Architect’s Complaint

AI Turns Cloud Gatekeeping Into a Live Ammunition Issue

The Data Act Was Never Going to End This Fight

Enterprise IT Will Feel This First in Contracts, Not Consoles

The Sovereignty Debate Finally Meets the Admin Console

Microsoft Has Seen This Movie, But the Ending Is Not Prewritten

The Cloud Market Is Being Regulated After the Lock-In Already Happened

The DMA’s Cloud Test Will Be Measured in Boring Details

The Real Signal for Windows Shops Is Leverage

What the Gatekeeper Notice Should Push Every Azure and AWS Customer to Do Next

References

Brussels Moves the DMA Below the App Layer

The Thresholds Were Never the Whole Law

Cloud Lock-In Is the Quiet Competition Problem

Microsoft’s Cloud Problem Is Bigger Than Azure

AWS Has Scale Without the Desktop Shadow

The DMA Enters the Server Room

Europe’s Cloud Sovereignty Push Is the Wider Frame

The Hyperscalers Will Fight on Definition

Administrators Should Read This as a Procurement Story

Developers Will Feel This Through APIs, Not Press Releases

The Competition Fight Is Also an AI Fight

The Risk Is Regulation That Solves Yesterday’s Cloud

The Six-Month Clock Would Be Only the Beginning

The Fine Print Now Belongs in the Architecture Review

References