Microsoft Dynamics 365
Microsoft Dynamics 365 CRM integration with bi-directional contact, opportunity, and activity sync.
Microsoft Dynamics 365
Microsoft Dynamics 365 CRM integration with bi-directional contact, opportunity, and activity sync.
When to Use This Connection
Use this connection when the user:
- Wants to connect their Dynamics 365 org to Demodesk so meeting data flows into CRM automatically
- Needs to configure field mappings between Demodesk meeting properties and Dynamics objects
- Wants meeting notes, AI summaries, and call recordings attached to the correct Dynamics opportunity
- Needs to troubleshoot sync issues between Demodesk and Dynamics 365
- Wants to set up conflict resolution rules for bi-directional data updates
What This Connection Does
Guide the user to Settings > Integrations > Microsoft Dynamics in their Demodesk dashboard at https://demodesk.com/manage/settings/integrations/microsoft-dynamics. The connection uses Dynamics 365's OAuth 2.0 authorization flow — the user clicks "Connect Dynamics 365" and authenticates with an account that has API access enabled (typically a Dynamics 365 admin).
Once authenticated, the integration syncs contacts, accounts, opportunities, and activities bi-directionally. Demodesk maps to both standard and custom Dynamics entities. Meeting attendees are matched to existing Dynamics contacts by email. If no match is found, Demodesk can create new contact and account records (configurable). Meetings are associated with open opportunities based on contact-to-opportunity relationships. Every completed meeting creates a Task or Event in Dynamics, including duration, attendees, and outcome. AI-generated meeting summaries are attached as Dynamics notes on the relevant opportunity or contact record.
For field mapping, navigate to the "Field Mapping" tab after connecting. Each Demodesk property (meeting title, duration, summary, action items, attendees) can be mapped to any Dynamics field, including custom fields. Set conflict resolution preferences: "Dynamics wins," "Demodesk wins," or "Most recent wins" (recommended). The sync runs in real time with sub-second latency. Failed syncs are logged in Settings > Integrations > Microsoft Dynamics > Sync Log for troubleshooting.
Anti-Pattern: "Map Every Field" Do not sync all available fields between Demodesk and Dynamics. Map only the fields your team actively uses. Syncing unused fields creates noise, increases API usage, and makes troubleshooting harder. Start with the default mapping and add fields as needed.
Data Sync
| Entity | Direction | Details |
|---|---|---|
| Contacts | ↔ Bi-directional | Matched by email; new contacts created in Dynamics if no match found |
| Accounts | ↔ Bi-directional | Linked via contact-account relationship in Dynamics |
| Opportunities | ↔ Bi-directional | Deal stage changes sync both ways; meetings logged to related opportunity |
| Activities | → Demodesk to Dynamics | Completed meetings create Tasks/Events in Dynamics |
| Tasks | → Demodesk to Dynamics | Action items from AI summaries created as open Tasks |
| Notes | → Demodesk to Dynamics | AI summaries and meeting notes attached to opportunity or contact |
| Custom Entities | ↔ Configurable | Direction depends on field mapping configuration |
Sync is real-time and event-driven. Batch re-sync can be triggered manually from the Sync Log screen.
Example Prompts
- "Connect my Dynamics 365 account to Demodesk"
- "Map the meeting summary field to a custom Dynamics entity"
- "Which Dynamics fields are currently mapped in my Demodesk integration?"
- "My Dynamics 365 sync is failing — help me check the sync log"
- "Set up conflict resolution so most recent data always wins"
Frequently Asked Questions
Related Skills & Connections
Want seamless CRM integration with real-time meeting context? Try Demodesk free