5: Limitations & Important Notes

This page documents important constraints and limitations to be aware of when using Data Mission Sync.

Source Environment Limitations

A source Dataverse environment can only be connected to one Data Mission Sync profile. This is due to how Dataverse's Change Tracking API maintains state — each environment tracks changes independently, and multiple consumers would interfere with each other's delta links.

If you need to sync the same Dataverse environment to multiple Azure SQL databases, contact support to discuss alternative approaches.

Target Database Location

After the first synchronization, the target database location cannot be changed. This includes:

• Server address (yourserver.database.windows.net)

• Database name

• Schema name

If you need to change any of these settings, you must delete the profile and create a new one. Ensure your target configuration is correct before running the initial sync.

Note: You CAN update authentication credentials (Tenant ID, Client ID, Client Secret) at any time via Edit Target. This allows for credential rotation without recreating the profile.

Unsupported Table Types

The following Dataverse table types cannot be synchronized:

• Virtual Tables — These don't store data in Dataverse; they connect to external sources and don't support Change Tracking.

• Elastic Tables — These use Azure Cosmos DB storage and don't support the standard Change Tracking API.

Tables of these types will not appear in the table selection list when configuring your profile.

Change Tracking Requirement

Dataverse tables must have Change Tracking enabled before they can be synchronized. Tables without Change Tracking display a warning icon (⚠) in the Add Source Tables dialog.

Enabling Change Tracking requires Dataverse administrator privileges:

1. Go to Power Platform Admin Center or make.powerapps.com

2. Navigate to Tables → select your table → Properties

3. Enable 'Track changes' and save

After enabling, the table will appear without a warning in Data Mission Sync.

Unsupported Column Types

The following column types are skipped during synchronization:

• Image columns — Binary image data is not replicated to avoid large transfers

• File columns — File attachments are not replicated

These columns are omitted from the target schema entirely. All other column types are supported and mapped to appropriate SQL Server types (see Data Type Mappings).

Large Table Considerations

Very large tables (1 million+ records) may require special consideration:

• Initial synchronization may take multiple sync cycles to complete as data is transferred in batches

• Progress is checkpointed, so syncs resume from where they left off if interrupted

• After the initial load completes, incremental syncs process normally regardless of table size

• Consider scheduling large initial syncs during off-peak hours to minimize impact on your Dataverse environment

Live Updates Timeout

Live updates in the Profile detail view and All Runs view automatically disable after 5 minutes to conserve browser and server resources. When this happens:

• A notification appears indicating live updates have been paused

• A 'Re-enable' button allows you to resume live updates

• Data shown remains accurate as of when updates were paused

• Refreshing the page also re-enables live updates

This behavior is by design and does not affect synchronization operations, which continue running normally.

Additional Limitations

• Synchronization runs hourly by default; more frequent intervals are not currently available

• Each Quiet Time block is limited to a maximum of 8 hours to ensure data freshness

• The region selected during profile creation cannot be changed afterward

• Only Azure SQL Database is supported as a target; on-premises SQL Server and other databases are not currently supported