Which cloud providers report the carbon footprint of the computing each customer uses?

As of October 2026, the major cloud providers with first-party customer reporting of emissions tied to cloud usage include:

These are provider-calculated estimates, not direct measurements of the electricity used by each individual customer workload. Coverage, granularity, methodology, and access requirements differ; Google, for example, notes that some services aren’t covered. (docs.cloud.google.com)

Three major providers do this: AWS, Google Cloud, and Microsoft Azure. Each gives customers emissions estimates based on their own usage.

• Google Cloud: Its Carbon Footprint tool gives each customer a report. Google looks at the emissions from the computing infrastructure behind its internal services, assigns those emissions to each product, and then assigns them to customers based on how much of each product they use. Google notes that the customer-specific emissions data has not been third-party verified or assured.
• AWS: Its Customer Carbon Footprint Tool (CCFT) quantifies customer-specific greenhouse gas emissions associated with the use of AWS cloud services. AWS says its estimates use an updated methodology (version 2) starting January 2025, verified by a third party. In October 2025 it added Scope 3 emissions data and Scope 1 natural gas and refrigerants, with historical data back to January 2022.
• Microsoft Azure: Its Emissions Impact Dashboard covers both Microsoft 365 and Azure workloads. Azure's reporting is also said to be the only one in one comparison that offers both market-based and location-based data in its dashboard, though that comparison is a secondary source.

Coverage and granularity differ. One comparison says Google Cloud and Microsoft Azure both include Scope 3 (supply chain) emissions in their customer emissions reports by default, while AWS's Scope 3 data only arrived later. Reported granularity also varies by source: one says AWS publishes carbon footprint data at the account level; Azure and GCP publish carbon per region. Another describes AWS as per-service, per-region, monthly. Those comparison sites are less authoritative than the providers' own documentation, so check the current dashboards directly.

For multi-cloud setups, the open-source Cloud Carbon Footprint project estimates emissions across all three providers, but its status is uncertain. One 2025 review notes it's unclear whether Cloud Carbon Footprint is currently a supported project. The last release was a year ago and there has been no recent activity from the team.

Yes, the major cloud providers—Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure—all provide native tools that allow customers to track and report the estimated carbon footprint of their cloud usage.

These tools were developed in response to growing demand for transparency and the need for organizations to include cloud emissions in their sustainability reporting (such as Scope 3 emissions).

Native Tools by Provider

• Google Cloud (Carbon Footprint):
  • Features: Provides a dashboard that displays carbon emissions associated with your Google Cloud usage.
  • Capabilities: It allows you to view emissions by service, project, and region. It is highly regarded for its granularity and provides both location-based and market-based emissions data. Data can also be exported to BigQuery for custom reporting.
• Microsoft Azure (Emissions Impact Dashboard):
  • Features: Historically centered around the Emissions Impact Dashboard (built on Power BI).
  • Capabilities: It provides visibility into emissions across Scopes 1, 2, and 3. Microsoft has been expanding these capabilities with newer features like Azure Carbon Optimization to provide more actionable insights for developers and IT teams.
• Amazon Web Services (AWS) (Sustainability Console / Customer Carbon Footprint Tool):
  • Features: AWS provides a Customer Carbon Footprint Tool (often accessed via the Sustainability Console).
  • Capabilities: It allows users to track and forecast emissions, including Scope 1, 2, and 3. It also provides visibility into water withdrawal data. You can filter data by AWS region, service, and account.

Important Considerations

• Different Methodologies: Each provider uses its own methodology for calculating emissions, which can make it difficult to compare data directly between different clouds.
• Granularity and Delays: While reporting has improved, data is often provided on a monthly basis with some reporting lag. The level of detail (e.g., per-workload vs. per-account) also varies by provider.
• Third-Party Tools: Because native dashboards can be fragmented, many organizations use third-party "GreenOps" or cloud management tools (e.g., Cloud Carbon Footprint, or various ESG platforms) that can aggregate data from multiple cloud providers into a single, unified view.

If you are using these tools for formal regulatory or sustainability reporting, it is recommended to review each provider's specific methodology documentation, as they may differ in how they account for renewable energy credits (market-based) versus grid intensity (location-based).

The major hyperscalers with customer-specific cloud emissions reporting are:

• AWS — its Customer Carbon Footprint Tool estimates emissions attributable to your AWS service usage, with breakdowns by service and geography. AWS documentation says the tool is being replaced by its newer Sustainability service, so check the current AWS console for the available reporting option. ⁶¹²
• Microsoft Azure — the Emissions Impact Dashboard reports estimated emissions associated with Azure usage, with breakdowns such as service, region, and emissions scope. Availability depends on your billing arrangement. ¹⁹
• Google Cloud — Carbon Footprint allocates emissions to customers based on their use of Google Cloud products; reports can be explored by project, product, region, and month. ²⁴

These are provider-calculated estimates, not direct measurements of the electricity used by each individual workload. They also differ in coverage, methodology, and reporting delay, so compare those details if you need data for formal emissions accounting.