Sustainability reporting has arrived on the data team's desk, and it arrived the way these things usually do: as a request from above to "get us the numbers," with an assumption that the numbers exist and are easy. Microsoft has been building tooling to help — sustainability data solutions, capacity-level energy and carbon reporting — and I've spent enough time in it now to give you the honest map. Which is more useful than the enthusiastic one, because the enthusiastic one will get you into trouble when someone acts on a number you oversold.

So: what can you actually track right now, and — the part nobody wants to say out loud — what can't you, and why does pretending otherwise matter.

What you genuinely can track

The tooling is real and some of it is genuinely good. As of this spring, the things you can honestly put a number on include:

  • The energy and estimated carbon of your own Microsoft cloud footprint. Microsoft can give you estimates of the energy consumption and associated emissions of your Azure and Fabric usage. For a data team asked "what's the environmental cost of our platform," that's a real, defensible starting figure — and, pleasingly, it overlaps almost entirely with the cost-efficiency work you should be doing anyway.
  • The link between waste and footprint. This is the part I find genuinely motivating: the same inefficiencies that inflate your bill — the duplicated models, the over-frequent refreshes, the pipelines reprocessing everything nightly — also inflate your energy use. Reducing them shows up in both ledgers. Sustainability and cost management turn out to be the same optimisation with two names, which makes the sustainability work far easier to fund.
  • Structured environmental data, governed like everything else. Where the tooling shines is giving environmental and emissions data a home in the same governed estate as the rest of your data — catalogued, lineage-tracked, reportable — rather than living in a spreadsheet on someone's laptop. That's a real maturity step for ESG reporting.

That's a solid, honest capability set. If someone asks "can we measure and report the footprint of our data platform, governed properly," the answer is genuinely yes.

What you can't — and must not pretend you can

Now the harder half, which I care about more because getting it wrong isn't just embarrassing, it's a responsible-tech failure with a compliance tail.

  • This is not full corporate carbon accounting. The energy figures for your cloud usage are one slice of one scope of your organisation's actual emissions. The full picture — especially Scope 3, the sprawling emissions of your supply chain and the products you buy and sell — is a vastly bigger, messier accounting problem that no data-platform dashboard solves. If leadership hears "we can track our emissions" and thinks the whole corporate footprint is now handled, you've created a dangerous false confidence.
  • Estimates are estimates, and the label matters. Much of what you get is modelled — reasonable, useful, but not metered-at-the-wall precision. That's fine, as long as it's labelled honestly. The failure mode is an estimate hardening into a "fact" as it travels up the reporting chain, until it's being quoted to regulators or in public disclosures with a confidence the underlying method never had.
  • A number you can produce is not a number you should publish. This is the responsible-tech crux. Environmental claims carry real legal and reputational weight now — greenwashing is a regulated concern, not just a PR one. A figure that's perfectly good for internal optimisation ("are we getting more efficient quarter on quarter?") may be nowhere near robust enough for external disclosure. Knowing the difference, and refusing to let an internal estimate become an external claim, is part of the job.
The dangerous sustainability number isn't the one you can't produce. It's the rough internal estimate that quietly graduates into a public commitment because nobody flagged how it was actually calculated.

How to handle the request responsibly

So when the "get us the sustainability numbers" request lands, the responsible response isn't to rush out a dashboard. It's to scope honestly: use the tooling for what it's genuinely good at — measuring and reducing the footprint of your own platform, tied to the cost work you're already doing — and be scrupulously clear about the boundary. State plainly what's measured versus estimated, what's covered versus out of scope, and draw a bright line between numbers fit for internal improvement and numbers fit for external reporting. That last line is one to hold firmly, even when someone senior would prefer it blurred, because it's the line between honest measurement and accidental greenwashing.

The verdict

Microsoft's sustainability tooling is a genuine, welcome capability, and I'd encourage any data team to use it — starting with the framing that your platform's footprint and your platform's waste are the same problem, which makes this the rare sustainability initiative that pays for itself. Track your energy, cut your waste, report your progress internally with confidence.

Just don't let "we can track our platform's footprint" become "we've got our emissions covered," and never let an internal estimate walk out the door as a public claim without the scrutiny public claims deserve. In sustainability, more than most places, the honest small number is worth far more than the impressive big one — because the impressive big one is the one that gets you in trouble when someone checks. Measure what you can, say clearly what you can't, and let the integrity of the number matter more than its size.