European Union regulators opened formal investigations into Amazon Web Services and Microsoft Azure on November 18, 2025, setting the stage for both hyperscalers to be designated as "gatekeepers" under the Digital Markets Act. The twin probes, confirmed by the European Commission in a press statement, mark the most aggressive regulatory move yet against cloud infrastructure providers and could force sweeping technical and commercial changes that directly impact enterprise Windows shops.

The DMA, which took full effect in early 2024, initially targeted consumer‑facing platforms such as search engines, social networks, and app stores. Cloud computing was always a potential next frontier, and the November 18 announcement removes any doubt that Brussels sees IaaS and PaaS as critical digital bottlenecks. For IT leaders managing Windows Server, Active Directory, SQL Server, and hybrid Azure environments, the investigations signal a new compliance reality: interoperability mandates, data‑portability requirements, and pricing transparency are no longer hypothetical.

What the DMA Gatekeeper Label Means for Cloud

Under the DMA, a company is designated a gatekeeper for a “core platform service” when it has a significant impact on the internal market, serves as an important gateway for business users to reach end users, and enjoys an entrenched and durable position. Once labeled, the firm must comply with a list of obligations and prohibitions within six months. These include allowing business users to interoperate with third‑party services, giving end users the right to uninstall pre‑loaded software easily, and banning self‑preferencing or data cross‑use across services without consent.

For AWS and Azure, the most disruptive obligations would be:

  • Interoperability mandates: Gatekeepers must provide free, effective interoperability with their core platform services. For Windows IT teams, this could mean Azure must expose APIs, interfaces, and migration tools that allow a company to move an Active Directory forest, SQL Server Always On availability group, or Azure Kubernetes Service cluster to another cloud without a forklift rebuild.
  • Data portability: Business users of the gatekeeper’s service must be able to port their data seamlessly. In practice, an enterprise running SAP HANA on Azure VMs would have to be given tools—at no cost—to export the entire VM configuration, disk snapshots, and networking state to a competitor’s equivalent service.
  • No bundling or tying: Gatekeepers cannot require business users to use additional core platform services. For Azure customers, that could affect the common practice of bundling Microsoft 365, Entra ID, and Azure Active Directory into a single enterprise agreement. IT procurement teams may gain new leverage to decouple identity from infrastructure.
  • Transparency in pricing and ranking: Gatekeepers must disclose how they rank and price services. This directly challenges the opacity of reserved instances, committed use discounts, and the infamous egress fees that lock‑in workloads.

Why AWS and Azure Suddenly Face the Heat

The European Commission had been gathering evidence for months. Multiple complainants, including smaller European cloud providers such as OVHcloud, Scaleway, and Deutsche Telekom’s T‑Systems, filed detailed submissions alleging that AWS and Azure leverage their dominance to stifle competition. The complaints focus on three areas: egress fees that make it financially punitive to leave the platform, technical barriers to interoperability, and licensing policies that disadvantage rivals. For Windows shops, the licensing angle is particularly acute: Microsoft’s practice of offering cheaper Windows Server and SQL Server licenses when run on Azure compared to AWS or Google Cloud has drawn sharp criticism. The Commission’s probe will explicitly examine whether such licensing differentials constitute unfair self‑preferencing.

An excerpt of the Commission’s statement, viewed by windowsnews.ai, explains: “The investigations will assess whether Amazon’s and Microsoft’s cloud infrastructure and platform services constitute important gateways for business users to reach end users, and if they enjoy an entrenched and durable position in the internal market.”

Direct Impact on Windows Enterprise Architectures

Windows IT teams building or maintaining hybrid landscapes will feel the DMA’s effects in four key areas:

  1. Identity and access management: For years, many enterprises have anchored identity on Azure Active Directory (now Entra ID), often with pass‑through authentication to on‑premises AD. If Azure is designated a gatekeeper, Microsoft may be required to provide APIs that let a company federate that identity fabric with a third‑party cloud provider without losing capabilities like Conditional Access or Privileged Identity Management. In practice, a Windows admin could someday manage a single identity plane that spans Azure, AWS IAM Identity Center, and GCP Cloud Identity, with true single sign‑on—something currently possible only through costly third‑party bridges.

  2. Virtual desktop infrastructure (VDI): Windows 365 and Azure Virtual Desktop are deeply integrated with Azure. DMA remedies could force Microsoft to offer the same management surface and licensing terms for Windows 365 on other clouds. That would fundamentally alter the desktop‑as‑a‑service market and give IT managers the freedom to run a Cloud PC on the cheapest available infrastructure.

  3. Hybrid management tools: Azure Arc extends Azure Resource Manager to on‑premises and multi‑cloud servers. Under DMA, Microsoft might have to provide an equivalent Arc‑like agent that talks to Google’s or AWS’s management plane, or allow third parties to build their own governance panels on top of Azure’s APIs. Windows Server admins comfortable with the Azure portal could see alternatives flourish.

  4. Licensing and cost management: The Commission’s investigation into licensing specifically calls out Windows Server and SQL Server pricing. If unfair, Microsoft may be forced to equalize BYOL pricing across all clouds. This would immediately lower the cost of running these workloads on AWS or GCP, potentially triggering a re‑evaluation of cloud strategy inside many enterprises.

