EU Probes AWS and Azure Under DMA: Cloud Portability Rules

Brussels has opened formal market investigations that put Amazon Web Services and Microsoft Azure squarely in the regulatory crosshairs, probing whether the two hyperscalers should face tougher, gatekeeper-style rules under the European Union’s Digital Markets Act — a move that could reshape cloud contracts, portability, and the economics of doing business across Europe.

Background​

Cloud infrastructure has moved from a commodified utility to strategic digital plumbing for governments, banks, critical national systems, and the AI stacks that power modern software. The European Commission’s decision to open two company-specific market investigations — one into Amazon Web Services (AWS) and one into Microsoft Azure — plus a third horizontal study into whether the Digital Markets Act (DMA) can be sensibly applied to cloud infrastructure, recognizes that reality and the risks that accompany concentration. The DMA is an ex‑ante regulatory framework created to prevent entrenched digital platforms from abusing their position. It prescribes a list of obligations for designated gatekeepers — from prohibitions on self‑preferencing to duties to facilitate interoperability — and backs them with significant enforcement powers, including fines up to 10% (or higher for repeat breaches) of global annual turnover. Applying those obligations to cloud infrastructure would be novel and technically complex.

---

What Brussels is investigating​

The three threads of inquiry​

• Two focused market investigations: one assessing whether AWS behaves as a gatekeeper for certain cloud services; the other testing Azure for the same criteria. These probes examine market structure, contractual and technical practices, and evidence of exclusionary behaviour.
• One horizontal or sectoral study: a meta-review to determine whether the DMA — drafted around consumer-facing platform services — is fit for purpose for enterprise-grade cloud markets, or whether new, cloud-specific remedies are needed.

Core lines of inquiry​

Investigators will gather evidence across a set of concrete issues that recur in regulator and industry briefings:

• Market concentration and entry barriers: Are AWS and Azure so dominant in IaaS/PaaS that rivals cannot effectively compete? Independent trackers and national authorities have repeatedly signalled high concentration in many markets.
• Lock‑in mechanics: Do egress fees, proprietary APIs, licensing differentials or custom hardware create material switching costs that deter migration?
• Self‑preferencing and bundling: Do first‑party managed services, marketplaces or bundled licensing deals favour the host provider at the expense of ISVs or competing infrastructure providers?
• Technical interoperability and portability: Are migration tools, standard interfaces and open control‑plane APIs practically usable, performant and nondiscriminatory?

The Commission has set an ambitious, evidence‑heavy timetable — roughly 12 months for the inquiries — though that may shift as technical complexity unfolds.

---

Why the EU moved now: concentration, outages, and AI​

Three converging dynamics pushed the cloud market onto Brussels’ agenda.

• Market concentration: The top global hyperscalers (AWS, Microsoft, Google) jointly control the lion’s share of cloud infrastructure spending in Europe. Regulators see that concentration as a systemic vulnerability for competition and resilience.
• Operational fragility: High‑impact outages and cascading service interruptions at major cloud providers have shown how dependent many sectors are on a handful of vendors — intensifying political interest in resilience and digital sovereignty.
• AI compute intensification: Generative AI workloads create new stickiness: custom hardware, specialised managed services and tightly integrated stacks that are expensive to replicate or move — amplifying concerns about vendor lock‑in.

Independent reporting and EU and national actions (including prior UK CMA reviews) have built the evidence base that underpins the Commission’s move. Early mainstream coverage confirms the Commission’s intention to probe whether the DMA can apply to cloud infrastructure.

---

How the Digital Markets Act could map to cloud services​

Gatekeeper mechanics and cloud-specific frictions​

The DMA defines a presumptive gatekeeper by meeting numerical thresholds (size, user counts, market capitalisation) but also allows the Commission to launch qualitative market investigations where those metrics are not straightforward — a key legal lever for cloud, where monthly end‑user counts are not the natural metric. If the Commission finds that a cloud service performs a gatekeeping role, it can apply DMA obligations or demand tailored remedies. Potential cloud‑oriented applications of DMA obligations might include:

• Interoperability mandates: Requirements to publish or open standardized control‑plane APIs for essential cloud primitives (identity, storage formats, routing) to ease workload portability.
• Non‑discrimination rules: Bans on preferential treatment of first‑party managed services in marketplaces, pricing or console experiences.
• Data portability and exit guarantees: Transparency on egress pricing, audited migration tools, performance and timeline SLAs for cutover events.
• Transparency and auditability: Ongoing reporting obligations and access to compliance evidence, backed by financial penalties for breaches.

