100%
GRIMOIRE
GrimoireDindon CorpusSynthesis VolumesThe Foundation of Iron
FRENAR
IUS
WORKING PAPER · SYSTEMIC ANALYSIS · JUNE 2026
◆◆◆
LOCK-IN BY DESIGN
A Six-Layer Taxonomy of Retention Mechanisms
in Hyperscaler Cloud Contracts
STRUCTURED ABSTRACT
BACKGROUNDAmazon Web Services, Microsoft Azure and Google Cloud Platform collectively hold over 65% of the global cloud infrastructure market (Synergy Research Group, Q1 2026). The academic literature on cloud vendor lock-in has predominantly addressed technical dimensions — proprietary APIs and non-portable data formats. Contractual, linguistic and behavioural dimensions have received comparatively little formal treatment. RESEARCH GAPThree of the six lock-in layers identified in this study — Skills Lock-in (Layer 4), Demand Lock-in (Layer 5) and Cognitive Lock-in (Layer 6) — are, to the author's knowledge, absent from the formalised academic literature on cloud computing. The mechanism of linguistic substitution as a vector for legal rights waiver is likewise undocumented in existing works. METHODSComparative analysis of 47 versions of contractual documents (General Terms, Product Terms, DPAs, SLAs and Addenda) published by AWS, Google Cloud and Microsoft Azure in French, English and German between 2022 and 2026. Algorithmic diff combined with manual legal review against French, German, UK and EU law. FINDINGSSix distinct and cumulative lock-in layers are identified. A specific undocumented mechanism is evidenced: the linguistic substitution clause, whereby the client-language version is declared "informational only" while the English version "prevails", enabling the inclusion of rights-waiver clauses in the English-only version absent from the client-language version. The temporal dimension is modelled in three phases (Adoption · Dependency · Captivity) with a formalised economic point-of-no-return. POLICY IMPLICATIONSFour regulatory proposals are formulated, including the extension of EU Data Act Article 25 to pricing-based switching obstacles (egress fees) and the formal designation of competent Data Act authorities by EU Member States.
Keywords: vendor lock-in · cloud computing · unfair contract terms · digital sovereignty · EU Data Act · data portability · linguistic substitution · switching costs · platform regulation
◆◆◆
Amine RAITI
Infrastructure Architect & SRE · Paris · Independent researcher
This document is based on the author's independent analysis of publicly available contractual documents.
It does not constitute legal advice. The author has no affiliation with the companies mentioned.
Public document · CC BY-NC-SA 4.0
Opération Dindon
IUS
SECTION 1 · INTRODUCTION & METHODOLOGY
1. INTRODUCTION & METHODOLOGY
1.1 Context and motivation

Cloud infrastructure market concentration has reached historically high levels. According to data published by Synergy Research Group for Q1 2026, Amazon Web Services (AWS), Microsoft Azure and Google Cloud Platform (GCP) jointly account for 67% of the global cloud services market. This concentration creates structural dependency for private and public organisations on an oligopoly whose contractual practices have attracted increasing regulatory scrutiny — including the Bundeskartellamt's §19a GWB proceedings against Amazon (2022) and Microsoft (2023), the Competition and Markets Authority's Cloud Market Study (2023), and the entry into force of the EU Data Act (Regulation (EU) 2023/2854, applicable since September 2025).

The academic literature on cloud vendor lock-in (Armbrust et al., 2010; Petcu, 2013; Opara-Martins et al., 2016) has predominantly addressed technical dimensions of lock-in — proprietary APIs, non-portable data formats, single-vendor architectures. Economic dimensions (Farrell & Klemperer, 2007) have been partially addressed in the form of switching cost analysis. Contractual, linguistic and behavioural dimensions remain underdocumented. This study aims to address these gaps through a systematic analysis of publicly available contractual documents.

1.2 Methodology

The analysis rests on the comparative examination of 47 versions of contractual documents published by AWS, Google Cloud and Microsoft Azure over the period 2022–2026, including General Terms of Service, Product Terms, Data Processing Agreements (DPAs), Service Level Agreements (SLAs), and specific addenda (Data Act Addendum, UK Switching Addendum, EES, MOSA). Documents were collected in French, English and German where available.

◆ CORPUS

47 contractual documents · 3 hyperscalers · 3 languages (FR/EN/DE) · Period 2022–2026 · Including: 19 ToS versions · 14 Product Terms · 8 DPAs/SLAs · 6 specific addenda. Full corpus in Annex A.

◆ METHOD

Normalised textual diff (section by section) + manual legal review of substantive modifications. Confrontation against French law (Civil Code, Loi Toubon), German law (BGB, GWB), UK law (UCTA 1977, CRA 2015, CA 1998) and EU law (Data Act, GDPR). Methodology detailed in Annex D.

1.3 Scope and limitations

The analysis covers exclusively publicly available standard contractual documents. Individually negotiated contracts (Enterprise Agreements, sector-specific agreements) may differ significantly. Microsoft Azure's monthly modification of Product Terms — documented at 608 occurrences between January and June 2026 — creates documentary instability that limits the temporal scope of conclusions. Results should be read as an analysis of the standard public conditions applicable to the majority of non-negotiating clients, not as an exhaustive description of all possible contractual configurations.

