![\"Microsoft](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/A-Smarter-Way-to-Control-Data-Replication-in-Microsoft-Fabric.png\")
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
To see how this enhancement improves the setup experience, consider the following scenario.<\/p>\n
Michael Johnson, a Sales Operations Manager at Contoso Electronics, uses:<\/p>\n
His leadership team requires reporting and analytics based only on the following Dataverse tables:<\/p>\n
No additional tables are required for reporting purposes.<\/p>\n
When Michael started configuring the Dataverse-to-Fabric link, he expected to choose only the tables needed for reporting.<\/p>\n
Expected Experience<\/strong><\/p>\n Actual Experience<\/strong><\/p>\n Instead, Dataverse automatically selected and synchronized all eligible tables, including:<\/p>\n In Michael’s environment, nearly 666 tables were synchronized even though only four were required.<\/p>\n Prerequisites for Dataverse-to-Fabric Sync<\/strong><\/p>\n Before configuring Dataverse synchronization with Microsoft Fabric, ensure the following prerequisites are met:<\/p>\n 1. Dataverse Environment<\/strong><\/p>\n An active Dynamics 365 or Power Apps environment with Dataverse enabled.<\/p>\n 2. Microsoft Fabric Workspace<\/strong><\/p>\n A Fabric workspace must be available to receive the synchronized data.<\/p>\n 3. Required Permissions<\/strong><\/p>\n The user performing the configuration should have:<\/p>\n 4. Microsoft Fabric Licensing<\/strong><\/p>\n Microsoft Fabric must be enabled and licensed for your organization.<\/p>\n 5. Link to Microsoft Fabric Availability<\/strong><\/p>\n Verify that the Link to Microsoft Fabric<\/strong> option is available within your Dataverse environment.<\/p>\n To create a Fabric link:<\/p>\n Key Limitation<\/strong><\/p>\n All eligible Dataverse tables were automatically selected, and administrators had no opportunity to choose only the tables they needed before the initial sync.<\/p>\n Important:<\/strong> All Dataverse tables were synchronized regardless of whether they were required for analytics or reporting.\u00a0<\/strong><\/p>\n Excessive Storage Consumption<\/strong><\/p>\n Fabric created storage objects for every replicated table, including many that were never used for reporting or analytics.<\/p>\n Although only four business tables were required, hundreds of additional tables consumed storage resources.<\/p>\n Increased Operational Costs<\/strong><\/p>\n Synchronizing unnecessary data resulted in:<\/p>\n Additional Administrative Effort<\/strong><\/p>\n Administrators had to manually:<\/p>\n This process was both time-consuming and prone to error.<\/p>\n Complex Onboarding Experience<\/strong><\/p>\n New administrators often struggled to identify:<\/p>\n As a result, onboarding became more complex than necessary.<\/p>\n Microsoft’s Solution: Guided Table Selection<\/strong><\/p>\n With Guided Table Selection<\/strong>, table selection is now integrated directly into the initial setup experience.<\/p>\n Instead of synchronizing everything first and cleaning up later, administrators can choose exactly which tables should be synchronized before data movement begins.<\/p>\n Step 1: Create the Fabric Link<\/strong><\/p>\n Navigate to:<\/p>\n Step 2: Review Available Tables<\/strong><\/p>\n The system now presents a list of available Dataverse tables before synchronization starts.<\/p>\n Example:<\/p>\n Administrators can select only the tables relevant to their reporting and analytics requirements.<\/p>\n Step 3: Confirm Table Selection<\/strong><\/p>\n In Michael’s case, only the following tables were selected:<\/p>\n This reduced the synchronization scope from 300 tables to just 4 tables<\/strong>.<\/p>\n Step 4: Start Synchronization<\/strong><\/p>\n Synchronization begins only for the selected tables, eliminating unnecessary data replication from the start.<\/p>\n Why This Feature Matters<\/strong><\/p>\n The most significant improvement is not technical – it’s operational.<\/p>\n Organizations no longer need to:<\/p>\n Instead, they can:<\/p>\n The introduction of Guided Table Selection for First-Time Dataverse Sync gives administrators greater control over the Dataverse-to-Fabric integration process. Rather than synchronizing every eligible table and removing unwanted ones later, organizations can now select only the tables that support their reporting and analytics requirements.<\/p>\n This streamlined approach reduces storage consumption, minimizes administrative effort, improves onboarding, and helps organizations realize value from Microsoft Fabric more quickly. For businesses looking to build efficient analytics solutions with Dataverse and Microsoft Fabric, this enhancement makes the setup process significantly more focused and manageable.<\/p>\n Guided Table Selection is a new enhancement that allows administrators to select specific Dataverse tables before the first synchronization with Microsoft Fabric begins, rather than automatically replicating all eligible tables.<\/p>\n 2. Why is Guided Table Selection important?<\/strong><\/p>\n It helps organizations avoid synchronizing unnecessary tables, reducing storage consumption, compute usage, and administrative effort while creating a cleaner analytics environment.<\/p>\n 3. Does this feature affect existing Dataverse-to-Fabric links?<\/strong><\/p>\n No. Guided Table Selection is primarily designed for the initial setup experience<\/strong>. Existing Fabric links continue to be managed through the standard table management options<\/p>\n 4. Can system tables be excluded during setup?<\/strong><\/p>\n Yes. Administrators can review the available table list and choose only the business-relevant tables required for reporting and analytics.<\/p>\n 5. What are the benefits of synchronizing fewer tables?<\/strong><\/p>\n Benefits include:<\/p>\n 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\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2354,38,2361],"tags":[3376],"class_list":["post-44969","post","type-post","status-publish","format-standard","hentry","category-dataverse","category-microsoft-powerapps","category-technical","tag-microsoft-fabric"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/44969","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=44969"}],"version-history":[{"count":5,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/44969\/revisions"}],"predecessor-version":[{"id":44984,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/44969\/revisions\/44984"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=44969"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=44969"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=44969"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-1.jpg\")
<\/p>\n![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-2.jpg\")
<\/p>\nTraditional Dataverse-to-Fabric Setup<\/strong><\/h3>\n
\n
![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-3.jpg\")
<\/p>\n![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-4.jpg\")
<\/p>\nChallenges with the Previous Approach<\/strong><\/h3>\n
![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-5.jpg\")
<\/p>\n\n
\n
![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-6.jpg\")
<\/p>\n\n
How the New Experience Works<\/strong><\/h3>\n
\n
![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-7.jpg\")
<\/p>\n\n
![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-8.jpg\")
<\/p>\n\n
![\"A](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/06\/Data-Replication-9.jpg\")
<\/p>\n\n
\n
\u00a0<\/strong>Conclusion:<\/strong><\/h3>\n
Frequently Asked Questions (FAQs)<\/strong><\/h3>\n
1. What is Guided Table Selection in Dataverse-to-Fabric Sync?<\/strong><\/h3>\n
\n