Iurie Diaconu, Founder, IDPROIT SRL. Former Microsoft Solution Assignment Specialist (SAS), CEE, 2023–2024.
Updated: 2026-10-03
Mid-2026 Dynamics 365 Copilot is an agent layer on the ERP, not a second system of record. Agents can classify, draft, and trigger. Posting still belongs to a named user.
Finance and operations agent management is a production-ready preview. It needs version 10.0.44 or later, a linked Dataverse environment, and the Copilot for finance and operations apps solution. Admins discover and configure agents. They do not get a free pass to post journals.
Source: https://learn.microsoft.com/
A business event, such as a confirmed purchase order, can trigger a Copilot Studio agent to notify a manager. The event is a trigger, not a posting.
Source: https://learn.microsoft.com/
Project Operations Approvals Agent, preview, reviews time, expense, and material entries against an uploaded policy. It marks them Ready for approval or Needs review. Classify mode still needs a project manager to approve. Classify and auto approve lets the agent approve low-risk entries.
Source: https://learn.microsoft.com/
In Dynamics 365 Customer Service, the formless Copilot workspace proposes emails, case updates, and case closure. Write actions run only after the representative approves. Public preview from April 2026.
Propose is not approve. The identity that approves is not the identity that proposed the change. SoD (Segregation of Duties) is the gate.
Do not enable Classify and auto approve on vendor payment, journal post, or release to the system of record. Use Classify, then a human approval in Dynamics 365 workflow.
The agent user in the deployment wizard is a service identity. It is not the approver.
Vendor payment, journal post, and release to the system of record. The orchestrator routes work. It does not post.
EU AI Act and Dynamics 365 Copilot Services for corporations
