Microsoft Fabric Link for Dataverse FAQ

This article provides information about frequently asked questions when you link Microsoft Dataverse to Microsoft Fabric.

General

What authentication methods are supported for Fabric link?

Fabric link supports three authentication methods when creating a connection:

• Organizational Account: Provide your credentials and save the connection.
• Service Principal: Provide Tenant ID, Client ID, and Key for authentication.
• Workspace Identity: Uses a Fabric-managed service principal bound to a specific workspace.

What happens when I unlink from Fabric?

When you unlink, the Fabric lakehouse is removed along with all shortcuts to your Dataverse tables.

Table support and limitations

Which Dataverse tables are selected by default when linking to Fabric?

During the initial Link to Fabric setup, the Select Entities step shows all Dataverse tables where the Track changes property is enabled. By default, all these tables are selected. You can clear any tables you don't want to sync before completing the wizard. Only selected tables are linked to Fabric and consume storage, so you can optimize costs by excluding tables you don't need. You can change your selection anytime after setup by using Manage Tables.

Which Dataverse tables aren't supported for Fabric link?

Any table that doesn't have change tracking enabled isn't supported. Additionally, certain Dataverse tables, such as postcomment, postregarding, postlike, post, and postrole, aren't available for customers to enable synchronization through Fabric link. In some cases, these tables might appear when Dataverse long term retention is enabled. If that happens, a subset or all records from these tables might be exported. This is expected behavior for long term retention scenarios.

Important

• These tables shouldn't be selected for synchronization.
• Their presence doesn't indicate full support for incremental sync.

Can I add or remove specific tables from Fabric link?

Yes, you can manage which tables are linked:

• Add more table links to Fabric by selecting Manage tables.
• To stop syncing specific tables, clear them in the Manage tables pane and then select Save
• After confirmation, shortcuts for unselected tables are removed from the Fabric Lakehouse and sync stops immediately.

Important

Removing a table doesn't delete the table in Dataverse; it only removes the OneLake shortcut and stops data sync.

Are elastic tables supported for Fabric link?

Yes, elastic tables are supported with Fabric link. Ensure that change tracking is enabled for elastic tables in Dataverse for the sync to happen.

Are Finance and Operations apps tables supported?

If your environment is linked to a Dynamics 365 finance and operations environment, the add tables option enables you to include tables from finance and operations apps. Finance and operations apps tables aren't autoselected when creating the initial Fabric link.

Are there system tables that are automatically synchronized and can't be unlinked?

Yes, certain system tables are automatically synchronized in Link to Fabric and can't be unlinked by users. Examples of these system tables include:

• bot
• msdyn_copilotknowledgeinteraction
• desktopflowmodule
• flowmachine
• flowmachinegroup
• workflow

These tables are essential for system functionality and are always included in the synchronization process.

Microsoft provided add-ins and table selection

Fabric link table selection is also dependent on Microsoft provided add-ins such as Business Process Advisor (BPA) and Customer Insights - Journeys. These products use the same pipeline to export data from Dataverse to provide transformed insights.

The tables that you can't unselect depends on which add-on products you enabled. When you enable an add-in (for example, Customer Insights - Journeys), the specific tables required by that add-in are added to the entityanalyticsconfig table in Dataverse.

Any table that has isenabledforadls set to true in the entityanalyticsconfig table can't be selected from the Fabric link.

What happens when I add a new column to a linked table?

If a new column is added to a table that's already part of the profile (metadata change), you can use the Refresh Fabric tables option from the command bar to update the change in Fabric. The update occurs after the next table data change is triggered.

Data Synchronization

How long does initial data synchronization take?

Initial sync time depends on several factors including table size, number of updates and transactions happening in the environment, number of tables, and row count. The data is converted to delta parquet format during this process. When you open Fabric Lakehouse, the links appear as unidentified until the initial sync is completed.

How often is data refreshed in Fabric?

When the initial sync is complete, the system continuously refreshes updates in Dataverse in the lakehouse. Incremental updates typically take up to one hour to appear, though actual timing depends on table size, number of updates and transactions happening in the environment, number of tables, row count, and system load periods.

Why am I seeing differences in `SinkModifiedOn` and `ModifiedOn` columns?

This is expected behavior. ModifiedOn is the date and time a record was last changed in Dataverse, while SinkModifiedOn is the date and time the record was written to the Dataverse data lake from where Fabric shortcuts point to. SinkModifiedOn is typically later than ModifiedOn, and the difference depends on factors such as batch size, system load, and the number of records being processed.

Important

In the case of long-running transactions in finance and operations apps, a record might be synchronized multiple times to ensure no data loss. In this scenario, SinkModifiedOn reflects the last synchronization time, not the first. For example, if a record is synced 10 times within an hour, SinkModifiedOn shows the time of the 10th sync even though the data was available from the first sync itself. Use caution when building latency reports based on the difference between SinkModifiedOn and ModifiedOn, as it can give a misleading impression of actual data availability.

Limitations and Errors

What are the limits for Fabric Link?

If you have more than 2,000 active Dataverse tables, Link to Fabric can fail with an error.

Can I link existing Azure Synapse Link profiles to Fabric?

