In recognition of Earth Month and the latest Intergovernmental Panel on Climate Change (IPCC) report1 urging parties to hasten progress to net zero, we’re pleased to announce timely updates to Microsoft Cloud for Sustainability. These new features deliver enhanced levels of insight (including Scope 3 waste data), data access and management, reporting, and customization to help organizations meet their goals and make progress faster.
Round out insights with custom dimensions
Organizations can now add custom dimensions (Preview) to data model entities in Microsoft Sustainability Manager, helping to refine calculations and analysis. For example, they can associate activity or emissions data with other contextual data such as emissions intensity per number of employees.
Once the data with custom dimensions are ingested, mapped, and calculated, it can be used to generate manufacturing intensities by domain. In the screenshot below, a dashboard shows emissions from laptop manufacturing by assembly line, model, and SKU.
A Practical Microsoft Sustainability Manager Rollout
An effective deployment is as much a data-governance project as a software configuration exercise. Define reporting boundaries, choose which Scope 1, Scope 2 and Scope 3 activity categories are relevant, and map the available source records before building dashboards. The first iteration should emphasize traceability, not just attractive charts. Product capabilities and licensing evolve, so validate the current Microsoft documentation for the tenant and region.
For architecture decisions, separate the initial proof of concept from the production operating model. Define a measurable success criterion, establish accountable ownership and make exceptions visible. Review permissions, integration dependencies, change control and incident response before rollout. Capture evidence of tests so the solution can be reviewed later without relying on individual recollections.
Implementation Checklist
| Area | Recommended practice |
|---|---|
| Discover | Inventory emission sources, owners and reporting periods |
| Model | Normalize units and map activity records |
| Validate | Review factor versions, estimates and exceptions |
| Operate | Monitor ingestion, permissions and reconciliation |
Frequently Asked Questions
Can sustainability reporting be fully automated?
Ingestion and calculations can be automated, but source-data quality, methodology selection, approvals and regulatory interpretations still require accountable human review.
How do architects measure success?
Track reliability, data quality, operating effort and the number of exceptions resolved within the agreed service levels. Compare these outcomes with the baseline before declaring the implementation complete.
Related Architecture Articles
Making Sustainability Reporting Auditable
Treat emissions calculations as controlled business records. Record source-system ownership, measurement units, emissions-factor versions and calculation dates. Flag estimated values and exceptions for review before reports are approved. Build a repeatable reconciliation process between raw activity records, calculated emissions and published totals.
Establish an accountable owner for every production integration and document the intended outcomes before deployment. Review permissions, change approval, monitoring and recovery procedures as part of the design. Keep evidence of validation so the implementation can be reassessed when business requirements or service capabilities change.
Operational Review
| Area | Validation |
|---|---|
| Security | Identity, permissions and data boundaries |
| Operations | Monitoring, escalation and rollback |
| Governance | Ownership and audit evidence |
Frequently Asked Questions
What should teams validate before rollout?
Run representative tests, review failure scenarios and confirm the solution meets its documented security, reliability and operating requirements.
How can progress be measured?
Compare results against a baseline and track quality, operating effort, exceptions and service reliability over time.
Related reading: Carbon fee management, Azure service models and Enterprise architecture foundations.
