Cloud Computing Carbon Footprint: AWS vs Azure vs Google Cloud Emissions Compared

Cloud computing accounts for roughly 1-2% of global electricity consumption — comparable to the aviation industry. For digital businesses, cloud infrastructure is typically the single largest source of Scope 3 emissions, often representing 60-80% of a company's total carbon footprint. Choosing between AWS, Azure, and Google Cloud is not just a technical or financial decision anymore. It is an environmental one.

The problem: all three providers claim to be sustainable. All three publish carbon data. But the methodologies, transparency levels, and actual performance differ substantially. This article cuts through the marketing to compare what we actually know about each provider's emissions.

The Current State: Carbon Reporting by Provider

Each hyperscaler offers a carbon reporting dashboard for customers. The quality and methodology vary significantly:

The most important distinction is between market-based and location-based accounting. Market-based accounting allows providers to claim zero emissions in regions where they have purchased Renewable Energy Certificates (RECs), even if the grid still runs partially on fossil fuels. Location-based accounting uses the actual grid carbon intensity where the data center operates. The difference can be enormous. For a detailed breakdown of Scope 1, 2, and 3 distinctions, see our complete emissions guide.

AWS: The Scale Leader With Transparency Gaps

Amazon Web Services operates the largest cloud infrastructure globally, with 34 regions and over 100 availability zones. AWS has committed to powering operations with 100% renewable energy by 2025 and reaching net-zero carbon by 2040 through The Climate Pledge.

What AWS Reports

The AWS Customer Carbon Footprint Tool (CCFT) provides market-based emissions estimates per service, per region. Since 2024, it includes partial Scope 3 estimates covering some embodied carbon from server manufacturing. AWS applies renewable energy credits at the regional level, meaning regions with high REC coverage show dramatically lower emissions.

Where AWS Falls Short

• No location-based option — AWS only reports market-based figures. You cannot see what your actual grid-based emissions are. For CSRD reporting that requires dual reporting, this is a significant gap.
• REC quality questions — AWS purchases unbundled RECs in some markets, which environmental accounting standards (like the GHG Protocol Scope 2 Guidance) consider lower quality than PPAs (Power Purchase Agreements) or on-site generation.
• Limited Scope 3 coverage — embodied carbon data is partial and methodology is not fully published.
• Water usage data — AWS publishes aggregate water efficiency metrics but does not provide customer-level water usage data, which is increasingly relevant for CSRD reporting.

Best and Worst AWS Regions for Carbon

AWS regions powered primarily by hydroelectric or nuclear energy have the lowest carbon intensity: eu-north-1 (Stockholm), ca-central-1 (Montreal), and eu-west-1 (Ireland) are among the cleanest. High-carbon regions include those in Asia-Pacific where grid intensity is higher: ap-southeast-1 (Singapore) and ap-south-1 (Mumbai).

Microsoft Azure: Best Dual Reporting, Aggressive Commitments

Azure operates across 60+ regions globally. Microsoft has committed to being carbon negative by 2030 and removing all historical emissions by 2050 — the most ambitious climate target among the three hyperscalers.

What Azure Reports

The Azure Emissions Impact Dashboard provides both market-based and location-based emissions. This dual reporting is valuable for companies subject to CSRD, which requires both methodologies. Azure breaks emissions down by subscription, making it easier to allocate carbon costs to specific business units or products.

Where Azure Excels

• Dual methodology reporting — the only major cloud provider offering both market-based and location-based data in its customer dashboard.
• Carbon removal investments — Microsoft has invested over $1 billion in carbon removal technologies, including direct air capture, biochar, and enhanced weathering. These are removal credits, not avoidance offsets.
• Internal carbon tax — Microsoft charges its own business units $15/tonne CO2e, creating internal incentives for efficiency. This has been in place since 2012.

Where Azure Falls Short

• Scope 3 growth from AI — Microsoft's 2024 sustainability report revealed a 29% increase in Scope 3 emissions, driven primarily by data center construction for AI workloads. The gap between Microsoft's carbon negative goal and its actual emissions trajectory is widening.
• Data center construction emissions — the embodied carbon of new data center construction (concrete, steel, equipment) is massive and growing as AI demand drives expansion.
• Natural gas backup — Azure data centers use diesel and increasingly natural gas generators for backup power. While operational hours are low, the capacity exists and emissions occur during outages and testing.

Google Cloud: 24/7 Carbon-Free Energy Pioneer

