D365 ERP agents are already changing how implementations get built, priced, and delivered.
A Microsoft Solution Engineer who covers enterprise accounts in the US recently joined one of our monthly D365contractors.com community calls. Former D365 end user, now working inside Microsoft on the enterprise side.
He demonstrated D365 ERP agents live: a Copilot Studio agent connected to a real D365 Finance and Supply Chain Management environment, creating sales orders and pulling trial balances from natural language prompts.
No forms. No navigation. Just a typed instruction and a completed transaction.
The technology is impressive. However, for IT leaders at manufacturing companies, the more important story is what the community discussion revealed about partner readiness, implementation pricing, and the questions you should be asking right now.
This blog is for the IT leader who is curious about the reality of ERP agents for D365. It is written from your side of the table. Because while your partner builds the SOW, you sign it. And the economics of that SOW are shifting faster than most partners are willing to admit.
What D365 ERP agents actually did on the call
This was a live demo on a real D365 Finance and Supply Chain Management environment. Specifically, the Microsoft engineer connected a Copilot Studio agent to D365 using the MCP server, which opens up roughly 600,000 actions within the system.
He typed a natural language instruction, and the agent:
- Created a sales order
- Looked up products
- Pulled a trial balance
No clicking through forms. No custom development.
He also shared a story from his own career as an end user. While working in the mining industry, one of their biggest headaches was creating bulk orders. They needed 100 sales orders at a time. That used to require custom X++ development, budget approval, and weeks of lead time. Now an agent does it from a typed prompt.
His exact words: “I thought it was BS. It’s not.”
For context, this is someone who reviews partner Statements of Work for Microsoft’s enterprise accounts. Essentially, he sees what partners are quoting, and he is already pushing back on pricing that does not reflect what D365 ERP agents can do.
When someone at Microsoft is telling partners their pricing models need to change, IT leaders should be paying attention.
BOOK A FREE DISCOVERY CALL
D365 ERP agents and your implementation budget
The engineer’s point was blunt: if AI tools can significantly reduce development time, why are partners still quoting the same hours?
In fact, he said some partners’ entire pricing structures for project costs “you could throw in the garbage.” That is a strong statement from someone who works at Microsoft and reviews SOWs for a living.
One of the independent consultants on the call reinforced this from the buyer’s side. She is currently evaluating nine partner RFP responses for a client’s multi-year D365 implementation. Her observation:
- Not one of the nine partners is pushing AI capabilities
- None have adjusted their development pricing to reflect what agents can do
- She expected a much stronger push and was surprised it was absent
For IT leaders, this raises an uncomfortable question. If you are about to sign a multi-million dollar SOW that prices custom development at traditional rates, are you overpaying for work that could be done faster with D365 ERP agents?
The answer is not necessarily yes for everything. However, the question deserves to be asked. The detailed partner evaluation framework in how to choose your D365 F&O implementation partner is a good starting point, and AI readiness should now be a core part of that conversation.
4 questions to ask your partner about D365 ERP agents
Based on the community discussion, here are four questions every IT leader should be asking their implementation partner right now.
1. What is your AI and agent strategy for D365 implementations?
This is the baseline question. Currently, if your partner cannot articulate how they are using Copilot Studio, MCP servers, or AI Foundry in their delivery model, they have not started thinking about it.
That does not necessarily make them a bad partner. However, it does mean they are not yet adapting to tools that already exist and already work. The Microsoft engineer on our call is asking this of every partner he works with. You should too.
2. How does this affect your development pricing?
If agents can handle tasks that previously required custom X++ development, are those hours reflected in your quote? For instance:
- Bulk order creation
- Certain data processing workflows
- Ad hoc reporting
The engineer shared his example from the mining industry: creating 100 orders used to require custom development. Now an agent does it. If your partner is still quoting development hours for work that agents can handle, ask why.
The questions in 5 questions to answer before you talk to any D365 F&O vendor will help you structure the broader evaluation.
3. What agent use cases have you actually deployed?
There is a significant difference between a partner who has a slide about AI and a partner who has built and deployed agents on real client projects. Instead of accepting vague claims, ask for specifics. Which processes? What were the outcomes?
During the call, the engineer described a real customer example: a document parsing workflow where the agent extracted data from a MILL weight kit through OCR, loaded it into Dataverse, and then populated specific D365 fields. All through Copilot Studio instructions. No traditional development required.
That is the kind of example you want to hear from your partner.
4. What does your Copilot Studio training plan look like for my team?
Importantly, the engineer’s advice to every partner he works with is that Copilot Studio training should be part of every implementation engagement.
If your partner’s training plan covers D365 navigation and standard processes but does not include how to build and use agents, you are being prepared for yesterday’s platform.
Building internal capability is always the goal. The assessment in how to build your internal D365 ERP team is a good place to start.
The use cases that should be on your radar
The community call surfaced several practical use cases where D365 ERP agents are already delivering value.
Return order processing. For example, the engineer described a scenario where:
- A customer email triggers an agent
- The agent communicates with the customer and pulls up their last five orders
- The customer identifies the order in question
- The return order is created automatically with case management triggered in the background
No forms, no manual data entry, no development.
Cross-entity inventory visibility. Similarly, an agent can see inventory across multiple legal entities without requiring the Inventory Visibility module. For manufacturing companies running multiple plants, that is a significant capability that previously required additional configuration and licensing.
Ad hoc reporting. Additionally, the analytics capability within the MCP framework allows your team to pull ad hoc reports directly from D365 in any file format. The engineer expects roughly 30% of F&O users will shift to Teams-based reporting. For C-suite stakeholders who want a quick answer without logging into D365, this changes the experience entirely.
Bulk data entry. Any process where your team is manually creating transactions in volume is a candidate for agent-based automation. The economics are worth comparing against Power Automate or hiring temporary data entry support. Learn more about how independent contractors’ D365 F&O capabilities are evolving with these tools.
Data governance matters even more now
The most sobering moment on the call came from a consultant who has been in the D365 space for 18 years.
Her point was direct: “You can do the best implementation in the world, but if they are not keeping their data clean six months afterwards, they are going to say Copilot is garbage. And it is not Copilot.”
Moreover, she mentioned that in 18 years, she could count on one hand the number of clients who had proper data governance in place. Two. That is the reality.
D365 ERP agents pull data directly from your system to make decisions and complete tasks. Consequently, if your vendor master has duplicates, your item master has inconsistent naming, or your inventory data does not match physical counts, the agent will confidently do the wrong thing. Fast.
An agent creating orders against dirty customer data is not a productivity gain. It is an automated way to make mistakes at scale.
This means data governance is no longer just an implementation readiness issue. It is an ongoing operational requirement. Additionally, every agent needs:
- Proper security roles configured around it
- FDDS (Function-based Data Security) applied
- An Entity ID assigned for governance
The governance layer is just as important as the technology layer. We covered why data readiness matters so much in why D365 F&O data readiness is the number one project killer. That blog is even more relevant now.
What is on the D365 ERP agents roadmap
The Microsoft engineer also shared several things on the roadmap that reinforce the urgency of getting ahead of this.
- Agent Zero is coming: a centralized hub for managing all agents with full governance. Think of it as the control center for every agent running in the environment.
- An agent for configuring F&O environments is actively being built. That alone should change how you think about implementation timelines and what your partner is quoting for configuration work.
- The MCP server is expanding to include the Data Management module, which will open up bulk import and export capabilities for migration and integration scenarios.
- Dataverse and F&O storage are being consolidated into a single model. For companies running Project Operations, Field Services, or CRM alongside F&O, this means faster data retrieval and more unified reporting.
These are not distant promises. In fact, some are already in preview. The 2026 Release Wave 1 plans confirm the direction Microsoft is moving.
Should you wait for this to mature?
No. The engineer was clear. Fundamentally, the technology is working today. It is going to get faster and cheaper. Waiting does not give you an advantage. It gives your competitors a head start.
Instead, make sure your implementation is built on a solid foundation that can take advantage of D365 ERP agents as they mature. That means:
- Clean data from day one
- Strong internal team capability so you are not entirely dependent on external consultants to build and manage agents
- A partner who is actively adapting their delivery model
If you are currently mid-implementation, start identifying use cases where agents could replace custom development or manual processes. The practical roadmap in D365 F&O post go-live optimization can help you structure where agent-based improvements fit into your priorities.
Ultimately, D365 ERP agents are changing the economics and the speed of what is possible. The IT leaders who get the best outcomes will be the ones who understand that shift early and ask the right questions before the SOW is signed.
BOOK A FREE DISCOVERY CALL
