Connect to the Emissions Impact Dashboard

Calculate your cloud-based carbon emissions today with the Emissions Impact Dashboard.

Accurate carbon accounting requires good information from partners, vendors, and suppliers. The Emissions Impact Dashboard gives you transparency on the carbon emissions generated by your usage of Azure and Microsoft Dynamics. Microsoft’s carbon accounting extends across all three scopes of emissions with a methodology validated by Stanford University in 2018. It uses consistent and accurate carbon accounting to quantify the impact of Microsoft cloud services on customers’ environmental footprint. Microsoft is the only cloud provider to provide this level of transparency to customers while compiling reports for voluntary or statutory reporting requirements.


This connector version only supports enrollments from the Azure Enterprise portal. China enrollments aren't currently supported.


To install the Emissions Impact Dashboard in Power BI and connect it to your data, make sure you have the following: before installing the app.

  • A Power BI Pro license. If you don’t have a Power BI Pro license, get a free trial now.
  • An admin role with read/write permissions on your Azure tenant. If you don't have such permissions, contact an Azure admin who has read/write permissions.
  • The Emissions Impact Dashboard is supported for EA Direct and MCA/MPA (CSP with Azure Plan) accounts.
    • If you have an EA Direct account, you must be an Enrollment Administrator with either read or write permissions and have your company's enrollment number.
    • If you have an MCA/MPA (CSP with Azure Plan) account (that is, you have a direct billing relationship with Microsoft), you must be a Billing Account Administrator with a role as Billing Account Reader/Contributor/Owner, and have your company's billing account ID.

Install the app

  1. Click the following link to get to the app: Emissions Impact Dashboard template app.

  2. On the AppSource page for the app, select GET IT NOW.

    Screenshot of Emissions Impact Dashboard on AppSource.

    You can also search for the app in Power BI.

  3. When prompted, click Install.

    Screenshot of install dialog.

  4. When the app finishes installing, it will appear on your Power BI Apps page. Click on the app and open it.

    Screenshot of app installed on app page.

  5. Select Connect your data.

    Screenshot of connect your data.

  6. In the Connect to Emissions Impact Dashboard dialog that appears, under EnrollmentIDorBillingAccountID, enter either your enrollment number (EA Direct customers) or billing account ID (MCA/MPA (CSP with Azure Plan) customers)

    Screenshot of connect to dialog 1.

    When done, click Next.

  7. Connect your account:

    • For Authentication method, choose OAuth2.
    • For Privacy level setting for this data source, choose Organizational.
    • When done, click Sign in and connect.

    Screenshot of authentication first dialog.

  8. Select the user account. Please make sure to login with the credentials which have access to the enrollmentID/Billing AccountID with valid permissions as explained in the prerequisites.

    Pick an account.

  9. Wait for the view to build. This can take up to 24 hours. Please refresh the dataset after 24 hours.

Update the app

Periodically you may receive update notifications from Appsource/Power BI about a new version of the app. When you install the new version, the following options are available:

Screenshot of Update app dialog.

Choose Update the workspace and the app, then click Install. This will install the update, overwriting the existing/installed workspace and app.


If there are any issues with the dataset refresh/app update during the updating process, please validate these steps and refresh the dataset.

Follow the steps below to make sure your dataset configurations are set correctly:

  1. Go to the workspace panel and open the app workspace.

  2. Open the Scheduled Refresh option in the dataset settings and make sure the Enrollment ID or Billing Account ID is correct.

    Screenshot of schedule refresh.

  3. Open the Parameters section and configure the data source once again in the Data Source section with the credentials with which you have access to the Enrollment ID / Billing Account ID with valid permissions, mentioned in the prerequisites.

    Screenshot of Data source Credentials Parameters.

  4. Once the above steps are validated, go back to the app workspace and click on the Refresh option.

    Screenshot of Data Refresh.

  5. Once the dataset has refreshed successfully, click the Update App option at the top-right corner of the app workspace.

    Screenshot of Updating App.