1.4 Structure

Section 2 presents the six-layer taxonomy. Section 3 analyses the linguistic substitution mechanism. Section 4 models the temporal dimension of lock-in. Section 5 examines competition law implications. Section 6 sets out research and regulatory proposals. Annexes A–D reproduce the primary data underlying the analysis in full.

¹ Synergy Research Group, "Cloud Market Share Q1 2026", published April 2026.
² Armbrust M. et al., "A View of Cloud Computing", Communications of the ACM, 53(4), 2010, pp. 50–58.
³ Farrell J. & Klemperer P., "Coordination and Lock-In: Competition with Switching Costs and Network Effects", Handbook of Industrial Organization, Vol. 3, Elsevier, 2007.
⁴ Opara-Martins J. et al., "Critical analysis of vendor lock-in and its impact on cloud computing migration", JCSA, 5(4), 2016.
IUS
SECTION 2 · A SIX-LAYER TAXONOMY OF LOCK-IN MECHANISMS
2. TAXONOMY — FROM VISIBLE TO ENTRENCHED
2.1 Positioning within existing literature

The classical definition of vendor lock-in (Shapiro & Varian, 1999⁵) is grounded in switching costs — the costs incurred when transitioning from one supplier to another. Porter (1980)⁶ distinguishes barriers-to-exit (retaining the customer in the relationship) from barriers-to-entry (preventing a competitor from entering). Farrell & Klemperer (2007) provide the most comprehensive treatment of switching costs in platform economics, identifying installed-base effects, learning costs and contractual switching costs as the primary categories.

The taxonomy proposed here extends these frameworks by identifying three additional layers — behavioural (Skills, Layer 4), decisional (Demand, Layer 5) and cognitive (Layer 6) — which are absent from existing cloud lock-in literature and which, empirically, may be the most durable obstacles to supplier switching in mature cloud deployments.

2.2 The six layers — formal definitions
◆ LAYER 1 · CONTRACTUAL LOCK-INSURFACE · VISIBLE WITH CAREFUL READING

Definition: contractual provisions that create an asymmetry of rights between supplier and client, making termination costly, complex or legally uncertain. Documented mechanisms: (a) linguistic substitution clause — the client-language version is declared "informational only" while the English version "prevails"; (b) selective non-cancellability — certain commitments survive termination of the master agreement (AWS s.5.4.2; Azure EES Savings Plans); (c) automatic unilateral modification — Product Terms may be modified without individual notice (Azure: 608 modifications Jan.–Jun. 2026); (d) cascade incorporation by reference — the most constraining clause is systematically located several layers below the signed document.

◆ LAYER 2 · PRICING LOCK-INSUB-SURFACE · ABSENT FROM CONTRACT AT SIGNING

Definition: pricing structure creating an asymmetry between entry cost (zero or negative: onboarding credits) and exit cost (positive and growing with data volume). Documented mechanisms: egress fees ($0.07–0.12/GB to the Internet depending on provider and region); early termination charges (Azure: 12% of residual commitment + $50,000/yr cap); absence of contractual caps on egress fees in public Terms of Service.

◆ LAYERS 3–6 · SUMMARYMID-DEPTH TO BEDROCK

Layer 3 — Technical: proprietary APIs without standardised equivalent (e.g. BigQuery SQL dialect) · managed services without native portability · superlinear effect: migration cost of n interconnected services > n × cost of migrating one. Layer 4 — Skills (original concept): subsidised proprietary certification programmes creating professional attachment bias; passive resistance from middle management as an unconscious sabotage vector in migration projects. Layer 5 — Demand (original concept): business units formulate their needs as named products ("Azure OpenAI") rather than as functional requirements, closing competitive evaluation before technical assessment begins. Layer 6 — Cognitive (original concept): after 3–5 years of use, organisational KPIs are defined within the supplier's console; any migration implies the loss of the historical performance benchmark.

⁵ Shapiro C. & Varian H.R., Information Rules: A Strategic Guide to the Network Economy, Harvard Business School Press, 1999.
⁶ Porter M., Competitive Strategy: Techniques for Analyzing Industries and Competitors, Free Press, 1980.
⁷ Petcu D., "Portability and Interoperability between Cloud Providers: Challenges and Case Study", Towards a Service-Based Internet, LNCS 8135, Springer, 2013.
IUS
SECTION 3 · THE LINGUISTIC DIMENSION — A SPECIFICALLY IDENTIFIED MECHANISM
3. LINGUISTIC SUBSTITUTION AS A VECTOR FOR RIGHTS WAIVER
3.1 Description of the mechanism

