Dynamics 365 Sustainability: Internal ESG Data Collection and Multilevel Approval Workflows

Tracked under Microsoft AI at Work roadmap ID 576783 and listed as generally available as of September 2026 for Worldwide (Standard Multi-Tenant) web environments, this update introduces a structured, governed workflow for harvesting internal ESG metrics directly from the employees who own the numbers. Rather than relying on ad-hoc chat messages and unverified attachments, sustainability practitioners can now orchestrate targeted data requests, assign deadlines, require documentary evidence, and route submissions through sequential, multilevel approval policies before the numbers ever touch downstream compliance calculations.

From Microsoft Sustainability Manager to Dynamics 365 Sustainability​

Before diving into the mechanics of the data collection engine, IT administrators and licensing specialists should take note of a recent branding shift. According to Microsoft Learn documentation, Microsoft Sustainability Manager has been officially rebranded as Dynamics 365 Sustainability.

Microsoft explicitly notes that this transition is a product name change only—core functionality, technical capabilities, service offerings, and underlying licensing structures remain unchanged. However, administrators working inside the environment or reading support guides will notice that some user interface labels, email references (which still occasionally refer to a tailored "MSM experience"), and documentation screenshots are still catching up to the new name.

More importantly for enterprise budget holders, while the roadmap entry indicates that the internal data collection feature is enabled for end users automatically within the left-hand navigation pane under the Data collection section, Microsoft Learn documentation specifies that the capability—along with multilevel approvals—is included in Microsoft Dynamics 365 Sustainability Premium. Organizations running non-Premium tiers or evaluating their licensing footprint will need to verify their entitlements before building operational workflows around it.

Solving the "Last Mile" of Internal ESG Data​

Why build a dedicated request-and-response portal inside an ERP sustainability tool when automated ingestion already exists? In any large enterprise, data ingestion falls into two distinct buckets:

1. Automated and Structured System Data: Metrics pulled directly via prebuilt provider connectors, Power Query flows, or bulk Excel template imports from ERP modules, smart meters, and fleet management platforms.
2. Human-Supplied Operational Inputs: Information that isn't digitized in a central database—such as localized facility refrigerant leaks, ad-hoc waste disposal receipts, regional HR social metrics, or governance policy attestations.

Historically, gathering that second bucket meant emailing spreadsheets back and forth, leaving sustainability auditors with no version control, weak accountability, and a nightmare during audit season. Microsoft’s internal data collection feature targets these internal data providers—facility managers, HR personnel, and business unit leads—by giving data managers a centralized command center.

Microsoft also draws a clean architectural boundary between internal and external contributors. Internal operational inputs flow through this native Data collection section, whereas external Scope 3 supply chain and partner inputs are segmented into a separate ESG Value Chain Portal. Keeping internal departmental requests separate from external supplier portals simplifies security governance and prevents external vendors from mingling with internal organizational hierarchies.

Summary: By separating human-driven internal inputs from both external supplier portals and automated system connectors, Dynamics 365 Sustainability gives administrators distinct governance controls for each data channel.

How the Internal Data Collection Workflow Operates​

The feature revolves around three primary personas: Data managers (or administrators) who orchestrate the campaign, Data owners who supply the figures and supporting documentation, and Approvers who validate the submissions.

[Data Manager]
   │ Creates Data Collection Plan / Targeted Request
   ▼
[Email Notification Sent]
   │ Links to tailored web submission experience
   ▼
[Internal Data Owner] (Facility Manager, HR, Business Unit)
   │ Enters response, adds comments, attaches evidence docs
   ▼
[Multilevel Approval Workflow] (Sequential: Level 1 -> Level 2...)
   ├─► [Approved] ──► Validated input flows to downstream ESG calculations
   └─► [Rejected] ──► Subsequent levels blocked; must be deleted & resubmitted

1. Orchestrating Plans and Requests​

Data managers can create individual targeted requests or scale the process across the enterprise using data collection plans. When configuring collection at scale, managers define:

• Data owners: The specific individuals or teams responsible for providing the metric.
• Reporting periods and due dates: Clear time boundaries so contributors know exact cutoffs.
• Approval workflows: Optional policies attached to the request to enforce validation before the data is committed.
• Automated reminders and status tracking: Plans allow managers to issue bulk requests, rely on automated reminders to nudge lagging contributors, and monitor submission statuses from a single view.

2. The Data Owner Submission Experience​

When a request is dispatched, the designated data owner receives an email containing a direct link to a tailored submission interface in the web app. Rather than navigating the full complexity of the Dynamics 365 Sustainability backend, the contributor sees a focused view of their assigned requests. From there, they can input their response data, write explanatory comments, and attach supporting evidence—such as PDF invoices, calibration logs, or signed attestations—to create an audit trail.

3. Sequential Multilevel Approvals​

