Organizations increasingly use Microsoft Fabric to build analytics and reporting solutions powered by Microsoft Dataverse data. However, during the initial Dataverse-to-Fabric setup, administrators often faced a challenge: they had little control over which tables were synchronized.
Previously, the first synchronization automatically replicated all eligible Dataverse tables, regardless of whether they were required for reporting or analytics. This often resulted in unnecessary data replication, increased storage consumption, and additional administrative effort.
To address this challenge, Microsoft has introduced Guided Table Selection for First-Time Dataverse Sync, enabling administrators to choose only the required tables before synchronization begins.
To see how this enhancement improves the setup experience, consider the following scenario.
Key Takeaways
- Administrators can now select specific Dataverse tables before the first Fabric sync.
- Unnecessary system and custom tables no longer need to be synchronized by default.
- Storage, compute usage, and administrative overhead are reduced.
- Analytics projects can be deployed faster with a cleaner and more focused data model.
Business Scenario
Michael Johnson, a Sales Operations Manager at Contoso Electronics, uses:
- Dynamics 365 Sales
- Microsoft Dataverse
- Microsoft Fabric
- Power BI
His leadership team requires reporting and analytics based only on the following Dataverse tables:
- Accounts
- Contacts
- Leads
- Opportunities
No additional tables are required for reporting purposes.
The Challenge Before Guided Table Selection
When Michael started configuring the Dataverse-to-Fabric link, he expected to choose only the tables needed for reporting.
Expected Experience
- Accounts
- Contacts
- Leads
- Opportunities
Actual Experience
Instead, Dataverse automatically selected and synchronized all eligible tables, including:
- Accounts
- Contacts
- Leads
- Opportunities
- Audit
- AsyncOperation
- PluginTraceLog
- Process Sessions
- System Jobs
- Hundreds of custom tables
In Michael’s environment, nearly 666 tables were synchronized even though only four were required.
Prerequisites for Dataverse-to-Fabric Sync
Before configuring Dataverse synchronization with Microsoft Fabric, ensure the following prerequisites are met:
1. Dataverse Environment
An active Dynamics 365 or Power Apps environment with Dataverse enabled.
2. Microsoft Fabric Workspace
A Fabric workspace must be available to receive the synchronized data.
3. Required Permissions
The user performing the configuration should have:
- System Administrator or Environment Admin access in Power Platform.
- Workspace Admin or Member access in Microsoft Fabric.
4. Microsoft Fabric Licensing
Microsoft Fabric must be enabled and licensed for your organization... Read More