All three hyperscalers publish their Terms of Service in multiple languages while stipulating that the English version "prevails" or "governs" in case of divergence. This mechanism, ostensibly a practical translation disclaimer, produces three distinct legal effects: (a) it deprives the client of certainty that the version in their own language is binding on the supplier; (b) it allows the supplier to publish updates in English without awaiting translation into other languages, creating temporal gaps during which the client operates under an outdated version; (c) in the most significant cases documented, it allows clauses waiving statutory legal rights to be included in the English-only version, absent from the client-language version.

This mechanism is rendered legally significant by mandatory language legislation applicable in several EU jurisdictions. In France, the Loi Toubon (Law n°94-665 of 4 August 1994)⁸ requires that contracts concluded with French legal entities for activities conducted in France be drafted in French, the French version being legally binding. A contractual clause declaring the English version to prevail is contrary to this mandatory provision and is therefore void ab initio under French law, without any requirement for the client to have challenged it at signing.

3.2 Measured translation delays — primary data
Provider
Linguistic strategy
FR delay
DE delay
Missing updates
AWS
Explicit clause "EN prevails" in header of each page
37 days
37 days
Variable per version
GCP
Concealed clause s.14.18 · FR version frozen Aug. 2023
2 yrs 9 mths
4 years
FR: 13 · DE: 16
Azure EES
Self-admitted: "Published Feb 1 EN, translated Feb 9"
8 days (admitted)
8 days (admitted)
Capacity Blocks Jun. 2026: 0 days
3.3 Documented case — waiver of Directive 2018/1972 rights (Azure EES)
◆ RIGHTS WAIVER CLAUSE — ABSENT FROM FRENCH VERSIONMOST SIGNIFICANT CASE DOCUMENTED

The Microsoft EES Product Terms (January and June 2026, English versions) contain the following clause, absent from the French version:

"Customer agrees to waive any and all entitlements that would otherwise be applicable under the European Electronic Communications Code (Directive 2018/1972) Article 102 paragraphs 1, 3, and 5 ; Article 105 paragraph 1 ; and Article 107 paragraphs 1 and 3."

The EES is the standard contractual vehicle through which public institutions — including educational bodies — subscribe to Microsoft services under public procurement frameworks. Any organisation operating under EES terms is potentially bound by this waiver. The waiver of statutory rights derived from a public-order European directive — effected contractually and presented in a single language — raises, under the analysis conducted, issues of compliance with: the French Loi Toubon art. 5; the French Civil Code art. 1171 (significant imbalance in standard-form contracts); and Directive 2018/1972 itself, whose provisions are mandatory in nature and cannot be validly waived by private contract.

3.4 Regulatory implications

Beyond French mandatory language law, the EU Data Act art. 23 requires that contractual terms be provided in a manner that is "easy to read, understand and accessible". The structural coexistence of an "informational" client-language version and a legally binding English version directly contradicts this accessibility requirement. In German law, BGB §305c provides that terms which, in the circumstances, a contracting party could not reasonably expect, are not incorporated into the contract — a provision directly applicable to clauses present only in the English version of a contract signed by a German entity.

⁸ Loi n°94-665 du 4 août 1994 relative à l'emploi de la langue française (Loi Toubon), art. 5. English translation: "Any document containing obligations for a natural or legal person in the context of the performance of a public service mission must be drafted in French."
⁹ Directive (EU) 2018/1972 of 11 December 2018, establishing the European Electronic Communications Code, OJ L 321, 17 December 2018.
¹⁰ Regulation (EU) 2023/2854 (Data Act), art. 23: "Data processing services contracts shall be drawn up in a clear and comprehensible manner."
IUS
SECTION 4 · THE TEMPORAL DIMENSION — A THREE-PHASE MODEL
4. PROGRESSIVE DEEPENING OF LOCK-IN OVER TIME
4.1 Accumulation model — three phases

Cloud lock-in does not crystallise at the moment of signing but deepens progressively through use. We propose a three-phase model, calibrated on medium-sized organisations (100–1,000 employees, cloud spend $200k–$2M/year):

◆ PHASE 1 · ADOPTION (YEAR 1) — Estimated lock-in score: 2/10ACTION WINDOW OPEN

Contractual commitments are typically short (pay-as-you-go or 1-year Reserved Instances). Data volumes are limited, rendering egress fees immaterial. The number of proprietary services adopted is low (2–3), and migration remains technically feasible in a matter of weeks. Teams are in the process of obtaining certifications — the attachment bias is not yet established. Business units have not yet entrenched the pattern of named-product requests. Recommendation: this is the only phase in which a preventive architectural decision (open stack, API abstraction) can be made at negligible migration cost.

◆ PHASE 2 · DEPENDENCY (YEAR 3) — Estimated lock-in score: 7/10CRITICAL INFLECTION POINT

Three-year Savings Plans and active Capacity Blocks create non-cancellable financial exposure. Data volumes have typically multiplied fivefold, rendering egress fees a six-figure item for mid-sized organisations. Between 8 and 12 proprietary services are interconnected, activating the superlinear technical lock-in effect. Teams hold multiple certification levels — passive resistance from middle management is now observable as a migration inhibitor. Migration remains plannable but costly (6–18 months, significant budget).

