Integrations
Dynamics 365 AI agent integration for sales and service
A Dynamics 365 AI agent integration connects an agent to Dynamics 365 Sales or Customer Service through the Dataverse Web API. The agent turns a website or WhatsApp conversation into a lead, a contact update or a task for the right dealer, and answers your team's questions with CRM data next to your ERP.
Short answer
Yes. An AI agent connects to Dynamics 365 through the Dataverse Web API, as an application user in Microsoft Entra ID whose security roles decide what it may read and write. At vanRaam an agent creates leads, contact updates and dealer tasks in Microsoft Dynamics from website conversations. Microsoft's own Copilot and agents work inside Dynamics 365; a BeeManaged agent connects it to your website, ERP and service channels.
What is a Dynamics 365 AI agent integration?
It is a connection through the Dataverse Web API that lets an AI agent read CRM records and, where you allow it, create or update them. A visitor asks for advice or a brochure; the agent answers, collects the details and prepares a lead or task in Dynamics 365 for the right person, while every step is logged.
Dynamics 365 Sales and Customer Service store their data in Microsoft Dataverse. The Web API is the documented way for other software to read and write Dataverse tables.
Sources
- Microsoft Learn: Dataverse Web API overview (learn.microsoft.com)
What do Copilot and the agents in Dynamics 365 do?
Copilot in Dynamics 365 Sales summarises leads, opportunities and accounts for sellers. Microsoft also offers prebuilt agents: a Sales Qualification Agent that researches leads and drafts outreach, a Sales Research Agent for questions about sales data, and a Case Management Agent and Customer Intent Agent for service. They work inside Dynamics 365 and run on Copilot Credits.
These agents help your own sellers and service staff inside Dynamics 365. They are not the advisor a visitor talks to on your website in six languages, and they do not read your ERP for stock or delivery dates. That is the part a BeeManaged agent adds.
- Sales Qualification Agent: researches leads, judges whether they fit and can send outreach emails.
- Sales Research Agent: answers business questions in plain language from your sales data.
- Case Management Agent: helps create, update, resolve and close cases. Customer Intent Agent: discovers intents from past and current cases and conversations.
- Licensing (October 2026): prebuilt Sales agents need Copilot Credits; each Sales Premium licence includes 1,000 Copilot Credits. For Customer Service, the agents need separately purchased credits on Professional and Enterprise and Premium includes base Copilot Credit capacity.
- List prices per user per month, annual, excluding VAT (Microsoft Netherlands, October 2026): Sales Professional €56.30, Sales Enterprise €91.00, Sales Premium €130.00; Customer Service Professional €43.30, Enterprise €91.00, Premium €169.00.
Sources
- Microsoft Learn: Copilot in Dynamics 365 Sales (learn.microsoft.com)
- Microsoft Learn: agents in Dynamics 365 Sales (learn.microsoft.com)
- Microsoft Learn: autonomous agents in Customer Service (learn.microsoft.com)
- Microsoft Netherlands: Dynamics 365 Sales pricing (Dutch) (microsoft.com)
- Microsoft Netherlands: Dynamics 365 Customer Service pricing (Dutch) (microsoft.com)
Is there an official MCP server for Dynamics 365?
Yes. The Dataverse MCP server, which also covers Dynamics 365 data, has been generally available since 15 December 2025. It offers tools to query, create and update records, and respects Dataverse security roles. Only the Copilot Studio client is enabled by default; an administrator must enable other clients such as Claude or GitHub Copilot.
- Tools include read_query, create_record, update_record and search_data; delete_record only runs after explicit user approval.
- Billing: since 15 December 2025, Dataverse MCP tools used by agents built outside Copilot Studio are charged in Copilot Credits. Dynamics 365 Premium licences and Microsoft 365 Copilot users are exempt for Dynamics 365 data.
- Microsoft also offers a separate Dynamics 365 Sales MCP server; according to Microsoft, Claude Desktop is not supported there at this time.
- An MCP server arranges the connection, not the process: which website conversation becomes a lead, which dealer gets the task and who approves it remain your choices.
Sources
- Microsoft Learn: Dataverse MCP server (learn.microsoft.com)
- Microsoft Learn: Dataverse MCP server release plan (learn.microsoft.com)
- Microsoft Learn: Dataverse MCP FAQ (learn.microsoft.com)
- Microsoft Learn: manage which clients use the Dataverse MCP server (learn.microsoft.com)
- Microsoft Learn: Dynamics 365 Sales MCP server (learn.microsoft.com)
Copilot in Dynamics 365, a self-service connector or a managed agent: which fits?
Use Copilot and Microsoft's agents when your sellers and service staff want help inside Dynamics 365. A self-service MCP connector suits one person querying Dataverse from an AI assistant. Choose a managed agent when visitors, customers or dealers start the process on your website or WhatsApp and the CRM needs data from your ERP too.
| The vendor's own AI | Self-service MCP connector | Managed agent from BeeManaged | |
|---|---|---|---|
| Who it is for | Sellers and service staff inside Dynamics 365 | Individual users with their own AI assistant | Website visitors, customers, dealers and your team |
| Systems | Dynamics 365 and Dataverse | Dataverse, via your AI assistant | Dynamics 365 plus ERP, website, WhatsApp and email |
| Write actions | Inside Dynamics 365, per agent | Create and update tools, per client | Leads, contacts and tasks through an approval queue |
| Management | Microsoft | You | BeeManaged, with monitoring and audit log |
| Cost | Licence per user plus Copilot Credits | Copilot Credits outside Copilot Studio | From €0.35 per conversation; internal agents in consultation |
What does an AI agent do with Dynamics 365 in a manufacturing company?
It turns conversations into CRM work: a lead with the right details, an updated contact, a task for the dealer who serves that region, a case with the missing information filled in. Your team approves where it matters and answers questions with CRM and ERP data together. Five examples below.
| Process | Question or trigger | What the agent reads or does | What comes back |
|---|---|---|---|
| Lead from a website conversation | Visitor asks for a brochure or test ride | Collects name, need and location, creates or updates the lead or contact | A complete lead in Dynamics 365, with the conversation |
| Dealer routing | Which dealer serves this visitor? | Matches the location to the dealer, creates a task for that dealer | A dealer task with the request and the next step |
| Contact update | An existing customer gives a new phone number | Finds the contact and prepares the change | Updated after approval, logged |
| Service case intake | Customer reports a fault by chat or email | Asks for the missing details, prepares a case | A case with the details, ready for your service team |
| Questions from sales | Seller: what is open at this account, and what did they order? | Reads opportunities in Dynamics 365 and orders in your ERP | One answer from both systems, with sources |
How does vanRaam use an AI agent with Microsoft Dynamics?
On the vanRaam website an agent advises visitors in six languages on the right adapted bike and collects brochure and test ride requests. In Microsoft Dynamics it creates a new lead, updates an existing contact, creates a task for the dealer, or starts the brochure workflow or test ride follow-up. One conversation can trigger several of these actions.
How does the Dataverse Web API connection work technically?
The agent uses the Dataverse Web API, which implements OData version 4, with OAuth through Microsoft Entra ID. Your administrator registers an application in Entra ID and adds it as an application user in the Power Platform admin center, with a business unit and a custom security role. That role decides exactly which tables the agent may read and write.
- Server-to-server: the application user authenticates with a client secret or an X.509 certificate; no person has to be signed in.
- Rights (as of October 2026): security roles and business units determine access, and column security can hide sensitive fields. We ask for a custom role with read access by default and create or update rights only on the tables a process needs.
- Records are created with POST and updated with PATCH; every write by the agent waits in the approval queue in app.beemanaged.com until an employee approves it.
- Service protection limits apply per user, per web server: by default 6,000 requests and 20 minutes of combined execution time within a five-minute window, and 52 or more concurrent requests. Application users get the same limits.
- Data location: Dynamics 365 and Power Platform fall under the EU Data Boundary when your tenant and environments are in the EU and EFTA region and your billing address is in an EU Data Boundary country, with limited exceptions; according to Microsoft, data for the Sales agents may be processed outside your primary region. Our agents and data run in the EU, with no training on your data.
Sources
- Microsoft Learn: authenticate with OAuth to Dataverse (learn.microsoft.com)
- Microsoft Learn: manage application users (learn.microsoft.com)
- Microsoft Learn: security concepts in Dataverse (learn.microsoft.com)
- Microsoft Learn: service protection API limits (learn.microsoft.com)
- Microsoft Learn: EU Data Boundary (learn.microsoft.com)
How we set it up, in four steps
01
Choose one process
For example brochure and test ride requests from the website, with the rules for which dealer gets which lead.
02
Connect with a custom role
Your administrator adds the application user with a security role that covers only the tables the process needs.
03
Go live with approval
Leads, contact updates and tasks wait in the approval queue until a colleague approves.
04
Monitor and improve
Conversation review, audit log and a monthly report with the themes that came up, then the next process.
Pricing for a Dynamics 365 agent
Customer-facing agents cost from €0.35 per conversation. Setup is quoted up front (development €175 per hour), monitoring and the dashboard cost €250 per month, and a consultation package is €1,750. Internal agents are custom work, priced in consultation. Your Dynamics 365 licences stay as they are.
When don't you need BeeManaged for Dynamics 365?
If your sellers mainly want summaries, lead research and help inside Dynamics 365, Copilot and Microsoft's Sales agents cover that, depending on your licences and credits. BeeManaged makes sense when the conversation starts with a visitor or dealer outside your organisation, when CRM work needs ERP data, and when you want approval and monitoring arranged.
Updated · As of October 2026 · Author Roy Rutten, AI architecture and development
Frequently asked questions
Can an AI agent create leads in Dynamics 365?
Yes, through the Dataverse Web API, as an application user whose security role allows it. At vanRaam the agent creates leads, contact updates and dealer tasks in Microsoft Dynamics from website conversations.
What is the difference with Copilot and the agents in Dynamics 365?
Microsoft's Copilot and agents help your own staff inside Dynamics 365 and run on licences and Copilot Credits. A BeeManaged agent talks to visitors and dealers on your website and WhatsApp, combines Dynamics 365 with your ERP, and runs with an approval queue and audit log.
Is there an MCP server for Dynamics 365?
Yes, the Dataverse MCP server has been generally available since 15 December 2025 and respects security roles. Use by agents built outside Copilot Studio is charged in Copilot Credits, with exemptions for Dynamics 365 Premium and Microsoft 365 Copilot users.
Which rights does the agent get?
Only what its custom security role allows, set by your administrator in the Power Platform admin center: read access by default and create or update rights on the tables a process needs.
Does this also work with Business Central?
Business Central is Microsoft's ERP, with its own API and MCP server. We connect it the same way, through the official API with limited rights; our MCP guide shows its current status.
What does it cost?
Customer-facing agents cost from €0.35 per conversation, setup is quoted up front and monitoring with the dashboard costs €250 per month. Internal agents are custom work, priced in consultation.
Related
Want to know what an agent can do with your Dynamics 365?
Plan a conversation. We look at one process with you and tell you whether Copilot and Microsoft's agents, a self-service connector or a managed agent fits best.