Competition Issues in Global Cloud Infrastructure Markets

1. Introduction

Global cloud infrastructure markets concern the provision of computing infrastructure over networks, particularly:

Infrastructure-as-a-Service (IaaS);

cloud computing capacity;

virtual machines;

storage;

networking;

databases;

computing clusters;

container infrastructure;

cloud security;

content delivery infrastructure; and

infrastructure supporting AI and machine learning.

The market is increasingly characterized by large providers, substantial economies of scale, high capital requirements, network effects, data advantages, long-term contracts and significant switching costs.

Competition concerns can therefore arise from:

cloud concentration;

switching costs;

data portability barriers;

interoperability restrictions;

egress fees;

tying and bundling;

exclusive arrangements;

self-preferencing;

discriminatory access;

acquisition of emerging competitors;

use of customer data;

interoperability with competing clouds; and

leveraging infrastructure dominance into adjacent markets.

A central competition-law question is:

When does legitimate cloud differentiation become conduct that materially restricts competition or entrenches market power?

2. Meaning of Cloud Infrastructure Markets

Cloud infrastructure generally provides computing resources without requiring customers to own the underlying physical infrastructure.

Simplified structure

Data centres

↓

Servers + storage + networking

↓

Virtualization / cloud infrastructure

↓

IaaS

↓

PaaS / SaaS / AI services

↓

Business and consumer applications

The provider operating at the infrastructure level may therefore have influence over several downstream markets.

3. Major Global Cloud Providers

The global market has historically been associated particularly with:

Amazon Web Services;

Microsoft Azure; and

Google Cloud.

Other providers include regional and specialist cloud operators.

The existence of large providers does not itself establish an antitrust violation. Market definition, market power, entry conditions and actual conduct must be assessed.

4. Why Cloud Markets Raise Competition Issues

A. Economies of Scale

Cloud infrastructure requires enormous investment in:

data centres;

electricity;

cooling;

networking;

servers;

security;

software;

specialized chips.

Large providers can spread these costs over millions of customers.

This may make entry difficult.

B. Network Effects

Cloud ecosystems can benefit from:

developer communities;

third-party applications;

certifications;

technical expertise;

marketplace participation;

complementary services.

More users can attract more developers and service providers.

C. Switching Costs

Customers may invest heavily in a particular cloud environment.

Switching may require:

rewriting applications;

migrating databases;

retraining employees;

redesigning architecture;

changing security systems;

moving workloads;

renegotiating contracts.

This can create substantial customer lock-in.

5. Cloud Vendor Lock-In

Lock-in is one of the most important competition issues.

A business may initially choose Cloud A because it is efficient.

Over time, it may build:

proprietary configurations;

databases;

APIs;

applications;

security systems;

AI workflows.

The cost of moving everything to Cloud B can then become very high.

Competition mechanism

Initial cloud adoption

↓

Investment in cloud-specific architecture

↓

Higher switching cost

↓

Reduced customer mobility

↓

Greater incumbent retention

↓

Potentially weaker competitive pressure

High switching costs alone, however, do not prove anticompetitive conduct.

6. Data Egress Fees

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

They may serve legitimate economic purposes, including covering network costs.

However, competition concerns may arise if contractual or technical structures make migration excessively difficult or expensive and thereby reinforce customer lock-in.

Questions include:

How large are the fees?

Are they cost-related?

Are customers adequately informed?

Are there alternatives?

Can data be moved efficiently?

Do the fees discriminate between services?

Do they operate together with other switching barriers?

7. Interoperability

Cloud customers increasingly operate across multiple providers.

This creates demand for:

common APIs;

portable databases;

interoperable identity systems;

container standards;

data portability;

cross-cloud networking.

A provider could potentially disadvantage competitors through restrictions on interoperability.

The Microsoft interoperability jurisprudence is therefore relevant by analogy to cloud environments.

8. Tying and Bundling

A cloud provider may offer:

infrastructure + database + cybersecurity + AI + productivity software.

Bundling can be beneficial because customers receive integrated services.

But competition concerns may arise if a dominant provider conditions access to one important service upon purchasing another and thereby forecloses competitors.

The relevant principles can be seen in cases involving:

Microsoft;

Google Android;

Google Shopping;

United Brands and other Article 102 jurisprudence.

9. Cloud and Software Ecosystem Leverage

Suppose a company has significant strength in enterprise software and cloud infrastructure.

It could potentially use:

software dominance

↓

cloud integration

↓

preferential compatibility

↓

customer migration toward its cloud

This is a form of ecosystem leveraging.

Competition authorities may examine whether technical or contractual integration creates an exclusionary advantage rather than merely reflecting legitimate product integration.

10. Data Advantages

Cloud providers can potentially obtain large quantities of information concerning:

customer usage;

