← Voice of Volge
VOLGE · VOICE OF VOLGEMicrosoft · 2026
OUR POINT OF VIEW · MICROSOFT SERVICE OFFERINGS

Agents inside the system of record

Agentic Dynamics 365 for ERP and CRM
Voice of Volge: Our Point of View on Microsoft Service Offerings · June 2026
In this point of view

Contents

: About Microsoft
01Executive summary
02Chapter one: Why the system of record is the highest-value, highest-blast-radius place to deploy agents
03Chapter two: The Dynamics 365 agent landscape and the layered architecture
04Chapter three: Controls: process integrity, segregation of duties, and the human-in-the-loop gate
05Chapter four: Reference architecture, adoption roadmap, and a maturity model
06Chapter five: The Business Applications leadership agenda
07Appendices
08Addendum: How Volge's forward-deployed engineers shall help: Business Applications (Dynamics 365)
Introduction · About Microsoft

About Microsoft

Microsoft, founded in 1975 by Bill Gates and Paul Allen, headquartered in Redmond, Washington, and led by chairman and chief executive Satya Nadella since 2014: is one of the world's most valuable companies (NASDAQ: MSFT). The Microsoft Cloud spans Azure, Microsoft 365, Dynamics 365, Microsoft Security, Microsoft Fabric and GitHub. Volge delivers across that estate through six alliance offerings.

What Volge delivers on Microsoft: six offerings

The offering this book covers: marked ◆: is Business Applications, delivered on Microsoft Dynamics 365.

Volge offeringWhat it coversAnchored on
Modern Workspace & E7Secure modern work on the E7 bundle; human-agent collaborationMicrosoft 365 · Copilot
Applied AIBuilding, governing and running enterprise AI agents and appsAzure AI Foundry
Zero Trust SecurityIdentity, threat protection and data governanceMicrosoft Entra · Defender · Purview
Business Applications ◆ERP, CRM and low-code, with in-process agentsDynamics 365 · Power Platform
Digital Product EngineeringAutonomous software engineering and CI/CDGitHub · GitHub Copilot
Cloud Infrastructure & OperationsCloud build, run and cost governance (FinOps)Microsoft Azure

Sources: Microsoft corporate and product documentation, 2025–26.

This book: Business Applications on Microsoft Dynamics 365

Microsoft Dynamics 365 is a portfolio of cloud ERP and CRM applications, Finance, Supply Chain, Sales, Customer Service, Field Service and Business Central, running on Dataverse and the Power Platform. With 2026 Release Wave 1 (18 March 2026), Microsoft reoriented it around agentic AI.

In the field in 2026

  • Enterprise ERP: Finance, Supply Chain, Commerce and Project Operations (plus Business Central for the mid-market)
  • CRM across Sales, Customer Service, Contact Center and Field Service, grounded in Dataverse
  • Prebuilt in-product agents: Finance, Account Reconciliation, Case Management, and the Sales Order and Payables agents
  • Build and orchestrate agents with Copilot Studio; Copilot Cowork brings ERP/CRM context to Microsoft 365 (GA 16 June 2026)
01
Chapter

Executive summary

Chapter 01 · Executive summary

The system of record is where agents stop drafting and start posting. A copilot that writes an email is a productivity feature; an agent that reconciles a sub-ledger, commits inventory, or promises a delivery date to a customer is acting on money and on the customer relationship directly. That is the prize and the hazard. The value of agentic automation is highest in the enterprise resource planning (ERP) and customer relationship management (CRM) layer, the period-end close, cash application, quote-to-cash, service throughput, and so is the cost of a wrong autonomous action, because a wrong action here writes a journal entry, depletes available-to-promise stock, or commits the firm to a service-level it cannot meet.

Microsoft moved the whole Dynamics 365 portfolio onto this footing in the space of a single release cycle. The 2026 Release Wave 1 plan, published on 18 March 2026, brings agentic AI across sales, service, finance, supply chain, human resources, and commerce, with general availability rolling out from April to September 2026 (Microsoft, 2026). Copilot has crossed from a prompt-based assistant into agents that execute multi-step workflows against live ERP data (Microsoft, 2026). The named agents are no longer demonstrations: the Account Reconciliation Agent and the Finance Agent in Dynamics 365 Finance, the Case Management Agent in Customer Service, the Scheduling Operations Agent in Field Service, and a natural-language agent builder in Business Central that turns described intent into sales-order and purchase-order automation (Microsoft, 2026).

The central finding. In Business Applications the hard part is process integrity and reconciliation, not the model. The winners embed governed agents into Dynamics 365 business processes, reusing the data-quality, identity, and human-in-the-loop controls established across this series, and treat in-product ERP agents and Copilot Studio orchestration as a deliberate layered architecture. The losers bolt a chatbot onto the CRM, grant it write access, and discover the blast radius in the general ledger.

The economics justify the discipline. Microsoft's internal benchmarks report up to 50 per cent faster invoice processing and a 25 to 30 per cent reduction in period-end close time in fully deployed setups (Microsoft, 2026). Independent analysis surfaced by MIT Technology Review puts AI-driven ERP processing-time savings at up to 45 per cent and decision-accuracy improvement at up to 60 per cent (MIT Technology Review, 2026). At Vera Bradley, a custom Copilot Studio agent integrated with Dynamics 365 Customer Service automates more than 2,000 support cases a month and has cut live-agent escalations by 25 per cent (Microsoft, 2026). And the cross-industry return holds: organisations running agents in production report an average return on investment of 171 per cent, rising to 192 per cent in the United States (McKinsey, 2025). The returns are real and conditional on production, and in the system of record, production is gated by controls, not by capability.

Five conclusions, developed in the chapters that follow.

