AI, in your work.

From the name change to practical scope

On November 3, Microsoft announced the addition of Microsoft Sustainability Manager to its ERP portfolio as Dynamics 365 Sustainability. The company aims to bring environmental information closer to financial and operational processes. Microsoft announcement.

The documentation clarifies that the name change itself leaves functionality, licensing and services unchanged. For customers, the practical question is what they can use in their environment and what remains an announced investment. Clarification on Microsoft Learn.

Capabilities with different statuses

The documentation distinguishes four areas. The availability of a general platform does not establish that every process that could be built on it is ready for deployment.

Licensing and permissions define usage

The guide requires a tenant license and a user subscription license (USL); Power Apps and Power Automate rights are limited to the Sustainability context. Essentials and Premium include Scope 1 and 2 calculations. Calculating Scope 3 categories 10, 11, 14 and 15 from activity data requires Premium; Essentials accepts those emissions as precalculated data. Plans and licensing.

MCP respects Dataverse roles and row-level security and supports querying, creating and updating records within those permissions. Microsoft documents charges for agents created outside Copilot Studio and exemptions for qualifying licenses. Access and cost therefore need to be assessed for the specific design. Dataverse MCP conditions.

What makes a calculation reviewable

The auditing guide explains how to enable change logging and inspect activity and record histories. As an implementation recommendation, that auditing should be accompanied by evidence linking the source file, units, factor and methodology to the result. A change history alone does not explain why a particular factor was selected. Auditing in Sustainability.

For purchased electricity, Microsoft distinguishes location-based and market-based methods and recommends obtaining consumption figures from bills or other purchase records. It also warns that Contoso demonstration data uses fictitious factors. A reproducible calculation requires checking both the input data and the applicable factor. Calculating Scope 2 emissions.

Synthetic example: one month of electricity

A Nexo teaching example with invented figures: a facility purchases 10,000 kWh of electricity in one month. Using an assumed factor of 0.20 kg CO₂e/kWh, the simplified calculation produces 2,000 kg CO₂e, equivalent to 2 tonnes. The factor is not an operational recommendation, and the result was not obtained by running the product.

To make this exercise reviewable, we propose retaining the following evidence and responsibilities.

Nexo's interpretation: integration is demonstrated through the process

Our interpretation is that bringing sustainability and ERP closer together could be useful if it improves the path from environmental data to an operational decision. The benefit will depend on configured connections, data quality and validation responsibilities. A name change alone does not demonstrate new automation or emissions reductions.

A focused pilot should make it possible to reconstruct an import and a calculation, check the agent's permissions and explain the cost of the complete process. If an assistant proposes fields or summarizes results, retaining its inputs and identifying who accepted the changes would support review. Preparing a report also does not automatically validate its figures or establish compliance with every applicable obligation.