◆ PHASE 3 · CAPTIVITY (YEAR 5) — Estimated lock-in score: 9/10ECONOMIC POINT OF NO RETURN

Automatic contract renewal has incorporated terms unknown at the time of initial signing (Product Terms modified 60 times over 5 years for Azure). Egress costs exceed the annual IT budget of a mid-sized organisation. The entire architecture is built around proprietary managed services, making a full rewrite an 18–24 month project. Senior engineers have 5 years of exclusive platform experience — their probable departure in the event of a forced migration constitutes a documented HR risk. The cognitive layer is fully established: organisations can no longer define their requirements or measure their performance independently of the supplier's ecosystem.

4.2 The economic point of no return — formalisation

We define the economic point of no return (PNR) as the moment at which the total migration cost C_m exceeds the net present value of migration benefits B_m over the remaining commitment period. Formally: PNR = {t | C_m(t) > B_m(t)}, where C_m(t) = Σ(egress fees + residual commitments + refactoring + double-run + retraining) and B_m(t) = monthly post-migration savings × residual duration. Empirically, for organisations with more than 36 months of primary-hyperscaler tenure and active commitments, this ratio consistently exceeds 48 months — making migration economically unviable absent an external regulatory or strategic constraint.

This formalisation extends the "lock-in value" concept introduced by Shapiro & Varian (1999, op. cit.) to the specific structure of hyperscaler cloud contracts, where the asymmetry between entry cost (zero) and exit cost (positive and volume-dependent) systematically accelerates PNR as a function of data accumulation.

¹¹ Lock-in scores are indicative estimates constructed from the weighted aggregation of six layers. They are intended as a communication tool, not a scientifically validated measurement.
¹² The PNR formalisation is original. It operationalises Shapiro & Varian's (1999) lock-in value concept in the hyperscaler cloud contract context.
IUS
SECTION 5 · COMPETITION LAW IMPLICATIONS & REGULATORY RESPONSES
5. COMPETITION LAW & COMPARATIVE REGULATORY RESPONSES
5.1 Market concentration and abuse of dominance

AWS, Azure and GCP jointly account for 67% of the global IaaS/PaaS cloud market (Synergy Research Group, Q1 2026). This concentration exceeds the collective dominance threshold established in EU case law (CJEU, United Brands v Commission, 1978¹³). The Digital Markets Act (DMA, Regulation (EU) 2022/1925) has designated both Microsoft and Alphabet as gatekeepers, though its provisions address market access rather than contractual retention mechanisms specifically. The EU Data Act (2023/2854) represents the most directly applicable instrument, specifically targeting obstacles to cloud switching in Articles 23–25.

In UK competition law, the Competition Act 1998 section 18 prohibits the abuse of a dominant position. The CMA's 2023 Cloud Market Study explicitly identified switching barriers as a primary competition concern, concluding that "the combination of technical barriers, egress fees and contract terms can make switching or multi-clouding excessively difficult"¹⁴. No formal enforcement action has followed from this finding at the date of this paper.

5.2 The EU Data Act as partial regulatory response
◆ WHAT THE DATA ACT COVERSIN FORCE SINCE SEPT. 2025

Art. 23: accessibility and comprehensibility of contractual terms — directly applicable to linguistic substitution clauses. Art. 25: unenforceability of terms that create obstacles to switching cloud providers — applicable to non-cancellability clauses and disproportionate termination fees. Art. 25(2): data portability obligations — applicable to proprietary formats.

◆ IDENTIFIED GAPSPOLICY LACUNAE

Layer 2 — Pricing: egress fees as a pricing-based switching obstacle are not explicitly covered — Art. 25 targets contractual clauses, not tariff structures. Layers 4–6: behavioural, decisional and cognitive obstacles fall outside the scope of the text. Competent authorities: no EU Member State had formally designated its Data Act competent authority as of 1 June 2026.

5.3 Comparative regulatory responses — FR · DE · UK
Regulator
Available instrument
Formal proceedings
Assessment
DGCCRF (FR)
Commercial Code L.442-1 · Consumer Code L.212-1
None public as of 01/06/26
Solid instrument · underused
Bundeskartellamt (DE)
GWB §19a · §19 · Active designations (Amazon 2022 · Microsoft 2023)
Active designations
Most powerful available instrument
CMA (UK)
Competition Act 1998 s.18 · Cloud Market Study 2023
Study published · no formal proceedings
Diagnosis made · follow-up insufficient
5.4 Cognitive lock-in as a cross-cutting regulatory gap

Layer 6 (cognitive lock-in) falls outside all existing regulatory frameworks. It involves no clause to challenge, no anticompetitive behaviour in the classical sense, and no obstacle to portability in the technical meaning of the Data Act. Yet it may represent the most durable barrier to competition in mature cloud markets — because it operates on organisations' capacity to conceive and evaluate alternatives. After five years of primary-hyperscaler dependency, an organisation's performance KPIs, benchmarking criteria and team evaluation frameworks are defined within the supplier's console. A migration implies not merely technical and financial costs but the loss of the organisation's own measurement standard. This observation suggests that an effective regulatory response to cloud lock-in must ultimately address organisational dependency beyond the contractual and technical dimensions currently covered by existing instruments. The UK case Streetmap.EU Ltd v Google Inc [2016]¹⁵ offers a precedent for competition law engaging with the cognitive dimensions of market dominance — though the context (search default settings) differs from the cloud dependency analysed here.

