European Union regulators said on June 25, 2026, that Amazon Web Services and Microsoft Azure should be designated as cloud “gatekeepers” under the Digital Markets Act, opening the door to interoperability, data portability, and anti-self-preferencing obligations across Europe’s dominant cloud infrastructure market. The finding is preliminary, but the direction is unmistakable: Brussels is no longer treating cloud as a neutral utility sitting behind the real platform wars. It is treating cloud as the platform war.
For WindowsForum readers, the Microsoft angle is obvious, but the bigger story is not merely that Azure may face another EU compliance regime. It is that the cloud layer underneath Windows, Microsoft 365, GitHub, Copilot, OpenAI integrations, enterprise identity, databases, and security tooling is now being pulled into the same regulatory logic that reshaped app stores, browsers, search, and messaging. The EU is arguing that infrastructure can be a gatekeeper even when most end users never see the gate.
The Digital Markets Act was originally sold to the public through consumer-facing examples: app store rules, search ranking, browser choice screens, messaging interoperability, and whether a platform owner could privilege its own services over rivals. Cloud computing was always in the background, but it did not have the same political simplicity. Nobody marches in the street because their Kubernetes cluster cannot be live-migrated from one hyperscaler to another.
That is precisely why the Commission’s move matters. The EU is now saying that market power in the digital economy does not need a consumer homepage, a social feed, or a smartphone icon to be systemically important. If enough businesses build on a platform, if switching costs are high enough, and if the provider’s ecosystem becomes the default route to customers, regulators see a gate.
The Commission’s preliminary findings followed a seven-month investigation into whether AWS and Azure act as important gateways between businesses and customers in the EU. The key phrase is not “largest cloud providers,” although that is true. The key phrase is important gateway, because it translates the DMA’s consumer-platform vocabulary into the language of enterprise infrastructure.
That translation is legally and commercially explosive. A cloud provider does not merely host workloads anymore. It sells databases, AI accelerators, model hosting, identity, observability, security services, developer tools, and managed application stacks. Once an enterprise has built deeply into that mesh, the cost of leaving can become less like changing vendors and more like rewriting institutional memory.
AWS and Azure became indispensable not simply by selling compute and storage, but by building large catalogs of services that reward customers for staying inside the same perimeter. The deeper a company goes into proprietary managed services, the less plausible it becomes to switch providers without re-architecting applications. A CIO can say “multi-cloud” on a slide deck while the actual database, identity layer, data pipeline, and AI deployment path quietly bind the organization to a single vendor.
That is where Brussels sees lock-in. Cloud lock-in is not only contractual; it is technical, operational, and cultural. Developers learn one provider’s idioms. Security teams tune policies around one provider’s controls. Finance teams learn one provider’s discount structures. Compliance teams document one provider’s assurances. At enterprise scale, these are not minor inconveniences. They are organizational facts.
Microsoft knows this terrain better than almost anyone. Azure’s strength is not just its data centers or its virtual machines. It is its integration with Windows Server, Active Directory and Entra ID, Microsoft 365, Defender, SQL Server, Visual Studio, GitHub, Power Platform, and now Copilot-branded AI services. That is an extraordinary enterprise stack. It is also exactly the kind of stack regulators scrutinize when they worry that adjacency can become leverage.
That posture is real, but it does not erase the fact that Microsoft’s enterprise footprint gives Azure a uniquely powerful sales channel. A company already committed to Microsoft 365, Entra ID, Intune, Defender, Windows Server, and SQL Server does not encounter Azure as just another cloud provider. It encounters Azure as the path of least resistance.
The Commission appears to understand that point. In cloud procurement, the question is often not which provider has the best isolated service. It is which provider reduces friction across the systems the enterprise already runs. For many Windows-heavy organizations, Azure benefits from decades of accumulated Microsoft standardization. That is not illegal by itself. It is also not invisible.
This is why Microsoft’s response pointing to Google Cloud and Gemini is strategically predictable. Microsoft wants the Commission to see AI cloud competition as dynamic, unsettled, and increasingly shaped by Google’s model and infrastructure ambitions. It is not an absurd argument. Google is a serious cloud and AI player. But the DMA question is not whether another giant exists. It is whether Azure has become a gateway with durable power over business users in the EU.
The distinction matters. Antitrust debates often become theater around who is “dominant,” as if dominance were a trophy awarded to only one company. The cloud market can be competitive in some dimensions and still produce gatekeeper power in others. A developer choosing where to test a new AI workload may have several options. A regulated enterprise with thousands of Windows devices, Microsoft identity dependencies, and a decade of Azure architecture may have far fewer.
That difference will shape the politics of the case. AWS can argue that customers have a wide range of cloud options and that excessive regulation will chill investment in European infrastructure. It can point to the constant arrival of new services, regional providers, open-source stacks, and multi-cloud architectures as evidence that the market is not static. Amazon’s defense is likely to be a version of: customers have choice, and the EU is mistaking success for foreclosure.
Microsoft’s defense is more complicated. Azure is not merely a cloud unit; it is a strategic layer across Microsoft’s entire enterprise business. Every time Microsoft bundles, integrates, discounts, or optimizes across that stack, it creates customer value and regulatory suspicion at the same time. The exact same integration that makes Azure attractive to IT departments can look, from Brussels, like a mechanism for steering demand.
That tension is familiar to anyone who remembers the browser wars or the more recent Teams bundling fight. Microsoft’s commercial superpower has always been integration. The EU’s recurring concern has always been that integration can be used to deny rivals a fair shot.
The cloud version is subtler because no one is forcing a customer to choose a managed database, a model-hosting service, or a proprietary analytics platform. But in enterprise IT, defaults are powerful. Procurement templates, technical documentation, partner incentives, and licensing structures can make one path feel obvious and every alternative feel like an exception requiring justification.
This is why the cloud investigation cannot be separated from AI. Generative AI has intensified the importance of cloud capacity, data gravity, and platform ecosystems. Training and inference are expensive. Enterprises want managed services rather than raw infrastructure. Vendors want to bind AI adoption to their existing cloud and software footprints.
For Microsoft, this means Azure is not just another business line under scrutiny. It is the infrastructure layer beneath Copilot, Azure OpenAI Service, GitHub Copilot integrations, Microsoft 365 AI features, and the company’s broader pitch that AI will be woven through work. If regulators impose interoperability and anti-self-preferencing obligations on Azure, they may indirectly shape how Microsoft can bundle and advantage its AI services in Europe.
For AWS, the AI story is different but no less important. Amazon has been racing to position AWS as a neutral and broad AI platform, with its own chips, managed model services, and partnerships. It wants to be the place where customers can choose among models and build at scale. Brussels is likely to ask whether that marketplace remains genuinely open when the cloud provider controls the surrounding infrastructure and economics.
The EU’s concern is not that AI services exist inside cloud platforms. It is that the next generation of enterprise dependency may form before regulators can see it clearly. By the time every business process is connected to a provider’s AI stack, portability may be a slogan rather than an option.
The technical challenge is real, but the economic challenge may be more important. Cloud providers have long faced criticism over egress fees, transfer costs, and pricing structures that make leaving more expensive than arriving. Even where fees are reduced or waived under certain conditions, the broader problem remains: moving a large, complex workload is expensive, risky, and disruptive.
DMA-style obligations could push AWS and Azure toward clearer migration paths, better documentation, less punitive switching economics, and stronger interoperability commitments. That would be welcomed by many CIOs who already want leverage in vendor negotiations. But the devil will be in the definitions. What counts as meaningful portability for a managed database? What does interoperability mean for proprietary AI governance tooling? How much compatibility can regulators demand without freezing product design?
These are not academic questions. If obligations are too vague, the hyperscalers will satisfy them with compliance theater. If they are too rigid, regulators could accidentally favor the lowest common denominator and make advanced cloud services harder to evolve. The EU will have to regulate lock-in without pretending that all cloud services are interchangeable commodities.
That balance is difficult, and the hyperscalers will exploit every ambiguity. They will argue that cloud innovation depends on specialized services, and that specialized services inevitably create dependencies. There is truth in that. There is also a convenient escape hatch. Not every dependency is abusive, but every gatekeeper would prefer to describe lock-in as innovation.
But interoperability under regulation is different from interoperability as marketing. The regulated version asks whether rivals can connect on fair terms, whether customers can move without unreasonable friction, and whether the platform owner withholds technical advantages from competitors. It is less about whether something is possible and more about whether it is practical, documented, supported, and economically sane.
For Windows administrators, this is where the story becomes operational. A more aggressive EU stance could eventually influence how Microsoft documents Azure migration paths, exposes APIs, treats third-party management tools, and structures integrations with Microsoft 365 and Entra ID. It may also affect how European customers negotiate contracts, especially if compliance obligations create new standardized expectations around portability and access.
The risk for Microsoft is that Azure’s most valuable integrations become the focus of regulatory line-drawing. If Defender, Sentinel, Entra, Intune, GitHub, Microsoft 365, and Copilot work best on Azure, is that legitimate product integration or self-preferencing? The honest answer may vary by feature. Regulators are rarely good at that level of nuance, but vendors are rarely neutral judges of their own incentives.
AWS faces a different version of the same question. Its service catalog is so broad that it can build convenience into its own ecosystem at every layer. A customer may be free to use third-party tools, but AWS-native options often win because they are already integrated, billed, monitored, and supported inside the same console. That is not coercion in the old sense. It is platform gravity.
That does not make the case illegitimate. Cloud concentration has real competitive consequences, and European businesses do face practical switching barriers. But the sovereignty framing changes the politics. It means the investigation is not only about whether AWS and Azure treat rivals fairly. It is also about whether Europe can tolerate depending on non-European infrastructure for AI, public services, defense-adjacent workloads, and regulated industries.
This is where critics will accuse the EU of protectionism dressed as competition policy. They will say Brussels wants to handicap American winners because Europe failed to produce equivalent hyperscalers. There is some force to that critique, especially when regulation becomes a substitute for industrial strategy. But it is too easy to stop there.
The United States also treats digital infrastructure as strategic. China does the same, more explicitly. The idea that cloud should be viewed as a neutral commercial market untouched by state interest is quaint. The only unusual thing about the EU is that it often expresses industrial anxiety through legal process, consultation periods, and compliance regimes.
That style frustrates American companies because it is slow, procedural, and intrusive. It also gives them room to respond. Amazon and Microsoft now get to challenge the preliminary findings before a final decision. The fight is not over; it has simply moved from speculation into the regulatory record.
The question is whether that investment should buy freedom from gatekeeper obligations. The Commission’s likely answer is no. In fact, the more essential the investment becomes, the stronger the case for obligations may appear. A bridge does not become less regulated because it is expensive to build.
Microsoft’s argument about Google Cloud and Gemini is more tactical. It seeks to widen the frame from a two-player cloud hierarchy to a three-way AI-platform race. If AI is the decisive frontier, Microsoft wants regulators to account for Google’s infrastructure, models, data, and distribution. This argument may resonate more in AI than in traditional enterprise cloud, where AWS and Azure remain the obvious first two names.
The broader industry will also argue about scope. If AWS and Azure are gatekeepers, why not Google Cloud? If cloud infrastructure is covered, what about enterprise SaaS platforms, developer platforms, cybersecurity platforms, or AI model marketplaces? The DMA was designed around “core platform services,” but the digital economy keeps turning more layers into platforms.
That is the deeper threat to Big Tech. Once Brussels proves it can extend gatekeeper reasoning into infrastructure, the DMA becomes less a fixed list of regulated services and more a doctrine of digital dependency. The next fight will be over where that doctrine stops.
Still, enterprise buyers should pay attention now. Regulatory pressure can create negotiation leverage before formal remedies arrive. If a customer is renewing a large Azure or AWS agreement in Europe, questions about portability, egress, migration support, third-party tool access, audit rights, and AI data governance are no longer just technical diligence. They are aligned with the direction of EU policy.
This matters especially for Windows-heavy organizations considering deeper Azure commitments. The easiest architecture today can become tomorrow’s bargaining weakness. Microsoft’s integrated stack is genuinely powerful, but the more an organization relies on Azure-specific services, Microsoft-native security tooling, and Copilot-era workflows, the harder it may be to maintain credible exit options.
The same is true for AWS customers who have embraced managed services across the stack. A workload built on generic compute and open databases is one thing. A workload woven through proprietary eventing, analytics, machine learning, identity, monitoring, and serverless primitives is another. Portability is not a checkbox added at renewal time. It is an architectural discipline.
The irony is that multi-cloud strategies can also become expensive theater. Running everything across multiple providers for theoretical leverage may increase complexity without creating real freedom. The smarter move is selective portability: know which workloads must be movable, which dependencies are acceptable, and which vendor-specific services are worth the lock-in because they create measurable value.
The company is not the same as it was then. Satya Nadella’s Microsoft is more open, more cloud-native, and more comfortable competing on platforms it does not control. But Microsoft’s strategic instincts still favor integration, and integration is where antitrust attention gathers. The better Microsoft gets at making Azure the natural home for enterprise workloads, the more Brussels will ask whether “natural” is being engineered.
There is also a Windows-specific lesson. Microsoft’s desktop dominance once made the operating system the center of the regulatory universe. Now Windows is one piece of a broader enterprise fabric, but it still feeds Azure’s advantage through identity, endpoint management, server workloads, developer tools, and administrative habit. The center of gravity has shifted from the PC to the cloud control plane.
That shift changes the stakes for WindowsForum’s audience. The most important Microsoft platform decision in many organizations is no longer the version of Windows on the endpoint. It is the architecture of identity, management, security, data, and AI services around those endpoints. Azure is where much of that architecture now lives.
If the EU succeeds in imposing meaningful gatekeeper obligations, Microsoft may have to make that architecture more permeable. That could benefit customers and competitors. It could also create new compliance complexity, uneven regional features, and another layer of legal review around product changes. Regulation rarely produces only clean wins.
AI makes this problem worse. In cloud, the frontier is moving from virtual machines to managed services, then to platform services, then to model services, agents, and integrated workflow automation. If the Commission writes obligations around yesterday’s cloud primitives, it may miss tomorrow’s lock-in. If it writes broad obligations around “fairness” and “interoperability,” it may create uncertainty that only the largest legal departments can navigate.
That paradox is uncomfortable. Regulation intended to constrain hyperscalers can sometimes entrench them, because only hyperscalers have the staff to absorb compliance. Smaller providers may welcome constraints on AWS and Azure, but they may also struggle if the regulatory environment becomes more complex for everyone.
The Commission will need to avoid confusing openness with paperwork. A cloud market is not more competitive because customers receive longer disclosures or because providers publish migration guides nobody can use. The useful test is practical: can a serious customer move, interoperate, or mix providers without being punished by hidden costs, degraded functionality, or contractual traps?
If the answer improves, the DMA intervention may be justified. If the result is merely another compliance dashboard, the hyperscalers will grumble publicly and adapt privately, while customers see little change. The EU’s tech regulation record contains examples of both outcomes.
That timeline gives both companies room to shape the remedy conversation. They may offer commitments, emphasize existing portability tools, revise commercial terms, or argue that other EU laws already address the same concerns. Microsoft will almost certainly keep pointing to Google’s AI momentum. Amazon will keep warning that duplicative regulation risks slowing Europe’s access to advanced infrastructure.
For customers, the temptation is to wait for the final decision. That would be a mistake. The legal outcome matters, but the strategic signal has already arrived. European regulators now view hyperscale cloud as a gatekeeping layer in its own right, and that view will influence future procurement norms, complaints, investigations, and political expectations.
It will also influence product strategy. Microsoft and Amazon may begin adjusting European-facing cloud practices before they are forced to do so. Large vendors often prefer controlled preemption to dramatic enforcement. Watch for changes in migration programs, interoperability language, partner access, data-transfer commitments, and AI governance positioning.
The Commission, meanwhile, must show that this is not merely symbolic escalation. If it designates AWS and Azure but cannot define obligations that matter, the DMA’s cloud expansion will look like a jurisdictional flex. If it lands concrete remedies, it will mark one of the most consequential expansions of European digital regulation since the DMA began.
For WindowsForum readers, the Microsoft angle is obvious, but the bigger story is not merely that Azure may face another EU compliance regime. It is that the cloud layer underneath Windows, Microsoft 365, GitHub, Copilot, OpenAI integrations, enterprise identity, databases, and security tooling is now being pulled into the same regulatory logic that reshaped app stores, browsers, search, and messaging. The EU is arguing that infrastructure can be a gatekeeper even when most end users never see the gate.
Brussels Moves the DMA Below the Waterline
The Digital Markets Act was originally sold to the public through consumer-facing examples: app store rules, search ranking, browser choice screens, messaging interoperability, and whether a platform owner could privilege its own services over rivals. Cloud computing was always in the background, but it did not have the same political simplicity. Nobody marches in the street because their Kubernetes cluster cannot be live-migrated from one hyperscaler to another.That is precisely why the Commission’s move matters. The EU is now saying that market power in the digital economy does not need a consumer homepage, a social feed, or a smartphone icon to be systemically important. If enough businesses build on a platform, if switching costs are high enough, and if the provider’s ecosystem becomes the default route to customers, regulators see a gate.
The Commission’s preliminary findings followed a seven-month investigation into whether AWS and Azure act as important gateways between businesses and customers in the EU. The key phrase is not “largest cloud providers,” although that is true. The key phrase is important gateway, because it translates the DMA’s consumer-platform vocabulary into the language of enterprise infrastructure.
That translation is legally and commercially explosive. A cloud provider does not merely host workloads anymore. It sells databases, AI accelerators, model hosting, identity, observability, security services, developer tools, and managed application stacks. Once an enterprise has built deeply into that mesh, the cost of leaving can become less like changing vendors and more like rewriting institutional memory.
The Cloud Was Never Just Someone Else’s Computer
The old joke that cloud is “just someone else’s computer” has always been comforting because it suggests interchangeability. If one rented server looks like another rented server, competition should take care of itself. But modern hyperscale cloud is not a rack of anonymous virtual machines. It is an operating environment with its own APIs, billing incentives, compliance defaults, privileged integrations, and gravitational pull.AWS and Azure became indispensable not simply by selling compute and storage, but by building large catalogs of services that reward customers for staying inside the same perimeter. The deeper a company goes into proprietary managed services, the less plausible it becomes to switch providers without re-architecting applications. A CIO can say “multi-cloud” on a slide deck while the actual database, identity layer, data pipeline, and AI deployment path quietly bind the organization to a single vendor.
That is where Brussels sees lock-in. Cloud lock-in is not only contractual; it is technical, operational, and cultural. Developers learn one provider’s idioms. Security teams tune policies around one provider’s controls. Finance teams learn one provider’s discount structures. Compliance teams document one provider’s assurances. At enterprise scale, these are not minor inconveniences. They are organizational facts.
Microsoft knows this terrain better than almost anyone. Azure’s strength is not just its data centers or its virtual machines. It is its integration with Windows Server, Active Directory and Entra ID, Microsoft 365, Defender, SQL Server, Visual Studio, GitHub, Power Platform, and now Copilot-branded AI services. That is an extraordinary enterprise stack. It is also exactly the kind of stack regulators scrutinize when they worry that adjacency can become leverage.
Azure’s Windows Advantage Is Now a Regulatory Liability
For two decades, Microsoft has worked to turn its enterprise dominance from a vulnerability into an advantage. The company did not merely survive the antitrust battles of the Windows era; it adapted. Azure was built for a world where Microsoft could say, plausibly, that it supported Linux, open source, hybrid cloud, containers, and competing platforms. The new Microsoft was interoperable, pragmatic, and developer-friendly.That posture is real, but it does not erase the fact that Microsoft’s enterprise footprint gives Azure a uniquely powerful sales channel. A company already committed to Microsoft 365, Entra ID, Intune, Defender, Windows Server, and SQL Server does not encounter Azure as just another cloud provider. It encounters Azure as the path of least resistance.
The Commission appears to understand that point. In cloud procurement, the question is often not which provider has the best isolated service. It is which provider reduces friction across the systems the enterprise already runs. For many Windows-heavy organizations, Azure benefits from decades of accumulated Microsoft standardization. That is not illegal by itself. It is also not invisible.
This is why Microsoft’s response pointing to Google Cloud and Gemini is strategically predictable. Microsoft wants the Commission to see AI cloud competition as dynamic, unsettled, and increasingly shaped by Google’s model and infrastructure ambitions. It is not an absurd argument. Google is a serious cloud and AI player. But the DMA question is not whether another giant exists. It is whether Azure has become a gateway with durable power over business users in the EU.
The distinction matters. Antitrust debates often become theater around who is “dominant,” as if dominance were a trophy awarded to only one company. The cloud market can be competitive in some dimensions and still produce gatekeeper power in others. A developer choosing where to test a new AI workload may have several options. A regulated enterprise with thousands of Windows devices, Microsoft identity dependencies, and a decade of Azure architecture may have far fewer.
AWS Is the Pure Cloud Target, Azure Is the Ecosystem Target
Amazon and Microsoft enter this fight from different directions. AWS is the archetypal hyperscaler: the cloud pioneer whose breadth, scale, and operational maturity made it the default infrastructure choice for much of the startup and enterprise world. Azure is the enterprise ecosystem cloud, fused to Microsoft’s long-standing software estate and now tightly linked to the company’s AI ambitions.That difference will shape the politics of the case. AWS can argue that customers have a wide range of cloud options and that excessive regulation will chill investment in European infrastructure. It can point to the constant arrival of new services, regional providers, open-source stacks, and multi-cloud architectures as evidence that the market is not static. Amazon’s defense is likely to be a version of: customers have choice, and the EU is mistaking success for foreclosure.
Microsoft’s defense is more complicated. Azure is not merely a cloud unit; it is a strategic layer across Microsoft’s entire enterprise business. Every time Microsoft bundles, integrates, discounts, or optimizes across that stack, it creates customer value and regulatory suspicion at the same time. The exact same integration that makes Azure attractive to IT departments can look, from Brussels, like a mechanism for steering demand.
That tension is familiar to anyone who remembers the browser wars or the more recent Teams bundling fight. Microsoft’s commercial superpower has always been integration. The EU’s recurring concern has always been that integration can be used to deny rivals a fair shot.
The cloud version is subtler because no one is forcing a customer to choose a managed database, a model-hosting service, or a proprietary analytics platform. But in enterprise IT, defaults are powerful. Procurement templates, technical documentation, partner incentives, and licensing structures can make one path feel obvious and every alternative feel like an exception requiring justification.
The DMA Enters the AI Supply Chain
The Commission’s emphasis on AI tools and partnerships is the sharpest part of the preliminary finding. Cloud infrastructure has become the staging ground for AI deployment, not merely a place to store data or run applications. The provider that hosts the data, supplies the GPUs, offers the model catalog, wraps it in governance tools, and connects it to productivity software may define the next enterprise computing platform.This is why the cloud investigation cannot be separated from AI. Generative AI has intensified the importance of cloud capacity, data gravity, and platform ecosystems. Training and inference are expensive. Enterprises want managed services rather than raw infrastructure. Vendors want to bind AI adoption to their existing cloud and software footprints.
For Microsoft, this means Azure is not just another business line under scrutiny. It is the infrastructure layer beneath Copilot, Azure OpenAI Service, GitHub Copilot integrations, Microsoft 365 AI features, and the company’s broader pitch that AI will be woven through work. If regulators impose interoperability and anti-self-preferencing obligations on Azure, they may indirectly shape how Microsoft can bundle and advantage its AI services in Europe.
For AWS, the AI story is different but no less important. Amazon has been racing to position AWS as a neutral and broad AI platform, with its own chips, managed model services, and partnerships. It wants to be the place where customers can choose among models and build at scale. Brussels is likely to ask whether that marketplace remains genuinely open when the cloud provider controls the surrounding infrastructure and economics.
The EU’s concern is not that AI services exist inside cloud platforms. It is that the next generation of enterprise dependency may form before regulators can see it clearly. By the time every business process is connected to a provider’s AI stack, portability may be a slogan rather than an option.
Data Portability Sounds Simple Until the Bill Arrives
Among the likely DMA consequences, data portability is the one that sounds most straightforward and becomes most complicated in practice. In consumer tech, portability often means exporting photos, contacts, playlists, or messages. In cloud, portability means moving enormous volumes of data, metadata, configurations, permissions, logs, application dependencies, and sometimes entire operational models.The technical challenge is real, but the economic challenge may be more important. Cloud providers have long faced criticism over egress fees, transfer costs, and pricing structures that make leaving more expensive than arriving. Even where fees are reduced or waived under certain conditions, the broader problem remains: moving a large, complex workload is expensive, risky, and disruptive.
DMA-style obligations could push AWS and Azure toward clearer migration paths, better documentation, less punitive switching economics, and stronger interoperability commitments. That would be welcomed by many CIOs who already want leverage in vendor negotiations. But the devil will be in the definitions. What counts as meaningful portability for a managed database? What does interoperability mean for proprietary AI governance tooling? How much compatibility can regulators demand without freezing product design?
These are not academic questions. If obligations are too vague, the hyperscalers will satisfy them with compliance theater. If they are too rigid, regulators could accidentally favor the lowest common denominator and make advanced cloud services harder to evolve. The EU will have to regulate lock-in without pretending that all cloud services are interchangeable commodities.
That balance is difficult, and the hyperscalers will exploit every ambiguity. They will argue that cloud innovation depends on specialized services, and that specialized services inevitably create dependencies. There is truth in that. There is also a convenient escape hatch. Not every dependency is abusive, but every gatekeeper would prefer to describe lock-in as innovation.
Interoperability Is the Word Everyone Supports Until It Has Teeth
Interoperability is one of those terms that almost no vendor opposes in public. Microsoft, in particular, has spent years presenting itself as a champion of cross-platform reality. Azure runs Linux. Microsoft contributes to open source. SQL Server runs on Linux. Visual Studio Code became a developer staple far beyond Windows. The company has earned some credibility here.But interoperability under regulation is different from interoperability as marketing. The regulated version asks whether rivals can connect on fair terms, whether customers can move without unreasonable friction, and whether the platform owner withholds technical advantages from competitors. It is less about whether something is possible and more about whether it is practical, documented, supported, and economically sane.
For Windows administrators, this is where the story becomes operational. A more aggressive EU stance could eventually influence how Microsoft documents Azure migration paths, exposes APIs, treats third-party management tools, and structures integrations with Microsoft 365 and Entra ID. It may also affect how European customers negotiate contracts, especially if compliance obligations create new standardized expectations around portability and access.
The risk for Microsoft is that Azure’s most valuable integrations become the focus of regulatory line-drawing. If Defender, Sentinel, Entra, Intune, GitHub, Microsoft 365, and Copilot work best on Azure, is that legitimate product integration or self-preferencing? The honest answer may vary by feature. Regulators are rarely good at that level of nuance, but vendors are rarely neutral judges of their own incentives.
AWS faces a different version of the same question. Its service catalog is so broad that it can build convenience into its own ecosystem at every layer. A customer may be free to use third-party tools, but AWS-native options often win because they are already integrated, billed, monitored, and supported inside the same console. That is not coercion in the old sense. It is platform gravity.
Europe’s Tech Sovereignty Argument Is Doing More Work Than It Admits
The Commission’s language about Europe’s digital future and technological sovereignty is not incidental. Cloud has become critical infrastructure, and Europe is uncomfortable with the fact that so much of it is controlled by American companies. The DMA gives Brussels a competition-law mechanism for a geopolitical anxiety.That does not make the case illegitimate. Cloud concentration has real competitive consequences, and European businesses do face practical switching barriers. But the sovereignty framing changes the politics. It means the investigation is not only about whether AWS and Azure treat rivals fairly. It is also about whether Europe can tolerate depending on non-European infrastructure for AI, public services, defense-adjacent workloads, and regulated industries.
This is where critics will accuse the EU of protectionism dressed as competition policy. They will say Brussels wants to handicap American winners because Europe failed to produce equivalent hyperscalers. There is some force to that critique, especially when regulation becomes a substitute for industrial strategy. But it is too easy to stop there.
The United States also treats digital infrastructure as strategic. China does the same, more explicitly. The idea that cloud should be viewed as a neutral commercial market untouched by state interest is quaint. The only unusual thing about the EU is that it often expresses industrial anxiety through legal process, consultation periods, and compliance regimes.
That style frustrates American companies because it is slow, procedural, and intrusive. It also gives them room to respond. Amazon and Microsoft now get to challenge the preliminary findings before a final decision. The fight is not over; it has simply moved from speculation into the regulatory record.
The Hyperscalers Will Fight on Investment, Innovation, and Scope
Amazon’s first line of defense is already visible: the EU has cloud regulation through other laws, and another DMA layer could deter investment and innovation. This is the standard hyperscaler argument, but it is not empty. Europe wants more data centers, more AI capacity, better sovereign cloud options, lower latency, and more secure infrastructure. Those goals require capital, and AWS and Microsoft are among the few companies able to deploy it at the necessary scale.The question is whether that investment should buy freedom from gatekeeper obligations. The Commission’s likely answer is no. In fact, the more essential the investment becomes, the stronger the case for obligations may appear. A bridge does not become less regulated because it is expensive to build.
Microsoft’s argument about Google Cloud and Gemini is more tactical. It seeks to widen the frame from a two-player cloud hierarchy to a three-way AI-platform race. If AI is the decisive frontier, Microsoft wants regulators to account for Google’s infrastructure, models, data, and distribution. This argument may resonate more in AI than in traditional enterprise cloud, where AWS and Azure remain the obvious first two names.
The broader industry will also argue about scope. If AWS and Azure are gatekeepers, why not Google Cloud? If cloud infrastructure is covered, what about enterprise SaaS platforms, developer platforms, cybersecurity platforms, or AI model marketplaces? The DMA was designed around “core platform services,” but the digital economy keeps turning more layers into platforms.
That is the deeper threat to Big Tech. Once Brussels proves it can extend gatekeeper reasoning into infrastructure, the DMA becomes less a fixed list of regulated services and more a doctrine of digital dependency. The next fight will be over where that doctrine stops.
Enterprise IT Should Read This as Leverage, Not Liberation
For CIOs, sysadmins, and architects, the immediate practical effect is limited. AWS and Azure have not yet been finally designated for cloud services under the DMA. Even if they are, compliance would unfold over time, and the most meaningful changes would likely arrive through contracts, documentation, migration tooling, interoperability commitments, and complaint-driven enforcement.Still, enterprise buyers should pay attention now. Regulatory pressure can create negotiation leverage before formal remedies arrive. If a customer is renewing a large Azure or AWS agreement in Europe, questions about portability, egress, migration support, third-party tool access, audit rights, and AI data governance are no longer just technical diligence. They are aligned with the direction of EU policy.
This matters especially for Windows-heavy organizations considering deeper Azure commitments. The easiest architecture today can become tomorrow’s bargaining weakness. Microsoft’s integrated stack is genuinely powerful, but the more an organization relies on Azure-specific services, Microsoft-native security tooling, and Copilot-era workflows, the harder it may be to maintain credible exit options.
The same is true for AWS customers who have embraced managed services across the stack. A workload built on generic compute and open databases is one thing. A workload woven through proprietary eventing, analytics, machine learning, identity, monitoring, and serverless primitives is another. Portability is not a checkbox added at renewal time. It is an architectural discipline.
The irony is that multi-cloud strategies can also become expensive theater. Running everything across multiple providers for theoretical leverage may increase complexity without creating real freedom. The smarter move is selective portability: know which workloads must be movable, which dependencies are acceptable, and which vendor-specific services are worth the lock-in because they create measurable value.
Microsoft’s Old Antitrust Ghosts Have Learned Cloud Architecture
There is a historical echo here that Microsoft would rather avoid. In the late 1990s and early 2000s, the company’s antitrust problem was the Windows desktop monopoly and the use of that position to influence browsers and adjacent software markets. Today’s cloud fight is more abstract, but the pattern is recognizable: a dominant platform, adjacent services, bundling incentives, and regulators worried that rivals cannot get a fair route to customers.The company is not the same as it was then. Satya Nadella’s Microsoft is more open, more cloud-native, and more comfortable competing on platforms it does not control. But Microsoft’s strategic instincts still favor integration, and integration is where antitrust attention gathers. The better Microsoft gets at making Azure the natural home for enterprise workloads, the more Brussels will ask whether “natural” is being engineered.
There is also a Windows-specific lesson. Microsoft’s desktop dominance once made the operating system the center of the regulatory universe. Now Windows is one piece of a broader enterprise fabric, but it still feeds Azure’s advantage through identity, endpoint management, server workloads, developer tools, and administrative habit. The center of gravity has shifted from the PC to the cloud control plane.
That shift changes the stakes for WindowsForum’s audience. The most important Microsoft platform decision in many organizations is no longer the version of Windows on the endpoint. It is the architecture of identity, management, security, data, and AI services around those endpoints. Azure is where much of that architecture now lives.
If the EU succeeds in imposing meaningful gatekeeper obligations, Microsoft may have to make that architecture more permeable. That could benefit customers and competitors. It could also create new compliance complexity, uneven regional features, and another layer of legal review around product changes. Regulation rarely produces only clean wins.
The Real Test Is Whether Brussels Can Regulate Without Freezing the Stack
The EU’s critics often portray Brussels as a bureaucracy that regulates what it cannot build. That line is too glib, but the underlying challenge is real. Cloud infrastructure evolves faster than traditional competition remedies. By the time regulators define a problematic practice, the market may have shifted to a new abstraction layer.AI makes this problem worse. In cloud, the frontier is moving from virtual machines to managed services, then to platform services, then to model services, agents, and integrated workflow automation. If the Commission writes obligations around yesterday’s cloud primitives, it may miss tomorrow’s lock-in. If it writes broad obligations around “fairness” and “interoperability,” it may create uncertainty that only the largest legal departments can navigate.
That paradox is uncomfortable. Regulation intended to constrain hyperscalers can sometimes entrench them, because only hyperscalers have the staff to absorb compliance. Smaller providers may welcome constraints on AWS and Azure, but they may also struggle if the regulatory environment becomes more complex for everyone.
The Commission will need to avoid confusing openness with paperwork. A cloud market is not more competitive because customers receive longer disclosures or because providers publish migration guides nobody can use. The useful test is practical: can a serious customer move, interoperate, or mix providers without being punished by hidden costs, degraded functionality, or contractual traps?
If the answer improves, the DMA intervention may be justified. If the result is merely another compliance dashboard, the hyperscalers will grumble publicly and adapt privately, while customers see little change. The EU’s tech regulation record contains examples of both outcomes.
The Calendar Now Belongs to the Commission
The next phase is procedural but important. Amazon and Microsoft can inspect the Commission’s file, respond in writing, and try to rebut the preliminary findings. A final decision is expected in the coming months, and a confirmed designation would trigger a compliance period before obligations bite.That timeline gives both companies room to shape the remedy conversation. They may offer commitments, emphasize existing portability tools, revise commercial terms, or argue that other EU laws already address the same concerns. Microsoft will almost certainly keep pointing to Google’s AI momentum. Amazon will keep warning that duplicative regulation risks slowing Europe’s access to advanced infrastructure.
For customers, the temptation is to wait for the final decision. That would be a mistake. The legal outcome matters, but the strategic signal has already arrived. European regulators now view hyperscale cloud as a gatekeeping layer in its own right, and that view will influence future procurement norms, complaints, investigations, and political expectations.
It will also influence product strategy. Microsoft and Amazon may begin adjusting European-facing cloud practices before they are forced to do so. Large vendors often prefer controlled preemption to dramatic enforcement. Watch for changes in migration programs, interoperability language, partner access, data-transfer commitments, and AI governance positioning.
The Commission, meanwhile, must show that this is not merely symbolic escalation. If it designates AWS and Azure but cannot define obligations that matter, the DMA’s cloud expansion will look like a jurisdictional flex. If it lands concrete remedies, it will mark one of the most consequential expansions of European digital regulation since the DMA began.
The Fine Print That Will Matter More Than the Press Release
The headline is that AWS and Azure may become DMA gatekeepers. The real story will be buried in implementation details, because cloud power is exercised through defaults, APIs, contracts, prices, and integration paths rather than a single obvious chokepoint.- AWS and Azure have only received preliminary findings, so the companies still have an opportunity to challenge the Commission before any final designation is made.
- A confirmed DMA designation would likely force closer scrutiny of interoperability, data portability, switching costs, and self-preferencing across cloud services in Europe.
- Microsoft faces a distinct risk because Azure’s value is tightly connected to Windows, Microsoft 365, Entra ID, Defender, GitHub, and Copilot-era AI services.
- Amazon’s strongest defense is that cloud remains broad and competitive, but the Commission is focused on entrenched customer bases, scale, and lock-in rather than consumer-style market share alone.
- Enterprise customers should treat the investigation as a reason to revisit portability assumptions, especially where AI services and managed cloud platforms are becoming deeply embedded.
- The most important outcome will not be whether Brussels wins a headline fight, but whether customers gain practical freedom to move workloads, mix providers, and resist ecosystem pressure.
References
- Primary source: The Express Tribune
Published: 2026-06-25T18:30:11.632208
EU targets Amazon, Microsoft cloud units for Big Tech “gatekeeper” rules
EU DMA designation may impose interoperability, data portability and self-preferencing limits on AWS and Azure
tribune.com.pk
- Related coverage: agenceurope.eu
European Commission designates Amazon and Microsoft as gatekeepers under DMA for their dominant cloud computing services | AGENCE EUROPE
The European Commission designates Amazon and Microsoft as gatekeepers under the Digital Markets Act.agenceurope.eu
- Related coverage: competition-policy.ec.europa.eu
Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMA
Commission reaches preliminary position that Amazon's and Microsoft's market leading cloud services should be designated under the DMAcompetition-policy.ec.europa.eu - Related coverage: eunews.it
- Related coverage: datacenterdynamics.com
AWS and Microsoft designated 'gatekeepers' under Europe's Digital Markets Act - DCD
European Commission's preliminary decision comes despite duo "not meeting the DMA's quantitative thresholds"www.datacenterdynamics.com - Related coverage: finanza.repubblica.it
- Related coverage: germany.representation.ec.europa.eu
DMA: Cloud-Dienste von Amazon und Microsoft könnten als „Gatekeeper“ eingestuft werden
Die EU-Kommission hat Amazon und Microsoft ihre vorläufige Auffassung mitgeteilt, dass ihre Cloud-Computing-Dienste – Amazon Web Services (AWS) bzw. Microsoft Azure (Azure) – im Rahmen des Digital Markets Act (DMA) als „Gatekeeper“ eingestuft werden sollten.germany.representation.ec.europa.eu - Related coverage: euperspectives.eu
Whoever controls the cloud controls the future. Brussels wants to rein in Amazon and Microsoft - EU Perspectives
The European Commission is taking aim at Amazon and Microsoft's cloud dominance in a move that could reshape AI markets.euperspectives.eu - Related coverage: digital-markets-act.ec.europa.eu
Commission launches market investigations on cloud computing services under the Digital Markets Act
The Commission opened three market investigations on cloud computing services under the Digital Markets Act (DMA). Two market investigations will assess whether Amazon and Microsoft should be designated as gatekeepers for their cloud computing services, Amazon Web Services and Microsoft Azure...digital-markets-act.ec.europa.eu - Related coverage: europapress.es
Bruselas quiere someter la computación en la nube de Amazon y Microsoft a la ley digital antimonopolio
La Comisión Europea ha concluido de manera preliminar que los servicios en computación de las...www.europapress.es
- Related coverage: digital-strategy.ec.europa.eu
Commission launches market investigations on cloud computing services under the Digital Markets Act
The European Commission opened three market investigations on cloud computing services under the Digital Markets Act (DMA).digital-strategy.ec.europa.eu
- Related coverage: elpais.com
Bruselas plantea que los servicios en la nube de Amazon y Microsoft se sometan a reglas comunitarias más estrictas | Economía | EL PAÍS
En una conclusión preliminar que se puede apelar, la Comisión considera que AmazonWeb Services y Microsoft Azure deben designarse como guardianes de acceso conforme a la Ley de Mercados Digitaleselpais.com