Forum Discussion
Advocate ILink to fabric and shortcut comparison for Dataverse
Hi Fabric Community,
I'm designing a Microsoft Fabric integration with Dataverse and I'm trying to choose the most appropriate approach between Dataverse Shortcuts and Link to Microsoft Fabric.
Our requirements are:
Analytics and reporting workloads on Dataverse data
Medallion architecture (Bronze / Silver / Gold)
Preference for least-privilege security principles
Ability to handle schema evolution over time
From my understanding:
Shortcuts avoid data duplication and seem simpler to manage.
Link to Fabric creates and maintains a replicated copy of the data in OneLake.
For those who have implemented Dataverse + Fabric in production:
Which approach did you choose and why?
What are the main pros and cons you've experienced with Shortcuts vs Link to Fabric?
How do the two options compare in terms of schema evolution and maintenance?
Are there any performance or cost considerations that influenced your decision?
I'd appreciate any real-world experiences, lessons learned, or recommendations.
Thank you!
Hi Luigia-Costabil ,
Thank you for sharing your requirements.
Based on what you've described, both Dataverse Shortcuts and Link to Microsoft Fabric can work, but they are optimized for slightly different use cases.
If your goal is simply to access Dataverse data in Fabric while avoiding additional data copies and storage costs, Dataverse Shortcuts are a straightforward option. They provide direct access to the source data and require minimal data movement.
However, if you're building a dedicated analytics platform with a Bronze/Silver/Gold (Medallion) architecture, Link to Microsoft Fabric is typically the approach many teams choose. It makes Dataverse data available in OneLake in a format that works well with Lakehouse, Spark, Warehouse, and Power BI workloads, while also providing more flexibility for managing schema changes and downstream transformations.
For your specific requirements analytics and reporting, Medallion architecture, schema evolution, and long-term scalability Link to Microsoft Fabric would generally be the stronger fit. If minimizing data duplication and storage consumption is the primary concern, then Dataverse Shortcuts may be worth considering.
You may find these resources helpful:
Link your Dataverse environment to Microsoft Fabric and unlock deep insights - Power Apps | Microsoft Learn
Configure your environment and link to Microsoft Fabric - Power Apps | Microsoft Learn
Unify data sources with OneLake shortcuts - Microsoft Fabric | Microsoft Learn
I hope this helps clarify things. If there’s anything I may have misunderstood about your situation, please let us know.Regards,
Microsoft Fabric Community Support Team.
1 Reply
v-karpurapudCommunity Support
Hi Luigia-Costabil ,
Thank you for sharing your requirements.
Based on what you've described, both Dataverse Shortcuts and Link to Microsoft Fabric can work, but they are optimized for slightly different use cases.
If your goal is simply to access Dataverse data in Fabric while avoiding additional data copies and storage costs, Dataverse Shortcuts are a straightforward option. They provide direct access to the source data and require minimal data movement.
However, if you're building a dedicated analytics platform with a Bronze/Silver/Gold (Medallion) architecture, Link to Microsoft Fabric is typically the approach many teams choose. It makes Dataverse data available in OneLake in a format that works well with Lakehouse, Spark, Warehouse, and Power BI workloads, while also providing more flexibility for managing schema changes and downstream transformations.
For your specific requirements analytics and reporting, Medallion architecture, schema evolution, and long-term scalability Link to Microsoft Fabric would generally be the stronger fit. If minimizing data duplication and storage consumption is the primary concern, then Dataverse Shortcuts may be worth considering.
You may find these resources helpful:
Link your Dataverse environment to Microsoft Fabric and unlock deep insights - Power Apps | Microsoft Learn
Configure your environment and link to Microsoft Fabric - Power Apps | Microsoft Learn
Unify data sources with OneLake shortcuts - Microsoft Fabric | Microsoft Learn
I hope this helps clarify things. If there’s anything I may have misunderstood about your situation, please let us know.Regards,
Microsoft Fabric Community Support Team.