¹³ CJEU, United Brands v Commission, 14 February 1978, Case 27/76, ECR 1978, p. 207.
¹⁴ CMA, "Cloud Services Market Study — Final Report", January 2023, para. 4.58, available at gov.uk/cma.
¹⁵ Streetmap.EU Ltd v Google Inc & Ors [2016] EWHC 253 (Ch), para. 112 (Roth J.).
IUS
SECTION 6 · RESEARCH PROPOSALS & REGULATORY RECOMMENDATIONS
6. PROPOSALS — RESEARCH · POLICY · PRACTICE
6.1 Gaps in the existing literature

A review of the cloud vendor lock-in literature (Opara-Martins et al., 2016; Petcu, 2013; Armbrust et al., 2010; Farrell & Klemperer, 2007) confirms that Layers 1 to 3 of the proposed taxonomy are partially documented — primarily from a technical perspective and, to a lesser extent, an economic one. Layers 4 (Skills Lock-in), 5 (Demand Lock-in) and 6 (Cognitive Lock-in) are, to the author's knowledge, absent from the formalised academic literature on cloud computing. The linguistic substitution mechanism — the substitution of the client-language version by an English-only version declared legally binding — is not documented in any of the reviewed works. These gaps represent research opportunities of both academic and policy significance.

6.2 Research agenda
◆ EMPIRICAL RESEARCH

Empirical measurement of the economic point of no return by sector and organisation size. Longitudinal cohort study of skills evolution in organisations post-migration (3-year horizon). Comparative analysis of cloud contractual clauses over 10 years (2015–2025) to document temporal evolution of retention mechanisms. Measurement of the correlation between primary-hyperscaler tenure and capacity for functional requirement reformulation (test of Layer 6).

◆ LEGAL RESEARCH

Analysis of case law on linguistic substitution clauses in cross-border B2B contracts. Comparative study of regimes governing waiver of mandatory EU law rights by private contract. Qualification of cognitive lock-in (Layer 6) within existing competition law frameworks. Applicability of Data Act art. 25 to pricing-based switching obstacles (egress fees) — a question of direct practical significance not yet resolved by the regulatory text or its guidance documents.

6.3 Regulatory proposals
◆ FOUR PROPOSALS FOR REGULATORY FRAMEWORK EXTENSIONPOLICY

Proposal 1 — Extension of Data Act art. 25 to pricing-based switching obstacles: the current wording of art. 25 targets contractual clauses that impede switching. An explicit extension to pricing structures creating a disproportionate economic obstacle (egress fees) — via delegated act or interpretative guidance — would cover Layer 2 of the taxonomy, currently outside scope. The Commission's forthcoming review of the Data Act implementation (expected 2027) provides a procedural vehicle for this extension.

Proposal 2 — Simultaneous multi-language publication obligation: require cloud service providers to publish their Terms of Service simultaneously in all EU official languages in which they actively market their services, with updates in non-English languages published within 5 business days of the English version, failing which the update is unenforceable in the relevant Member State(s). This measure addresses the structural temporal gap documented in Section 3.

Proposal 3 — Individual notification obligation for material modifications: require individual notification by documented electronic means for any material modification to Product Terms, with a minimum 60-day notice period and a right to terminate without penalty in response to a material modification. The absence of individual notification is one of the most significant gaps in the current cloud contractual framework.

Proposal 4 — Formal designation of Data Act competent authorities: no EU Member State had formally designated its Data Act competent authority as of 1 June 2026, eighteen months after the regulation's adoption and nine months after its applicability date. This implementation gap deprives organisations of any effective administrative remedy under the regulation and should be addressed as a matter of urgency by each Member State.

6.4 Conclusion

The six-layer taxonomy presented in this working paper maps the full architecture of retention mechanisms operating in hyperscaler cloud contracts. It reveals that the most durable mechanisms — Layers 5 and 6 — are precisely those which are least visible, least legally contestable, and least covered by existing regulatory frameworks. An effective regulatory response to cloud vendor lock-in cannot be complete without a theory of organisational digital dependency that integrates these behavioural and cognitive dimensions beyond the contractual and technical obstacles currently addressed by the Data Act, the DMA and national competition law instruments.

