Equip enterprise sales and service teams to surface Dynamics 365 records instantly inside any chat conversation.
7 min read
Updated October 2026
Enterprise teams running Dynamics 365 often deal with a frustrating loop: a customer asks about their case or opportunity, the rep Alt-Tabs to Dynamics, runs a search, copies the data, and pastes it back into chat. Multiply that by dozens of conversations a day and the lost time adds up fast.
The Dynamics 365 integration lets your AI agent query accounts, contacts, opportunities, cases, and activities on the fly. Reps stay in the conversation while the AI fetches exactly the data they need.
Available actions depend on your agent type and plan. Customer-facing actions serve customers. Internal team actions are for authenticated team use. AI CoPilot is Enterprise-only. Plus enables up to 5 actions per agent, Pro enables 40, and Enterprise has no enabled-action limit.
| Action | Description | Audience |
|---|---|---|
| Add Note | Add a note to a contact in Dynamics 365 | Internal team |
| Create Contact | Create a new contact in Dynamics 365 | Internal team |
| Create Task | Create a task for a contact in Dynamics 365 | Internal team |
| Get Account | Get account from Dynamics 365 | Customer-facing |
| Get Case | Get support case from Dynamics 365 | Customer-facing |
| Get Contact | Get contact from Dynamics 365 | Customer-facing |
| Get Opportunity | Get opportunity from Dynamics 365 | Customer-facing |
| List Activities | List activities from Dynamics 365 | Customer-facing |
| Update Contact | Update an existing contact in Dynamics 365 | Internal team |
Before connecting Dynamics 365, make sure you have:
https://yourorg.crm.dynamics.com)user_impersonation| Field | Description | Example |
|---|---|---|
| Instance URL | Your Dynamics 365 organization URL | https://yourorg.crm.dynamics.com |
| Access Token | OAuth bearer token from Azure AD | eyJ0eXAi... |
After setup, open your AI Agent widget and try these realistic queries:
More test phrases:
Azure AD tokens expire after one hour. Regenerate the token and update it in ChatSpark. Also verify that the app registration has the correct Dynamics CRM permissions.
Dynamics uses internal entity names (e.g., account,incident for cases). If a lookup fails, confirm that the record exists and your user has read access to that entity.
Make sure the Instance URL matches your production environment exactly, including the region suffix (e.g., .crm.dynamics.com for North America, .crm4.dynamics.com for EMEA).