First, value and blast radius rise together in the system of record. The same property that makes an ERP process worth automating, it touches the ledger, the inventory position, or the customer commitment, is the property that makes a wrong autonomous action expensive. Screen the agent portfolio on value and reversibility, never on value alone.

Second, the architecture is layered, not a single chatbot. In-product ERP agents execute inside the application boundary, under its permissions and posting controls. Copilot Studio orchestrates across systems and surfaces. Treat the two as distinct layers with distinct governance, and reserve cross-system orchestration for work the in-product agents cannot reach.

Third, controls are the deliverable, not the garnish. Segregation of duties, human approval gates for financial postings, reconciliation, and a complete audit trail are the engineering that makes an agent safe to grant write access. Business Central's agent runtime already enforces company, environment, and tenant boundaries and user permissions, with a timeline view of every step (Microsoft, 2026), but the enterprise still owns the design of the gates.

Fourth, master-data quality and integration debt decide the outcome. An agent reconciling against dirty master data or reaching across a brittle dual-write integration inherits every defect beneath it. The reconciliation problem is a data-quality problem first.

Fifth, identity and grounding are preconditions, not features. An agent acting on the ledger needs a first-class identity, least-privilege authority, and grounding in governed data: the controls established in the companion papers on identity, grounding, and oversight. Without them the agent cannot be scoped, audited, or revoked, which means it cannot be trusted with a posting key.

This paper takes the Microsoft Dynamics 365 estate as its lens, consistent with its position as the default Business Applications platform of the large enterprise. The companion papers in this series, on operationalising autonomous agents, on identity and the agent control plane, on data grounding, and on human oversight, supply the cross-cutting disciplines; this paper applies them to the place where agents touch money and customers directly.


02
Chapter

Chapter one: Why the system of record is the highest-value, highest-blast-radius place to deploy agents

Chapter 02 · Chapter one: Why the system of record is the highest-value, highest-blast-radius place to deploy agents

The takeaway

The ERP and CRM layer is the most valuable place to deploy agents and the most dangerous, for the same reason: it is where software actions become financial and customer-facing facts. A wrong draft is deleted; a wrong posting is reversed with a correcting journal entry, an audit note, and a conversation with the controller. The portfolio screen that works everywhere else, volume, rule density, digital nativeness, verifiability, needs a fifth axis here: reversibility. Value without reversibility is where agent programmes in the system of record detonate.

2.1 The blast radius is denominated in money and relationships

Outside the system of record, an agent's worst output is a bad document. Inside it, the worst output is a financial or commercial commitment. Three blast-radius classes recur across Dynamics 365 deployments.

Ledger actions. An agent that posts a journal entry, applies a payment, or completes a reconciliation has altered the financial record. The error is recoverable, every ERP carries reversal mechanics, but recovery is itself a controlled, audited event, and a wrong posting that propagates into a closed period or a filed statement is expensive to unwind.

Inventory and supply commitments. An agent that commits available-to-promise stock, releases a purchase order, or reschedules a field-service technician has moved a physical and contractual position. Over-commitment depletes service levels; a wrong reschedule strands a customer and a technician.

Customer commitments. An agent in Customer Service or Sales that resolves a case, issues a credit, or confirms a delivery date has made a promise on the firm's behalf. The blast radius here is reputational and contractual, and it does not reverse cleanly.

The design consequence is direct. The control requirement is set by the blast-radius class of the action, not by the sophistication of the agent. A simple agent with a posting key needs heavier controls than a sophisticated agent that only drafts.

Reversibility is the second axis, and it is the one most often missed. A reconciliation clearance is reversible, a correcting journal unwinds it, and the audit trail records both. A customer credit issued and communicated is not: the money has left, the customer has been told, and the reversal is a fresh negotiation rather than a system action. Two agents may carry the same nominal value, yet one belongs in supervised autonomy and the other never leaves the human-in-the-loop gate, purely on the reversibility of the action. The early portfolio sorts on this axis before any model is selected.

2.2 Where the value concentrates, by process

The value in the system of record concentrates in the high-volume, rules-bound, reconciliation-heavy spine of the enterprise: record-to-report, procure-to-pay, order-to-cash, and case-to-resolution. These are the processes where cycle-time compression converts directly into working-capital and service gains.

Process spine Agentic opportunity Value signature Blast-radius class
Record-to-report Account reconciliation, anomaly detection, close orchestration 25–30% faster close (Microsoft, 2026) Ledger
Procure-to-pay Invoice capture, matching, AP exception handling Up to 50% faster invoice processing (Microsoft, 2026) Ledger
Order-to-cash Sales-order creation, cash application, credit and collections Working-capital release; DSO compression Ledger + customer
Case-to-resolution Case triage, routing, knowledge-grounded resolution 2,000+ cases/month automated (Microsoft, 2026) Customer
Service scheduling Technician scheduling, dispatch optimisation Dispatcher load reduction; first-time-fix uplift Inventory + customer

Performance figures are vendor or named-customer benchmarks for fully deployed configurations; results vary with master-data quality and process maturity.

By the numbers. Up to 50% faster invoice processing and a 25–30% reduction in period-end close time in fully deployed Dynamics 365 setups (Microsoft, 2026). Independent ERP analysis: processing-time savings up to 45% and decision-accuracy improvement up to 60% (MIT Technology Review, 2026).

2.3 The reconciliation problem is a master-data problem

An agent that reconciles a sub-ledger to the general ledger is only as good as the data it reconciles against. Duplicate vendor records, inconsistent chart-of-accounts mappings, unmatched tax codes, and stale customer master data each surface in the reconciliation as an exception the agent cannot clear, or, worse, clears wrongly. The Account Reconciliation Agent in Dynamics 365 Finance suggests journal-entry detail, supports matching, and flags discrepancies for review, with routine matching handled by the agent and the finance team focused on exceptions and approvals (Microsoft, 2026). That division of labour only holds if the master data underneath is clean enough that the exception queue stays small and meaningful.

