Forum Discussion
Dataverse integration into Fabric
Hi Community,
I'm evaluating different approaches for building a Dataverse Source-Aligned Data Product in Microsoft Fabric and would appreciate some feedback from people with real-world experience.
Initially, I was leaning towards Link to Fabric because it provides a managed analytical representation of Dataverse data and aligns well with the concept of a shared Source-Aligned Data Product.
However, after reviewing the documentation and some community discussions, I'm becoming concerned about the additional Dataverse storage consumption associated with Link to Fabric, especially for larger environments.
An alternative architecture I'm considering is:
Dataverse
→ Dataverse Shortcut
→ Fabric Notebook (incremental load using ModifiedOn watermark)
→ Bronze Delta tables in OneLake
→ Silver
→ Gold
The idea would be to use the Shortcut only as the ingestion source and materialize a physical Bronze layer in OneLake. This would avoid Dataverse Database Capacity growth while still providing a shareable and governed data product inside Fabric.
My questions are:
Has anyone implemented this pattern in production?
For large Dataverse environments, do you consider this approach more cost-effective than Link to Fabric?
Are there any significant drawbacks that I'm overlooking?
Does the additional development effort (notebooks, watermark management, delete handling, schema evolution) outweigh the Dataverse storage savings?
If you were building a Source-Aligned Data Product today, would you choose:
Link to Fabric
Shortcut + Bronze Delta in OneLake
and why?
Thanks!
Hi Luigia-Costabil
Thanks for sharing your architecture considerations. Both approaches are valid, but the trade-off is generally between managed simplicity and full control.
Link to Fabric is often the preferred option because Microsoft manages synchronization, updates, deletes, and schema changes for you, reducing development and maintenance effort.
The Shortcut ->Bronze Delta pattern can be a better fit if you need a standardized Bronze layer, more control over ingestion, or are evaluating storage/capacity impacts in large Dataverse environments. However, you'll need to handle incremental loads, delete detection, schema evolution, and operational monitoring yourself.
So the decision is not only about whether you want to transform the data. It also depends on factors such as scale, storage considerations, governance requirements, and how much engineering ownership you're willing to take on.
For most scenarios, Link to Fabric is the simpler starting point, while a custom Bronze ingestion pattern is typically chosen when there are specific cost, governance, or architectural requirements.
For additional guidance, see the Microsoft documentation:
Link your Dataverse environment to Microsoft Fabric and unlock deep insights - Power Apps | Microsoft Learn
I hope this helps clarify things. If there’s anything I may have misunderstood any part of your query, please let us know.
Regards,
Microsoft Fabric Community Support Team.
4 Replies
Link to Microsoft Fabric is the best choice unless you want to alter data at all.
Hi Luigia-Costabil
Thanks for sharing your architecture considerations. Both approaches are valid, but the trade-off is generally between managed simplicity and full control.
Link to Fabric is often the preferred option because Microsoft manages synchronization, updates, deletes, and schema changes for you, reducing development and maintenance effort.
The Shortcut ->Bronze Delta pattern can be a better fit if you need a standardized Bronze layer, more control over ingestion, or are evaluating storage/capacity impacts in large Dataverse environments. However, you'll need to handle incremental loads, delete detection, schema evolution, and operational monitoring yourself.
So the decision is not only about whether you want to transform the data. It also depends on factors such as scale, storage considerations, governance requirements, and how much engineering ownership you're willing to take on.
For most scenarios, Link to Fabric is the simpler starting point, while a custom Bronze ingestion pattern is typically chosen when there are specific cost, governance, or architectural requirements.
For additional guidance, see the Microsoft documentation:
Link your Dataverse environment to Microsoft Fabric and unlock deep insights - Power Apps | Microsoft Learn
I hope this helps clarify things. If there’s anything I may have misunderstood any part of your query, please let us know.
Regards,
Microsoft Fabric Community Support Team.
I wanted to check if you’ve had a chance to review the information provided. Has your issue been resolved, or do you need any further assistance? If not, please provide more details so we can help.
Thank You.We were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank You.
