CRM · Dynamics365 + Claude
Dynamics 365 MCP with Claude: Automate Leads, Contacts and Support Tickets
The short answer
Claude works with Dynamics 365 through the Model Context Protocol (MCP), an open standard that acts as a secure adapter between the two. Once connected with OAuth sign-in, Claude can read records and carry out approved actions such as creating contacts, updating lead status or logging sales activity, all requested in plain language.
What is Dynamics365?
Dynamics 365 is Microsoft's business platform that brings together customer relationship management (CRM), enterprise resource planning (ERP) and productivity apps. It helps teams run sales, marketing, customer service and operations in one place. Sales managers, service desks, marketing teams, finance and operations staff all use it to keep customer and business information organised and up to date.
How Claude connects to Dynamics365 through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a business tool. Through an MCP server or a direct API, Claude can reach Dynamics 365 without anyone copying data by hand or building a fragile custom link.
Once connected, Claude can typically look up accounts and contacts, review lead and opportunity records, summarise recent sales activity and open or update support cases. A team member can simply ask, for example, to find all open leads in a region that have not been contacted this month, and Claude can retrieve and organise them.
Access is controlled by the organisation. Sign-in uses OAuth, so Claude only sees what the signed-in user is allowed to see, and access can be limited to the least permissions needed. Consequential actions, such as changing a deal stage or closing a ticket, can require a person to approve them first, so people stay in charge throughout.
What you can automate
Lead intake and qualification
New enquiries from websites, events or email can be captured and checked against your rules. Claude can create lead records, flag missing details and suggest the right owner, so sales staff spend time on real conversations rather than data entry.
Contact creation and clean-up
Claude can create new contacts from business cards, emails or forms and spot likely duplicates. Staff can ask in plain language for a list of contacts missing a phone number or company name, then approve the updates in bulk.
Sales activity tracking
After calls or meetings, Claude can help log activities against the right account and opportunity. Managers can ask for a summary of what happened across a territory last week, without opening each record one by one.
Support ticket management
Service teams can have Claude open, categorise and route support tickets, or find cases that have been waiting too long. Agents can ask for the history of a customer's open cases before replying, which often shortens resolution times.
Pipeline reporting for leaders
Leaders can ask natural-language questions about the pipeline, such as which deals are stalled or which regions are behind target. Claude can pull the relevant records and present a clear, plain-English overview for the weekly review.
An end-to-end workflow: Web enquiry to qualified lead and support hand-off
TriggerA new enquiry arrives from the website contact form
Claude reads the enquiry and checks Dynamics 365 for an existing contact with the same email or company name.
If none is found, Claude creates a new contact and a lead record with the source and product interest filled in.
Claude scores the lead against the qualification rules your team agreed and suggests an owner based on region.
The suggested owner receives a notification in Microsoft 365 Teams with a short summary and the next recommended step.
When the lead is marked qualified, Claude opens a follow-up task and, if the enquiry is a service question, creates a support ticket in the service module.
A team member approves the final assignment before any customer-facing reply is sent.
OutcomeEnquiries are captured and assigned within minutes instead of hours, fewer leads are lost in inboxes, and service questions reach the right team with the context already attached. Results vary by organisation, but teams commonly report faster response times and cleaner records.
How we set it up
Free automation audit
We review how your sales, marketing and service teams work in Dynamics 365 today and identify the workflows worth automating first, at no cost to you.
Secure connection with OAuth sign-in
We connect Claude to Dynamics 365 through an MCP server or direct API, using OAuth sign-in so access follows your existing user permissions. Access is limited to the minimum needed.
Workflow design with approvals
We design the end-to-end process across Dynamics 365 and your other systems, such as Microsoft 365, ERP and ticketing, and agree which actions need a person's approval.
Testing on real cases
We test the workflows against past leads, contacts and tickets from your own records, check the results with your team and refine the rules until they match how your business works.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on how to use Claude with Dynamics 365 and how to review and approve its actions.
Who benefits
- Sales director
- Gets a clear view of the pipeline and recent activity through simple questions, and spends less time on administrative updates.
- Marketing manager
- Sees leads from campaigns arrive cleanly categorised, so follow-up is faster and campaign results are easier to measure.
- Customer service lead
- Can route and track support tickets more reliably and see a customer's history before replying.
- IT or operations head
- Keeps control of permissions, data access and audit trails while reducing manual data handling across departments.
Security and control
- Claude uses OAuth sign-in and only sees data the signed-in user is permitted to access.
- Access is set to least privilege, with clear limits on which records and actions Claude can use.
- People approve consequential actions such as deal changes, bulk updates and ticket closures before they take effect.
- Audit logs record what Claude read and changed, supporting review and accountability.
- Testing on your own records happens before launch, and monitoring continues afterwards.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can design their workflows to align with local data protection expectations, and we help you review them. In India, we design with the Digital Personal Data Protection Act, 2023 in mind. For organisations in the Middle East, including the UAE and Saudi Arabia, we take account of local data protection laws. Hosting region for any custom application can be chosen, in India, the United States, the United Kingdom or the European Union, to help meet your requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Dynamics 365 MCP server do?
The Dynamics 365 MCP server acts as a secure bridge between Claude and your Dynamics 365 data. It lets Claude read records and, where permitted, carry out actions such as creating contacts or updating leads. It follows the permissions of the signed-in user, so Claude can only work with what that user is allowed to access.
Is connecting Claude to Dynamics 365 secure?
Security depends on how it is set up. Using OAuth sign-in, least-privilege access, approval steps for important actions and audit logs gives your team clear control. We design and test these safeguards with you before launch, and monitor them afterwards.
What can Claude do with Dynamics 365 once connected?
Typically, Claude can look up accounts, contacts, leads and opportunities, create or update records, log sales activity and manage support tickets. Staff can ask for these things in plain language, and the scope is set by the permissions you approve.
How long does setup take?
It depends on how many workflows you want and how your data is organised. A focused first project often takes a few weeks from the audit to launch, including testing and team training. We agree a timeline during the free audit.
Which plan or permissions do I need?
You need a Dynamics 365 environment and a user account with the permissions required for the records you want Claude to use. The exact licences depend on your Microsoft agreement, so we check your current setup during the audit and recommend the least-privilege access needed.