The practical sequence is unforgiving. Master-data remediation precedes agent deployment; it does not follow it. An agent deployed onto dirty master data does not fix the data: it amplifies the defect rate into the exception queue and erodes the trust that the human reviewers need in order to approve the agent's clearances. The data-grounding discipline from the companion paper in this series applies here at the level of the ledger: ground the agent in governed, deduplicated, reconciled master data, or accept that the reconciliation will not reconcile.

2.4 What this fixes downstream

The system of record is where agentic value is largest and most measurable, close-cycle compression, working-capital release, service throughput, and where the cost of an ungoverned action is highest. The screen that follows from this chapter is a five-axis screen: volume, rule density, digital nativeness, verifiability, and reversibility. Add reversibility, and the early portfolio sorts itself: reconciliation and AP matching, where actions are bounded and reversible, lead; autonomous credit issuance and unsupervised posting wait. The next chapter sets out the agent landscape and the layered architecture that lets the enterprise place each process at the right point.


03
Chapter

Chapter two: The Dynamics 365 agent landscape and the layered architecture

Chapter 03 · Chapter two: The Dynamics 365 agent landscape and the layered architecture

The takeaway

Dynamics 365 agents are not one product; they are two architectural layers that must be governed differently. In-product agents execute inside an ERP or CRM application, under its permissions, its posting controls, and its audit trail. Copilot Studio agents orchestrate across systems and surfaces, reaching ERP data through a controlled connector or the Model Context Protocol. Confusing the two, granting an orchestration agent the standing of an in-product agent, is how a chatbot ends up with a posting key. Design the layers on purpose.

3.1 The in-product layer: agents that execute inside the application boundary

In-product agents run inside the Dynamics 365 application that owns the process. They inherit that application's security model, its workflow and approval structures, and its audit trail, which is precisely why they are the safer place to put an agent that takes consequential action. The 2026 Release Wave 1 catalogue is organised by module.

D365 module Named agent (2026) What it does Primary blast radius
Finance Account Reconciliation Agent; Finance Agent Reconciles high-volume accounts, suggests journal detail, flags discrepancies; role-based finance intelligence across M365 Ledger
Finance / SCM Anomaly detection, automated matching Flags ledger and AP anomalies; matches invoices to receipts and orders Ledger
Customer Service Case Management Agent; Customer Intent Agent Triages, routes, and progresses cases; resolves knowledge-grounded queries Customer
Field Service Scheduling Operations Agent Evaluates availability and unscheduled work; proposes or makes assignments within guardrails Inventory + customer
Supply Chain AI picking, inventory rebalancing Drives picking, rebalancing, and order processing Inventory
Business Central Sales Order Agent; Payables Agent; custom agent builder Turns email or natural-language intent into structured sales and purchase documents Ledger + inventory

Source: Microsoft 2026 Release Wave 1 plans and module overviews, 2026. The Case Management, Customer Intent, and related Customer Service agents reached general availability in October 2025; the Business Central custom agent builder reached general availability in May 2026 (Microsoft, 2026).

The Field Service example shows the pattern at its cleanest. The Scheduling Operations Agent evaluates technician availability, existing bookings, and unscheduled work, then proposes optimised schedules, or makes assignments itself within defined guardrails, rather than waiting for a dispatcher to assign every job manually (Microsoft, 2026). The guardrails are the product of the application's own configuration, not a bolt-on. That is the in-product layer's advantage: the controls are native.

3.2 The orchestration layer: Copilot Studio across systems

Copilot Studio is the build-and-orchestration layer. It composes agents that span systems and surfaces, a website, Teams, Outlook, a third-party platform, and reaches Dynamics 365 data through governed connectors or, increasingly, the Model Context Protocol (MCP). The Vera Bradley deployment is the reference: a custom Copilot Studio agent integrated with Dynamics 365 Customer Service automates more than 2,000 support cases a month through a website agent, and has cut live-agent escalations by 25 per cent (Microsoft, 2026).

The orchestration layer earns its place where the work crosses an application boundary that an in-product agent cannot. A customer-facing website agent that needs case context from Customer Service, order context from Commerce, and a knowledge base from SharePoint is an orchestration problem. The governance consequence is that an orchestration agent operates outside the in-product security and posting controls, and so its write paths back into Dynamics 365 must be the narrowest possible, ideally read-and-propose, with the consequential write executed by an in-product workflow under the application's own approval gate.

Volge schematic

3.3 Business Central, natural-language agent building, with a runtime that governs

Business Central's custom agent builder lets organisations and partners describe an agent's behaviour in natural language and have the system generate the logic, rather than writing AL code for every automation (Microsoft, 2026). The Sales Order Agent interprets email content or natural-language instructions and transforms them into structured sales documents; the Payables Agent does the same for procurement (Microsoft, 2026). The capability is powerful precisely because it lowers the cost of putting an agent next to a posting process, which is exactly why the runtime underneath it matters.

The Business Central agent runtime enforces human-in-the-loop governance: agents respect company boundaries, environment boundaries, tenant isolation, and user permissions, and the runtime provides a timeline view of every step the agent takes (Microsoft, 2026). This is the control model the rest of the estate should be measured against: a generated agent is still bounded by the application's permission model and rendered fully auditable through the timeline.

3.4 Copilot Cowork: ERP context into the work surface, governed

