Design considerations for Emissions Impact Dashboard
This article provides design considerations to note while designing Emissions Impact Dashboard to monitor carbon emissions for Azure and Microsoft 365.
Emissions Impact Dashboard for Azure
- Cloud solution providers (CSPs) are supported. Customers who purchase Azure from a CSP aren't supported and must work directly with their CSP partner to learn about their cloud emissions. Legacy accounts aren't supported.
- Emissions Impact Dashboard for Azure is supported for EA Direct, MCA, and MPA accounts with direct billing relationships with Microsoft.
- Review the considerations and limitations that apply to Power BI as outlined in the product article.
- The consumption data combines with Microsoft energy and carbon tracking data to compute the estimated emissions associated with your consumption of Azure services. This consumption is based on the data centers that provide those services.
- The estimates include all Azure services in all Azure regions associated with the tenant ID provided during setup.
- Emissions Impact Dashboard for Azure doesn’t obtain any information specifically about your on-premises data centers except what you provide. Emissions Impact Dashboard for Azure relies on industry research and user inputs about the efficiency and energy mix of on-premises alternatives to estimate on-premises emissions.
- Being resource and cost-efficient in Azure reduces the environmental impact from your use of Azure. Microsoft Cost Management gives you the tools to plan for, analyze, and reduce your spending to maximize your cloud investment.
Emissions Impact Dashboard for Microsoft 365
- Emissions Impact Dashboard for Microsoft 365 isn't currently supported for national/regional cloud deployments. These deployments include, but aren't limited to, Microsoft US Government clouds and Office 365 operated by 21Vianet.
- Emissions Impact Dashboard for Microsoft 365 reports data center emissions and active usage associated with Exchange Online, SharePoint, OneDrive, Microsoft Teams, Word, Excel, PowerPoint, and Outlook applications.
- Emissions data for a given month are available by the 14th day after the end of that month, including nonbusiness days.
- Currently, information on Microsoft 365 usage is only available in the report from June 2022 onwards. For more usage history, see the usage report in the Microsoft 365 admin center.
- Microsoft 365 emissions are allocated based on data storage, active usage, and compute associated with Microsoft 365 applications. Emissions allocated based on compute can occur in regions outside your Microsoft 365 data location.
- Data used to produce the Emissions Impact Dashboard for Microsoft 365 is stored in the US.
- Emissions Impact Dashboard for Microsoft 365 doesn't obtain any information specifically about your on-premises data centers, except what you provide.