workload patterns;

resource requirements;

application performance;

cybersecurity;

developer behavior.

The data itself may not necessarily confer market power.

But data advantages can become important when combined with:

scale;

network effects;

AI;

ecosystem integration;

switching costs.

11. AI and Cloud Infrastructure

The cloud market is becoming increasingly connected to AI infrastructure.

AI development may require:

GPUs;

AI accelerators;

high-performance computing;

specialized networking;

enormous storage;

model-serving infrastructure.

Cloud providers may therefore become important gateways to AI markets.

Potential competition concerns include:

exclusive GPU arrangements;

preferential access to AI chips;

tying AI services to cloud infrastructure;

preferential treatment of own AI models;

cloud credits linked to particular services;

acquisition of AI startups;

interoperability restrictions.

12. Exclusive Cloud Arrangements

Cloud providers may negotiate contracts involving:

minimum spending;

volume commitments;

preferred-provider requirements;

cloud credits;

discounts;

exclusivity.

These arrangements can generate efficiencies and predictable demand.

But exclusivity can also potentially make it harder for rival cloud providers to obtain customers.

The competition analysis depends upon:

market power;

duration;

coverage;

switching costs;

foreclosure;

customer alternatives.

13. Cloud Marketplaces

Cloud providers often operate marketplaces where third-party software can be purchased.

This creates potential conflicts.

A cloud provider can act simultaneously as:

infrastructure provider;

marketplace operator;

software competitor.

Possible concerns include:

self-preferencing;

ranking discrimination;

access discrimination;

use of third-party merchant data;

preferential commissions;

tying marketplace access to cloud services.

This has parallels with the concerns examined in Google Shopping.

14. Vertical Integration

Cloud infrastructure can be vertically integrated with:

operating systems;

databases;

cybersecurity;

enterprise software;

AI models;

productivity applications;

advertising;

hardware.

Vertical integration can produce efficiency.

But it may also enable:

Input foreclosure

or

Customer foreclosure

For example, a cloud provider could potentially make a rival software product technically less attractive within its cloud environment.

15. At Least 6 Important Case Laws

1. Microsoft Corp. v Commission

Case T-201/04, General Court, 2007

Facts

Microsoft's dominance in PC operating systems was accompanied by conduct concerning interoperability information and Windows Media Player.

Principle

The case addressed the competitive significance of interoperability and leveraging dominance from one technological environment into adjacent markets.

Relevance to cloud

Cloud infrastructure similarly depends on:

APIs;

interoperability;

technical interfaces;

compatibility.

Microsoft therefore provides a major precedent for understanding how technical control can affect competition in interconnected technology markets.

16. 2. Google Android

Case T-604/18, General Court, 2022

Facts

The Commission examined contractual practices involving Android, including arrangements concerning Google Search, Chrome and the Google Play Store.

Principle

The case demonstrated how restrictions across an interconnected ecosystem can reinforce the position of a dominant undertaking.

Relevance to cloud

Cloud providers similarly combine multiple services.

Potential competition concerns can therefore arise when:

infrastructure + software + marketplace + applications

are contractually or technically integrated in ways that disadvantage competing services.

17. 3. Google Shopping

Case T-612/17, General Court, 2021

Facts

Google was found to have systematically favored its own comparison-shopping service in general search results.

Principle

The case concerned discriminatory treatment and leveraging through control of an important digital gateway.

Relevance to cloud

A cloud provider may similarly operate a marketplace or platform while simultaneously competing with businesses using that platform.

The case is therefore relevant by analogy to:

cloud marketplaces;

ranking;

self-preferencing;

preferential visibility;

affiliated services.

It is not itself a cloud case.

18. 4. Bronner v Mediaprint

Case C-7/97, CJEU, 1998

Principle

The CJEU adopted a stringent approach to mandatory access to infrastructure under the essential-facilities/refusal-to-supply doctrine.

Relevance to cloud

Customers or competitors cannot automatically demand access to every cloud infrastructure component.

To require access under Article 102, the relevant legal conditions must be established.

This provides an important counterweight to arguments that every important cloud service must be made interoperable with competitors.

19. 5. Deutsche Telekom v Commission

Case C-280/08 P, CJEU, 2010

Facts

The case concerned pricing and access conditions in telecommunications infrastructure.

Principle

The CJEU addressed margin squeeze and exclusionary effects arising from the relationship between wholesale access and downstream pricing.

Relevance to cloud

The telecommunications infrastructure context provides a useful analogy because cloud computing similarly involves:

infrastructure;

wholesale-type access;

downstream services;

vertically integrated providers.

A cloud provider controlling an important infrastructure layer could potentially face similar scrutiny where its pricing structure disadvantages downstream competitors.

20. 6. Slovak Telekom