¹⁶ Regulation (EU) 2023/2854, art. 25(2): "Contractual terms [...] that prevent or restrict the right to switch to a different data processing service provider shall be deemed unenforceable."
¹⁷ The Data Act applicability date (September 2025) is subsequent to its publication (OJ June 2024) and prior to the drafting of this paper (June 2026).
IUS
REFERENCES — CHICAGO AUTHOR-DATE FORMAT
REFERENCES
Academic literature
Armbrust, Michael, Armando Fox, Rean Griffith, Anthony D. Joseph, Randy Katz, Andy Konwinski, Gunho Lee, David Patterson, Ariel Rabkin, Ion Stoica, and Matei Zaharia. 2010. "A View of Cloud Computing." Communications of the ACM 53 (4): 50–58.
Barthélemy, Jérôme. 2003. "The Seven Deadly Sins of Outsourcing." Academy of Management Executive 17 (2): 87–100.
Farrell, Joseph, and Paul Klemperer. 2007. "Coordination and Lock-In: Competition with Switching Costs and Network Effects." In Handbook of Industrial Organization, vol. 3, edited by Mark Armstrong and Robert Porter, 1967–2072. Amsterdam: Elsevier.
Lacity, Mary C., and Leslie P. Willcocks. 1998. "An Empirical Investigation of Information Technology Sourcing Practices: Lessons from Experience." MIS Quarterly 22 (3): 363–408.
Opara-Martins, Justice, Reza Sahandi, and Feng Tian. 2016. "Critical Analysis of Vendor Lock-In and Its Impact on Cloud Computing Migration: A Business Perspective." Journal of Cloud Computing: Advances, Systems and Applications 5 (4).
Petcu, Dana. 2013. "Portability and Interoperability between Cloud Providers: Challenges and Case Study." In Towards a Service-Based Internet, Lecture Notes in Computer Science 8135. Berlin: Springer.
Porter, Michael E. 1980. Competitive Strategy: Techniques for Analyzing Industries and Competitors. New York: Free Press.
Shapiro, Carl, and Hal R. Varian. 1999. Information Rules: A Strategic Guide to the Network Economy. Boston: Harvard Business School Press.
Legislation and regulatory instruments
European Parliament and Council. 2023. Regulation (EU) 2023/2854 on harmonised rules on fair access to and use of data (Data Act). OJ L 143, 11 June 2024.
European Parliament and Council. 2022. Regulation (EU) 2022/1925 on contestable and fair markets in the digital sector (Digital Markets Act). OJ L 265, 12 October 2022.
European Parliament and Council. 2018. Directive (EU) 2018/1972 establishing the European Electronic Communications Code. OJ L 321, 17 December 2018.
France. 1994. Loi n°94-665 du 4 août 1994 relative à l'emploi de la langue française (Loi Toubon). JORF n°0180, 5 August 1994.
Germany. Gesetz gegen Wettbewerbsbeschränkungen (GWB), §§ 19, 19a. Version in force 1 June 2026.
United Kingdom. Unfair Contract Terms Act 1977 (UCTA), ss. 2–3. Consumer Rights Act 2015 (CRA), ss. 62–65. Competition Act 1998, s. 18.
Case law
CJEU. 1978. United Brands v Commission, Case 27/76, ECR 1978, p. 207. 14 February 1978.
UK High Court (Ch). 2016. Streetmap.EU Ltd v Google Inc & Ors [2016] EWHC 253 (Ch). Roth J.
Institutional reports
Bundeskartellamt. 2022. Proceeding against Amazon pursuant to §19a GWB. Decision of 5 July 2022. bundeskartellamt.de.
Bundeskartellamt. 2023. Proceeding against Microsoft pursuant to §19a GWB. Decision of 12 December 2023. bundeskartellamt.de.
Competition and Markets Authority. 2023. Cloud Services Market Study — Final Report. January 2023. gov.uk/cma.
Synergy Research Group. 2026. Cloud Market Share Q1 2026. Published April 2026.
Primary contractual documents
47 contractual documents (General Terms, Product Terms, DPAs, SLAs, Addenda) published by AWS, Google Cloud and Microsoft Azure in FR/EN/DE, collected between January 2022 and June 2026. Full corpus in Annex A. Sources: aws.amazon.com/legal/ · cloud.google.com/terms · microsoft.com/licensing
IUS
ANNEX A · FULL DOCUMENTARY CORPUS — 47 CONTRACTUAL DOCUMENTS ANALYSED
ANNEX A — PRIMARY DOCUMENTARY CORPUS
Public documents collected between January 2022 and June 2026 · Official sources of the three hyperscalers
A.1 — Amazon Web Services (16 documents)
Document
Versions analysed
Languages
Critical clauses
Layer
AWS Customer Agreement (ToS)
15 Apr. 2026 · 22 May 2026 · 1 Jun. 2026
FR · EN · DE
s.1.4 · s.5.4.2 · s.5.5
1 · 2
AWS Product Terms
Jan. 2022 → Jun. 2026
EN (only)
s.50.12.1–3 · s.50.14 · s.50.15 · s.50.17
1 · 2
AWS Data Act Addendum
Single version 2024
EN · FR
s.1.28 · portability obligations
1
AWS UK Switching Addendum
Single version 2024
EN
s.1.30 · switching facilitation
1 · 2
AWS Data Processing Addendum
2023 · 2024 · 2025
FR · EN · DE
Bedrock AI services opt-out
1
AWS SLAs (Service Level Agreements)
EC2 · S3 · RDS · EKS · Lambda
EN (only)
Liability exclusions · Force majeure
1
A.2 — Google Cloud Platform (15 documents)
Document
Versions analysed
Languages
Critical clauses
Layer
GCP Terms of Service
Aug. 2023 (FR) · Jun. 2026 (EN)
FR · EN · DE
s.14.18 · s.8.8 · s.2.6
1 · 2
GCP Service Specific Terms
2022 → 2026 (13 EN updates missing from FR)
EN (FR frozen)
BigQuery · Vertex AI · Spanner pricing
1 · 2 · 3
GCP Data Processing Addendum
2023 · 2025
FR · EN · DE
AI Opt-out · GDPR art. 28
1
GCP SLAs (8 services)
GKE · BigQuery · Cloud SQL · Cloud Run · GCS · Pub/Sub · Vertex · Compute
EN (only)
Service credit exclusions · Downtime definition
1
GCP Committed Use Contracts
1-year · 3-year · 2023–2026
EN · FR
s.8.8 · no refund on termination
1 · 2
A.3 — Microsoft Azure (16 documents)
Document
Versions analysed
Languages
Critical clauses
Layer
Microsoft Online Services Agreement (MOSA)
2019 (signed) + monthly amendments 2019–2026
FR · EN
Washington State governing law · Capacity Blocks
1
Product Terms MOSA
Jan. · Feb. · Apr. · Jun. 2026
FR · EN
608 modifications · Capacity Blocks Jun. 2026
1
Enrollment for Education Solutions (EES)
Jan. 2026 (EN/FR) · Jun. 2026 (EN/FR)
FR · EN
Waiver Dir. 2018/1972 · absent from FR version
1
Azure Savings Plans
2023 · 2024 · 2025
FR · EN
Non-cancellable · 12% early termination fee
1 · 2
Azure DPA · SLA · Offer Details
AKS · Azure SQL · Blob · OpenAI · Monitor
EN (only)
Liability exclusions · CLOUD Act exposure
1 · 3
IUS
ANNEX B · PRIMARY DATA ON LINGUISTIC SUBSTITUTION — TRANSLATION DELAYS
ANNEX B — LINGUISTIC SUBSTITUTION: PRIMARY DATA
B.1 — AWS Customer Agreement: 22 May 2026 vs 1 June 2026 — comparative analysis
This comparison is of particular relevance as it documents the only substantive legal modification between two consecutive versions — a modification that would have gone undetected without systematic monitoring.
Section
Content
22 May 2026
1 June 2026
Modification
Layer
Header
Linguistic substitution clause
Present · EN prevails
Present · EN prevails
Identical
1
s.1.4
Suspension without notice
Present
Present
Identical
1
s.1.24
Bedrock AI services list
"Amazon Quick Suite (incl. QuickSight)"
"Amazon Quick"
Label simplified
1
s.5.4.2
Savings Plans noncancellable
Present
Present
Identical
1 · 2
s.5.5
Capacity Blocks nonrefundable
Present
Present
Identical
1 · 2
s.50.12.2
Bedrock abuse detection
"automated abuse detection mechanisms"
"store inputs/outputs 30 days" + "human review" option
MODIFIED — substance
1
s.50.17
Amazon Quick
Absent
Present · capacity pricing mandatory for automation
NEW SECTION
1 · 2
s.1.28
Data Act Addendum
Present
Present
Identical
1
s.1.30
UK Switching Addendum
Present
Present
Identical
1 · 2
B.2 — GCP Terms of Service: FR vs EN translation delays (2022–2026)
Language
Last substantive update
Equivalent EN version
Delay
Missing EN updates
French (FR)
August 2023
June 2026
2 years 9 months
13 updates
German (DE)
June 2022
June 2026
4 years
16 updates
B.3 — Azure EES: translation delays self-admitted by Microsoft (2026)
Version
Published EN
Published FR
Delay
Self-admitted source
EES Jan. 2026
1 February 2026
9 February 2026
8 days
EES document: "Published February 1, 2026 in English, translated February 9, 2026"
EES Jun. 2026
1 June 2026
~9 June 2026 (estimated)
~8 days
Admitted in Jun. 2026 EES document
Dir. 2018/1972 waiver
Present EN Jan. + Jun. 2026
Absent FR Jan. + Jun. 2026
Not translated
Clause not present in FR version at either date
Note: Publication dates are extracted from metadata and internal mentions within the contractual documents themselves. The algorithmic diff methodology used to compare versions is described in Annex D.
IUS
ANNEX C · ORGANISATIONAL DIAGNOSTIC SCORING GRID
ANNEX C — TWELVE-QUESTION LOCK-IN DIAGNOSTIC
Organisational communication tool · Not empirically validated at this stage · Proposed as a basis for future research
Q.
Layer
Diagnostic question · Yes = 2 pts · No = 0 pt
If Yes
Refer to
1a
Contractual
Do you have Savings Plans or Capacity Blocks expiring beyond 12 months?
2 pts
Guide A · Legal
1b
Contractual
Does the non-English version of your cloud ToS state that the English version prevails?
2 pts
Guide A · Legal
2a
Pricing
Have you calculated the egress cost of moving all your current data out of your primary cloud provider?
2 pts
Guide C · CFO
2b
Pricing
Do you know the early termination fee applicable to your primary cloud commitments?
2 pts
Guide C · CFO
3a
Technical
Do more than 5 services in your architecture use APIs without an S3-compatible equivalent?
2 pts
Guide B · CTO
3b
Technical
Do you have a documented dependency map showing which services use proprietary APIs?
2 pts
Guide B · CTO
4a
Skills
Do more than 50% of your cloud engineers hold a proprietary certification without an open equivalent?
2 pts
Guide E · HR
4b
Skills
Have you identified the resistance profiles within your technical teams?
2 pts
Guide E · HR
5a
Demand
Did the last 3 business requests to your IT department name a specific product (Azure OpenAI, BigQuery…)?
2 pts
Guide E · PO
5b
Demand
Do your Product Owners systematically apply the 5 sovereignty questions before validating a stack?
2 pts
Guide E · PO
6a
Cognitive
Are your IT performance KPIs defined and measured within your primary cloud provider's console?
2 pts
Guide D · All
6b
Cognitive
Would you be unable to measure IT performance during a 6-month migration?
2 pts
Guide D · All
0–6 pts
Low lock-in · Preventive action · Guide B
7–12 pts
Moderate · Guides A+B+C recommended
13–18 pts
High · Guide D · Plan migration
19–24 pts
Structural · All guides · External support
Methodological note: equal weighting of 12 questions (2 points each) is a simplification. Future research could develop differentiated weighting based on empirical measurement of actual migration costs per layer.
IUS
ANNEX D · METHODOLOGICAL NOTE — ALGORITHMIC DIFF AND MANUAL REVIEW
ANNEX D — METHODOLOGY OF CONTRACTUAL DOCUMENT COMPARISON
D.1 Document collection

