Domain 3 · Optimize Usage and Cost
Optimise carbon where you optimise spend.
Sustainability brings carbon reduction into the Optimize phase — cutting the carbon footprint of workloads alongside their cost. CloudMonitor surfaces per-workload kgCO2e beside the savings recommendation, on the same allocation tree, so GreenOps and FinOps run as one practice.
The problem
Carbon and cost, optimised separately.
Two practices, no overlap.
FinOps optimises spend, GreenOps optimises carbon, and the two teams meet at the executive summary. The workloads they care about overlap; the data doesn't.
No workload signal.
Microsoft's emissions impact dashboard reports at tenant level. Engineering can't tell which app is the carbon problem.
Wins lost on the carbon side.
A rightsizing recommendation that cuts spend usually cuts carbon — but the GreenOps team never hears about it. The story stops at the dollar line.
How CloudMonitor answers
Carbon next to every saving.
Per-workload kgCO2e.
Carbon at the resource group, attributed via the same allocation tree as spend. Engineering finally has a number to act on.
Surfaced beside savings.
Every rightsizing or workload recommendation carries a carbon delta in the same card. Approving a saving is approving an emissions cut.
Same cost-group tree.
No second allocation, no parallel taxonomy. The product that owns the spend owns the carbon, with the same rollups.
GreenOps-ready exports.
Audit-trailed exports for the ESG reporting cycle, mapped to the same workloads the FinOps practice is already optimising.
Outcomes
One optimisation queue, two metrics.
Workload
kgCO2e per resource group
Paired
Carbon delta on every saving
One tree
No parallel taxonomy
Related Capabilities
More in the Optimize Usage and Cost Domain.
Usage Optimization
Architectural patterns flagged when a workload could be cheaper.
Licensing & SaaS
Azure Hybrid Benefit, BYOL, and marketplace SaaS — licenses and subscriptions reviewed against actual usage.
All Optimize Usage and Cost Capabilities
See every Capability in this Domain side by side.
Sustainability in CloudMonitor
Carbon rides the same tree as cost.
Same allocation tree
Workloads grouped once, for spend and carbon.
Resources roll up through the same cost-group tree that carries the bill — so per-workload kgCO2e attributes exactly where spend already does, with no parallel taxonomy to maintain.
Beside every saving
The recommendation that cuts cost usually cuts carbon.
Right-sizing and workload recommendations are where the emissions win hides. Surfaced on the same card as the saving, approving the dollar cut is approving the carbon cut — and GreenOps finally hears about it.
Source: this page interprets the Optimize Usage and Cost domain published by the FinOps Foundation, licensed under CC BY 4.0. The wording, examples, and product mapping on this page are CloudMonitor’s own.
See savings and emissions in one queue.
The demo tenant pairs every recommendation with a carbon impact at the same level of detail.