Joined Cases C-165/19 P and C-166/19 P, CJEU, 2021

Facts

The case concerned access to telecommunications infrastructure and exclusionary conduct.

Principle

The CJEU examined the relationship between dominant infrastructure control and downstream competition.

Relevance

Cloud infrastructure has comparable vertical characteristics.

The case is therefore useful when analyzing:

access conditions;

interoperability;

infrastructure control;

downstream foreclosure.

Again, it is an analogy rather than a cloud-specific precedent.

21. 7. Commercial Solvents

Joined Cases 6/73 and 7/73, CJEU, 1974

Facts

A dominant undertaking controlled an important upstream input and sought to restrict downstream competition.

Principle

A dominant firm cannot necessarily exploit control over an upstream input to eliminate effective competition in a downstream market.

Relevance to cloud

The analogy is:

Cloud infrastructure

↓

Platform/service layer

↓

Downstream applications

If a cloud provider uses control of infrastructure to disadvantage downstream rivals, the Commercial Solvents principle may become relevant.

22. 8. IMS Health

Case C-418/01, CJEU, 2004

Facts

IMS Health controlled a structured information system used by pharmaceutical companies.

Principle

The CJEU established stringent conditions for requiring a dominant undertaking to license protected infrastructure/IP.

Relevance to cloud

Cloud infrastructure often contains proprietary:

APIs;

software;

data structures;

technical systems.

IMS Health reinforces the principle that competition law does not automatically create a right to access proprietary infrastructure.

23. Case-Law Comparison

24. Cloud Switching Costs

Switching costs can arise from:

Technical costs

rewriting applications;

adapting APIs;

migrating databases.

Commercial costs

terminating contracts;

losing discounts;

losing cloud credits.

Human-capital costs

retraining engineers;

hiring specialists.

Operational costs

downtime;

testing;

security certification.

Data costs

transferring large datasets;

converting data formats.

The combined effect may make customers effectively dependent upon a provider.

25. Multi-Cloud Competition

Many enterprises use more than one cloud.

This is called multi-cloud.

It can increase competitive pressure because customers can distribute workloads between providers.

However, multi-cloud strategies can be undermined by:

proprietary APIs;

high migration costs;

contractual restrictions;

technical incompatibility;

egress fees;

service-specific dependencies.

Thus interoperability can become a major competition parameter.

26. Cloud Credits and Discounts

Cloud providers may provide:

free credits;

volume discounts;

startup credits;

long-term discounts.

These can encourage adoption and produce legitimate efficiencies.

Competition concerns may arise where such arrangements effectively make it uneconomic to use rival cloud services.

Relevant questions include:

How long does the arrangement last?

What percentage of customer demand is covered?

Is switching practically possible?

Is there exclusivity?

Are discounts conditional?

Does the provider have substantial market power?

27. Self-Preferencing in Cloud

Consider a cloud marketplace.

The provider hosts:

third-party cybersecurity software;

its own cybersecurity product.

If the provider systematically gives its own service:

better ranking;

preferred APIs;

lower fees;

superior integration;

exclusive technical functionality,

the issue may resemble the competitive theory in Google Shopping, although the precise legal test depends on the jurisdiction and conduct.

28. Cloud Data Use

A cloud provider may process data belonging to customers.

A potential concern arises if the provider uses commercially sensitive customer information to compete against those customers.

Example:

A cloud marketplace observes that a particular SaaS product is extremely successful and uses detailed platform data to develop a competing product.

Possible competition concerns could involve:

leveraging;

information advantages;

exclusion;

unfair competitive use of data.

The actual legal assessment would depend on evidence and market conditions.

29. Interoperability and Open Standards

Open standards can reduce:

switching costs;

technical lock-in;

entry barriers.

Examples include:

container standards;

standardized APIs;

interoperable identity systems;

common data formats.

But standardization itself can raise competition concerns if participants use the process to:

exclude competitors;

restrict alternative technologies;

discriminate against outsiders.

Thus:

Interoperability can promote competition, while control over interoperability can also become a source of market power.

30. Cloud Acquisitions

Large cloud providers may acquire:

cybersecurity companies;

database companies;

AI firms;

observability providers;

infrastructure startups;

SaaS companies.

Competition authorities may examine whether the acquisition:

removes a potential competitor;

increases vertical integration;

gives access to sensitive data;

reinforces ecosystem lock-in;

eliminates an interoperability solution.

31. AI Compute Concentration

A particularly important emerging issue is the concentration of AI compute.

Advanced AI may require:

high-performance GPUs;

specialized accelerators;

high-speed networking;

enormous data storage.

If access to these resources becomes concentrated, competition concerns may involve:

capacity allocation;

long-term supply arrangements;

exclusive cloud partnerships;

preferential access;

tying compute to AI models;