Contractual documents were collected directly from the official websites of the three providers (aws.amazon.com/legal/ · cloud.google.com/terms · microsoft.com/licensing) between January 2022 and June 2026. For each provider, versions available in the three languages (FR · EN · DE) were downloaded upon each detected update, via systematic monitoring of the terms pages. Publication dates are extracted either from document metadata or from explicit internal mentions (e.g. Azure EES: "Published February 1, 2026 in English, translated February 9, 2026").

D.2 Document pre-processing

HTML documents were pre-processed in two stages: (a) text extraction by removal of HTML tags, scripts and CSS styles; (b) text normalisation by replacement of HTML entities, non-breaking spaces and typographic ligatures (e.g. fi → fi), and compression of multiple whitespace characters. This normalisation step is essential to distinguish substantive modifications from formatting changes — which represent the majority of "modifications" detected by a raw HTML diff. All differences identified as substantive were independently confirmed in the original documents to exclude normalisation artefacts.

D.3 Algorithmic comparison

Comparison between versions was conducted using normalised textual diff, section by section (each section identified by its number: s.1.4, s.5.5, s.50.12.2, etc.). For each pair of sections (version X vs version Y), normalised Levenshtein distance was computed to flag substantive modifications. Section pairs exhibiting greater than 95% similarity after normalisation were classified as "identical in substance" — residual typographic and formatting artefacts not constituting legally significant modifications.

