Forum Discussion
Helper IShortcut - Dataverse vs Fabric Link
I'm referencing this
https://www.reddit.com/r/MicrosoftFabric/comments/1hdiyg8/create_dataverse_shortcuts_for_single_table/?rdt=57843
thread regarding creating shortcuts from Dataverse.
What is the purpose of creating a shortcut from Dataverse when the Fabric link needs to be created first?
If a lakehouse (L1) is created when establishing a Fabric link, why can’t I just create a the shortcut from this lakehouse ?
Can someone explain the rationale behind the option to create shortcuts specifically from Dataverse?
Thanks for your help in advance
Hello Rohitb ,
Great question! The key difference between Fabric Link Lakehouse and Dataverse Shortcuts lies in security and data governance.
When using Fabric Link Lakehouse, all tables are synced into OneLake, allowing anyone with workspace access to view the entire dataset, even if they don't have Dataverse permissions. On the other hand, Dataverse Shortcuts enforce Dataverse security controls, ensuring only users with explicit Dataverse table permissions can access specific data.
From a governance perspective, Fabric Link Lakehouse inherits Fabric workspace security, granting broad access, while Dataverse Shortcuts maintain Dataverse role-based security for granular table control. If you need full dataset availability for analytics, Fabric Link Lakehouse is ideal. However, if controlled access with Dataverse security is required, Dataverse Shortcuts are the better choice.
For further details, you can refer to these Microsoft documentation links:
Create a shortcut to Dataverse environment - Microsoft Cloud for Sustainability | Microsoft Learn
Dataverse Shortcuts provide an additional layer of security and governance by enforcing Dataverse-specific permissions, whereas Fabric Link Lakehouse grants access to all tables in the workspace.
I hope my suggestions give you good ideas, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
11 Replies
RohitbI'm referencing this
https://www.reddit.com/r/MicrosoftFabric/comments/1hdiyg8/create_dataverse_shortcuts_for_single_tabl...thread regarding creating shortcuts from Dataverse.
What is the purpose of creating a shortcut from Dataverse when the Fabric link needs to be created first?
If a lakehouse (L1) is created when establishing a Fabric link, why can’t I just create a the shortcut from this lakehouse ?
Can someone explain the rationale behind the option to create shortcuts specifically from Dataverse?Thanks for your help in advance
- nilendraFabric
Super User
Hello Rohitb
Great question
The "Link to Microsoft Fabric" feature creates the Dataverse Managed Lake within OneLake. This lake is essential because it converts Dataverse tables into a Delta Parquet format optimized for Fabric analytics tools. Without this step, the tables wouldn't be accessible for creating shortcutCurrently, there is no functionality to synchronize just a single table from Dataverse into Fabric without using the "Link to Fabric" feature. The process inherently brings in multiple tables, even if you only need one
I know it sound tedious n effort duplication but
Creating shortcuts directly from Dataverse allows users to select specific tables for integration into other workspaces or lakehouses. This avoids exposing all tables synced via the Fabric link. When the Fabric link is established, all tables with "Change Tracking" enabled are synchronized to the Dataverse Managed Lake, but shortcuts let you pick and choose which tables to include in specific workspaces. This provides finer control over data access and sharing Hi Rohitb ,
Thanks for reaching out to the Microsoft fabric community forum.
I would also like to take a moment to personally thank nilendraFabric for actively participating in the community forum and for providing a solution. Additionally, I am including detailed information for your understanding.
The "Link to Microsoft Fabric" feature automatically creates the Dataverse Managed Lake in OneLake, converting Dataverse tables into Delta Parquet format for Fabric analytics tools. This step is required because Dataverse tables are not natively available in Fabric without this transformation.
Currently, there is no option to synchronize a single table from Dataverse into Fabric—all tables with "Change Tracking" enabled are automatically synced when the Fabric Link is established. Even if only one table is needed, multiple tables will still be imported.
However, creating shortcuts directly from Dataverse allows users to reference specific tables within different workspaces or lakehouses, without exposing the entire dataset. Unlike Fabric Link, which synchronizes all eligible tables, shortcuts provide greater control over which tables are available in each workspace, ensuring better governance, reduced storage costs, and improved data security.
I hope my suggestions give you good ideas, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Rohitb
Anonymous nilendraFabric Thank.you for your response.
When there is already a workspace containing a lakehouse that contains all the entities shortcuts, can't we create shortcuts in another workspace mapping to those specific entities refrencing the fabric link lakehouse. Why is there a need for the shortcut functionality from dataverse ? (Is this functioanlity providing some different security aspects)
Also I am tryoing to understand the data governance aspect of the same:
In case if the fabric link is established, users having access on the workspace hosting the lakehouse are able to see the data even if they do not directly have access on the dataverse.
So does it mean incase of Shortcut to dataverse, the user needs to have specific access on the dataverse tables where as in case of lakehouse shortcut he/she needs to be given access on the fabric lakehouse ?Hello Rohitb ,
Great question! The key difference between Fabric Link Lakehouse and Dataverse Shortcuts lies in security and data governance.
When using Fabric Link Lakehouse, all tables are synced into OneLake, allowing anyone with workspace access to view the entire dataset, even if they don't have Dataverse permissions. On the other hand, Dataverse Shortcuts enforce Dataverse security controls, ensuring only users with explicit Dataverse table permissions can access specific data.
From a governance perspective, Fabric Link Lakehouse inherits Fabric workspace security, granting broad access, while Dataverse Shortcuts maintain Dataverse role-based security for granular table control. If you need full dataset availability for analytics, Fabric Link Lakehouse is ideal. However, if controlled access with Dataverse security is required, Dataverse Shortcuts are the better choice.
For further details, you can refer to these Microsoft documentation links:
Create a shortcut to Dataverse environment - Microsoft Cloud for Sustainability | Microsoft Learn
Dataverse Shortcuts provide an additional layer of security and governance by enforcing Dataverse-specific permissions, whereas Fabric Link Lakehouse grants access to all tables in the workspace.
I hope my suggestions give you good ideas, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- ObungiNiels
Resolver III
Hi Rohitb ,
you are correct, you totally can create shortcuts from the LH which is created by the Fabric Link.
I think what the user wanted is a solution for a single table with less overhead than the Fabric Link, which is currently not supported as the Fabric Link cannot depict single tables.
Kind regards,
Niels