Copilot Cowork reached general availability worldwide on 16 June 2026, shipping plugins for Dynamics 365 Sales, Customer Service, the ERP apps, and Microsoft Fabric (Microsoft, 2026). The Dynamics 365 ERP apps plugin connects Copilot Cowork to Finance, Supply Chain Management, Commerce, and the other ERP apps through the Dynamics 365 ERP MCP server, bringing ERP business data and process context into the conversational surface alongside email and documents (Microsoft, 2026).

The architectural reading is that Cowork extends the experience layer, not the execution layer. It brings ERP data and operational context to where employees already work, Teams, Outlook, Loop, while keeping Dynamics 365 as the controlled operational backbone (Microsoft, 2026). The principle to hold: Cowork surfaces ERP context broadly; the consequential write stays inside the in-product layer, under the in-product gate.

The governance cost of broad surfacing is data exposure, not posting risk. A plugin that brings ledger balances and customer records into a conversational surface widens the audience that can read sensitive financial and customer data, which makes data-scoping and the underlying permission model the control that matters here. The release ships metered cost controls and governance tooling for exactly this reason (Microsoft, 2026); the enterprise still owns the decision of which roles see which ERP context in the work surface, and should scope the plugin to the population that already holds the equivalent access inside the application.

3.5 What this constrains

The landscape is a layered architecture, and the layers carry different control postures. In-product agents are the default home for consequential action because the controls are native. The orchestration layer reaches across systems but must write back through the narrowest governed path. Cowork brings ERP context to the work surface without becoming an execution surface. The leadership question is no longer "which agent" but "which layer, with which write path, under which gate", and the gate is the subject of chapter three.


04
Chapter

Chapter three: Controls: process integrity, segregation of duties, and the human-in-the-loop gate

Chapter 04 · Chapter three: Controls: process integrity, segregation of duties, and the human-in-the-loop gate

The takeaway

In the system of record, the controls are the product. An agent is safe to grant write access only when four controls are demonstrably in place: segregation of duties that the agent cannot violate, a human approval gate on every consequential posting, reconciliation that proves the agent's actions tie out, and an audit trail that records what the agent did, on whose authority, and under what policy. These are not new controls invented for agents. They are the controls the enterprise already runs for its human workforce, extended to a non-human actor, and Dynamics 365 enforces most of them upstream of the posting engine already.

4.1 Segregation of duties applies to the agent as to a person

Segregation of duties (SoD) in Dynamics 365 is defined through duties and roles; when a role is created or assigned, the system checks whether the combination violates an active SoD rule, and incompatible access cannot reach the ledger (Rand Group, 2026). The decisive point for agents is that an agent is granted authority through the same security model. An agent assigned a role that combines, say, vendor creation and payment posting inherits a toxic combination exactly as a human user would, and the SoD engine should block it exactly as it blocks a human.

The error to avoid is treating the agent as exempt from SoD because it is "just automation." An agent with a posting key is an actor in the duties model, and it must be scoped so that no single agent holds an incompatible combination. Where a process genuinely requires two duties, split them across two agents, or across an agent and a human approver, so the separation survives.

A subtler failure is duty creep through orchestration. An orchestration agent that calls two in-product agents, one that creates a vendor, another that posts a payment, can reconstitute a toxic combination that neither in-product agent holds alone. The SoD engine sees two compliant agents; the composed workflow violates the principle. The control is to evaluate segregation at the level of the orchestrated process, not only at the level of the individual agent role, and to route any composition that crosses a duty boundary through a human gate. Dynamics 365 enforces SoD upstream of the posting engine for the roles it can see; the enterprise owns the analysis of what the orchestration layer composes on top.

4.2 The human-in-the-loop gate on consequential postings

The teaming model from the companion papers in this series resolves, in the system of record, to a single hard rule: a consequential financial posting requires human sign-off until evaluation evidence justifies otherwise. The Account Reconciliation Agent embodies the pattern, it handles routine matching and flags discrepancies, while the finance team owns the exceptions and the approvals (Microsoft, 2026). The agent proposes; the human posts, or approves the post.

Volge schematic

The gate is set by blast-radius class, not by uniform policy. High-value, low-volume, irreversible actions, a manual journal into a closed period, a customer credit above a threshold, stay human-in-the-loop indefinitely. High-volume, bounded, reversible actions, routine three-way match clearance, can migrate to human-on-the-loop as the audited error rate justifies it. Select per action; never apply one gate across all postings.

4.3 Reconciliation as the proof that the agent tied out

Reconciliation is not only a process the agent performs; it is the control that proves the agent's own actions are sound. Every agent that writes to the ledger should leave a reconciliation that a human or a second control can verify, sub-ledger to general ledger, agent-cleared items to source documents, agent-posted journals to approved proposals. The control question is always answerable: does the agent's work tie out, and can we prove it without trusting the agent.

This is where master-data quality (chapter one) and control design meet. A clean master-data foundation keeps the exception queue small enough that human reviewers can actually clear it; a reconciliation discipline keeps every agent action provable after the fact. Together they make the agent's output auditable rather than merely fast.

4.4 Identity, grounding, and the audit trail

The cross-cutting disciplines from the companion papers land here in concrete form.

Identity. Each agent carries a first-class identity, so its actions are attributable, its authority is scoped to least privilege, and it can be revoked instantly. An agent without a first-class identity cannot be held to SoD, cannot be audited, and cannot be trusted with a posting key: the companion paper on identity and the agent control plane sets out the mechanism.

Grounding. The agent acts on governed, reconciled master data and on knowledge sources the enterprise controls, not on whatever it can reach. The companion paper on data grounding sets the standard; in the system of record it is the difference between a reconciliation that clears and one that clears wrongly.

