Configure Microsoft Dynamics 365 as a data pipeline source ​

Set up Microsoft Dynamics 365 as a data pipeline source to extract Sales, Customer Service, Field Service, and Marketing data from Microsoft Dataverse into your destination.

Use this guide to register a Microsoft Entra ID app, set up a connection, configure your pipeline, add objects, review sync behavior, and understand known limitations.

Features supported ​

The following features are supported when you use Microsoft Dynamics 365 as a pipeline source:

• Cloud connectivity: Connect to your Dataverse environment over HTTPS. On-prem agents aren't required. Refer to Limitations for deployment restrictions.
• Dynamic object discovery: Sync any table your connection can read, including custom tables. Refer to Supported objects for the objects Workato commonly syncs.
• Full sync and incremental sync: Supports full sync and incremental sync modes. Incremental sync uses Dataverse's Change Tracking feature on the tables your administrator enables it for. Refer to Sync modes for more information.
• Delete tracking: Detect deletions for supported objects and mark deleted records in your destination. Refer to Delete tracking for more information.
• Schema drift detection and handling: Detect and apply schema changes automatically with Auto-sync new fields, or keep the schema fixed with Block new fields.
• Field-level data protection: Replicate sensitive fields as is or hash them before they reach your destination.
• Configurable sync frequency: Schedule syncs on a time-based interval or with a cron expression. The minimum supported interval is 15 minutes.

Prerequisites ​

Complete the following requirements before you connect Microsoft Dynamics 365 as a data pipeline source:

• A Microsoft Dynamics 365 environment (Sales, Customer Service, Field Service, or Marketing) hosted on Microsoft Dataverse. Refer to Limitations for deployment restrictions.
• A Microsoft Entra ID app registration, and credentials for your chosen authentication method:
  • Client credentials: Client ID, Client secret, and Tenant ID from your app registration, plus an Application User in your Dataverse environment. Refer to Register the Workato app in the Azure Portal for setup steps.
  • Authorization code grant: Client ID and Client secret from your app registration. Refer to Register the Workato app in the Azure Portal for setup steps.

Supported connection types ​

Microsoft Dynamics 365 data pipelines support the following authentication methods:

• Client credentials: Connect with a Microsoft Entra ID app registration and an Application User in your Dataverse environment. Workato recommends this method because pipelines run on an unattended schedule and don't depend on an interactive user session. Refer to Register the Workato app in the Azure Portal for setup steps.
• Authorization code grant: Connect interactively with a Microsoft Entra ID app registration that has delegated permission to your Dataverse environment. Refer to Register the Workato app in the Azure Portal for setup steps.

Resource owner password credentials grant, supported by the Microsoft Dynamics 365 workflow connector, isn't available for data pipelines. Microsoft is deprecating password-based grants because they can't satisfy mandatory multi-factor authentication requirements.

Register the Workato app in the Azure Portal ​

Register a Microsoft Entra ID app registration in the Azure Portal before you connect Microsoft Dynamics 365 as a data pipeline source. The steps vary based on your chosen authentication method:

https://www.workato.com/oauth/callback

https://www.workato.com/oauth/callback

Return to Workato to finish setting up your connection.

Connect to Microsoft Dynamics 365 ​

Complete the following steps to connect to Microsoft Dynamics 365:

Configure the pipeline ​

Complete the following steps to configure Microsoft Dynamics 365 as your data pipeline source:

[minute] [hour] [day of month] [month] [day of week]

0 8 * * *

Supported objects ​

Microsoft Dynamics 365 data pipelines sync data from Microsoft Dataverse, the shared data platform behind Sales, Customer Service, Field Service, and Marketing (Customer Insights – Journeys). Workato dynamically discovers every table your connection can read, including custom tables, so you're not limited to the objects listed below. The following tables list commonly synced objects, grouped by app area. Each object syncs as a separate table in your destination.

Shared across apps ​

Sales ​

Customer service ​

Field service ​

Bookable Resource, Bookable Resource Booking, and Customer Asset ship with the base Universal Resource Scheduling capability. The remaining objects in this category require the Field Service app.

Marketing ​

Subscription List, Consent, Purpose, and Topic ship with base Dataverse. The remaining objects in this category require Customer Insights – Journeys (Marketing).

Marketing also writes to the shared Contact and Lead tables in the Shared across apps category rather than a separate marketing-only person record.

Custom tables and fields ​

Dataverse customers can create entirely new custom tables, not just custom fields on standard tables. Workato discovers custom tables the same way it discovers standard tables, and syncs them identically. Custom tables and fields use a publisher-defined prefix, such as new_ or cr123_. Workato preserves this prefix in the field and table names it syncs to your destination.

