Integration DepthWide moat

Integration depth is where the abstraction of a 'switching cost' turns into a wall you can feel. A large enterprise does not merely use Microsoft's programs side by side; it has wired them into custom applications, automated reports, security policies, compliance workflows, and the daily muscle memory of tens of thousands of employees. A spreadsheet feeds a macro that feeds a database that feeds a report an executive reads every Monday — and every link in that chain silently assumes Microsoft.

What makes this so binding is that no one person understands the whole. The integrations accumulated over years, built by employees long since departed and documented nowhere completely. To migrate is to risk breaking connections no one remembers building, inside systems no one fully maps — a prospect that turns even an eager reformer cautious.

The depth also means the switching cost is not one decision but ten thousand small ones, each carrying its own risk of something quietly breaking. The migration that looks feasible on a slide dissolves, on contact with the actual tangle, into a multi-year project with a hundred ways to go wrong and no obvious upside for the executive who would have to champion it.

For the owner this is the most reassuring kind of moat, because it grows on its own and defends itself. Every new integration a customer builds is another strand Microsoft did not have to spend a dollar to create, and another reason the migration stays forever postponed to a someday that never quite arrives — Entra identity alone wires sign-on into nearly everything an enterprise runs¹.