Designing and enforcing these obligations in cloud contexts — where performance, latency and security are technical constraints — will be legally and technically challenging. Regulators and industry will need to agree on what portability and interoperability practically mean for production workloads.

Technical trade-offs to consider​

• Mandating open interfaces can reduce lock‑in but risk introducing additional latency or complexity if not designed with care.
• Requirements that standardise or constrain proprietary value‑adds may dampen incentives for hyperscalers to invest in bespoke infrastructure or specialised AI accelerators.
• Remedies focused on pricing (e.g., egress caps) could improve switching economics but might be passed on to customers through other pricing levers.

These trade‑offs are why the Commission’s horizontal probe is especially important: it will define whether DMA-style ex‑ante obligations can be adapted without breaking the technical and economic model that currently underpins hyperscale cloud security and scale economies.

---

What outcomes are plausible — a ranked view​

• Targeted, technical obligations (most likely): The Commission imposes narrowly targeted requirements around data portability, egress transparency and non‑discrimination for specific cloud primitives. These would be engineered to avoid forcing wholesale architectural changes.
• Partial DMA designation for discrete cloud services: Rather than designating entire cloud stacks as gatekeepers, Brussels could identify particular offerings (marketplaces, identity services, DNS/resolution services) as regulated core platform services.
• Sectoral hybrid approach: A bespoke combination of DMA-style duties plus newly drafted sectoral rules (or delegated acts) that align cloud obligations with other EU files like the Data Act, EUCS (cybersecurity certification) and the AI Act.
• No DMA action — competition law remedies only (less likely): Traditional antitrust actions targeting specific contractual or pricing abuses rather than ex‑ante rules.
• Structural remedies or divestiture (least likely short-term): Reserved for extreme cases of entrenched, sustained malpractice; a remote but high‑impact possibility under the DMA enforcement toolset.

---

Reactions: industry, customers and European providers​

How the hyperscalers have framed their response​

Both AWS and Microsoft emphasize competition, investment and customer choice. Microsoft has signalled cooperation with EU investigators and is highlighting investments in in‑country and sovereignty options for European workloads. Amazon stresses that scale benefits customers through lower prices and innovation. These public stances aim to shift the narrative from regulatory restraint to competitive benefits of large‑scale investment.

Customers and enterprise buyers​

Enterprises and public procurers face short‑term uncertainty and potential leverage:

• Procurement teams could use the regulatory window to renegotiate exit terms, portability guarantees and egress commitments.
• IT organisations may accelerate investments in cloud‑agnostic architectures (Kubernetes, containerization, platform abstractions) and robust multi‑cloud failover plans.

European and local cloud providers​

Smaller European cloud providers and sovereign cloud initiatives (including procurement pushes and the Commission’s own sovereign cloud tendering) view the probes as an opportunity to reduce barriers to entry and grow market share — especially if remedies meaningfully lower switching friction. The Commission’s strategic procurement for sovereign cloud services and the GAIA‑X initiative form part of a broader policy push for European cloud alternatives.

---

Risks, strengths and unresolved facts​

Notable strengths of the Commission’s approach​

• Proactive, systemic framing: Treating cloud concentration as a structural and resilience risk reflects current technological realities: cloud hosts not only infrastructure but critical services and AI workloads.
• Legal flexibility: The DMA’s qualitative market investigation tool allows the Commission to address markets where standard gatekeeper metrics are not apt — important for cloud.
• Evidence-driven process: The probe’s emphasis on technical annexes, retention orders and requests for information signals an evidence-first method that can produce narrowly tailored remedies.

Material risks and caveats​

• Technical feasibility: Translating legal obligations into operational requirements for cloud control planes, storage semantics and custom silicon is non-trivial; poorly specified mandates could harm performance or security.
• Investment disincentives: If remedies unduly limit proprietary innovations or revenue models, hyperscalers might reduce investment in local data centres or advanced hardware — a concern for EU capacity and AI readiness.
• Fragmentation and compliance costs: Divergent obligations across jurisdictions (EU vs UK vs US) could increase complexity for multinational customers and providers alike, with compliance overheads that smaller players struggle to bear.

Unverified and provisional claims​

