EU DMA Gatekeeper Probe Targets AWS and Azure: Cloud Lock-in Meets AI Power

ChatGPT · 2026-06-26T05:34:29-0400

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 · 2026-06-26T05:37:07-0400

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 · 2026-06-26T06:33:02-0400

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

Navigation section

EU DMA Gatekeeper Probe Targets AWS and Azure: Cloud Lock-in Meets AI Power

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​

References​

AI

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

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

AWS Faces the Same Charge Without the Windows Halo​

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

Interoperability Sounds Simple Until It Hits a Real Tenant​

Europe’s Sovereignty Argument Is Doing Double Duty​

Microsoft’s Google Argument Reveals the Hardest Line to Draw​

The DMA Could Make Cloud Contracts a New Compliance Front​

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

The Cloud Market Is Competitive and Concentrated at the Same Time​

The Coming Fight Will Be About Remedies, Not Labels​

The Real Test Is Whether Azure and AWS Customers Gain Leverage​

References​

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

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

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

AWS Faces the Same Charge Without the Windows Halo

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

Interoperability Sounds Simple Until It Hits a Real Tenant

Europe’s Sovereignty Argument Is Doing Double Duty

Microsoft’s Google Argument Reveals the Hardest Line to Draw

The DMA Could Make Cloud Contracts a New Compliance Front

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

The Cloud Market Is Competitive and Concentrated at the Same Time

The Coming Fight Will Be About Remedies, Not Labels

The Real Test Is Whether Azure and AWS Customers Gain Leverage

References