Connect Microsoft Dynamics 365 to Docket Marketing Agents
Last updated: July 21, 2026
Connect Dynamics 365 at the workspace level, then choose which CRM records each Marketing Agent can update after a conversation ends.
Use the Microsoft Dynamics 365 integration to carry visitor and conversation context into your CRM. Docket can create a Lead when no active Lead or Contact matches the visitor's email, update matching records, and optionally add Phone Call and Appointment activities.
In Docket, this integration appears as MS Dynamics CRM. This article uses Dynamics 365 when referring to the Microsoft product.
What the Integration Can Do
Dynamics record | Docket behavior |
|---|---|
Lead | Updates the first active Lead that matches the visitor's email. If no active Lead or Contact matches and Lead writeback is enabled, Docket can create a Lead. |
Contact | Updates the first active Contact that matches the visitor's email. |
Account | Updates the parent Account of a matched Contact. Docket does not search Accounts independently using the visitor's email. |
Opportunity | Updates up to 10 open Opportunities related to a matched Contact or the Contact's Account. |
Phone Call | Optionally creates a Phone Call activity after a conversation. |
Appointment | Optionally creates an Appointment when the visitor books a meeting through Docket. |
A visitor email is required for CRM matching. If both an active Lead and an active Contact use the same email, Docket can update both records when their write settings are enabled.
Before You Start
Docket access: You need the Admin role to connect a workspace integration.
Dynamics environment: Use a cloud Dynamics 365 Sales environment. On-premises deployments are not supported.
Dynamics access: Use a Microsoft work account that can approve the requested access and make changes in the target Dataverse environment.
Tenant ID: Have the Microsoft tenant ID for the Dynamics environment ready.
Dynamics domain: From the environment URL, copy the part between
https://and.dynamics.com. For example, usecontoso.crm4fromhttps://contoso.crm4.dynamics.com. You can find the URL in the environment details in the Power Platform admin center.
1. Connect Microsoft Dynamics 365

In Docket, open Settings.
Select the Integrations tab. The page is titled Apps and Integrations.
Find MS Dynamics CRM and select Connect.
Enter the Microsoft tenant ID and Dynamics domain when prompted.

Continue to Microsoft sign-in. Review the permissions requested for your organization, then approve access using an authorized account. Your tenant's consent policy determines whether an administrator must approve the request. See Microsoft's permissions and consent overview.
Return to Docket and wait for the integration card to show that it is connected.

The connected status confirms Microsoft authorization. Docket then completes the required Dynamics setup in the background. You do not need to import a managed solution file.
Note: The custom Docket fields created during setup are not automatically visible in the Dynamics 365 interface. A Dynamics administrator must open the appropriate solution in Power Apps, add the fields to the relevant form or view, then save and publish the customization. Until this step is complete, the fields exist in the underlying Dataverse schema but do not appear to CRM users.
2. Review Workspace Data Access
The connected Dynamics integration includes workspace Data Access settings for Lead, Contact, Account, and Opportunity. These are separate from the writeback settings configured for each Marketing Agent.

On the connected Dynamics card, select the settings icon.
Select Settings.
Under Data Access, review the Read setting for Lead, Contact, Account, and Opportunity.
Select Save.
3. Enable Sync for a Marketing Agent

Open Marketing Agents and select the agent you want to configure.
Open Analysis and Actions.
Under Post Call Actions, expand Sync to Dynamics 365.
Turn on Sync to Dynamics 365 for the agent.
The workspace connection makes Dynamics available. The agent-level switch determines whether this specific agent can run the Dynamics writeback workflow.
4. Choose Records and Map Fields
Expand a record type to review its saved field mappings and choose how each Dynamics field is updated.

Enable Lead if the agent should update matching Leads or create a Lead when no active Contact or Lead matches.
Enable any other record types this agent should update.
Expand a record type to review its field mappings.
Select a Docket Field and the corresponding Dynamics Field.
Choose the mapping Behavior:
Fill if empty writes the Docket value only when the Dynamics field has no value.
Overwrite replaces the existing Dynamics value with the Docket value.
Add or remove mappings as needed.
Select Save.
Reopen the section and confirm the intended write controls and mapping behaviors persisted.
5. Add Conversation and Meeting Activities
Docket creates activities related to each Lead or Contact updated during the writeback.

Expand Docket Activity to configure optional Dynamics activities:
Phone Call: Creates a Phone Call activity after a conversation. Its description includes conversation details and the transcript when available.
Appointment: Creates an Appointment when the conversation includes a Docket meeting booking. Docket adds the matching Dynamics user when the meeting owner's email belongs to an active Dynamics user.
Enable the activities you need, then select Save.
Troubleshooting
Problem | What to check |
|---|---|
The connection does not complete | Confirm the tenant ID and Dynamics domain, and verify the connecting Microsoft account can approve access and make Dataverse changes. |
Dynamics is connected, but the agent does not write | Confirm Sync to Dynamics 365 is enabled for that agent, the required record type is enabled, the mapping is complete, and the configuration was saved. |
No Lead or Contact is updated | Confirm the conversation contains a visitor email and that the matching Dynamics record is active. Docket checks active Contact and Lead records independently. |
Account or Opportunity is not updated | Confirm a Contact matched first. Account and Opportunity writeback follows the matched Contact's relationships. |
A field is missing or a mapping is invalid | Refresh the agent configuration page, reopen Sync to Dynamics 365, then replace any invalid mapping and save again. |
No Appointment is created | Confirm the conversation produced a Docket meeting booking, Appointment is enabled, and Docket updated a Lead or Contact. |
Contact Docket Support
If you need help with your Microsoft Dynamics 365 integration, contact Docket Support.