Some early reporting relied on anonymous briefings; those attributions should be treated cautiously until formal Commission documents and notices are published. The precise mechanics — which services will be considered, the data sets relied upon, and the technical specifications for any interoperability obligations — remain to be made public during the formal inquiry. Readers should regard speculative details circulating in press briefings as provisional until corroborated by official Commission filings.

---

Practical implications and actions for enterprise IT leaders​

Enterprises should treat the next 12 months as an operational and contractual planning window. Practical steps to reduce exposure and seize potential benefits:

• Inventory cloud dependencies: Map workloads, data flows, managed services and critical APIs tied to a single vendor. Prioritise systems whose migration would be costly or complex.
• Harden exit options: Negotiate explicit migration plans, audited egress pricing, performance SLAs for migration tooling and clear IP/lock‑in clauses in contracts.
• Adopt cloud‑agnostic patterns: Expand use of container orchestration, immutable infrastructure, and abstraction layers that reduce coupling to provider‑specific managed services.
• Test failover and portability: Run migrations and disaster‑recovery drills across providers to measure real‑world migration costs and performance impacts.
• Engage procurement and legal teams early: Build clauses that anticipate regulatory changes (e.g., carve-outs for mandated interoperability obligations) and ensure procurement has leverage in renegotiations.

These actions are practical insurance whether the Commission ends up imposing DMA obligations or pursuing narrower competition remedies.

---

Geopolitics and the wider regulatory landscape​

The probes sit at the intersection of competition policy, digital sovereignty, cybersecurity certification (EUCS), the EU Data Act and the AI Act. Any EU decisions will ripple across transatlantic relations and global tech governance debates. The Commission’s sovereign cloud procurements and the push for regional certification and sovereignty options illustrate that the EU’s ambition goes beyond competition fixes to strategic autonomy in critical infrastructure. Expect intense negotiation — between Brussels and the hyperscalers, among EU member states, and between regulators in the EU, UK and the U.S. — as the technical record builds and companies submit detailed evidence. There is also a material risk that heavy-handed remedies, if poorly targeted, could prompt legal challenges and protracted litigation.

---

Conclusion​

The European Commission’s decision to probe AWS and Azure under the Digital Markets Act marks a pivotal moment for cloud governance. The inquiry recognizes that cloud infrastructure is now a strategic market with implications for competition, resilience and AI‑era innovation. The most likely near‑term outcome is carefully targeted obligations that improve portability, transparency and non‑discrimination without undermining the technical performance that modern cloud services provide. Yet the stakes are high: ill‑designed rules risk reducing investment or fragmenting the market, while too‑light interventions could leave the EU exposed to systemic dependency.
Enterprises should act now: inventory dependencies, test portability, strengthen contractual exit terms and accelerate cloud‑agnostic architectures. Regulators, for their part, face a rare engineering-and-policy challenge — to convert legal principles into technically precise, enforceable standards that protect contestability while preserving the scale economics and security advantages that hyperscalers supply.
This regulatory chapter will play out over the coming year in dense technical filings, evidence briefs, and stakeholder consultations — and its outcome will influence how cloud platforms operate in Europe and beyond for years to come.

---

Source: Channels Television https://www.channelstv.com/2025/11/...oud-services-could-face-tougher-eu-rules/amp/
Source: Yen News https://yen.com.gh/business-economy/294884-amazon-microsoft-cloud-services-face-tougher-eu-rules/

 

[ChatGPT]

The European Commission has opened three formal market investigations to determine whether Amazon Web Services (AWS) and Microsoft Azure should be treated as “gatekeepers” under the EU’s Digital Markets Act (DMA) — and whether the DMA’s existing toolbox is fit to police competition, portability and resilience in cloud infrastructure.

Background​

Cloud infrastructure once sat quietly in IT budgets as a utility; today it is strategic industrial infrastructure that underpins banking, government systems, streaming platforms and the compute stacks for large generative AI models. That shift has placed hyperscalers — in particular AWS and Microsoft Azure — squarely into regulators’ crosshairs in Europe. The EU’s action comprises two company-specific market investigations (one for AWS, one for Azure) and a horizontal probe examining whether the DMA’s rules and enforcement model are appropriate for the cloud sector. The DMA was designed as an ex‑ante regulatory regime to prevent entrenched digital platforms from using their intermediary role to foreclose competition. It prescribes specific obligations for designated “gatekeepers” (non-discrimination, interoperability, portability, bans on certain kinds of tying and bundling) and levies substantial fines for breaches. While gatekeeper designation usually follows clear quantitative thresholds, the DMA contains a qualitative route: the Commission can investigate services that functionally act as gateways between businesses and users even if they don’t neatly meet the numerical tests. That legal pathway is now being deployed for cloud.

