Emissions

Overview

Cloud Ctrl Emissions is the single place to review vendor-reported cloud carbon emissions. Open it at /emissions. The page combines a monthly summary, a trend, source readiness, and an interactive breakdown for Azure, Amazon Web Services (AWS), and Google Cloud (GCP).

The figures come from each provider's native reporting service. Cloud Ctrl does not estimate emissions from spend, apply a generic emissions factor, or combine provider reports into a synthetic usage model.

Vendor-native monthly reports

The collection service normalizes provider reports into monthly rows measured in kilograms of CO₂ equivalent (kg CO₂e):

For Azure, both Azure Cost Management Export (CME) and Azure CDR account types are collected; both resolve Azure Active Directory application credentials with ARM access, so the Carbon Optimization API works the same way for each.

Reports are collected monthly. A new account receives a 12-month backfill; regular collection refreshes the current month and the two preceding months so that provider restatements are reflected.

Summary

The summary defaults to the previous 12 months. Use the 3-, 6-, or 12-month controls to change the range. The chart is monthly and includes:

• total emissions in the selected range;
• the monthly trend;
• a comparison with the preceding period; and
• a source-status panel explaining which cloud accounts contributed data.

Only sources with usable vendor data contribute to the total. A source that is pending, denied, not configured, or not yet published is shown by name and excluded; it is never represented as a zero-valued source.

Market-based and location-based methods

Choose MBM (market-based method) or LBM (location-based method) in the methodology control.

• Scope 1 and Scope 3 are always included.
• Scope 2 uses only the selected methodology; MBM and LBM are never added together.
• Azure supplies MBM data only. Under LBM, Azure contributes no Scope 2 row, while its Scope 1 and Scope 3 rows remain included.
• AWS and GCP can supply both MBM and LBM Scope 2 rows.

The API returns kg CO₂e. The page converts values to tonnes (t CO₂e) for display.

Breakdown

Select a grouping to compare and drill into the sources:

Provider → Account → Region → Service

Here, Account means the provider's reporting account: an Azure subscription, an AWS usage account, or a GCP project. It does not mean the Cloud Ctrl cloud-account connection.

Scope is also available as a breakdown dimension. Azure can continue to resource detail where ItemDetailsReport provides it. AWS and GCP stop at their native service grain.

Source readiness and exclusions

The source-status panel reports the state for every connected cloud account. The states are:

• Ready — a completed vendor report is available.
• Pending / warming — the provider has accepted the account, but its first report is not available yet.
• Access denied — the configured identity cannot read the provider report.
• Not configured — required provider reporting configuration is missing.
• Data not yet published — the provider has not published the requested month.

Each non-ready source includes an exclusion reason where available. Resolve the provider permission or reporting configuration, then wait for the next collection cycle. Historical rows are append-only and later provider restatements supersede earlier rows when the page reads the data.

API behavior

The emissions API is available only when the tenant's emissions feature is enabled and the caller has read permission. It returns kg CO₂e and uses the same methodology rules as the page.

Summary requests require Months (3, 6, or 12) and Methodology (MBM or LBM). Breakdown requests additionally require GroupBy (provider, account, region, service, or scope) and accept optional Provider, Account, Region, and Service filters.

The response includes MonthlyTrend, TotalEmissionsKgCO2e, PreviousPeriodEmissionsKgCO2e, the selected Methodology, and SourceStatus. Breakdown rows include their grouping key and label, EmissionsKgCO2e, methodology, and whether another drill-down is available.

Availability

The /emissions page is one unified surface. The former estimation overview, explorer, map, and provider-specific dashboards are not separate destinations. Emissions is not included in the spend grids or saved spend reports; use this page and the emissions API for vendor-native carbon reporting.

If no source is ready, the page still shows the connected accounts and their readiness or exclusion reasons, rather than presenting an empty total without explanation.