Audit trail. Every agent action is logged with what it did, on whose authority, and under what policy. Business Central's runtime already renders this as a timeline view of every step (Microsoft, 2026); Dynamics 365 Finance records electronic-signature approvals as verifiable audit entries (Rand Group, 2026). The audit trail is what makes the agent answerable to the same controls, internal audit, external audit, the regulator, that the human process already answers to.

4.5 The controls matrix

Control What it enforces Dynamics 365 mechanism Owned by the enterprise
Segregation of duties No agent holds a toxic duty combination Duties/roles SoD engine, checked at assignment Role design; agent scoping
Human approval gate Consequential postings require sign-off Workflow + electronic signature Gate policy per blast-radius class
Reconciliation Agent actions tie out and are provable Reconciliation agent + manual review Exception thresholds; review staffing
Identity Actions attributable, scoped, revocable First-class agent identity; least privilege Identity assignment; revocation drills
Grounding Agent acts on governed master data Dataverse; governed knowledge sources Master-data remediation; source curation
Audit trail Complete, attributable record of agent action BC timeline; F&O audit entries Retention; audit-readiness review

By the numbers. Companies automating accounts-payable processing with AI report per-invoice processing-time reductions of 70–80% and error-rate reductions exceeding 90% (industry analysis, 2026): gains that are only bankable behind a posting gate and a reconciliation that ties out.

4.6 What this resolves

The controls are the precondition for write access, not an afterthought to it. Segregation of duties, the human approval gate, reconciliation, identity, grounding, and the audit trail together make an agent safe to act on the ledger. Dynamics 365 enforces most of them upstream of the posting engine; the enterprise owns the design decisions, the gate policy, the agent scoping, the master-data remediation, the exception thresholds. With the controls in place, the architecture and roadmap of chapter four can climb the autonomy spectrum on evidence rather than hope.


05
Chapter

Chapter four: Reference architecture, adoption roadmap, and a maturity model

Chapter 05 · Chapter four: Reference architecture, adoption roadmap, and a maturity model

The takeaway

A durable agentic Business Applications architecture is layered and gated: experience, orchestration, in-product execution, and the system of record, with a governance plane spanning all of them. What ships from that architecture is staged: start where actions are reversible and the controls are native, prove an audited return, and extend to higher-blast-radius processes only as the gate evidence justifies it. Autonomy never outruns the controls, and in the system of record the controls are heavier than anywhere else in the enterprise.

5.1 The reference architecture

The architecture below anchors to the Microsoft estate and separates the layers so each can be governed and changed on its own. The governance plane, identity, SoD, audit, is not a layer the agent passes through; it spans every layer, because an agent action in any layer can reach the ledger.

Volge schematic

5.2 The quote-to-cash agent flow, with gates

Order-to-cash shows the architecture in motion, with the approval gate placed at the ledger boundary.

Volge schematic

5.3 The adoption roadmap: controls ahead of autonomy

The cadence is conservative on autonomy and aggressive on controls: the inverse of the failed-programme pattern.

Volge schematic

Stage one, first 90 days: assistive layer and the control foundation. Deploy Copilot and Cowork to a defined finance and service population for read-and-summarise work. Concurrently, stand up the control foundation: assign agent identities, configure SoD for the agent roles you will use, define the posting-gate policy by blast-radius class, and remediate the master data the first agents will reconcile against. The controls precede the first writing agent; they do not follow it.

Stage two, months three to nine: supervised agents on reversible processes. Deploy in-product agents on the reversible, high-volume processes first: account reconciliation, AP matching, case triage. Run them human-in-the-loop, fully instrumented, with every posting gated and every action reconciled. The objective is an audited production return on one or two processes, not a proliferation of pilots.

Stage three, months nine to eighteen: supervised autonomy and scale. For the proven processes, migrate routine, reversible actions from human-in-the-loop to human-on-the-loop as the audited error rate justifies it. Extend to adjacent processes. Introduce orchestration agents for cross-system work, keeping their write paths narrow. The objective is a governed agent portfolio across the process spine, supervised as a fleet.

A note on integration debt, because it determines whether stage three is reached at all. Many Dynamics 365 estates carry years of dual-write and middleware integration between finance and operations, between CRM and ERP, and into surrounding systems. An agent acting across that integration inherits its latency, its reconciliation gaps, and its failure modes: a sales-order agent that commits stock against an inventory position synchronised on a lag can over-commit cleanly and be wrong by the time the position settles. The MCP-based connectivity in Copilot Cowork and the in-product agents reduces the need for new bespoke integration, but it does not retire the integration debt already in place beneath the agent. Map that debt before deploying an agent that acts across it, and treat the integration boundary as a control surface in its own right: where an agent's action depends on data that crosses a lagging integration, gate the action until the position is confirmed.

5.4 An agentic Business Applications maturity model

Level Description Controls posture Teaming Typical outcome
0: Ad hoc Unsanctioned Copilot use; no agents in process No agent identity or SoD scoping Undefined Shadow-AI risk; no return captured
1: Assistive Sanctioned Copilot / Cowork for read-and-summarise Human identity; SoD for humans only Human as actor Modest productivity gain
2: Supervised in-product In-product agents on reversible processes Agent identity; SoD scoping; posting gate; reconciliation Human-in-the-loop on every posting First audited production return
3: Supervised autonomy Routine reversible actions human-on-the-loop; orchestration for cross-system work Full gate policy by blast-radius; estate-wide audit Human-on-the-loop; exception handling Close-cycle compression; throughput uplift
4: Governed agentic enterprise Agents across the process spine; narrow orchestration write paths Governance plane spanning all layers; continuous assurance Human supervises fleet; HITL retained for irreversible Process-level transformation in the system of record