---

Why Brussels moved on cloud: the case the Commission is making​

Three converging drivers explain the timing and intensity of the EU inquiry:

• Market concentration and entrenched positions. National reviews and industry trackers show that a small group of hyperscalers captures much of public-cloud spend in many European markets, giving rise to scale advantages that are difficult for new entrants to overcome.
• Switching friction and anti‑competitive conduct. Regulators and rivals have repeatedly flagged contractual and technical friction points — notably egress fees, proprietary APIs, and licensing differentials (for example, how Microsoft licenses Windows Server or SQL Server on rival clouds) — that can lock customers in. These are core lines of inquiry for the Commission.
• Systemic resilience and the AI accelerant. High‑profile outages, plus the explosion of AI workloads that require specialized accelerators and tightly integrated stacks, have converted a competition problem into a national-security and industrial-policy issue: over-dependence on a few providers can amplify systemic risk and shape who can compete in AI.

The Commission’s public timetable targets completion of the company-level probes in roughly 12 months, with the horizontal DMA fitness study potentially stretching longer and able to propose legislative or delegated-act changes if gaps are found.

---

What the investigations will examine (technical and legal lines of inquiry)​

The Commission has outlined multiple concrete themes it will probe. These are the practical points that will determine whether cloud services can be treated as gatekeepers and whether DMA obligations map onto cloud markets.

Portability, egress fees and data access​

• Are data export processes practically usable for production workloads?
• Do egress fees or slow, partial export tooling make migration prohibitively expensive or operationally risky?
• Can customers access billing, telemetry and application data in formats that permit real migration?

These questions get to the heart of lock‑in: if a customer cannot move without months of engineering work and high fees, the cloud provider gains durable strategic leverage. Regulators will want evidence, contracts, technical documentation and real migration case studies.

Licensing and pricing practices​

• Do software licensing terms and discounts materially favor running the software on the provider’s own cloud?
• Are there differential obligations or charges that make rival clouds economically unattractive for certain workloads?

The UK Competition and Markets Authority (CMA) already flagged these concerns in its cloud market work earlier in 2025; the CMA noted differential pricing/licensing for Microsoft products as a competitive friction. Brussels will test whether similar structural effects exist across the EU.

Self‑preferencing, bundling and managed services​

• Do hyperscalers give preferential placement, performance or pricing to their own managed services, marketplaces or developer tooling?
• Is bundling used in ways that make independent ISVs and alternative infrastructure providers less discoverable or viable?

If gatekeeper behaviour is found, the DMA can require non‑discrimination and ban unfair tying — remedies that would change how hyperscalers present and operate their stacks.

Interoperability, APIs and control‑plane primitives​

• To what extent are important control‑plane features proprietary?
• Are there standard interface options that truly allow multi‑cloud orchestration with predictable performance for latency‑sensitive workloads?

Cloud portability is not just about moving data; it’s about moving runtime behaviour, networking constructs, identity and orchestration. Technical assessments will consider whether the absence of standard interfaces is an unavoidable technical reality or a deliberate lock‑in mechanism.

Systemic risk, outages and resilience​

Regulators will ask whether concentration increases systemic fragility. Are key public services or industry-critical systems concentrated in ways that create single points of failure? The Commission has explicitly tied resilience concerns to its cloud inquiries.

---

Legal mechanics: how the DMA’s designation process works for cloud​

Under the DMA, a presumptive designation as a gatekeeper is normally triggered by specific quantitative thresholds (notably significant EU turnover/market capitalisation and platform metrics such as 45 million monthly active end users). However, the Commission can open a market investigation and designate a service on qualitative grounds if it finds the service functions as an essential gateway. The current cloud probes use that qualitative pathway. If the Commission designates AWS or Azure (or particular cloud services) as gatekeepers, the DMA’s obligations would apply and the firms would typically have a compressed compliance window (often six months) to adapt. Non‑compliance carries heavy fines (up to 10% of worldwide turnover for first breaches, higher for repeat breaches).

---

What’s already on the record: prior regulatory findings and market data​

Several national regulators and industry trackers laid groundwork for Brussels’ action:

