Forum Discussion
Dataverse tables enabling themselves on Link to Fabric
I have a Link to Fabric connection to bring some Dataverse tables and D365 FnO tables in my company. Seems that in the past months Microsoft is improving it, like letting you select only the tables that you want (better that all the 600 system tables from Dataverse), but sometimes I go take a look in my lakehouse and look! 100 Dataverse tables arrived without no one selecting them. And as it's already something that bothers me, I can't even unselect these tables, only after a few weeks (maybe after Microsoft patches/updates something) I'm able again to unselect and keep only the ones I did select.
I don't want to write a script to delete the tables or to call an API and delete the shortcuts, I just want to have the tables that I want and I selected. Any thoughts on why this keeps happening?
jose_henrique
This is by default behavious, i checked with microsoft documentation and found this information.By selecting Link to Microsoft Fabric, the system adds all nonsystem Dataverse tables that have the Track changes property enabled. You can add more tables later.
If you used this feature during public preview, you can continue to use the tables selected earlier. If you choose the Link to Fabric option in new environments (or unlink and relink existing environments), all tables are added.
Enabling this feature results in an increase in Dataverse database storage consumption. You can view additional storage consumption in the environment storage capacity details view in Power Platform admin center. For an example, you notice an additional file Account-Analytics if you selected the Account table for Fabric link. Also note that the chart only displays tables consuming the most storage. You can get a complete list of tables using the menu on the top right of the chart.
A practical workaround is to use two Lakehouses in Microsoft Fabric:
Create a Bronze Lakehouse to store all incoming data from Dataverse (even if it includes unwanted tables).
Create a second curated Lakehouse that contains only the tables required for your analysis and reporting.
This approach helps isolate unnecessary data while keeping your working environment clean and controlled.
If this helps, ✓ Mark as Kudos | Mark as Solution| Help Othershey jose_henrique adding from other answers above.
When you enable Link to Fabric:
- Fabric creates shortcuts in OneLake
- These shortcuts are driven by Dataverse metadata, not just your checkbox selection
Sometimes when Microsoft rolls out schema sync changes, new table classifications, system-table handling improvements and F&O schema updates, the Link to Fabric service will re-evaluate the source and rehydrate tables. Hence why you're seeing those additional 200 tables.
Since this is an expected behaviour from Microsoft Learn:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-view-in-fabricI suggest:
- Treat Link to Fabric as “eventually consistent” (Expect occasional drift after service updates)
- Separate ingestion from consumption, (+1 to Murtaza_Ghafoor)
Bronze lakehouse - raw Link to Fabric shortcuts
Avoid using the auto-linked tables for Power BI consumption and production workloads.
Silver lakehouse / Warehouse - only curated tables
Appreciate if you can 'Kudos' and/or 'Accept as Solution' if this answered your query.
5 Replies
jose_henrique
This is by default behavious, i checked with microsoft documentation and found this information.By selecting Link to Microsoft Fabric, the system adds all nonsystem Dataverse tables that have the Track changes property enabled. You can add more tables later.
If you used this feature during public preview, you can continue to use the tables selected earlier. If you choose the Link to Fabric option in new environments (or unlink and relink existing environments), all tables are added.
Enabling this feature results in an increase in Dataverse database storage consumption. You can view additional storage consumption in the environment storage capacity details view in Power Platform admin center. For an example, you notice an additional file Account-Analytics if you selected the Account table for Fabric link. Also note that the chart only displays tables consuming the most storage. You can get a complete list of tables using the menu on the top right of the chart.
A practical workaround is to use two Lakehouses in Microsoft Fabric:
Create a Bronze Lakehouse to store all incoming data from Dataverse (even if it includes unwanted tables).
Create a second curated Lakehouse that contains only the tables required for your analysis and reporting.
This approach helps isolate unnecessary data while keeping your working environment clean and controlled.
If this helps, ✓ Mark as Kudos | Mark as Solution| Help Othersjose_henrique
Note- AI helped me in formatting this contentTry to follow below step and it is not your mistake.
- Reopen and re-save the table selection periodically
Sometimes just reapplying your intended selection helps the system reconcile state faster. - Check if “auto-include new tables” behavior is enabled
Some environments implicitly enable inclusion of newly created tables. - Separate critical workloads
If this is impacting production, consider isolating into a separate Link to Fabric connection with stricter control. - Monitor update cycles
Since you’ve noticed the issue resolves after “a few weeks,” it likely aligns with backend deployments. Not ideal, but useful to anticipate. - Raise a Microsoft support ticket
Given the pattern you described, this is very likely a product bug rather than misconfiguration. Providing timestamps and affected tables helps them trace the sync jobs.
- Reopen and re-save the table selection periodically
hey jose_henrique adding from other answers above.
When you enable Link to Fabric:
- Fabric creates shortcuts in OneLake
- These shortcuts are driven by Dataverse metadata, not just your checkbox selection
Sometimes when Microsoft rolls out schema sync changes, new table classifications, system-table handling improvements and F&O schema updates, the Link to Fabric service will re-evaluate the source and rehydrate tables. Hence why you're seeing those additional 200 tables.
Since this is an expected behaviour from Microsoft Learn:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-view-in-fabricI suggest:
- Treat Link to Fabric as “eventually consistent” (Expect occasional drift after service updates)
- Separate ingestion from consumption, (+1 to Murtaza_Ghafoor)
Bronze lakehouse - raw Link to Fabric shortcuts
Avoid using the auto-linked tables for Power BI consumption and production workloads.
Silver lakehouse / Warehouse - only curated tables
Appreciate if you can 'Kudos' and/or 'Accept as Solution' if this answered your query.
Thank you for reaching out to the Microsoft Fabric Forum Community.
Murtaza_Ghafoor anilgavhane rizalard0684 Thanks for the inputs.
I hope the information provided by users was helpful. If you still have questions, please don't hesitate to reach out to the community.
Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.