AWS Faces Its Own Set of Restrictions

Amazon’s AWS is not exempt. Similar licensing concerns exist around Amazon’s own database services (Aurora, Redshift) and its AI/ML stack. The DMA could mandate that AWS publish APIs for its SageMaker platform so that data scientists can train models on AWS but deploy them on another cloud without heavy re‑engineering. The probe also targets AWS’s Marketplace practices, questioning whether the 20% listing fee and preferential treatment for AWS’s own services deter independent software vendors.

For IT teams running Windows workloads on EC2, the most immediate change could be in data transfer. The DMA explicitly bans “unfair or biased” access conditions. Egress fees—sometimes exceeding $0.09 per GB—may have to be eliminated or capped at cost. This would remove one of the largest financial barriers to multi‑cloud architectures.

What Windows IT Leaders Should Do Now

Although the investigations will likely take 12 to 18 months, with potential gatekeeper designations following later, the direction of travel is unmistakable. Prudent IT organizations can start preparing today.

  • Audit cloud dependencies: Map every Azure‑only service your organization relies on, from Azure DevOps to Cosmos DB. Identify which of these would be hardest to replace if interoperability were mandated. This exercise alone often reveals hidden lock‑in.
  • Review licensing agreements: Work with your Microsoft EA negotiator to understand the precise discount you receive for running workloads on Azure versus other clouds. Quantify the potential cost delta if parity is forced.
  • Demand exit proofs of concept: Even if you never plan to leave Azure, demand that your cloud architects demonstrate a fully scripted exit. In light of the DMA, such a demonstration may become a board‑level governance requirement.
  • Engage with industry groups: Organizations like CISPE (Cloud Infrastructure Services Providers in Europe) have been instrumental in pushing the investigation forward. Their technical whitepapers provide concrete examples of interoperability gaps that IT teams can use in internal advocacy.
  • Stay close to the regulatory process: The Commission will publish preliminary findings and invite public comments. Windows IT leaders who contribute real‑world evidence about migration friction, licensing pain, or data‑egress costs can directly shape the eventual remedies.

Microsoft’s and Amazon’s Likely Responses

Microsoft has publicly stated its intent to comply with the DMA, pointing to recent initiatives such as the Azure Migration Program, the Azure Dedicated Hosts that support multi‑tenant isolation, and the 2024 removal of egress fees for customers who want to leave Azure entirely. However, critics note that the fee removal applies only when a customer terminates everything—partial migrations still incur substantial data transfer charges. Amazon has launched a similar “free data transfer out” option but requires contacting support and is limited to 500 TB per month.

Both companies will argue that the cloud market is highly competitive, citing growth from Google Cloud, Oracle Cloud, and regional players. Yet the Commission’s preliminary data reportedly shows that AWS and Azure together command over 55% of the European IaaS/PaaS market, with the nearest rival at less than 10%. That concentration easily meets the DMA’s quantitative threshold of a significant economic position.

The Broader Regulatory Horizon

Europe is not alone. The United Kingdom’s Competition and Markets Authority has an ongoing cloud market investigation, and the United States’ Federal Trade Commission has signaled interest, though no formal probe has been announced. For global Windows enterprises, the EU DMA could become a de facto global standard, much as GDPR did for data privacy. Already, Cisco, SAP, and other software vendors are redesigning their cloud products to be multi‑cloud ready in anticipation of the rules.

The push also aligns with the NIS2 Directive and the proposed EU Cybersecurity Act, which emphasize digital supply‑chain resilience. Regulators increasingly see vendor lock‑in as a systemic risk: if a single cloud provider suffers a catastrophic failure or breach, entire sectors could be crippled. Mandating portability is therefore not just a competition remedy but a security imperative.

What Comes Next

The Commission’s investigations will proceed in three phases. First, a market investigation to confirm gatekeeper status—expected to conclude by mid‑2026. Second, a specification of the precise obligations AWS and Azure must meet. Third, a compliance monitoring phase, with potential fines of up to 10% of global annual turnover for non‑compliance. For Microsoft, that could mean penalties exceeding €16 billion based on FY2025 revenue.

Windows IT teams that begin adapting now will navigate the transition with minimal disruption. Those that wait risk being forced into hurried, expensive re‑architectures when the final rules drop. The smartest move is to treat the DMA not as a threat but as a forcing function to finally build genuine cloud portability—a discipline that pays for itself in negotiating leverage and resilience long before any regulation is enforced.

For daily updates on how the EU cloud probe affects your Windows environment, keep windowsnews.ai bookmarked. We will continue to identify specific technical remedies, licensing changes, and migration tools as the story develops.