Competition Law and Distributed Cloud Ecosystems and Antitrust

1. Meaning

A distributed cloud ecosystem is a cloud environment in which computing, storage, databases, applications, AI services, security, networking and data are distributed across multiple cloud providers, regions, platforms or interconnected services.

It may include:

multi-cloud systems;

hybrid cloud;

public + private cloud;

cloud-to-cloud services;

distributed databases;

cloud marketplaces;

edge computing;

cloud APIs;

cloud security services;

AI/cloud infrastructure;

container and Kubernetes ecosystems;

data-transfer and migration services.

Competition-law concern

The central question is:

Can a cloud provider use control over infrastructure, software, data, licensing, APIs or switching conditions to restrict competition in the wider cloud ecosystem?

This is increasingly important. In July 2025, the UK CMA's cloud-services market investigation concluded that Amazon and Microsoft had positions of significant market power and identified concerns including egress fees, interoperability barriers and Microsoft software licensing. (GOV.UK)

2. UAE Competition-Law Framework

For UAE analysis, the current federal statute is Federal Decree-Law No. 36 of 2023 Regulating Competition.

The law addresses:

restrictive agreements;

abuse of dominant position; and

economic concentration. (Ministry of Education)

Article 6 prohibits a dominant undertaking from engaging in conduct whose object or effect is to distort, lessen, restrict or prevent competition. It includes, among other things, unjustified discriminatory treatment. (Ministry of Education)

For distributed cloud ecosystems, the law can therefore become relevant to:

cloud-provider agreements;

interoperability restrictions;

data portability;

switching barriers;

tying and bundling;

discriminatory cloud pricing;

exclusive arrangements;

licensing practices;

cloud mergers and acquisitions.

3. What Makes Distributed Cloud Different?

Traditional cloud competition may involve:

Customer → Cloud Provider

Distributed cloud creates:

Customer → Cloud A ↔ Cloud B ↔ Cloud C → Applications/Data/AI

The customer may want to use several providers simultaneously.

Therefore, competition depends heavily on:

interoperability;

portability;

switching;

multi-cloud compatibility;

data transfer;

common standards;

licensing;

API access.

4. Core Competition Formula

C-L-I-S-D-E-R

One-line formula

Cloud dominance + lock-in + restrictive interoperability/licensing + foreclosure = potential antitrust concern.

5. Major Antitrust Issues

5.1 Customer Lock-In

Cloud customers may invest heavily in:

applications;

databases;

APIs;

security systems;

employee training;

cloud architecture.

Moving to another provider can therefore be expensive.

Result

High switching cost → customer dependency → reduced competitive pressure.

The European Commission's current cloud investigation specifically identifies strong customer lock-in, interoperability limitations, tying/bundling and data-portability restrictions as issues requiring examination. (Digital Markets Act (DMA))

6. Data Egress Fees

Egress fees are charges associated with moving data out of a cloud environment.

Example:

Company stores 500 TB with Cloud A.

Company wants to move to Cloud B.

Cloud A imposes very high data-transfer charges.

The economic effect may be:

High exit cost → customer stays → weaker multi-cloud competition.

The UK's CMA identified egress fees as one of the factors limiting customer choice in cloud services. (GOV.UK)

7. Interoperability

Interoperability means that:

Cloud A can effectively communicate and work with Cloud B.

Possible barriers include:

proprietary APIs;

incompatible databases;

restricted interfaces;

technical restrictions;

proprietary formats;

identity-system incompatibility;

application portability restrictions.

Competition effect

If Cloud A deliberately prevents effective integration with Cloud B:

Technical incompatibility → higher switching costs → customer lock-in → reduced competition.

The European Commission's cloud investigation specifically covers obstacles to interoperability between cloud services. (Digital Markets Act (DMA))

8. Multi-Cloud Competition

A competitive cloud ecosystem should allow customers to use:

AWS + Azure + Google Cloud + specialist providers

where technically appropriate.

A provider may create concerns if its commercial practices make multi-cloud unnecessarily difficult.

Important distinction

Technical difficulty is not automatically unlawful.

The competition question is whether the difficulty results from:

legitimate technical design;

security requirements;

or

strategic exclusionary conduct.

9. Tying and Bundling

A cloud provider may combine:

cloud infrastructure;

database;

productivity software;

security;