• The UK’s CMA reported strong market concentration, concluding that AWS and Microsoft each hold substantial shares of cloud spending in the UK and recommending further action under new UK rules. It highlighted switching costs and licensing differentials as material concerns.
• Industry data from market research firms show the top three global providers (AWS, Microsoft, Google) account for a large portion of European cloud spending; the precise percentages vary by segmentation and metric, but independent trackers consistently report a highly concentrated top tier.
• The Commission’s press release confirms the three market investigations and frames them as both competition and strategic policy work related to AI and resilience.

These prior findings provide both the empirical basis and political momentum for the EU’s stepped-up scrutiny. Cross‑jurisdictional activity (UK CMA, EU Commission) and complaints from rivals (notably Google) created an evidentiary mosaic Brussels is now integrating.

---

Potential outcomes and remedies: what could change​

The investigations open a spectrum of possible regulatory outcomes, from modest commitments to sweeping obligations:

• No designation, but sectoral remedies or commitments. The Commission could conclude the DMA is not the right vehicle for cloud and instead secure legally binding commitments (behavioural remedies) from providers to address specific practices (egress transparency, improved export tooling).
• Designation of specific cloud services as gatekeepers. The Commission could designate AWS, Azure or parts of their service stacks as gatekeeper core platform services under the DMA’s qualitative route. Designation would trigger:
• Non‑discrimination obligations for business users.
• Interoperability and portability duties where technically feasible.
• Bans on unfair tying and bundling for certain integrations.
• Enhanced transparency and audit requirements.

These obligations would reshape procurement, integration patterns and product roadmaps for hyperscalers.

• Legislative or delegated‑act adaptation of the DMA. The horizontal probe could recommend targeted updates to the DMA (via delegated acts or guidance) to clarify how portability, active-user metrics and interoperability rules apply to enterprise infrastructure and AI stacks. That would create a longer-term change in the regulatory architecture for cloud.
• Monetary fines or structural remedies for breaches discovered during the investigation. If the Commission uncovers past infringements, fines and structural interventions remain legally available, though they are typically reserved for severe, repeated non‑compliance.

---

Strategic impacts — who stands to gain and who will be exposed​

For hyperscalers (AWS and Microsoft)​

• Short term: resource burden of massive compliance processes, disclosure, and possible contractual changes. Public statements from both companies warned that heavy‑handed remedies could raise costs and complicate service delivery.
• Medium term: potential curbs on bundling, preferential pricing, and proprietary control‑plane features. This would reduce some incumbent advantages but could also limit how hyperscalers innovate in tightly integrated managed services.
• Long term: if the DMA is successfully adapted to cloud, hyperscalers will face a recurring compliance regime across the EU that affects product design, pricing and go‑to‑market strategy.

For customers (enterprises, governments)​

• Benefits: stronger contractual portability, clearer data access rights, and potentially fairer pricing and non‑discrimination for business users. Gatekeeper obligations could materially reduce lock‑in for many workloads.
• Risks: increased complexity and potential cost increases as providers reprice offerings or pass compliance costs downstream; fragmentation where providers expose APIs to satisfy regulators but with differing semantics; and the chance that stricter rules slow rapid rollouts of managed, integrated services (including managed AI offerings).

For smaller cloud providers and challengers​

• Benefits: reduced anti‑competitive self‑preferencing and better interoperability could lower barriers to adoption and help alternative cloud or national providers compete.
• Risks: if the regulatory response is poorly designed, it could inadvertently raise customer switching costs or create compliance overheads that favour the largest vendors who can absorb them — a classic regulatory capture hazard.

---

Critical analysis: strengths, gaps and risks in the Commission’s approach​

Strengths — why the investigation is justified​

• The move addresses real structural issues: concentration, dependency, and lock‑in that national reviews have already documented. Treating cloud as a strategic infrastructure for competition and resilience is consistent with broader EU industrial and digital sovereignty goals.
• The DMA’s qualitative pathway is a legitimate legal instrument to reach services that function as gatekeepers but don’t fit consumer‑facing metrics; using it avoids a regulatory vacuum and demonstrates adaptability.
• The Commission is combining company probes with a horizontal study — a prudent design that separates firm-specific findings from systemic rule‑making. This reduces the risk of premature, one-size-fits-all remedies.

Gaps and open questions​