Google Cloud operates across 40 regions globally. Google has been carbon neutral since 2007 (through offsets) and has set a target to run on 24/7 carbon-free energy (CFE) everywhere by 2030 — a fundamentally different approach from annual REC matching.

What Makes 24/7 CFE Different

Most renewable energy claims work on an annual matching basis: a company buys enough RECs or generates enough renewable energy over a year to match its total consumption. The problem is temporal: a data center might run on coal-generated electricity at 2 AM and "match" it with solar RECs generated at 2 PM. The grid impact is zero.

Google's 24/7 CFE approach tracks carbon-free energy on an hourly basis, region by region. A region with 90% CFE means that 90% of the time, the actual electricity flowing into that data center comes from carbon-free sources — not that enough certificates exist somewhere to cover annual consumption.

Current 24/7 CFE Scores by Region

Google publishes hourly CFE scores for every region. Top performers as of early 2026:

• europe-north1 (Finland) — 97% CFE (hydro + nuclear + wind)
• northamerica-northeast1 (Montreal) — 98% CFE (hydro)
• us-central1 (Iowa) — 95% CFE (wind PPAs)
• europe-west1 (Netherlands) — 89% CFE

Lower performers:

• asia-south1 (Mumbai) — 42% CFE
• asia-southeast1 (Singapore) — 38% CFE
• asia-east1 (Taiwan) — 29% CFE

These scores are published transparently, which is itself a significant differentiator. For businesses tracking their website carbon footprint, Google Cloud's regional CFE data enables accurate Scope 3 calculations.

Where Google Cloud Falls Short

• Legacy "carbon neutral" claim — Google's corporate "carbon neutral since 2007" claim was based on offsets. While Google has been transparent about this, the claim sat awkwardly alongside stricter EU rules on neutrality claims. Google has shifted messaging toward 24/7 CFE metrics.
• AI energy demand — like Microsoft, Google's AI expansion (Gemini training, inference infrastructure) is driving significant energy demand growth that risks outpacing CFE procurement.
• Smaller region coverage — fewer regions than AWS, which may force some customers to choose higher-carbon regions for latency reasons.

Head-to-Head: Which Provider Is Greenest?

The honest answer: it depends on your specific usage pattern.

For CSRD-reporting companies, Azure's dual methodology is a practical advantage. For companies optimizing for actual grid impact, Google Cloud's 24/7 CFE approach is more rigorous than annual REC matching. For companies where cloud cost is the primary driver, choosing low-carbon regions within any provider achieves 80% of the emissions benefit.

Practical Steps: Reducing Your Cloud Carbon Footprint

Regardless of provider, these actions reduce cloud emissions:

1. Region Selection

Move workloads to low-carbon regions where latency permits. The difference between a high-carbon and low-carbon region can be 5-10x in emissions per compute hour. This is the single highest-impact decision.

2. Right-Sizing and Utilization

Over-provisioned instances waste energy. Use autoscaling, spot instances, and reserved capacity that matches actual demand. A server running at 15% utilization consumes 60-70% of the energy it would at full load — most of the energy is wasted.

3. Carbon-Aware Scheduling

Shift flexible workloads (batch processing, ML training, backups) to times when the grid is cleanest. Google's Carbon-Aware Computing and emerging tools for AWS and Azure enable this. Our guide to reducing website carbon footprint covers additional optimization techniques.

4. Measure and Report

Enable your provider's carbon dashboard. Export the data monthly. Include it in your Scope 3 inventory. What gets measured gets managed. For a methodology overview, see our measurement guide.

5. Challenge Your Provider

As a customer, request location-based data from AWS if you need it for CSRD. Request hourly CFE data from Azure. Customer pressure drives provider transparency — it is how Google's 24/7 CFE reporting came to exist.

The AI Elephant in the Data Center

All three providers are experiencing massive demand growth from AI workloads. Training a large language model can emit hundreds of tonnes of CO2. Inference (running the model for users) has a lower per-query footprint but scales with millions of daily queries.

The uncomfortable truth: cloud computing emissions are likely to increase in absolute terms over the next 3-5 years, even as efficiency improves per unit of compute. AI demand is growing faster than renewable energy procurement. Microsoft's 29% Scope 3 increase in 2024 is a preview, not an anomaly.

For businesses choosing a cloud provider with sustainability in mind, the question is not "who is green" but "who is most transparent about the problem and most credible in addressing it." On that metric, Google Cloud leads in transparency, Microsoft leads in financial commitment to carbon removal, and AWS leads in absolute renewable energy procurement. None of them have solved the AI energy problem yet.