Setup takes four steps: register an app in Microsoft Entra ID, give it access to your Dynamics environment, connect it in Invoca, and attach the skill to your agent.
Before you begin
- Microsoft Dynamics is enabled on your Invoca account. If you don’t see it in Manage Integrations, contact Invoca.
- You use a Dataverse-based Dynamics 365 app, such as Dynamics 365 Sales. Dynamics 365 Business Central isn’t supported.
- A Microsoft Entra ID admin is available to register an app and create a client secret.
- A Dynamics 365 admin is available to add that app as an application user in your environment and give it a security role.
- You have two values ready: your Entra tenant ID, and your Dynamics organization name (the
yourorgpart ofyourorg.crm.dynamics.com).
Connect Microsoft Dynamics
You connect with an app registration that you own in Microsoft Entra ID. The agent works as that app, not as a signed-in person, so you control its access through the security role you give it. In Microsoft Entra ID (admin):- Go to App registrations and create a new registration. Copy its Application (client) ID and your Directory (tenant) ID.
- Under Certificates & secrets, create a client secret and copy its value. Note when it expires.
- Open your environment and go to Settings > Users + permissions > Application users.
- Add a new app user for the app you registered.
- Give it a security role that can read, create, and update Leads and Contacts. A custom role with only these rights is safest.
- Open Manage Integrations and select Microsoft Dynamics.
- Add a new credential with your client ID, client secret, tenant ID, and organization name.
- Save, and confirm the connection shows as connected.
Fields the agent can write
The agent works with a fixed set of standard Lead and Contact fields. It can’t write custom columns or any other fields.
Last name is required to create a record. If your environment has required fields or business rules beyond these, saves may fail, so check them with your Dynamics admin before you go live.
Add the skill to your AI agent
- Open your agent in Agent Builder.
- Open the action where the agent should save caller details. CRM skills work on any action except Schedule Appointment.
- In the skill field, choose the Microsoft Dynamics skill, then choose your Dynamics connection.
- Test the agent with a test record, then publish it.
How the agent works with Microsoft Dynamics
The agent always searches Dynamics before it creates a record, and Invoca blocks any create that wasn’t preceded by a search. It saves details without asking the caller to approve each change, and only says something was saved after Dynamics confirms it.
The agent doesn’t delete records, and can’t change your environment’s settings or schema.
Data and privacy
- Your security role sets the limits. The agent can only do what the app user’s security role allows. Keep that role limited to Leads and Contacts.
- No reading back stored data. The agent only confirms details the caller gave, and never shares other people’s records.
- No made-up results. The agent only says a record was saved after Dynamics confirms it.
- No internal details. The agent doesn’t say record IDs or system terms to the caller.
- Every write is logged by Invoca for auditing.
- You stay in control. To stop access, remove the connection in Manage Integrations, delete the client secret, or remove the app user from your environment. Replace the client secret in Invoca before it expires.
Limitations
- Leads and contacts only. The agent doesn’t work with accounts, opportunities, activities, notes, or call transcripts.
- No email search. The agent finds records by phone or name, not email.
- Phone must match exactly. Phone search matches the number as it’s stored in Dynamics, so differently formatted numbers may not match. Store phone numbers in one consistent format.
- Fixed fields. Custom columns can’t be written.
- No deletes. The agent never deletes records.
Troubleshooting
Still stuck? Contact Invoca with the agent name and the time of the conversation.