For organizations preparing for strict regulatory frameworks—Microsoft highlights the European Union’s Corporate Sustainability Reporting Directive (CSRD) and the Global Reporting Initiative (GRI) as key targets—unverified self-reporting is a compliance hazard. To address this, MicrosoftLearn's procedural guidance outlines how administrators can enforce multilevel approvals.

Here is the step-by-step configuration and operational flow documented by Microsoft:

1. Assign Security Roles: Before configuring workflows, administrators must grant reviewers the Sustainability data approver security role so they have read/write permissions on approval record details.
2. Create an Approval Policy: In the left navigation pane under Approvals, select Policies and click New. After naming and saving the policy, administrators use the Approvers grid to select New Approval Policy Approver.
3. Define the Sequence: For each level, the admin assigns an individual or team and specifies their numerical position in the sequence (for example, sequence 1 for a regional facility supervisor and sequence 2 for a corporate sustainability director).
4. Link Policy to Requests: When creating a data collection request, the data manager selects the policy in the Approval policy to use for responses field.
5. Review and Act: Approvers navigate to the Approvals tab under the Approvals section, filter by the Approver column, and open the approval artifact to inspect both the submitted figures and any files in the Documents section. They then set the Approval status to Approved or Rejected and log notes in the Approval message field.

There is an important operational quirk that administrators and end users must understand: approvals are strictly sequential and uncompromising on rejections. While the first approver's record is marked Active, all subsequent approvers remain in a Pending state. If an approver rejects a submission, the workflow halts; subsequent records in the chain remain locked in the Pending state and cannot be approved. According to Microsoft’s documentation, a rejected response cannot simply be edited in place during review—it must be corrected via a fresh submission cycle.

Summary: The workflow combines bulk planning and email-driven contributor access with a rigid, sequential sign-off chain that prevents unverified numbers from polluting corporate ESG ledgers.

Critical Analysis: The Gap Between Software Workflows and Compliance Reality​

In its release plan, Microsoft states that standardizing internal submissions and applying governed workflows improves data accuracy, reduces manual effort, clarifies accountability, and accelerates preparation for CSRD, GRI, and other regulatory mandates. From an enterprise IT and governance standpoint, those are logical goals, and moving away from chaotic email chains is an undeniable operational upgrade.

However, veteran IT leaders and compliance officers should keep a few practical realities in mind:

• Tooling Assists Compliance; It Doesn't Guarantee It: While centralizing evidence attachments and sign-offs helps build an audit trail, software alone does not guarantee CSRD or GRI compliance. The accuracy of downstream emissions or social metrics still depends entirely on whether the facility manager typed the right kilowatt-hour or headcount figure into the form, and whether the approver actually opened the attached PDF invoice to verify it.
• Roadmap Status vs. Documentation Preview Caveats: Although Microsoft’s AI at Work roadmap lists feature ID 576783 as "Launched" with a General Availability date of September 2026, Microsoft Learn’s technical documentation for multilevel approvals (updated in October 2026) still carries a prominent banner warning that "some or all of this functionality is available as part of a preview release" and is subject to change or restricted functionality. In the Microsoft cloud ecosystem, it is not uncommon for core capabilities to hit GA while specific sub-features or documentation pages lag in preview status. Administrators should test the exact approval chains in a sandbox environment before relying on them for legally mandated disclosures.
• Role Management Overhead: Even though the feature is "enabled for end users automatically", it is not zero-touch for IT. Because data owners and approvers require specific Dynamics 365 security roles (such as the Sustainability data approver role) and access to a Premium-licensed environment, identity and access management (IAM) teams will need to map out Entra ID groups and role assignments across departments like HR and Facilities that may never have logged into a Dynamics 365 application before.

Actionable Takeaways for IT and Sustainability Admins​

If your organization is running Dynamics 365 Sustainability and preparing for upcoming ESG reporting cycles, here is how to evaluate and deploy the internal data collection workflow:

1. Verify Premium Licensing and Access: Confirm that your tenant holds Microsoft Dynamics 365 Sustainability Premium entitlements and check the left navigation pane for the Data collection and Approvals sections.
2. Audit Your Data Gaps: Identify which ESG metrics are currently gathered via manual spreadsheets or emails from internal teams (HR, legal, regional facilities) versus which should remain on automated Power Query or API connectors.
3. Provision Security Roles Early: Work with your Dynamics 365 administrators to assign the Sustainability data approver role (and corresponding data owner permissions) to department leads before launching a collection campaign.
4. Pilot a Two-Step Approval Policy: Test the sequential approval workflow with a small internal team first. Train contributors and reviewers on how rejections behave so no one is caught off guard if a rejected record locks subsequent approval steps close to a filing deadline.

By bringing structured ticketing, evidence attachments, and sequential sign-offs to internal ESG metrics, Microsoft is tackling one of the most frustrating bottlenecks in corporate sustainability reporting. It won't make regulatory audits painless, but for IT and sustainability teams tired of playing spreadsheet detective every quarter, it brings welcome order to the chaos.