Most large enterprises sit between Level 0 and Level 1 as of mid-2026. The named production references, Vera Bradley in service, fully deployed finance configurations reporting close-cycle compression, sit at Level 2 to 3. Level 4 is emergent.

5.5 Capability comparison: in-product versus orchestration

Dimension In-product agents Copilot Studio orchestration
Execution boundary Inside the D365 application Across systems and surfaces
Security model Native application permissions + SoD Connector / MCP scope; external to posting controls
Posting controls Native workflow and approval gates Must write back through in-product gate
Audit trail Native (BC timeline; F&O audit entries) Orchestration logs + in-product trail on write
Best for Consequential action on the ledger Cross-system, customer-facing, multi-source work
Governance burden Lower: controls are native Higher: write paths must be narrowed deliberately

By the numbers. Cross-industry agentic return on investment averages 171%, rising to 192% in the United States (McKinsey, 2025). At Vera Bradley, a Copilot Studio agent automates 2,000+ support cases a month and has cut live-agent escalations by 25% (Microsoft, 2026).

5.6 What this delivers

The architecture and the roadmap are inseparable from the controls of chapter three. The layered architecture keeps consequential action inside the in-product layer where the controls are native; the staged roadmap keeps autonomy from outrunning the gate evidence; the maturity model locates the enterprise and defines its next increment. The enterprise that builds the control foundation first, deploys on reversible processes first, and climbs on audited evidence is the enterprise that captures the close-cycle and throughput gains without writing a wrong journal into a closed period.


06
Chapter

Chapter five: The Business Applications leadership agenda

Chapter 06 · Chapter five: The Business Applications leadership agenda

The shift from Copilot-as-assistant to agents executing multi-step workflows on live ERP data is the defining Business Applications change of this cycle, and Microsoft has made it the organising principle of the Dynamics 365 portfolio with the 2026 Release Wave 1 (Microsoft, 2026). The evidence in this paper resolves to a short agenda for the chief information officer, the chief financial officer, and the Business Applications owner.

The capability is settled and shipping. The constraint is the enterprise's capacity to grant agents write access to the system of record without losing control of the ledger, the inventory position, or the customer commitment, and that capacity is a controls problem, not a model problem. The returns are large and conditional on production, and in the system of record production is gated by segregation of duties, the human approval gate, reconciliation, identity, grounding, and the audit trail.

Five questions for the leadership agenda. First, is the agent portfolio screened on reversibility as well as value, so that consequential, irreversible actions are not the first to be automated. Second, are in-product agents the default home for consequential action, with orchestration agents writing back only through the narrowest governed path. Third, is the master data remediated before the first reconciliation agent is deployed, or is the agent inheriting the defect. Fourth, is every consequential posting gated, every agent scoped against segregation of duties, and every action reconciled and audited. Fifth, does each agent carry a first-class identity that can be scoped, audited, and revoked.

Volge's work is in the execution. For most enterprises the platform decision is already made by existing Microsoft and Dynamics 365 commitments. The disciplines that convert that commitment into an audited return in the system of record, the layered architecture, the controls design, the master-data foundation, the staged roadmap, are where Business Applications programmes succeed or stall, and where Volge concentrates. We would welcome the chance to apply this framework to a specific finance, service, or supply-chain context in detail.


07
Chapter

Appendices

Chapter 07 · Appendices

Appendix A: Agent catalogue and capability comparison by D365 module

Module Named agent Layer Action class Default teaming GA status (as of June 2026)
Finance Account Reconciliation Agent In-product Ledger Human-in-the-loop Release Wave 1, 2026
Finance Finance Agent (role-based, M365) Experience / in-product Ledger (read + propose) Human-in-the-loop Release Wave 1, 2026
Customer Service Case Management Agent In-product Customer Human-on-the-loop GA October 2025
Customer Service Customer Intent Agent In-product Customer Human-on-the-loop GA October 2025
Field Service Scheduling Operations Agent In-product Inventory + customer Human-on-the-loop within guardrails Release Wave 1, 2026 (preview→GA)
Supply Chain AI picking / inventory rebalancing In-product Inventory Human-on-the-loop Release Wave 1, 2026
Business Central Sales Order Agent In-product Ledger + inventory Human-in-the-loop Release Wave 1, 2026
Business Central Payables Agent In-product Ledger + inventory Human-in-the-loop Release Wave 1, 2026
Business Central Custom agent builder In-product Varies Per agent GA May 2026
Cross-system Copilot Studio custom agents (e.g. Vera Bradley) Orchestration Customer; read-and-propose to ledger Human-on-the-loop GA
Work surface Copilot Cowork: D365 ERP apps plugin Experience Read ERP context N/A (read) GA 16 June 2026

Source: Microsoft 2026 Release Wave 1 plans and module overviews, 2026. GA dates as published; preview-to-GA items roll out April–September 2026.

Appendix B: Implementation and controls checklist

A minimum control set for deploying agents that write to the Dynamics 365 system of record. Drawn from Microsoft 2026 Release Wave 1 guidance, Dynamics 365 security and segregation-of-duties practice, and the cross-cutting disciplines of the companion papers in this series.

Master data and grounding

  • Master data (vendor, customer, chart of accounts, tax codes) is deduplicated and reconciled before the first reconciliation agent is deployed.
  • The agent is grounded in governed Dataverse data and curated knowledge sources, not in uncontrolled reach.
  • Exception thresholds are set so the human review queue stays clearable.

Identity and segregation of duties

  • Every agent carries a first-class identity, scoped to least privilege.
  • No agent holds a toxic duty combination; the SoD engine checks the agent's roles at assignment.
  • Where a process needs separated duties, they are split across two agents or across an agent and a human.
  • Credential revocation and an estate-wide kill-switch are tested, not assumed.

