# Cloud Vendor Lock-In Risks

> Chapter 54 of the Courseiva AZ-900 curriculum — https://courseiva.com/learn/az-900/vendor-lock-in

**Official objective:** 1.5 — Cloud Concepts

## Introduction

This chapter covers vendor lock-in risks. AZ-900 tests under 1.5.

## Getting Stuck With One Vendor

Choosing a proprietary system that only one vendor supports makes it hard to switch later. Vendor lock-in is a similar risk with cloud providers.

## Core explanation

Vendor lock-in occurs when switching from one cloud is difficult due to proprietary services or data formats. Risks include dependency and inflexible pricing.

## Real-world context

A company uses only managed Azure services with no equivalent elsewhere; switching later would be difficult.

## Exam focus

Objective 1.5 expects awareness of lock-in risks.

## Step by step

1. **Understand proprietary services** — Services specific to one cloud increase lock-in risk.
2. **Plan for portability** — Design with portability in mind if flexibility matters.
3. **Evaluate contracts** — Contract terms affect lock-in risk.

## Key takeaways

- Proprietary services increase lock-in risk.
- Portability reduces risk.
- Not always a bad choice; depends on priorities.

## FAQ

**What is vendor lock-in?**

When switching from one cloud provider is difficult due to proprietary services or data formats, making customers dependent on the provider.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/az-900/vendor-lock-in