You can link your existing Azure Synapse Link for Dataverse profiles with Fabric if you select the Enable Parquet/Delta lake option. However:

• Existing profiles where the data is saved as CSV files can't be linked to Fabric.
• Azure Synapse Link profiles secured with managed identities currently can't be linked to Fabric.

See also

Link to Microsoft Fabric

Troubleshooting common issues with link to Fabric

Work with Dataverse data and generate Power BI reports

This article provides information about frequently asked questions when you link Microsoft Dataverse to Microsoft Fabric.

Fabric link supports three authentication methods when creating a connection:

• Organizational Account: Provide your credentials and save the connection.
• Service Principal: Provide Tenant ID, Client ID, and Key for authentication.
• Workspace Identity: Uses a Fabric-managed service principal bound to a specific workspace.

When you unlink, the Fabric lakehouse is removed along with all shortcuts to your Dataverse tables.

During the initial Link to Fabric setup, the Select Entities step shows all Dataverse tables where the Track changes property is enabled. By default, all these tables are selected. You can clear any tables you don't want to sync before completing the wizard. Only selected tables are linked to Fabric and consume storage, so you can optimize costs by excluding tables you don't need. You can change your selection anytime after setup by using Manage Tables.

Any table that doesn't have change tracking enabled isn't supported. Additionally, certain Dataverse tables, such as postcomment, postregarding, postlike, post, and postrole, aren't available for customers to enable synchronization through Fabric link. In some cases, these tables might appear when Dataverse long term retention is enabled. If that happens, a subset or all records from these tables might be exported. This is expected behavior for long term retention scenarios.

Important

• These tables shouldn't be selected for synchronization.
• Their presence doesn't indicate full support for incremental sync.

Yes, you can manage which tables are linked:

• Add more table links to Fabric by selecting Manage tables.
• To stop syncing specific tables, clear them in the Manage tables pane and then select Save
• After confirmation, shortcuts for unselected tables are removed from the Fabric Lakehouse and sync stops immediately.

Important

Removing a table doesn't delete the table in Dataverse; it only removes the OneLake shortcut and stops data sync.

Yes, elastic tables are supported with Fabric link. Ensure that change tracking is enabled for elastic tables in Dataverse for the sync to happen.

If your environment is linked to a Dynamics 365 finance and operations environment, the add tables option enables you to include tables from finance and operations apps. Finance and operations apps tables aren't autoselected when creating the initial Fabric link.

Yes, certain system tables are automatically synchronized in Link to Fabric and can't be unlinked by users. Examples of these system tables include:

• bot
• msdyn_copilotknowledgeinteraction
• desktopflowmodule
• flowmachine
• flowmachinegroup
• workflow

These tables are essential for system functionality and are always included in the synchronization process.

Microsoft provided add-ins and table selection

Fabric link table selection is also dependent on Microsoft provided add-ins such as Business Process Advisor (BPA) and Customer Insights - Journeys. These products use the same pipeline to export data from Dataverse to provide transformed insights.

The tables that you can't unselect depends on which add-on products you enabled. When you enable an add-in (for example, Customer Insights - Journeys), the specific tables required by that add-in are added to the entityanalyticsconfig table in Dataverse.

Any table that has isenabledforadls set to true in the entityanalyticsconfig table can't be selected from the Fabric link.

If a new column is added to a table that's already part of the profile (metadata change), you can use the Refresh Fabric tables option from the command bar to update the change in Fabric. The update occurs after the next table data change is triggered.

Initial sync time depends on several factors including table size, number of updates and transactions happening in the environment, number of tables, and row count. The data is converted to delta parquet format during this process. When you open Fabric Lakehouse, the links appear as unidentified until the initial sync is completed.

When the initial sync is complete, the system continuously refreshes updates in Dataverse in the lakehouse. Incremental updates typically take up to one hour to appear, though actual timing depends on table size, number of updates and transactions happening in the environment, number of tables, row count, and system load periods.

This is expected behavior. ModifiedOn is the date and time a record was last changed in Dataverse, while SinkModifiedOn is the date and time the record was written to the Dataverse data lake from where Fabric shortcuts point to. SinkModifiedOn is typically later than ModifiedOn, and the difference depends on factors such as batch size, system load, and the number of records being processed.

Important

In the case of long-running transactions in finance and operations apps, a record might be synchronized multiple times to ensure no data loss. In this scenario, SinkModifiedOn reflects the last synchronization time, not the first. For example, if a record is synced 10 times within an hour, SinkModifiedOn shows the time of the 10th sync even though the data was available from the first sync itself. Use caution when building latency reports based on the difference between SinkModifiedOn and ModifiedOn, as it can give a misleading impression of actual data availability.

If you have more than 2,000 active Dataverse tables, Link to Fabric can fail with an error.

You can link your existing Azure Synapse Link for Dataverse profiles with Fabric if you select the Enable Parquet/Delta lake option. However:

• Existing profiles where the data is saved as CSV files can't be linked to Fabric.
• Azure Synapse Link profiles secured with managed identities currently can't be linked to Fabric.

See also

Link to Microsoft Fabric

Troubleshooting common issues with link to Fabric

Work with Dataverse data and generate Power BI reports