Microsoft Sustainability Manager and Dynamics 365

How Microsoft Sustainability Manager captures emissions and ESG data on Dataverse — connectors, calculations, reporting, and integration with Dynamics 365.

Updated 2026-08-24

Carbon accounting and ESG reporting have moved from nice-to-have to compliance requirement for many organisations. Microsoft Sustainability Manager is Microsoft's solution — built on Dataverse, accessing data from across the Microsoft cloud (including Dynamics 365) and external systems. It's not part of Dynamics 365 directly but shares the platform foundation and integrates closely.

What Sustainability Manager does.

  • Data ingestion — from Microsoft and external sources.
  • Activity tracking — emission-generating activities (electricity use, fuel consumption, business travel, materials).
  • Emission calculations — applying emission factors to activities.
  • Scope categorisation — Scope 1, 2, 3.
  • Reporting — sustainability KPIs and compliance reports.
  • Targets and progress — track against reduction commitments.

The underlying data model is on Dataverse; the same patterns developers know.

Emission scopes.

  • Scope 1 — direct emissions from owned/controlled sources (company vehicles, on-site fuel combustion).
  • Scope 2 — indirect emissions from purchased electricity, heat, cooling.
  • Scope 3 — indirect emissions across the value chain (suppliers, business travel, employee commuting, product end-of-life, etc.).

Scope 3 is hardest to measure and often the largest share of total emissions.

Data sources.

  • Microsoft 365 telemetry — building energy data via Microsoft cloud.
  • Dynamics 365 Finance — financial transactions tagged by category.
  • Dynamics 365 Supply Chain — procurement, logistics, manufacturing energy.
  • IoT sensors — direct measurement of energy, water, emissions.
  • Excel uploads — for data not in connected systems.
  • Custom connectors — for industry-specific systems.

Connectors. Sustainability Manager includes pre-built connectors:

  • Microsoft Azure (cloud usage emissions).
  • Microsoft 365.
  • Dynamics 365.
  • Common third-party energy and travel platforms.

For external systems without connectors, file-based ingestion or custom Dataflow.

Calculation engine.

  • Activity data — raw measurements (kWh, gallons, miles).
  • Emission factor — kgCO2e per unit of activity.
  • Emission calculation — activity × factor = emissions.
  • Aggregation — by site, region, business unit, time.

Emission factors come from authoritative sources (EPA, IEA, country-specific bodies); pre-loaded by Microsoft and updateable.

Allocation rules. When activities don't directly map to entities:

  • Building energy allocated to departments by floor area.
  • Fleet emissions allocated to business units by usage.
  • Cloud emissions allocated to projects by consumption.

Allocation logic configurable; results flow to reporting.

Reporting.

  • GHG Protocol alignment — the industry-standard framework.
  • TCFD (Task Force on Climate-related Financial Disclosures) — disclosure framework.
  • CDP (Carbon Disclosure Project) — annual reporting.
  • CSRD (Corporate Sustainability Reporting Directive) — EU mandatory.
  • CSDDD (Corporate Sustainability Due Diligence Directive) — EU value chain.
  • SEC climate disclosures — US (where in force).

Each has specific requirements; Sustainability Manager produces aligned data.

Targets.

  • Science-Based Targets initiative — set targets aligned with climate science.
  • Net Zero commitments.
  • Interim targets — annual reductions.

Targets configured in the system; progress tracked.

Beyond emissions.

  • Water usage — withdrawal, consumption, discharge.
  • Waste — generation, recycling, diversion.
  • Biodiversity — emerging area.
  • Social metrics — pay equity, diversity, training (partially in scope).

The product expands beyond pure carbon to broader sustainability metrics.

Integration with Dynamics 365 specifics.

  • Procurement (F&O) — supplier emissions linked to purchases.
  • Logistics (F&O) — shipment emissions calculated.
  • Field Service (CE) — technician travel emissions.
  • Customer Engagement — customer-facing sustainability commitments.

For F&O customers, Sustainability Manager extracts financial and operational data automatically; less manual data wrangling.

Audit and assurance.

  • Data lineage — track where each data point came from.
  • Calculation transparency — recalculate from raw activity data.
  • Audit trail — changes to data, factors, calculations.
  • External assurance — auditors review for ESG reports.

Assurance-ready data structures matter as regulatory reporting becomes mandatory.

Common pitfalls.

  • Scope 3 underestimated. Effort to collect supplier-level data large; many organisations punt initially.
  • Data quality. Old, inconsistent activity data; emissions imprecise.
  • Allocation rules contested. "Why is my department's emission this high?" — be transparent about allocations.
  • Reporting bottlenecks. Annual report scramble; data not gathered through the year.
  • Targets without operational change. Targets set; no operational changes; targets missed.
  • Connectors expectations. Out-of-box covers some; many sources still need custom ingestion.

Operational rhythm.

  • Monthly data ingestion — activities captured.
  • Quarterly review — progress vs targets.
  • Annual reporting — formal disclosure.
  • Continuous improvement — emission reduction projects identified and prioritised.

Strategic positioning. Sustainability Manager is Microsoft's bet on ESG as a discipline that integrates with enterprise data. For organisations on Dynamics 365 / Microsoft cloud already, it's a natural extension; the data already lives in Dataverse-adjacent systems.

Alternatives:

  • Specialty ESG platforms (Persefoni, Watershed, Sphera) — purpose-built; sometimes deeper.
  • Generic reporting via Excel and Power BI — for small organisations.
  • Industry-specific platforms — for industries with unique factors (mining, oil and gas).

Sustainability Manager wins for breadth and integration; specialty platforms win for depth and certain industries. Choose based on:

  • Existing Microsoft footprint.
  • Reporting requirements (CSRD, CDP, etc.).
  • Internal data maturity.
  • Team capability.

For most mid-market and enterprise on Microsoft stack, Sustainability Manager is a credible default. The investment scales with reporting requirements; the payback is compliance and operational insight into emissions hotspots.

Related guides