⚠ The Multi-Cloud DefaultModerate threat

The cross-sell advantage assumes a company wants a single cloud vendor; the danger is that sophisticated enterprises increasingly want the opposite. Burned by past lock-in and wary of concentrating risk, many large companies now adopt a deliberate multi-cloud strategy¹ — placing some workloads on Azure, others on AWS, others on Google — precisely so that no single provider can hold them hostage. When multi-cloud is the stated policy, 'you already use Microsoft' stops being a reason to give Microsoft everything.

The threat is sharpest for the highest-value, most portable new workloads, where an architecture team picks the best cloud for the job rather than defaulting to the incumbent. Portable technologies like Kubernetes make spreading workloads more feasible than it once was, and a company running everywhere is a company Microsoft must keep winning rather than simply keep.

In Microsoft's favor, multi-cloud is real but expensive and complex to run — every additional cloud means another set of skills, tools, and security models — and in practice many 'multi-cloud' enterprises still concentrate the bulk of their spend with one primary provider, which for Microsoft's installed base is often Azure. The relationship and the identity system still tilt the default.

A moderate worry. Multi-cloud genuinely dilutes the 'one easy yes,' and it is now the fashionable enterprise posture — but the operational cost of true multi-cloud keeps most companies anchored to a primary vendor, and Microsoft's incumbency makes it the natural anchor for the enterprises it already serves.