Data GravityWide moat

Data gravity is the quiet, relentless force by which years of accumulated documents, emails, and records pull everything around them into Microsoft's orbit. Data, once it settles somewhere, exerts a pull: the new tool a company buys must work with where its data already lives, and where the data lives, for most enterprises, is inside Microsoft's applications and storage — the mailboxes, the SharePoint sites, the OneDrive folders, the databases that have filled up over a decade.

The force compounds because every new integration deepens it. A company connects an analytics tool to its Microsoft data, then a reporting tool, then a workflow automation, and each connection quietly assumes the data stays where it is. The mass at the center grows, and its gravitational pull grows with it, until moving the data would mean rebuilding every one of those connections at the same time.

Measured eventually in the petabytes, the sheer physical cost of moving becomes its own deterrent — the transfer time, the egress fees, the risk of something breaking in transit — but the deeper cost is the web of dependencies, the thousand workflows that assume the data is exactly where it has always been. The files are heavy, but the wiring around them is heavier.

For the owner, data gravity is the most patient of moats: it requires no cleverness to maintain, only time. Every day a customer uses Microsoft's products, a little more data settles into the well, and the well grows a little deeper, and leaving grows a little harder — automatically, silently, without Microsoft lifting a finger to make it so — across a Microsoft Cloud that took $214.4 billion last year, nearly double what it took three years earlier¹.