foreclosure of AI startups.

These issues remain technologically and legally developing.

32. Geographic and Global Dimensions

Cloud infrastructure is inherently global.

A provider may operate:

data centres in multiple countries;

global networks;

cross-border cloud services.

Competition authorities may therefore consider:

different geographic markets;

international merger effects;

cross-border data;

national security restrictions;

regulatory fragmentation;

localization requirements.

Different jurisdictions can reach different conclusions because market conditions and legal frameworks differ.

33. Consumer and Business Effects

Cloud competition affects not only cloud providers but also downstream users.

Potential effects of stronger competition include:

lower prices;

better service quality;

better security;

greater innovation;

easier switching;

better interoperability.

Potential competition harm can include:

higher switching costs;

reduced choice;

slower innovation;

reduced interoperability;

higher infrastructure prices.

34. Important Distinction: Concentration vs Abuse

A highly concentrated cloud market is not automatically unlawful.

Similarly:

Large market share ≠ automatic abuse.

Competition law normally requires analysis of:

relevant market;

market power/dominance;

conduct;

competitive effects;

efficiencies or objective justification where relevant.

This distinction is particularly important in cloud markets because large scale may itself produce legitimate efficiency benefits.

35. Competition Assessment Framework

For an exam or legal analysis, use the following sequence.

Step 1 — Define the market

Determine whether the relevant market concerns:

IaaS;

PaaS;

SaaS;

cloud storage;

cloud databases;

AI compute;

cloud security;

specific enterprise workloads.

Step 2 — Measure market power

Consider:

market shares;

switching costs;

customer dependence;

entry barriers;

economies of scale;

network effects.

Step 3 — Identify conduct

Examine:

tying;

bundling;

exclusivity;

discriminatory access;

egress restrictions;

interoperability restrictions;

self-preferencing;

acquisitions.

Step 4 — Analyze effects

Ask whether conduct:

forecloses competitors;

raises rivals' costs;

increases switching costs;

reduces innovation;

strengthens dominance.

Step 5 — Examine efficiencies

Consider:

security;

reliability;

integration;

performance;

cost savings;

innovation.

36. Practical Example

Assume Cloud A has substantial market power.

It provides:

infrastructure;

database services;

AI compute;

enterprise software;

cloud marketplace.

Cloud A introduces a policy under which customers receive major discounts only if they commit most of their cloud spending to Cloud A.

At the same time:

data migration is expensive;

egress charges are high;

competing databases receive inferior integration;

Cloud A's own database receives automatic technical advantages.

Possible competition concerns

exclusivity;

tying/bundling;

switching-cost reinforcement;

interoperability restrictions;

self-preferencing;

downstream foreclosure.

Possible legitimate explanations

Cloud A may argue:

infrastructure-cost savings;

security;

reliability;

technical integration;

volume efficiencies.

The final assessment requires evidence concerning the actual market effects.

37. Key Competition Risks

38. Key Case-Law Lessons

Microsoft

Control over interoperability can become an important competition issue in a technology ecosystem.

Google Android

Restrictions across interconnected products can reinforce ecosystem power.

Google Shopping

Control over a digital gateway can create competition concerns when used to favor an affiliated service.

Bronner

Competition law does not automatically require infrastructure owners to provide competitors with access.

Deutsche Telekom

Control over infrastructure and access conditions can affect downstream competition.

Slovak Telekom

Infrastructure access and exclusionary vertical conduct require careful competition analysis.

Commercial Solvents

Control over an important upstream input can raise concerns when used to eliminate downstream competition.

IMS Health

Compulsory access to proprietary infrastructure or information remains exceptional.

39. Conclusion

Global cloud infrastructure markets present a distinctive combination of scale economies, network effects, switching costs, data advantages, vertical integration and technological dependency.

The principal competition concerns include:

cloud lock-in;

high switching costs;

egress barriers;

interoperability restrictions;

exclusive arrangements;

tying and bundling;

self-preferencing;

discriminatory marketplace treatment;

data exploitation;

vertical foreclosure;

AI-compute concentration; and

potentially exclusionary acquisitions.

The existing case law does not provide a single comprehensive "cloud competition test." Instead, established principles from Microsoft, Google Android, Google Shopping, Bronner, Deutsche Telekom, Slovak Telekom, Commercial Solvents and IMS Health provide a framework for applying competition law to cloud infrastructure.

Exam-ready definition

Competition issues in global cloud infrastructure markets arise where concentration, network effects, switching costs, interoperability barriers, contractual restrictions, vertical integration, data advantages or control over critical computing infrastructure may enable cloud providers to restrict competition, foreclose rivals or reinforce market power. Competition law distinguishes legitimate economies of scale and technological integration from conduct that unjustifiably excludes competitors or raises barriers to effective competition.