Additional resources

Finding your company’s enrollment number (EA Direct customers only)

Follow the steps below to find your company's enrollment number, or ask your organization’s Azure administrator.

  1. Sign into the Azure Enterprise portal as an admin.

  2. Select Active Directory or Manage on the left-hand navigation bar. Your company’s enrollment number will display.

    Screenshot of find enrollment number.

Finding your company's billing account ID (MCA/MPA CSP with Azure Plan customers only)

Follow the steps below to find your company's billing account ID, or ask your organization’s Azure administrator.

  1. In the Azure portal, navigate to Cost Management + Billing.

  2. Select your billing account.

  3. Under Settings, select Properties. Your billing account ID will display under Billing account.

    Find billing account ID


App setup

I’m receiving an error at the time of connecting my data with the dashboard. What can I do?

First, check in Azure Cost Management that you have IT Admin privileges. If you don’t, request this access from your administrator. Next, ensure you’re using the correct enrollment number.

I entered my enrollment number, but my company data isn’t loading. What’s the issue?

The Emissions Impact Dashboard may take up to 24 hours to load your data. Return after 24 hours and select the Refresh button in Power BI.

Is Microsoft trying to shift responsibility for emissions from Microsoft to me?

No. Carbon emissions from Azure services are reported as Microsoft's scope 1 and 2 emissions, consistent with the industry-standard Greenhouse Gas (GHG) Protocol. The GHG Protocol defines scope 3 emissions as emissions another entity emits on your behalf, and are inherently double-counted. The Emissions Impact Dashboard provides new transparency to your scope 3 emissions associated with the use of Azure services, specifically Scope 3 Category 1 "Purchased goods and services".

Why are my emissions from use of the Microsoft cloud so much lower than they would be if I were using an on-premises solution?

Microsoft conducted a study, published in 2018 that evaluated the difference between the Microsoft cloud and on-premises or traditional datacenters. The results show that Azure Compute and Storage are between 52 and 79 percent more energy-efficient than traditional enterprise datacenters, depending on the specific comparison to low, medium, or high efficiency on-premises alternative being made. When taking into account our renewable energy purchases, Azure is between 79 and 98 percent more carbon efficient. These savings are due to four key features of the Microsoft Cloud: IT operational efficiency, IT equipment efficiency, datacenter infrastructure efficiency, and renewable electricity.

If Microsoft's operations are carbon neutral and powered by renewables, why aren't customer emissions from Azure services zero?

There are two primary reasons why customer emissions from Microsoft aren’t zero. The first is related to GHG accounting practices, and the second has to do with the boundary of this analysis. To achieve carbon neutral operations, Microsoft uses carbon offsets to reduce certain emission sources such as onsite fuel combustion for backup generators, refrigerants, and vehicle fleets. These reduce Microsoft’s net emissions to zero. The dashboard reports gross GHG emissions before the application of these offsets, though the volume of offsets applied and net emissions is reported in the GHG Reporting tab for further transparency. The second reason is that in addition to the energy and emissions associated with the operation of Microsoft's datacenters, the emissions footprint includes the energy used by Internet Service Providers outside of Microsoft’s operational boundary to transmit data between Microsoft datacenters and Azure customers.

How am I supposed to use this data, and where do I report it?

Your emissions can be reported as part of your company's Scope 3 indirect carbon emissions. Scope 3 emissions are often disclosed in sustainability reports, CDP climate change, and other reporting outlets. In addition to the emissions totals, the emissions savings provide a clear example of how your company's decision to use Microsoft Azure services is contributing to global emissions reductions. To contextualize, the app indicates the equivalent vehicle miles avoided corresponding to the reduction in GHG emissions, based on EPA’s equivalency calculator factors as of January 2020.

What can I do to reduce emissions further?

