Microsoft almost leaked all of Azure Cosmos DB's secrets

A routine code review caught Microsoft nearly publishing the full source for Azure Cosmos DB — the database that quietly powers a huge chunk of the cloud. The keys stayed in the vault, but the scare made people sit up: one slip and the whole thing would have gone open.

Cosmos DB is Microsoft's answer to NoSQL at scale, and it's been in the cloud since 2014. It handles document, key-value, graph, and column-family workloads from a single service, and it's been the engine behind everything from Teams to Azure Functions. When a database that big goes open, it changes the competitive math — competitors can read the wiring and build against the same patterns.

The fix was surgical: a small diff that removed the offending files before the release window closed. No outage, no fanfare, just the quiet relief of catching a leak before it becomes a flood.

Why this matters for us: databases like this are the plumbing under the apps la gente use every day. When Microsoft's open source gets right, it's a win for everyone building on top. When it leaks, it's a reminder that the code is always one commit away from being free.