• Measurement and metrics. The DMA’s thresholds (45 million monthly active users, turnover thresholds) are poorly aligned with cloud metrics (contract value, capacity, active workloads). How the Commission maps those concepts to cloud will be decisive and remains an open methodological challenge.
• Technical feasibility of portability. For some workloads, particularly GPU‑accelerated AI training or specialized managed services, true portability may be technically infeasible without major redesign. The Commission must balance enforceable interoperability with realistic technical constraints.
• Investment and innovation trade‑offs. Overly prescriptive obligations could disincentivize the capital‑intensive investments that hyperscalers make in global datacenter footprints and specialized accelerators — the very investments that underpin cloud performance and availability. The Commission must calibrate remedies to avoid chilling investment while protecting competition.

Risks and unintended consequences​

• Regulatory fragmentation: If the EU requires provider‑specific interfaces or mandates particular portability formats, the ecosystem risks splintering into variations that increase vendor lock‑in in practice (different “standard” APIs for different regions). Coordination across jurisdictions will be crucial.
• Cost pass‑through: Compliance costs could be passed to customers, particularly SMEs, harming the very organizations the DMA aims to protect.
• Litigation and delay: Gatekeeper designation and complex technical remedies will prompt legal challenges that could delay outcomes (and leave markets in regulatory limbo). The Commission’s 12‑month target is ambitious; expect procedural contestation.

---

Practical guidance for IT leaders and procurement teams​

The regulatory landscape is shifting. Regardless of final outcomes, IT and procurement teams should act now to strengthen their cloud posture:

• Audit and document portability risk. Identify the workloads, data and services that would be hardest to migrate (specialized accelerators, proprietary managed databases) and cost‑model migration scenarios.
• Reinforce exit clauses and SLAs. Negotiate stronger contractual guarantees for export tooling, reasonable egress terms, transitional support and performance SLAs.
• Design for mobility. Where feasible, adopt containerization, standardized orchestration (Kubernetes), and abstraction layers to decouple applications from provider-specific primitives.
• Stress-test resilience. Simulate failovers and recovery plans that do not rely on a single cloud region or provider for mission‑critical services.
• Monitor procurement law and compliance obligations. Public-sector buyers should watch the probes closely; a designation could alter supplier selection, tender requirements and audit obligations.

These steps are practical hedges that reduce risk whether or not the DMA is adapted to cloud.

---

Geopolitical context and the transatlantic dimension​

Cloud regulation in the EU sits inside a larger geopolitical competition over AI, digital sovereignty and industrial policy. U.S. tech firms push back on rules they say could fragment markets or raise costs; European policymakers emphasize resilience and competitiveness for EU companies. The Commission’s move also echoes UK regulatory work and draws scrutiny from U.S. policy actors, making this a transatlantic regulatory flashpoint where trade, technology and security concerns intersect. Coordinated multilateral approaches or at least cross‑jurisdictional alignment would reduce the risk of conflicting obligations and compliance fatigue.

---

What to watch next: timeline and signals​

• Short term (weeks–months): the Commission will collect evidence, invite stakeholder submissions and request contractual and technical documentation from AWS and Microsoft. Expect a steady stream of position papers from cloud rivals, industry associations and national authorities.
• Medium term (up to 12 months): targeted market investigation decisions on whether to designate one or both services as gatekeepers; if designation occurs, a compressed compliance window will follow.
• Longer term (12–18+ months): the horizontal study could recommend delegated‑act changes to the DMA or sector‑specific guidance clarifying how portability, interoperability and gatekeeper obligations apply to cloud and AI infrastructure.

Key signals that will matter: whether the Commission finds systemic lock‑in mechanisms (egress practices, licensing asymmetries), whether it opts to designate services or prefer commitments, and whether member states or other regulators push for harmonized remedies.

---

Conclusion​

The European Commission’s decision to probe AWS and Microsoft Azure under the DMA marks a watershed moment for cloud governance. It brings competition law, resilience policy and industrial strategy into a single initiative aimed at one of the economy’s most strategic inputs: compute and storage at massive scale. The investigations are legally and technically complex, and their outcomes will reshape contract terms, product roadmaps and procurement practices across Europe and beyond. For IT leaders, the practical takeaway is immediate: treat portability and exit planning as priority risk items, reinforce contractual protections, and plan for a regulatory environment that may soon demand greater interoperability and transparency from cloud providers. Caution: some numerical market-share and revenue figures cited in public commentary vary by source and by market segmentation; where precise percentages or revenue totals are consequential, those figures should be verified against the primary regulator reports and the companies’ financial disclosures.

---

Source: The Brussels Times EU probes Amazon, Microsoft cloud services under new digital rules