Approval gates and posting controls

  • Posting-gate policy is defined per blast-radius class (ledger, inventory, customer).
  • Consequential, irreversible postings require human sign-off, recorded by electronic signature.
  • Orchestration agents write back into the system of record only through an in-product approval gate.

Reconciliation and audit

  • Every agent action that writes to the ledger leaves a reconciliation that ties out independently.
  • Every agent action is logged with what, on whose authority, and under what policy (BC timeline; F&O audit entries).
  • The audit trail is retained to the same standard as the human process it automates.

Roadmap discipline

  • Reversible, high-volume processes (reconciliation, AP matching, case triage) are deployed before irreversible ones.
  • Migration from human-in-the-loop to human-on-the-loop is justified by audited error-rate evidence, per process.

Appendix C: Glossary

  • Account Reconciliation Agent. A Dynamics 365 Finance in-product agent that matches high-volume accounts, suggests journal detail, and flags discrepancies for human review.
  • Available-to-promise (ATP). The inventory position an order can commit against; committing it is a consequential supply action.
  • Blast radius. The scope of harm from a wrong autonomous action; in the system of record, denominated in money, inventory, or customer commitments.
  • Copilot Cowork. Microsoft's delegated-work experience in M365 Copilot; its Dynamics 365 ERP apps plugin brings ERP data and context into the work surface via the ERP MCP server (GA 16 June 2026).
  • Copilot Studio. Microsoft's build-and-orchestration layer for agents that span systems and surfaces.
  • In-product agent. An agent executing inside a Dynamics 365 application, under its native permissions, posting controls, and audit trail.
  • MCP (Model Context Protocol). An open standard for connecting agents to tools and data; the Dynamics 365 ERP MCP server exposes ERP data to Cowork.
  • Order-to-cash / quote-to-cash. The process spine from order intake through invoicing to cash application and reconciliation.
  • Record-to-report. The process spine from ledger posting through reconciliation to the period-end close and reporting.
  • Scheduling Operations Agent. A Dynamics 365 Field Service in-product agent that evaluates availability and unscheduled work and proposes or makes assignments within guardrails.
  • Segregation of duties (SoD). The control preventing one actor, human or agent, from holding an incompatible combination of duties; enforced in Dynamics 365 through the duties/roles model.
  • System of record. The authoritative ERP/CRM store of financial, inventory, and customer data: the general ledger and Dataverse.

Appendix D: Sources

This paper draws on the following, accessed June 2026. Figures are attributed in-text to their primary source and year. Where a statistic appears across multiple secondary outlets, the most authoritative attribution is given.

  • Microsoft: 2026 Release Wave 1 plans for Microsoft Dynamics 365, Power Platform, and Copilot Studio (18 March 2026); module overviews and Microsoft Learn release-plan documentation for Finance, Customer Service, Field Service, Supply Chain, and Business Central agents, 2026.
  • Microsoft: Dynamics 365 Finance Account Reconciliation Agent and Finance Agent documentation; internal benchmarks on invoice-processing and period-end-close time reduction, 2026.
  • Microsoft: Dynamics 365 Business Central custom agent builder, Sales Order Agent, Purchase Order Agent, and agent-runtime governance documentation, 2026.
  • Microsoft: Copilot Cowork general availability and Dynamics 365 ERP apps plugin (Microsoft Learn; 16 June 2026), 2026.
  • Microsoft Customer Stories: Vera Bradley designs efficiency and better customer experiences with Dynamics 365, 2026.
  • MIT Technology Review: Reimagining ERP for the agentic AI era (20 January 2026), on AI-driven ERP processing-time savings and decision-accuracy improvement.
  • McKinsey & Company: The state of AI in 2025: agents, innovation, and transformation, on agentic return on investment (171% average; 192% United States).
  • Rand Group: Dynamics 365 Finance and Operations security and segregation-of-duties practice, 2026.
  • Companion papers, Voice of Volge series, on operationalising autonomous agents, agent identity and the control plane, data grounding, and human oversight, 2026.

08
Chapter

Addendum: How Volge's forward-deployed engineers shall help: Business Applications (Dynamics 365)

Chapter 08 · Addendum: How Volge's forward-deployed engineers shall help: Business Applications (Dynamics 365)

The Volge engagement team

Volge delivers through one accountable team that runs from the boardroom to the production branch. Four roles carry the engagement, and they hold their remit from the first workshop to operational handover rather than handing off between phases.

Role What they own
Principal The client relationship and the account. Sets the engagement's business outcomes, the governance cadence, and the value tracking, and stays the single point of accountability throughout.
Architect The target architecture and the transformation roadmap. Sequences the work, sets the standards, and makes the platform, build-versus-buy, and control-design calls.
Principals The senior engineering leads. Each owns a workstream, makes the hard technical calls, sets the quality bar, and mentors the embedded engineers.
Forward-deployed engineers The embedded build. They sit inside the client's team, build and ship in the client's own environment, and own the last mile to production.
Volge schematic

The Principal holds the outcome, the Architect holds the design, the Principals hold the workstreams, and the forward-deployed engineers hold the keyboard, one team, accountable from strategy to shipped software.

The thesis of this paper is that the hard part in the system of record is process integrity and reconciliation, not the model, and that an agent earns a posting key only behind segregation of duties, a human approval gate, a reconciliation that ties out, and a complete audit trail. That is engineering work in the duties model, the workflow layer, and the master-data foundation, not a model-selection exercise. Volge is a deep-tech engineering firm whose Business Applications practice builds, governs, and operates Dynamics 365 estates, Finance and Supply Chain Management, Customer Engagement, Business Central, and the Dataverse, Power Platform, and Copilot Studio fabric beneath them, so that governed agents can act on the ledger, the inventory position, and the customer commitment without losing control of any of the three.

