Latest / The Cloud Business Podcast with Fexingo: AWS, Azure, GCP, and Enterprise Infrastructure / How Cloud Contracts Now Tie Discounts to Carbon Metrics
Transcript
- Lucas: So you've been hearing this term 'sustainability-linked discount' in cloud procurement circles, and it's not just a marketing slide anymore. In the last six months, I've tracked three concrete enterprise deals where the discount on a three-year compute commitment was explicitly tied to carbon reduction targets. Luna: Wait — the cloud provider is saying, 'We'll give you a better price if you pollute less'? That's a new flavor of contract clause. Lucas: Exactly. And it's a clever one. Let me give you the specific example that caught my attention. A mid-sized financial services firm — I'll call them Eastgate Capital — signed a three-year AWS deal in March 2026. Their baseline reserved-instance discount was around 25 percent off on-demand. But they negotiated an additional 2 percent on top of that — so 27 percent total — by agreeing to two things: first, shift at least 30 percent of their compute to AWS's low-carbon regions, and second, implement carbon-aware instance scheduling for batch jobs. Luna: Two percent doesn't sound huge, but on a multi-million dollar commitment, that's real money. And the scheduling piece — that's the part where you let the cloud provider pause or shift non-urgent workloads to times when the local grid has a lower carbon intensity? Lucas: Right. AWS calls it 'carbon-aware instance scheduling' inside their internal tools, but the concept is the same as what Google Cloud has been piloting with their Carbon Sense suite. You tag a workload as 'flexible' — maybe a batch data-processing job that doesn't need to finish until 6 a.m. — and the scheduler runs it during hours when the local energy mix has a higher percentage of renewables. The provider gets to use your compute demand as a flexible load to help balance their own carbon accounting. And they share some of that benefit back to you as a discount. Luna: So the cloud provider is basically buying demand-side flexibility from you, and paying you in the form of a lower reservation price. That's a pretty elegant mechanism if it works. Lucas: It is. And Microsoft Azure is rolling out something similar under their 'Emissions Impact Dashboard for Contracts' program. The difference is Azure ties the discount to a percentage reduction in your scope three emissions — the ones from using their cloud — measured against a baseline year. If you cut your Azure-related carbon footprint by 15 percent year-over-year, you unlock a discount tier on your next Azure Consumption Commitment. Luna: That's trickier, because it means the customer has to actually track and report their cloud carbon footprint with some accuracy. Not every enterprise has that capability yet. Lucas: And that's exactly where the third-party carbon accounting firms see an opportunity. Companies like Watershed, Persefoni, and Salesforce's Net Zero Cloud are now offering modules specifically for cloud carbon tracking that integrate with AWS, Azure, and GCP billing APIs. Eastgate Capital used Watershed to verify their compliance with the low-carbon region shift clause. The cloud provider doesn't just take your word for it — they want auditable data. Luna: So the contract essentially outsources some of the carbon accounting burden to a third party. That makes sense, because the cloud provider doesn't want to be in the business of auditing every customer's energy mix choices. Lucas: Right. And the providers have their own incentives here. AWS, Azure, and GCP have all made public commitments to be carbon-neutral or carbon-negative by 2030. If they can show that a significant portion of their customer base is voluntarily shifting workloads to low-carbon regions or time-shifting to renewable-heavy hours, that improves their own carbon accounting. It's a shared-value story, but it's also a compliance hedge. Regulators in the EU and the US are starting to require more detailed scope three reporting for large enterprises. Luna: I want to challenge the 'genuine innovation' reading a little. Couldn't this just be a way for cloud providers to pack more demand into their cheapest regions — which happen to be the ones with hydro or nuclear power — and call it green? Lucas: That's a fair critique, and I've heard it from procurement officers too. If the 'low-carbon region' list happens to map exactly to the regions where the provider has excess capacity and lower electricity costs, the discount might just be a repackaged volume discount. But there are signs that it's not just that. For instance, Google Cloud's Carbon Sense pricing experiment from late 2025 offered a discount specifically for workloads running in regions where the grid carbon intensity was below a certain threshold — not just a list of pre-approved regions, but a dynamic threshold that changes hourly based on real-time grid data. Luna: That's harder to game. If the discount is tied to real-time grid carbon intensity, you can't just park your workloads in a low-cost region and call it a day. You actually have to shift compute to follow renewable availability. Lucas: Exactly. And that requires a more sophisticated operational model. But some enterprises are already doing it. A large European retailer — I'm thinking of a case study from the Google Cloud Next conference in April — described how they moved their nightly inventory-reconciliation batch jobs to follow the sun across Google's European regions. When wind power was abundant in the Nordics, the jobs ran in Finland. When solar peaked in Spain, they shifted south. They claimed a 22 percent reduction in compute-related carbon emissions and a 4 percent cost savings from the dynamic discount. Luna: Four percent doesn't sound like a huge incentive for most companies to re-architect their batch processing. But combined with the regulatory pressure and the ESG reporting benefits, it might tip the scales for some. Lucas: That's the real story here. The discounts alone aren't massive — we're talking 2 to 5 percent on top of standard reservation discounts. But the contractual structure is new. It changes the conversation between cloud procurement and the sustainability team. Before, the sustainability team might have had to beg the cloud architect to consider region choices. Now, the contract itself creates a financial incentive for the architect to care. Luna: That's a structural shift. If the cloud architect's bonus is tied to cloud cost optimization, and the contract now rewards carbon-aware decisions, you've aligned two incentives that used to be separate. Lucas: And that alignment is what makes me think this isn't just a fad. I've seen early drafts of similar clauses in Azure Enterprise Agreements and GCP committed-use contracts. AWS is the most advanced so far — their 'Carbon Savings Plan' product, which launched in preview in February 2026, bundles a committed spend level with a carbon reduction target. You commit to spending, say, $1 million over three years, and you get a base discount. But if you also commit to reducing your carbon intensity by 10 percent per year, you get an additional 1.5 percent discount. If you hit 15 percent, you get 2.5 percent. Luna: So it's a tiered incentive. And presumably the baseline is measured from your first month of usage under the plan, so the provider is betting that you can improve. Lucas: Right. And they have data to suggest that most large customers can achieve at least a 10 percent reduction just by moving off older instance families and choosing regions with better grid mixes. It's not even that hard — it's just that nobody had a financial reason to do it before. Luna: What about the risk of perverse incentives? Could a customer deliberately inflate their baseline carbon footprint in month one to make the reduction targets easier to hit? Lucas: The contracts I've seen address that by using a trailing twelve-month average as the baseline, measured from the first three months of the agreement. So there's a window where you can't easily game it. And the third-party auditor — like Watershed or a consulting firm — validates the baseline. It's not foolproof, but it's more robust than a self-reported number. Luna: I want to zoom out. How widespread do you think this will be by the end of 2026? Is it going to become a standard clause, like data egress credits or GPU resale clauses? Lucas: I think it will be a standard negotiating point for any enterprise cloud deal above, say, $5 million total contract value within eighteen months. The providers are all racing to show they're serious about sustainability, and the customers — especially publicly traded or eu based — need to show scope three reductions. The clause gives both sides something to point to. My prediction is that by Q2 2027, over half of new large enterprise cloud contracts will include some form of sustainability-linked pricing. Luna: That's a bold call. But it does feel like a natural evolution. First we had reserved instances, then committed-use discounts, then spot instance guarantees, and now carbon-aware discounts. Each layer adds more flexibility and more complexity. Lucas: And each layer also adds more data. The cloud provider now knows not just how much compute you're buying, but when and where you're running it, and what the carbon impact is. That data is valuable for them too — they can optimize their own grid purchasing and renewable energy credits based on customer behavior patterns. Luna: So there's a feedback loop. The more customers adopt carbon-aware scheduling, the better the provider's grid forecasting becomes, and the more renewable energy they can integrate, which lowers their own carbon costs, which lets them offer better discounts. That's a virtuous cycle — if it works. Lucas: Exactly. And speaking of making things work — this show exists because we love digging into these structural shifts in cloud and enterprise infrastructure. If you find these conversations useful for what you're building or running, listener support is what keeps it ad-free. People can head to buy me a coffee dot com slash fexingo — that's buy me a coffee dot com slash fexingo — if they want to help us keep exploring these topics without sponsors. No pressure, just if it's valuable to you. Luna: Yeah, and we're grateful for everyone who's already chipped in. It makes a real difference in how much time we can spend on research for episodes like this one. Lucas: Alright — back to the carbon clause. One more angle I want to touch on: the implications for multicloud strategy. If you have two different cloud providers offering different sustainability-linked discount structures, how do you compare them? A dollar saved on AWS might come with a 10 percent carbon reduction target, while Azure offers a tiered discount based on absolute emissions reduction. Those aren't directly comparable. Luna: That's going to be a headache for procurement teams. They'll need to model not just cost, but also carbon outcomes under different workload distributions. It adds another dimension to the already complex cloud cost optimization problem. Lucas: And that's where I think we'll see new consultancies and software tools emerge to handle that trade-off. CloudHealth, Flexera, and others are already adding carbon modules to their cost optimization platforms. The next generation of FinOps will include 'CarbonOps' as a discipline. Luna: CarbonOps. I like that term. It's going to be a real job title before long. Lucas: I think so. And for anyone listening who negotiates cloud contracts — the advice I'd give is: don't wait for the provider to bring up sustainability-linked discounts. Ask for it explicitly in your next renewal or new commitment. Even if they don't have a formal program yet, the fact that you're asking signals that you value it, and they might be willing to experiment with a custom clause. Luna: That's a smart takeaway. Be the customer who pushes the provider to innovate on this front. It might pay off in both cost and carbon. Lucas: And that's the cloud business in 2026 — every contract clause is a lever for something beyond just price. Thanks for listening, and we'll be back next week with another angle.