identity;

AI;

developer tools.

Bundling may generate efficiencies.

But a competition concern can arise if:

Dominant Product A + Product B → rivals cannot effectively compete in Product B.

The European Commission's current cloud investigation expressly includes tying and bundling among practices being examined. (Digital Markets Act (DMA))

10. Software Licensing

Cloud competition may be affected when software licensing terms make a rival cloud provider more expensive.

Example:

Software Provider A owns popular enterprise software.

It charges substantially more when customers run that software on rival Cloud B than on its affiliated Cloud A.

Potential effect:

Higher rival cost → weaker rival → stronger integrated cloud provider.

The UK's 2025 cloud investigation identified Microsoft software licensing as a factor limiting customer choice and competition in cloud services. (GOV.UK)

11. Self-Preferencing

A cloud provider may also operate:

AI services;

databases;

cybersecurity;

developer tools;

cloud marketplaces.

If the infrastructure operator gives its own downstream services preferential treatment, competition concerns can arise.

Example:

Cloud A gives its own AI service privileged access to computing capacity while rival AI providers receive inferior terms.

This can resemble the broader self-preferencing concerns examined in Google Shopping.

12. Cloud Marketplace Power

Cloud marketplaces can become important gateways for software vendors.

A dominant marketplace might:

rank its own applications higher;

impose discriminatory fees;

restrict competing marketplaces;

bundle cloud credits with selected applications;

make rival applications difficult to discover.

Thus:

Cloud infrastructure + marketplace + downstream services = ecosystem leverage risk.

13. Data Portability

Portability means that customers can move their data from one provider to another.

Distributed cloud competition depends heavily on portability.

Formula

Portable data → easier switching → more customer choice → stronger competition.

Conversely:

Non-portable data → lock-in → reduced switching → greater provider power.

14. API Restrictions

APIs are gateways through which cloud services communicate.

A dominant provider could theoretically:

restrict API access;

delay API functionality;

impose excessive charges;

give its own services better API functionality.

This can create an interoperability barrier.

15. Interoperability and Security

Cloud providers may legitimately restrict interoperability for:

cybersecurity;

encryption;

authentication;

system stability;

data protection;

resilience.

Therefore:

Security justification must be distinguished from exclusionary conduct.

A competition authority should examine whether a restriction is:

necessary + proportionate + technically justified.

16. Network Effects

Cloud ecosystems can exhibit network effects.

Positive feedback loop

More customers

↓

More developers

↓

More applications

↓

More complementary services

↓

More customers

↓

More data

↓

Better infrastructure

This can create ecosystem entrenchment.

17. Economies of Scale

Cloud infrastructure requires massive investment in:

data centres;

servers;

networking;

energy;

security;

engineering;

AI chips;

storage.

Large providers can therefore benefit from economies of scale.

This is not itself anti-competitive.

But economies of scale combined with:

switching costs + data advantages + ecosystem effects + restrictive practices

may make entry more difficult.

18. Cloud AI Integration

AI is increasingly connected with cloud infrastructure.

A cloud provider may control:

Cloud compute + AI chips + foundation models + AI applications + data

This can produce vertical integration.

The FTC has examined major cloud/AI partnerships and investments, including relationships involving Amazon, Microsoft, Google/Alphabet, Anthropic and OpenAI, to understand their potential competitive effects. (Federal Trade Commission)

19. Economic Concentration

A distributed cloud ecosystem can become concentrated through acquisitions.

Example:

Major Cloud A acquires a specialised cloud-security provider.

Or:

Cloud A acquires a cloud-migration company.

Or:

Cloud A acquires a database technology essential to multi-cloud interoperability.

The concern is whether the acquisition eliminates an important competitive constraint.

The UAE Ministry specifically regulates economic concentrations and examines mergers/acquisitions for their potential effect on dominance and competition. (Ministry of Education)

20. Six+ Important Case Laws

Important: There are currently relatively few reported judicial decisions specifically deciding distributed-cloud ecosystem antitrust disputes. Therefore, the following are comparative competition authorities applying principles relevant to cloud ecosystems. The recent UK/EU cloud investigations are regulatory proceedings, not judicial case law, and are discussed separately.

Case 1 — Microsoft Corp. v Commission, T-201/04

Principle

