Latest / The Cloud Business Podcast with Fexingo: AWS, Azure, GCP, and Enterprise Infrastructure / The Cloud Carbon Accounting Debacle Enterprises Face
Transcript
- Lucas: A $200 million enterprise customer ran a carbon audit of its cloud footprint last quarter and got three different numbers from three different cloud providers — and none of them matched. The gap was as wide as thirty percent. Luna: Wait — same workloads, same regions, same time period? Lucas: Identical. And this isn't a one-off data quality issue. It's structural. The way AWS, Azure, and Google Cloud calculate the carbon impact of the electricity powering your virtual machines is fundamentally different. And they all claim to follow the same standard. Luna: Which standard is that? Lucas: The Greenhouse Gas Protocol. It's the de facto global framework for corporate carbon accounting. But the protocol allows two different methods for reporting electricity emissions — market-based and location-based. And the cloud providers are making different choices about which one to surface as the headline number. Luna: So the methodology choice itself creates the gap. Lucas: Exactly. Location-based uses the average emission factor of the regional power grid where the data center sits. Market-based lets you use contractual instruments — like renewable energy certificates — to claim a lower carbon intensity. AWS and Azure lean heavily into market-based reporting because they've purchased massive amounts of renewables. Google Cloud does too, but they've historically claimed to match one hundred percent of their global electricity use with renewables — and they calculate that differently. Luna: So a customer running exactly the same compute on AWS versus Azure versus Google Cloud could get different carbon scores — and think one is greener — when really it's just an accounting difference. Lucas: That's the risk. And it matters because regulators are paying attention. The SEC's climate disclosure rule that came into effect earlier this year requires large public companies to report Scope 1 and Scope 2 emissions — and Scope 3 if it's material. For most enterprises, their cloud bill is a big chunk of Scope 3, which covers the value chain. If you're a CIO preparing that report, you need consistent data across your providers. Luna: But the providers don't make it easy to get comparable numbers. Let's talk about what each one actually does. Lucas: AWS publishes a Customer Carbon Footprint Tool. It shows estimated emissions based on usage, and it uses a combination of location-based and market-based factors — but they don't fully transparency on how they blend them. Amazon also purchases renewable energy to match its global electricity use, but they report on an annual basis, not hourly, which means there can be hours where a data center runs on grid power with a dirty fuel mix, but the annual average looks clean. Luna: Azure's approach is similar but not identical. Microsoft has been buying renewable energy for over a decade, and they report emissions using a market-based approach that includes renewable energy certificates. But here's the thing: Microsoft also reports location-based numbers in its own sustainability report — but the Azure customer tool only shows the market-based number. Lucas: Right. So a customer can't see the location-based figure unless they dig into Microsoft's corporate disclosures. And Google Cloud — they've been carbon neutral since 2007, but they also claim to operate on one hundred percent renewable energy. Their methodology is different: they use hourly matching in some regions, meaning they try to match each hour of consumption with renewable generation. That's more accurate than annual matching, but it's not universal across all their regions. Luna: So the customer is stuck comparing apples to oranges — or maybe apples to slightly different apples. Lucas: And it gets worse. The underlying emission factors — the amount of carbon per kilowatt-hour — come from different databases. AWS uses the EPA's eGRID for US regions. Azure uses a mix of eGRID and the International Energy Agency data. Google Cloud uses its own model. So even if two providers used the same methodology, the input data could differ. Luna: It reminds me of a conversation I had with a sustainability officer at a large retailer. She said her team spent three months trying to reconcile the cloud carbon numbers across their three providers. Eventually they just picked one methodology and forced all the providers to report that way — but the providers wouldn't give them the raw data to do it. Lucas: That's the core problem: the data isn't portable. And as enterprises move toward multi-cloud strategies, they need a unified view. Some startups are trying to solve this — companies like Carbon Relay and Greenpixie offer cloud carbon management platforms that sit on top of the providers and try to normalize the data. But they rely on the same provider APIs that expose these calculated numbers — they can't change the underlying methodology. Luna: So what's the practical takeaway for a procurement team signing a cloud contract today? Should they demand specific carbon reporting language? Lucas: Absolutely. If you're a large enterprise, you should ask for location-based emissions data in your contract. Not just the market-based number. You should also ask for hourly granularity if possible — or at least daily. And you should request the methodology documentation up front. Some providers will push back because they don't want to expose the less flattering location-based number, but if you're a big enough customer, you have leverage. Luna: And for the rest of us who aren't negotiating billion-dollar deals? Lucas: Start by looking at the carbon footprint tools each provider offers. Compare them for the same workload — run a test. You'll likely see discrepancies. Then decide which provider's methodology aligns best with your own reporting requirements. If your investors or regulators want location-based, don't settle for a market-based number that makes you look greener than you are. Luna: One thing that's been on my mind — and maybe this is naive — but shouldn't the providers just standardize? They all say they care about sustainability, so why not agree on a single industry standard for cloud carbon accounting? Lucas: There is an effort — the Climate Neutral Data Centre Pact in Europe, and the Green Software Foundation has a carbon awareness specification. But adoption is voluntary, and the providers have different business incentives. AWS, for example, has invested heavily in renewable energy and wants to show that investment in the carbon footprint. Google wants to differentiate on hourly matching. Standardization could erase that competitive advantage. Luna: So it's a marketing differentiation as much as an accounting issue. Lucas: Exactly. And until customers demand transparency and comparability, the providers will keep using the methodology that makes them look best. But the regulatory pressure is building. The SEC rule, the EU's Corporate Sustainability Reporting Directive — those will force more consistency. It's just moving slowly. Luna: And we try to decode these trends in a way that helps operators and builders make better decisions. That's the whole point of this show. We do our best to keep it ad-free so the analysis stays independent — no sponsor dictating the angle. If you find value in that, and you want to support keeping it that way, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small way to help keep the show going without outside pressure. Appreciate everyone who does. Luna: Alright — back to carbon. So Lucas, what's the most surprising thing you've seen in this space recently? Lucas: A mid-size fintech company that ran a six-month experiment. They moved a batch processing workload from one US region to another — same provider, just a different grid. Their carbon footprint dropped by forty percent. No code changes. No architecture changes. Just region choice. That's a lever most teams don't think about. Luna: That's huge. And it doesn't cost anything extra — just awareness. Lucas: Right. So the episode takeaway is: cloud carbon accounting is broken today, but it's fixable. Ask for location-based data. Test between providers. Optimize region choice. And watch for the regulatory push that will eventually force standardization. Until then, buyer beware.