This chapter covers vendor lock-in risks. AZ-900 tests under 1.5.
Jump to a section
A simple way to picture Cloud Vendor Lock-In Risks
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.
Vendor lock-in occurs when switching from one cloud is difficult due to proprietary services or data formats. Risks include dependency and inflexible pricing.
Understand proprietary services
Services specific to one cloud increase lock-in risk.
Plan for portability
Design with portability in mind if flexibility matters.
Evaluate contracts
Contract terms affect lock-in risk.
A company uses only managed Azure services with no equivalent elsewhere; switching later would be difficult.
Objective 1.5 expects awareness of lock-in risks.
Proprietary services increase lock-in risk.
Portability reduces risk.
Not always a bad choice; depends on priorities.
When switching from one cloud provider is difficult due to proprietary services or data formats, making customers dependent on the provider.
You've just covered Cloud Vendor Lock-In Risks — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?