Microsoft Dynamics 365
Sync data from your warehouse to Microsoft Dynamics 365 CRM entities via the Dataverse Web API. Keep your Dynamics 365 Contacts, Accounts, and Leads up to date with your latest customer data.
Prerequisites
- A Microsoft Dynamics 365 account with a valid license
- An Azure AD application with Dynamics CRM permissions
- Your Dynamics 365 organization URL (e.g.,
https://myorg.crm.dynamics.com)
Authentication
Dynamics 365 uses OAuth 2.0 via Microsoft identity platform.
- Click Connect with OAuth in SignalSmith
- Sign in with your Microsoft account
- Grant the requested permissions
- You are redirected back to SignalSmith
OAuth scopes: https://graph.microsoft.com/.default, offline_access.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Organization URL | Text | Yes | Your Dynamics 365 organization URL. Must match https://*.dynamics.com. |
| API Version | Text | No | Dataverse Web API version. Default: v9.2 |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Entity Name | Text | Yes | The Dynamics 365 entity to sync data to (e.g., contacts, leads, accounts) |
Supported Operations
Sync Modes
| Mode | Supported |
|---|---|
| Upsert | Yes |
| Insert | Yes |
| Update | Yes |
| Mirror | — |
Audience Sync Modes
| Mode | Supported |
|---|---|
| Add | Yes |
| Remove | Yes |
| Mirror | Yes |
| Upsert | Yes |
Features
- Field Mapping: Yes
- Schema Introspection: Yes — SignalSmith reads entity attributes from the Dataverse EntityDefinitions API
Common Entity Names
| Entity | Logical Name |
|---|---|
| Contact | contacts |
| Account | accounts |
| Lead | leads |
| Opportunity | opportunities |
| Case | incidents |
Use the plural logical name of the entity, not the display name.
Troubleshooting
Authentication failed: token expired or invalid
Microsoft OAuth tokens have a limited lifespan. Reconnect via OAuth to refresh the token.
Organization URL is incorrect
The URL must match the pattern https://*.dynamics.com. Find your correct URL in the Dynamics 365 admin center under Environments.
Entity not found
Verify the entity logical name (plural form, lowercase). Custom entities typically end with a publisher prefix (e.g., new_myentities).
Insufficient privileges
The authenticated user needs at least Read and Write privileges on the target entity. Check the user’s security role in Dynamics 365 Settings > Security.