Is your Dynamics 365 ready for agents? Find out in five days, on your own estate.
Most Dynamics 365 agent programmes stall before the first agent is switched on, and none of it is the AI. The version is below the MCP server's minimum, the environment is the wrong tier, the users who will invoke agents carry roles with segregation-of-duties conflicts, the posting setup the first-party agents depend on is incomplete in two legal entities, and nobody has priced the tool calls. The Agent Readiness & Controls Review finds all of that in five days on your own Finance & Supply Chain Management, and hands back a verdict, a gap list and a costed next step. It starts with a free ninety-minute check on one process, and it can continue as a one-week read-only pilot on your overdue purchase orders or your aged GRNI, with no change to anything in your ERP.
The ladder
- 01
Agent Readiness Check
One ninety-minute call · No cost, no obligation.
- 02
Agent Readiness & Controls Review
Five days on your environment · Fixed scope. Quoted before it starts.
- 03
Read-only pilot
One week on your own data · No change in Dynamics 365. Scoped from the review.
Three steps, each one small enough to say yes to
Every step ends in a document you keep, whether or not the next step happens.
- 01
Agent Readiness Check
One ninety-minute call
One process, your Dynamics 365 version and environment, the agents you are considering. You get a one-page playback with a red, amber or green verdict on readiness and the single thing that would move it.
No cost, no obligation.
- 02
Agent Readiness & Controls Review
Five days on your environment
Five deliverables: the readiness verdict against Microsoft's prerequisites; the data and customization gap list; the role and segregation-of-duties check for every user who will invoke an agent; the controls gap list in the terms your auditors use; and a credit forecast with a costed next step.
Fixed scope. Quoted before it starts.
- 03
Read-only pilot
One week on your own data
The PO Receipt Chase Agent or the Aged GRNI Investigation Agent runs read-only against a sandbox copy of your environment: it lists, groups and explains, and changes nothing. You see your overdue lines or your aged GRNI the way the agent sees them, before any write is on the table.
No change in Dynamics 365. Scoped from the review.
What the five-day review checks, item by item
Each line is something Microsoft documents as a prerequisite, a limit or a customer responsibility. Read on the date at the top of the page.
| Deliverable | What we check | Why it decides the outcome |
|---|---|---|
| Readiness verdict | Finance & Supply Chain Management version and quality update against the ERP MCP server's minimum (10.0.47, or 10.0.46 PQU-2, or 10.0.45 PQU-7); environment tier (Tier 2 or above, or a Unified Developer Environment; not a cloud-hosted environment); the MCP feature flag; the Allowed MCP Clients list. | Below the minimum or on the wrong tier, no agent can connect. The allowed-clients list is the first governance control and is usually still at Microsoft's defaults. |
| Data and customization gap list | Posting profiles, bank and tax setup per legal entity for the Account Reconciliation Agent; order links and planning data for the Procurement Agent; your X++ classes and ISV modules against what data and form tools can reach; custom controls form tools skip. | First-party agents inherit your setup and go noisy on incomplete posting profiles. Your own logic is invisible to agents until it is registered as an action tool. |
| Role and segregation-of-duties check | The roles, duties and privileges of every user who will invoke an agent; conflicts an agent would inherit; the System agent role and scoped roles for autonomous agent identities. | An agent acting for a user can do everything that user can do. Agent-only roles arrive in preview in October 2026 and still need a design per legal entity. |
| Controls gap list, in auditor terms | Approval before any write, read-back after it, the action ledger and its retention beyond Microsoft's default agent history, where data goes after the MCP server returns it (the agent client and the model), data policies and managed environments. | Microsoft provides no audit mapping for agent actions and states that data handling after the server depends on the client. Your auditors will ask; this is the answer written down. |
| Credit forecast and costed next step | Tool calls per transaction for the agents in scope, Copilot Studio versus other clients, the Finance Premium and Supply Chain Management Premium exemption, a spending ceiling; then the scope and length of activation or a pilot. | Copilot Studio bills a fixed rate per agent action; other clients are metered per tool call. The design decides the bill, and the CFO wants it before go-live, not after. |
Sources: Microsoft Learn, Use Model Context Protocol for finance and operations apps and Security for Dynamics 365 ERP MCP; Microsoft roadmap item 571677. The facts in full: the Dynamics 365 MCP server, fact by fact. Every agent with its status: the agent catalog.
Who asks for it, and what they get back
Four readers, four different documents out of the same five days.
CFO or controller
The cost per process before go-live, and which close exceptions an agent would actually clear on your setup.
Dynamics administrator or IT
Version, tier, feature flags, allowed clients and agent identities, checked against Microsoft's pages rather than a vendor deck.
Internal audit
The controls gap list: approvals, ledger, retention, data handling, roles. Written so it can be tested.
Your implementation partner
A scope they can run with. We do not replace the partner that owns your Dynamics 365; the review hands them a list.
Readiness, piloting, governance and audit, in detail
The articles behind each deliverable: what blocks activation, how to pilot narrowly, the governance gap, and making agents auditable.
AI account reconciliation in Dynamics 365: what the agent clears, and the part it hands back
Microsoft's Account Reconciliation Agent clears reconciliation exceptions in bulk across Dynamics 365 Finance. Here's what it handles well, the exceptions it hands back, and how to close that last gap.
Read more3 min read
AI collections in Dynamics 365: what the agent drives, and where the relationship stays human
Microsoft's Finance Agent brings AI to collections in Dynamics 365 — prioritising accounts, drafting outreach, surfacing risk. Here's what it drives well, where the customer relationship stays human, and how to make it run on your policy.
Read more3 min readAI on top of your ERP: the four layers, and which one actually moves your margin
AI on top of the ERP has become four different things sold to four different buyers. Here's how to tell them apart — and which layer actually moves your margin — on Microsoft Dynamics 365 and Business Central.
Read more4 min read
Business Central AI agents: what the Payables and Expense agents do, and where a custom build takes over
Business Central now ships AI agents — a Payables Agent that reconciles POs and an Expense Agent that checks reports for policy violations. Here's what they do, where they stop, and when a mid-market team needs a custom build.
Read more3 min readCodifying your procedures as governed business skills for Dynamics 365 agents
Microsoft's 'business skills' let you define your procedures as reusable, governed context for Dynamics 365 agents. Here's how to turn the way your business actually runs into skills an agent can use — and why that's the real work.
Read more3 min read
A Dynamics 365 agent can do anything the user can. Close that gap before you turn it on.
Microsoft's ERP Copilot plugin is GA — and an agent acting for a user can currently do anything that user can do. The role-based controls have no release date. Here's how to close the governance gap before you activate agents on Dynamics 365.
Read more3 min readWhy Microsoft's Dynamics 365 agents stumble on your customized F&O — and the last-mile fix
Microsoft's ERP agents work beautifully on standard Finance & Operations — and stall on the X++ and ISV customizations that make your estate yours. Here's the last-mile fix: exposing your logic as governed MCP Action tools.
Read more3 min read
AI Agent Readiness for Dynamics 365: are you actually ready to turn agents on?
Most teams that can't activate Microsoft's Dynamics 365 agents aren't blocked by the AI — they're blocked by data quality, role design, customizations and governance. Here's the honest readiness checklist.
Read more3 min read
Agent readiness on Dynamics 365, answered plainly
- What is a Dynamics 365 agent readiness assessment?
- A short review of whether your Finance & Supply Chain Management estate can run AI agents safely: version and environment against the ERP MCP server's prerequisites, the Allowed MCP Clients list, the roles and segregation-of-duties conflicts of the users who will invoke agents, the posting and master-data setup the first-party agents depend on, your customizations against what agents can reach, the controls an auditor will test, and the tool-call cost of the design. Ours takes five days and produces five documents.
- Is the readiness check really free?
- The first step is one ninety-minute call on one process, and it costs nothing and commits you to nothing. You get a one-page playback with a verdict. The five-day review is a fixed scope, quoted before it starts.
- Does the pilot change anything in our ERP?
- No. The read-only pilot runs an agent against a sandbox copy of your environment and it lists, groups and explains only. The PO Receipt Chase Agent shows your overdue lines by buyer; the Aged GRNI Investigation Agent explains your old accruals. No receipt is posted and no record is changed until a later, separately approved step.
- Which Dynamics 365 versions can run AI agents through the MCP server?
- Per Microsoft Learn, the dynamic ERP MCP server needs finance and operations apps version 10.0.47, or 10.0.46 with PQU-2, or 10.0.45 with PQU-7, on a Tier 2 or higher environment or a Unified Developer Environment. It is not supported on cloud-hosted environments. The review checks this first, because nothing else matters until it passes.
- Which agent platforms can connect to our Dynamics 365 by default?
- Microsoft's security documentation lists Copilot Studio, Visual Studio Code, Microsoft Cowork, Finance Agent and Finance Agent (Sydney) as allowed by default. Any other platform is registered in Entra ID and added to the Allowed MCP Clients form by your administrator. We check what is on the list and whether anything is there that nobody decided.
- What permissions does an agent have?
- The permissions of the identity it runs as. Microsoft states the MCP server adds no privileges and that a user can never do more through it than in the application client. That is also the risk: a user with a segregation-of-duties conflict hands it to every agent acting for them. The role check is the part of the review that most often changes the plan.
- Do you replace our Dynamics 365 partner?
- No. The partner owns the implementation; we review the estate for agents and hand back a list anyone can run. Where the next step is building an action tool or an agent, we do that on your environment and the partner keeps the ERP.
- What happens after the review?
- You get the costed next step in writing: a read-only pilot, the activation of a Microsoft agent on a fixed setup, an action tool for your own logic, or nothing, if the review says the estate is not ready. The verdict is the deliverable, not the sale.