A forward-deployed engineer is a senior Volge engineer embedded in the client's own team. They configure and build inside the client's own Dynamics 365 and Power Platform environment, not a sandbox alongside it, and carry the work through to a governed production agent. The FDE owns the real-world business-applications engineering the rest of this paper describes: the process integrity and segregation-of-duties scoping, the approval gates on financial postings, the reconciliation and audit that prove an agent's work ties out, the integration and dual-write boundary treated as a control surface, and the application lifecycle management that moves a design from a controlled build to a supervised production fleet. They work the last mile, from a reference architecture on a slide to an agent posting under an approval gate in the client's general ledger, which is where Business Applications programmes most often stall.

The model is built to compound. Each embedded engagement feeds a loop: patterns proven in one client's estate harden into reusable accelerators, agent-identity templates, segregation-of-duties role sets, gate-policy patterns by blast-radius class, reconciliation tie-out checks, and reference configurations for the common process spines, which shorten the controlled path for the next. The relationship is structured around the client's outcome, the audited production return on a process spine, rather than a count of hours, so the firm and the client are pulled toward the same target: write access the enterprise can trust.

What Volge delivers

The practice spans the full Dynamics 365 estate end to end, with the controls treated as the deliverable rather than the garnish.

Capability Client outcome
Finance & Operations (ERP): general ledger and close, global compliance and tax, planning and analytics; Account Reconciliation Agent and Finance Agent grounded in Dataverse A close that compresses because routine matching is delegated and the finance team works the exceptions, with every agent clearance traceable to source records
Supply Chain Management: demand and supply planning, capacity-to-promise date protection, warehouse picking and rebalancing Order promises the inventory position can actually keep, and throughput gains in the warehouse that do not over-commit available-to-promise stock
Customer Engagement (CRM): Sales, Customer Service, Contact Center, Field Service; case triage, knowledge-grounded resolution, the Scheduling Operations Agent within guardrails An unbroken record from sales opportunity through service case to field work order and its settlement in Finance, with customer-facing commitments gated by blast-radius class
Business Central: all-in-one mid-market ERP; pre-built Payables and Sales Order agents, plus custom agents through the Agent Designer Agentic ERP at the mid-market tier, with each generated agent bounded by company, environment, and tenant boundaries and rendered auditable through the runtime timeline
Power Platform & Copilot Studio agents: Power Apps, Power Automate, Power Pages; interactive and autonomous trigger-driven agents, built and governed centrally Extension and orchestration on the same data model and governance boundary as the applications, so a tailored process and the agent that runs it never fragment the estate
Integration & dual-write: Dataverse-grounded connectivity, MCP-based access, the boundary between finance and operations and between CRM and ERP An integration boundary treated as a control surface, so an agent acting across a lagging position is gated until the position settles rather than committing cleanly and wrongly
ALM & governance: agent identity, segregation-of-duties scoping, approval-gate policy, reconciliation discipline, audit-trail retention, credit caps A control foundation that lets autonomy climb on audited evidence, with agent roles checked at assignment and consequential postings signed off by electronic signature

Volge's Dynamics 365 delivery approach

Volge schematic

The Volge difference

Process-integrity-first, not model-first. Volge starts where this paper does: with the screen on value and reversibility, the master-data remediation that precedes the first reconciliation agent, and the posting-gate policy set by blast-radius class. The agent is the last thing configured, not the first.

Segregation of duties evaluated at the orchestrated process. Volge scopes each agent so no single actor holds a toxic duty combination, and evaluates segregation across composed workflows: catching the duty creep where an orchestration agent calls two compliant in-product agents and reconstitutes a combination neither holds alone.

Reconciliation and audit as proof, not paperwork. Every agent action that writes to the ledger leaves a reconciliation that ties out independently and an audit entry recording what was done, on whose authority, and under what policy, so the agent's work is provable without trusting the agent.

Accelerators that shorten the controlled path. A reusable control foundation, agent-identity assignment, SoD role templates, gate-policy patterns by blast-radius class, and reconciliation tie-out checks, lets the estate reach a first audited production return on one or two reversible processes rather than a proliferation of pilots.

Capability to outcome

Volge schematic

The outcome figures above are directional and illustrative; actual results vary with master-data quality, process maturity, and the controls posture the enterprise is willing to fund.

A concrete first step. Volge runs a scoped engagement on a single process spine, record-to-report, procure-to-pay, order-to-cash, or case-to-resolution, that screens candidate agents on value and reversibility, surfaces the master-data and integration debt beneath them, and returns a posting-gate policy and a staged roadmap to a first audited production return. It is bounded, evidence-led, and designed to be read by the chief financial officer, the chief information officer, and the Business Applications owner together. We would welcome the chance to apply it to a specific finance, service, or supply-chain context.


Prepared by Volge · June 2026. This document is a point of view intended to inform executive decision-making. It is not legal, financial, or investment advice. Statistics are attributed to their sources and were accurate to the best of available knowledge as of June 2026; readers are advised that the agentic-AI field and the Dynamics 365 release cadence are moving rapidly, and figures and release dates should be reconfirmed before they are relied upon for investment or deployment decisions.

VOLGE

Voice of Volge: the firm's point of view on the technology it delivers. Sourced, year-stamped, and built to be handed to a board.

Volge is an independent deep-tech enterprise service provider and premier Microsoft delivery partner. That interest is disclosed; the analysis in this book is independently sourced.

Voice of Volge: Our Point of View on Microsoft Service Offerings · June 2026
Figures are sourced and were accurate as of June 2026. Not investment advice.