Microsoft concerned refusal to provide interoperability information to competing work-group server products, along with other conduct involving Microsoft's dominant operating system.

The General Court upheld the competition-law significance of Microsoft's refusal to supply interoperability information under the circumstances of the case. (InfoCuria)

Cloud relevance

A dominant cloud provider could face a similar issue where competitors require necessary interoperability information to compete effectively.

Memory

Interoperability information can become competitively important infrastructure.

21. Case 2 — Oscar Bronner v Mediaprint, C-7/97

The case concerned access to a dominant newspaper group's home-delivery infrastructure.

The Court adopted a stringent approach to compulsory access and required, among other things, that the infrastructure be indispensable and that refusal be capable of eliminating effective competition, with no objective justification. (InfoCuria)

Cloud relevance

Not every cloud provider must open every proprietary system to competitors.

The question is whether the relevant infrastructure is genuinely indispensable.

Memory

Important infrastructure ≠ automatic access obligation.

22. Case 3 — IMS Health GmbH v NDC Health, C-418/01

IMS Health involved refusal to license a copyrighted structure used for pharmaceutical sales data.

The Court considered the exceptional circumstances under which refusal to license intellectual property could constitute abuse of dominance. (InfoCuria)

Cloud relevance

Cloud ecosystems contain:

proprietary APIs;

database structures;

software interfaces;

copyrighted technologies.

The case helps analyse the tension between:

IP protection ↔ interoperability ↔ competition.

Memory

IP rights are strong, but exceptional circumstances can create competition-law issues.

23. Case 4 — Slovak Telekom v Commission, C-165/19 P

The case concerned access to telecommunications infrastructure and conditions for competitors' access to the incumbent's local loop.

The Court dealt with:

access;

indispensability;

margin squeeze;

costs;

dominant-position abuse. (EUR-Lex)

Cloud relevance

The case is useful where a cloud provider gives nominal access but imposes conditions that make effective competition commercially difficult.

Example

API access exists technically, but the price or terms make rival cloud operation commercially unrealistic.

Memory

Access must be assessed together with its competitive conditions.

24. Case 5 — Google and Alphabet v Commission, T-612/17

Google Shopping

The General Court examined Google's conduct in giving favourable positioning to its own comparison-shopping service relative to competing services. (InfoCuria)

Cloud relevance

A cloud provider could potentially leverage infrastructure power into:

AI;

cybersecurity;

databases;

cloud marketplaces;

developer services.

Memory

Infrastructure gateway + downstream preference = possible leveraging concern.

25. Case 6 — Google and Alphabet v Commission, T-604/18

Google Android

The case involved Google's Android ecosystem and practices concerning:

product bundles;

exclusivity payments;

anti-fragmentation obligations;

exclusionary effects. (InfoCuria)

Cloud relevance

Cloud ecosystems can similarly combine:

Infrastructure + operating software + applications + AI + security.

The case demonstrates how interconnected technological products can be assessed as part of a wider ecosystem.

26. Case 7 — Google Android / C-738/22 P

The Android litigation continued before the Court of Justice on appeal.

The broader importance is the treatment of ecosystem leverage and exclusionary arrangements in digital markets.

Cloud relevance

A distributed cloud ecosystem may similarly involve:

Core cloud service

↓

Developer tools

↓

Database

↓

AI

↓

Security

↓

Marketplace

A competition analysis may need to examine how restrictions in one layer affect competition in another.

27. Case-Law Revision Table

28. Current Regulatory Developments

UK Cloud Investigation

The UK's CMA completed its cloud-services market investigation in July 2025.

It concluded that Amazon and Microsoft had significant market power and identified:

egress fees;

interoperability barriers;

Microsoft licensing practices

as factors limiting customer choice and competition. The CMA recommended prioritising strategic-market-status investigations into Amazon and Microsoft cloud activities. (GOV.UK)

In March 2026, the CMA reported that Amazon and Microsoft had taken material steps concerning egress fees and interoperability, while stating that further assessment remained necessary. (GOV.UK)

29. EU Cloud Competition Developments

In November 2025, the European Commission opened three DMA market investigations concerning cloud computing.

The Commission examined whether:

AWS;

Microsoft Azure

should be treated as gatekeeper cloud services and whether existing DMA obligations could address cloud practices affecting fairness and contestability. (Digital Markets Act (DMA))

