In short
The big cloud providers publish customer carbon data in their billing or sustainability consoles: the AWS Sustainability console, Microsoft's Azure emissions tools and Google Cloud's Carbon Footprint dashboard. They break emissions down by service, region and scope, but are monthly and estimated, so treat them as a trend and pair them with your own per-workload measurements.
Steps
- Find your provider's carbon tool, usually in the billing or sustainability console.
- Export the data and break it down by service, region and account.
- Note whether figures are location-based, market-based or both, and which scopes are included.
- Use the totals as a monthly trend, not a precise measurement.
- Add your own per-workload estimates or measurements for AI features.
Your cloud's carbon report usually sits in the billing console, not where engineers look. It is a useful starting point for reporting, as long as you know its limits.
Where is it?
| Provider | Tool | What it covers |
|---|---|---|
| AWS | Sustainability console, a free standalone service that expands on the older Customer Carbon Footprint Tool | Emissions by region, service and scope 1, 2 and 3 |
| Microsoft Azure | Emissions Impact Dashboard (Power BI), which Microsoft says retires on 31 March 2027, with Azure Carbon Optimization as its replacement | Emissions from Azure usage across all three scopes |
| Google Cloud | Carbon Footprint dashboard | Estimated emissions, with scope 2 both market-based and location-based, and scope 3 |
Tools change often, so check the provider's documentation for the current name and location.
What are the limits?
- Monthly and delayed. You can't use them to see the effect of a change made yesterday.
- Estimated. Hardware counters are usually unavailable on cloud virtual machines, so providers model your share.
- Coarse. They show services, not individual AI features or prompts.
- Different methods. Figures from two providers may not be comparable.
What makes the biggest difference
Combining the provider's totals with your own finer data: token logs and estimates for hosted AI calls (estimating API call energy) and metering where you run your own GPUs.
See reporting AI emissions in a sustainability report and how to measure AI energy.
Sources
- AWS launches Sustainability console for carbon emissions tracking, Amazon Web Services (2026)
- Connect to the Emissions Impact Dashboard for Azure, Microsoft Learn (2026)
- View Carbon Footprint data, Google Cloud documentation (2026)
Related
How do I report AI emissions in our sustainability report?
Where AI belongs in Scope 2 and Scope 3 reporting, how to estimate it when suppliers give little data, and how to state method and uncertainty.
How do I estimate the energy of my AI API calls?
You can't meter a hosted AI API, but you can estimate energy per call from token counts and model assumptions with EcoLogits, and log it next to cost.
How do I check whether my AI runs on renewable energy?
Tell hourly clean power from annual certificates: ask where your AI runs, the grid's carbon intensity and the hour-by-hour clean share for that region.
How to measure the energy and carbon of AI
A practical guide to metering or estimating the energy and carbon of AI work: tools, system boundaries, per-task metrics and honest uncertainty.