Multi-cloud in risk-averse environments

Multi-cloud often starts as a procurement hedge and becomes an operating tax. Two landing zones, two IAM models, two backup tools — and a risk team that now has twice the evidence to collect.

A better pattern: one primary cloud for commodity workloads, a second only where there is a hard constraint (data residency, a vendor’s SaaS, or a genuine concentration limit from the board). Shared control plane for identity and logging. Explicit exit notes, not a fantasy of bursting overnight.

If your team cannot operate one cloud well, adding another will not make you resilient. It will make incidents harder to narrate.