In June 2026, the Commission announced its preliminary view that AWS and Azure should be designated as DMA gatekeepers for cloud computing. This is a preliminary position, not a final designation. (Digital Markets Act (DMA))

The Commission's investigation specifically examines:

interoperability, financial conditions, contractual conditions, data portability, tying/bundling and switching barriers. (Digital Markets Act (DMA))

30. Distributed Cloud and Competition

A truly competitive distributed-cloud ecosystem should permit:

Multi-homing

Customer uses several cloud providers.

Switching

Customer can move to another provider.

Portability

Customer can move data and workloads.

Interoperability

Different clouds can communicate.

Neutrality

Infrastructure provider does not unfairly favour its own downstream services.

Transparency

Customers understand costs and technical restrictions.

31. Main Anti-Competitive Practices

32. Objective Justifications

A cloud provider may legitimately rely on:

cybersecurity;

encryption;

data sovereignty;

system integrity;

technical compatibility;

resilience;

intellectual-property protection;

privacy;

regulatory compliance.

The question is not simply:

“Did the provider restrict access?”

It is:

“Was the restriction objectively necessary and proportionate, or did it unnecessarily protect market power?”

33. UAE Application — Step by Step

Step 1 — Relevant market

Identify whether the market is:

public cloud infrastructure;

storage;

database services;

AI cloud;

cloud security;

cloud marketplace;

multi-cloud management;

cloud migration.

Step 2 — Market power

Consider:

market share;

infrastructure scale;

switching costs;

data;

network effects;

ecosystem;

customer dependency.

Step 3 — Conduct

Check:

egress fees;

licensing restrictions;

interoperability restrictions;

tying;

bundling;

exclusivity;

discriminatory treatment.

Step 4 — Competitive effects

Ask whether conduct:

raises rivals' costs;

prevents entry;

reduces multi-cloud use;

increases switching costs;

limits innovation;

reduces customer choice.

Step 5 — Justification

Examine:

security;

technical necessity;

IP;

privacy;

efficiency.

Step 6 — Concentration

Examine acquisitions or mergers that increase control over:

cloud infrastructure;

databases;

AI;

cybersecurity;

interoperability tools.

34. Practical Example

Facts

Cloud A has a very large enterprise customer base.

A customer wants:

Cloud A + Cloud B

Cloud A:

charges high egress fees;

gives its own database better interoperability;

charges rival Cloud B more for key software;

bundles AI services with infrastructure;

restricts certain APIs.

Competition analysis

Market

→ Enterprise cloud infrastructure.

Power

→ Large customer base + ecosystem + switching costs.

Conduct

→ Egress restrictions + interoperability + licensing + bundling.

Effect

→ Cloud B becomes more expensive and less attractive.

Potential result

→ reduced multi-cloud competition.

This is the type of economic mechanism regulators are currently examining in cloud markets. (GOV.UK)

35. Ultra-Short Revision Points

Distributed cloud = interconnected cloud ecosystem.

Multi-cloud increases customer choice.

Interoperability is essential for effective multi-cloud use.

Data portability reduces lock-in.

Egress fees can increase switching costs.

Proprietary APIs can create technical barriers.

Licensing can affect rival cloud providers.

Bundling can leverage market power.

Self-preferencing can favour integrated cloud services.

Cloud marketplaces can become important gateways.

Network effects can reinforce concentration.

AI can increase cloud ecosystem integration.

Cloud acquisitions can increase structural concentration.

Security restrictions may be legitimate.

Dominance itself is not automatically unlawful.

UAE Federal Decree-Law No. 36 of 2023 is the current federal competition framework. (Ministry of Education)

36. Ultra-Short Exam Table

Final Conclusion

Distributed cloud ecosystems create a new form of competition-law problem: control over infrastructure can translate into control over switching, interoperability, data and downstream digital services.

The key chain is:

Cloud infrastructure → ecosystem power → lock-in → interoperability/switching barriers → possible foreclosure → antitrust scrutiny.

For UAE purposes, the analysis should principally proceed under Federal Decree-Law No. 36 of 2023 through the rules on restrictive agreements, abuse of dominant position and economic concentration. (Ministry of Education)

One-line memory

“Distributed cloud competition requires interoperability, portability and switching; use of cloud power to block those mechanisms may create antitrust concerns.”