Being resource and cost efficient in Azure will reduce the environmental impact from your use of Azure. As an example, unused virtual machines are wasteful whether in the cloud or on-premises. Right-sizing virtual machines to improve compute utilization factors (CUF) decreases energy use per useful output, just as it does with physical servers. Azure Cost Management gives you the tools to plan for, analyze and reduce your spending to maximize your cloud investment.

My company contract renewal process is underway and we'll have a new account number. Will I lose my historical emissions data?

Yes, you will. Before your renewal, be sure to download all historical data and reports you'll need for your records.


What is the methodology behind the tool?

The Emissions Impact Dashboard reflects the specific cloud services consumed and the associated energy requirements, efficiency of the datacenters providing those services, electricity fuel mixes in the regions in which those datacenters operate, and Microsoft’s purchases of renewable energy. As part of the app’s development, the methodology and its implementation went through third-party verification to ensure that it aligns to the World Resources Institute (WRI)/World Business Council for Sustainable Development (WBCSD) Greenhouse Gas (GHG) Protocol Corporate Accounting and Reporting Standard. The scope of the verification, conducted in accordance with ISO 14064-3: Greenhouse gases--Part 3: Specification with guidance for the validation and verification of greenhouse gas assertions, included the estimation of emissions from Azure services, but excluded the estimation of on-premises emissions given the counterfactual nature of that estimate. A more detailed description of the carbon calculation is documented in the Calculation Methodology tab in the tool.

What data is required to calculate the Azure carbon footprint? Do you access my company's data?

The estimated carbon calculations are performed based on consumption of Azure services accessed using Azure Consumed Revenue. The dashboard does not access any of your stored customer data. The consumption data is combined with Microsoft's energy and carbon tracking data to compute the estimated emissions associated with your consumption of Azure services based on the datacenters that provide those services.

Does this calculation include all Azure services and all Azure regions?

The estimates include all Azure services in all Azure regions associated with the tenant ID provided during setup.

Characterizing on-premises emissions

Where does the Emissions Impact Dashboard obtain data about my on-premises emissions and operations?

The Emissions Impact Dashboard doesn’t obtain any information specifically about your on-premises datacenters except what you provide. As described in subsequent FAQs, the Emissions Impact Dashboard relies on industry research and user inputs about the efficiency and energy mix of on-premises alternatives to develop an estimate of on-premises emissions.

What are the assumptions regarding on-premises estimations? Are efficiency savings just from improvements in Power Usage Effectiveness (PUE)?

Efficiencies associated with Microsoft cloud services include far more than improved PUE. While Microsoft datacenters strive to optimize PUE, the primary efficiency improvements come from IT operational efficiency (dynamic provisioning, multitenancy, server utilization) and IT equipment efficiency (tailoring hardware to services ensuring more energy goes towards useful output), in addition to datacenter infrastructure efficiency (PUE improvements). Our 2018 study quantifies these savings compared to a range of on-premises alternatives ranging from low-efficiency to high-efficiency datacenters. These findings are used to estimate the energy use required for a corresponding on-premises datacenter to provide the same services that each customer consumes on the Microsoft cloud.

What is the assumed energy mix for the on-premises infrastructure?

By default, the Emissions Impact Dashboard estimates on-premises emissions based on the mix of renewables and non-renewables on the grid. It is assumed that the on-premises datacenter would be located on the same grid as Microsoft’s datacenters. However, for customers who purchase renewable electricity in addition to what’s on the grid (for example, through Power Purchase Agreements), users can select the percentage of renewable electricity, and the Emissions Impact Dashboard will adjust on-premises emissions accordingly.

When should I choose Low, Medium, or High for the efficiency of the on-premises infrastructure?

Users should select the efficiency most representative of the on-premises deployment they would like to compare against, based on the equipment and datacenter characteristics here:

  • Low: Physical servers and direct attached storage in small localized datacenter (500-1,999 square feet)
  • Medium: Mix of physical/virtualized servers and attached/dedicated storage in mid-tier internal datacenter (2,000-19,999 square feet)
  • High: Virtualized servers and dedicated storage in high-end internal datacenter (>20,000 square feet)