Forum Discussion
Shortcut table visible in SQL endpoint but not accessible as a standard lakehouse table
Hi AdarshChekodu ,
Building a semantic model and a Power BI report on top of the shortcut table is completely fine. We’ve tested the same setup, and the semantic model can read the shortcut data without any issues, even when the user doesn’t have access to the original workspace. The SQL endpoint treats the shortcut as a normal table in the destination Lakehouse, so the model refresh and report queries work as expected.
Regarding whether this behaviour will be changed: right now this is considered expected. A shortcut shows up fully in the SQL endpoint because the SQL layer relies on the metadata of the destination Lakehouse, not the source workspace. But the Lakehouse UI is stricter and checks the source permissions, which is why users without access to Workspace A can’t open the shortcut there.
Microsoft hasn’t announced a change yet, but this is something they’re aware of. If they do update it in the future, it will likely be in the direction of making the UI and SQL endpoint consistent — but as of now, this is how it works.
Hope this helps. If so, please give a Kudos 👍 or mark as Accepted Solution ✔️
– Gopi Krishna
Ugk161610
Thanks alot; I am thinking to build a semantic model and a PowerBi report on top of that; Do you see any issue in doing that.
In my test it worked fine. Also will this "Expected Behaviour" be "Fixed / Updated"?
Hi AdarshChekodu ,
Building a semantic model and a Power BI report on top of the shortcut table is completely fine. We’ve tested the same setup, and the semantic model can read the shortcut data without any issues, even when the user doesn’t have access to the original workspace. The SQL endpoint treats the shortcut as a normal table in the destination Lakehouse, so the model refresh and report queries work as expected.
Regarding whether this behaviour will be changed: right now this is considered expected. A shortcut shows up fully in the SQL endpoint because the SQL layer relies on the metadata of the destination Lakehouse, not the source workspace. But the Lakehouse UI is stricter and checks the source permissions, which is why users without access to Workspace A can’t open the shortcut there.
Microsoft hasn’t announced a change yet, but this is something they’re aware of. If they do update it in the future, it will likely be in the direction of making the UI and SQL endpoint consistent — but as of now, this is how it works.
Hope this helps. If so, please give a Kudos 👍 or mark as Accepted Solution ✔️
– Gopi Krishna