Sync modes ​

Microsoft Dynamics 365 data pipelines support full sync and incremental sync. The sync mode is configured per object when you add it to your pipeline.

Full sync ​

A full sync reads all available records for the selected object from Dataverse and overwrites the destination table. Objects without Change Tracking enabled always use full sync, because Dataverse doesn't provide a way to fetch only changed records for them.

Incremental sync ​

An incremental sync extracts only records created, updated, or deleted since the last successful run. Microsoft Dynamics 365 data pipelines use Dataverse's Change Tracking feature for incremental sync. The first sync requests a delta link for the object, and later syncs use that delta link to fetch only the changes since the previous run.

Change Tracking is a per-table setting your Dataverse administrator enables in the Power Apps maker portal, and it's permanent. Your administrator can't turn it off again. Workato uses full sync instead for any object without Change Tracking enabled, so expect some tables in the same environment to have it enabled and others not. This is normal.

Refer to the Supported objects tables for commonly synced objects, and to Microsoft's Change Tracking documentation to enable it for eligible tables.

Delete tracking ​

Delete tracking is per-object, and depends on the object's sync mode:

• Objects with incremental sync: Dataverse's Change Tracking feed includes a "removed" entry with the deleted record's ID whenever a tracked record is deleted. Workato marks these records as deleted in the destination and doesn't remove them.
• Objects with full sync: Dataverse doesn't expose a native delete signal for these objects. Workato compares each full sync against the previous run and marks records that no longer appear in Dynamics 365 as deleted in the destination, because it reads the complete object every time.

Refer to Synthetic columns for the destination column this sets, and to the Supported objects tables for which objects use each sync mode.

Schema and data type handling ​

The following considerations apply to schema and data types when you sync data from Microsoft Dynamics 365.

Custom fields ​

Custom fields appear identically to standard fields in the schema Workato discovers for each object. Select Auto-sync new fields in Configure the pipeline so new custom fields sync automatically. Dataverse administrators can add custom fields to any table at any time.

Picklist, State, and Status fields ​

Picklist, State, and Status fields sync as their underlying integer option value, not the display label shown in the Dynamics 365 UI. Look up the label for a specific value in your Dataverse environment's option set definitions if you need the corresponding text.

Lookup fields ​

Dataverse doesn't nest related records inside an object's data. A lookup field, including Customer and Owner fields, syncs as the GUID of the related record rather than an expanded object. Sync the parent object as its own table to look up the related record's details.

Money fields ​

Money fields sync as a single decimal value. The related transaction currency syncs separately, as a lookup field on the same record, rather than paired with each Money field.

Timestamps ​

Dataverse returns date and time fields in UTC through the Web API, regardless of the timezone shown in the Dynamics 365 UI. Workato preserves these values as returned.

Synthetic columns ​

Workato adds the following synthetic column to destination tables for objects that use incremental sync:

Sensitive data handling ​

Microsoft Dynamics 365 objects can contain significant personally identifiable information (PII), and Customer Service and Field Service objects can contain health or safety-adjacent information. The following objects commonly contain sensitive fields:

Use the Hash option in field-level data protection during pipeline configuration to protect PII before it reaches your destination. Refer to the Configure the pipeline steps for more information.

Limitations ​

The following limitations apply when you use Microsoft Dynamics 365 as a data pipeline source:

Cloud-hosted Dataverse only ​

Microsoft Dynamics 365 data pipelines connect to cloud-hosted Dataverse environments only. On-premises Dynamics 365 deployments that use AD FS for authentication, supported by the Microsoft Dynamics 365 workflow connector, aren't supported as a data pipeline source.

Marketing engagement data is not synced ​

Segment and Customer Journey definitions sync as ordinary tables, but most engagement data isn't available through the Dataverse Web API, including who's in a segment, email opens, clicks, page views, form fills, and journey-step events. This applies whether your environment uses legacy outbound marketing or real-time marketing (Customer Insights – Journeys). The pipeline can still sync segment and journey definitions, consent records, email and form templates, and Marketing's writes into the shared Contact and Lead tables.

Calculated, formula, and rollup fields can go stale between syncs ​

Values in these fields can lag behind their true value until the object's next full sync, on objects configured for incremental sync. Updates to the data these fields are based on don't reliably trigger a Change Tracking event. Configure a periodic full sync for objects where these fields matter.

Minimum sync frequency ​

The minimum supported sync interval is 15 minutes. You can't trigger syncs more frequently than this.