Dataverse integration into Fabric

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.