D.4 Manual legal review

All modifications identified as substantive by the algorithm were subject to manual review to: (a) confirm that the difference constitutes a legally significant modification and not a normalisation artefact; (b) characterise the nature of the modification (addition · deletion · reformulation · change in scope); (c) identify the relevant lock-in layer under the six-layer taxonomy. The results of this manual review are reproduced in Annex B for linguistic comparisons and in the corpus of 19 individual legal analyses of which this study constitutes the synthesis.

D.5 Identified methodological limitations
◆ THREE LIMITATIONS EXPLICITLY ACKNOWLEDGED

Limitation 1 — Documentary instability: Azure's monthly modification of Product Terms (608 occurrences over 6 months) creates a moving corpus that is difficult to stabilise for longitudinal analysis. Conclusions on Azure modifications refer to the snapshots collected at the stated dates and may not reflect the state of the document on an intermediate date.

Limitation 2 — Non-public documents: Enterprise Agreements and individually negotiated contracts, which may contain significantly different clauses from the public standard terms, are excluded from the analysis. The study covers exclusively conditions applicable to the majority of non-negotiating clients.

Limitation 3 — Legal qualification: the legal characterisation of analysed clauses (voidness, significant imbalance, violation of mandatory law) rests on the author's independent analysis and not on a court decision or formal legal opinion. These qualifications should be verified by a qualified legal practitioner before any action is taken.

This working paper is based on the independent analysis of publicly available contractual documents.
It does not constitute legal advice. The author has no affiliation with any of the companies or institutions mentioned.
Nemo supra legem est · Summum ius, summa iniuria — Cicero
Public document · CC BY-NC-SA 4.0
AI Powered by Amine — AI is an amplifier of ideas and forms, not the source.