The European Commission recently signaled a transformative shift in its regulatory strategy by identifying Amazon Web Services and Microsoft Azure as potential gatekeepers under the Digital Markets Act, moving beyond the usual focus on social media platforms. While previous enforcement actions focused heavily on consumer-facing platforms like search engines and social networks, this new move targets the foundational cloud infrastructure that powers modern business operations and essential public services across the continent. By expanding its reach into these invisible back-end systems, Brussels aims to ensure that the core layers of the digital economy remain fair, competitive, and accessible to emerging players. This expansion marks a pivotal moment where the invisible plumbing of the internet is treated with the same scrutiny as the most visible digital storefronts. Regulators are no longer content with just monitoring surface-level interactions; they are now digging into the deep dependencies that define how data flows through global networks and influences market dynamics.
Establishing New Oversight for the Cloud Economy
Evaluating Dominance: Part 1. The Gateway Factor
Current findings identify Amazon Web Services and Microsoft Azure as the two primary forces in the European cloud sector, acting as essential gateways between business users and their global customer base. If these preliminary designations are finalized, both companies will be required to meet strict obligations under the Digital Markets Act within six months, adding to the regulatory burdens they already face for services like LinkedIn or Amazon’s retail marketplace. This shift reflects a growing concern among policymakers that cloud providers have become too central to the digital marketplace to remain unregulated by traditional antitrust frameworks. As businesses increasingly migrate their operations to off-site servers, the power held by those managing the physical and software-defined layers of the cloud has ballooned significantly. The Commission believes that the current market concentration allows these giants to dictate terms that smaller competitors cannot challenge without intervention, creating a bottleneck that stifles the broader ecosystem.
Evaluating Dominance: Part 2. Market Control
The market dominance of these providers is not merely a matter of infrastructure scale but also involves the proprietary software stacks that run atop the hardware. By integrating deeply with various enterprise applications, these gatekeepers have effectively created environments where the entry of new competitors is restricted by the complexity of the existing ecosystem. Regulators have noted that the sheer volume of data hosted by these two entities gives them an unparalleled advantage in training artificial intelligence models, further entrenching their position at the top of the digital food chain. This concentration of data and processing power has led to calls for structural separations or at least more robust access requirements to ensure that third-party developers can compete on equal footing. As the digital economy evolves, the role of the cloud provider is transforming from a simple service vendor into a powerful intermediary that controls access to the most vital resources of the modern era.
Managing Dependency: Part 3. Technical Barriers
The Commission’s decision is largely driven by the concept of business dependency, where companies become so integrated into a specific provider’s architecture that switching to a rival becomes nearly impossible or cost-prohibitive. High costs for data transfer, commonly referred to as egress fees, and complex technical barriers often trap businesses within a single ecosystem for years, a phenomenon known in the industry as vendor lock-in. This dependency is further intensified by the strategic bundling of software and generative artificial intelligence tools, which can force organizations to stick with one provider just to maintain their daily operations. When an enterprise builds its entire workflow on proprietary cloud-native tools, moving those workloads to another platform requires massive re-engineering and significant financial investment. By regulating these practices, the European Union hopes to lower these walls and allow for a more fluid movement of capital and data across different service providers, fostering a more dynamic market.
Managing Dependency: Part 4. Systemic Integration
Beyond the financial costs of switching, there are significant technical hurdles related to how data is structured and how different cloud services interact with one another. Many organizations find that their internal processes are so tightly coupled with a specific provider’s API that any attempt to diversify their infrastructure leads to significant downtime or performance degradation. This technical gravity makes it difficult for smaller, specialized cloud providers to win contracts, even if they offer superior or more cost-effective solutions for specific tasks. The European Union’s push to regulate these gateways aims to break this gravity by mandating more open standards and requiring gatekeepers to provide clear, easy-to-use migration paths for their clients. By addressing both the economic and technical aspects of lock-in, regulators hope to shift the power back to the business users, allowing them to build truly multi-cloud strategies that enhance their operational resilience and leverage the best innovations.
Navigating Regulatory Mandates and Corporate Objections
Promoting Interoperability: Part 1. Technical Mandates
Under the provisions of the Digital Markets Act, designated gatekeepers must follow specific rules regarding data portability and interoperability to ensure customers can move workloads between providers without facing prohibitive costs. Regulators intend to dismantle the technical silos that currently prevent a business from running a database on one cloud while using analytics tools from another. These measures are designed to promote a multi-cloud environment where businesses can choose services based on performance and price rather than being forced by technical restrictions to stay with one vendor. By mandating that infrastructure remains open and compatible, the European Commission is attempting to create a market where innovation is driven by quality rather than by capturing and holding customers through technical friction. This represents a fundamental shift in how cloud services are sold, moving away from closed ecosystems toward a more modular approach that benefits the end user and promotes a healthy competitive landscape.
Promoting Interoperability: Part 2. Corporate Resistance
Technical giants have expressed significant caution and resistance toward these proposed rules, arguing that additional regulation could slow down innovation and limit the amount of capital investment flowing into Europe. Amazon has stated that the cloud market is already subject to extensive oversight and that the competitive nature of the sector drives constant improvement and lower prices for all users. Meanwhile, Microsoft suggests that targeting Azure without including other significant competitors like Google Cloud could create unfair market distortions that favor certain American firms over others. These concerns highlight the extreme difficulty of drawing clear regulatory lines in a sector where AI-driven purchasing decisions are rapidly changing how companies procure digital services. Industry representatives argue that overly prescriptive rules might prevent providers from offering highly integrated, optimized solutions that customers value for their efficiency. Balancing regulation with the need for technological progress remains a central challenge.
Implementation Strategy: Part 3. Future Outlook
Applying laws originally designed for consumer platforms to complex business-to-business services presented significant technical and contractual hurdles throughout the initial implementation phases of the Digital Markets Act. Unlike social media platforms, cloud computing involves deep technical integration and long-term security requirements that proved difficult to standardize across different providers. The ultimate success of this regulation depended on whether it truly reduced the friction of moving between providers or if it simply added a new layer of compliance costs that were eventually passed down to enterprise users. Moving forward, organizations should have prioritized modular architecture designs that favored open standards to remain resilient against future shifts in the regulatory landscape. Proactive firms began diversifying their cloud portfolios earlier, ensuring that no single vendor held absolute control over their operational data. In the end, the path toward a competitive cloud market required both legislative pressure and architectural changes.
