Microsoft Dynamics 365
Ask neil about CRM accounts, opportunities and cases using the records your team chooses to share.
Put this connection to work Set up Microsoft Dynamics 365 in the docs
Prepare an account handover from this Dynamics account and the cases I’ve referenced. What needs follow-up?
I’ll use the selected CRM summaries, keep their source references and flag missing context before suggesting next steps.
Selected Dataverse CRM captures
Account handover
- Account context and supplied case summaries
- Priorities with source references
- Follow-up questions and missing details
What’s connected.
Connect Dynamics 365 Sales and CRM through Microsoft Dataverse. Select accounts, contacts, leads, opportunities, cases and products, then ask neil questions with @ references to their captured summaries. Keep source permissions and the Seal sharing audience explicit.
Connection setup and permissions
This connector uses commercial Dataverse Web API v9.2 and Microsoft Entra application credentials. The application user’s role limits table, row and column access. The selected Seal audience controls who can read copied summaries; individual CRM user permissions are not mirrored.
It captures documented summary fields, source update time, original status codes and available display labels. Opportunity amounts retain currency context. Custom columns, relationships, owners, notes, attachments, activities and order lines are excluded.
Set up Microsoft Dynamics 365
- Register a Microsoft Entra application and create its Dataverse application user with a dedicated read-only role in the intended environment.
- In Settings → Integrations → Microsoft Dynamics 365, enter the environment home URL, tenant ID, application ID and secret value. Test, choose a CRM record type and select records by name or GUID.
- Enable content copying, choose the Seal audience and sync. Use @ references in neil to ask questions about the selected summaries.
Turn selected CRM records into a useful brief.
Choose the records needed for the question. neil uses shared captures and their sync time; a question about all open cases needs evidence covering all those cases.
- Prepare an account handover
- Summarise an account with the selected contacts and cases. Identify information still needed from the team.
- Review opportunities
- Compare supplied status, expected close dates and amounts with their currencies. Flag missing context.
- Explain customer issues
- Compare the selected case descriptions and priorities, then draft follow-up questions with source references.
Connection questions.
Is this the Finance & Supply Chain connector?
No. This is the Dataverse connector for Dynamics 365 Sales and CRM. Finance & Supply Chain and Business Central have different APIs and setup requirements.
Does neil query Dynamics live when I ask a question?
Questions with @ references use the selected saved captures. Ordinary Seal Scripts can use the existing integration read bindings for current selected-record summaries when Operational source entity sync is enabled.
Can a colleague see data they cannot open in Dynamics?
The chosen Seal audience can read shared copies through the application user’s access. Individual Dynamics permissions are not mirrored, so administrators must choose the audience accordingly. Opening the original requires the colleague’s source access.
Before it goes live.
Access and write-back
Reading records and writing back are separate decisions. Define which records are in scope, whose permissions apply and which changes require approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.