Forum Discussion
Mirrored Database Table level security for Notebook use
SQL Endpoint → respects table-level security.
Fabric Notebooks → only respect workspace/item-level permissions, not SQL table security.
Result: users need Lakehouse/Mirrored DB item access to use Notebooks.
Workarounds:
Give workspace/item read access.
Copy allowed tables into a separate Lakehouse.
Limitation: table-level security in Notebooks isn’t supported yet (on Microsoft’s roadmap).
Hi stellahe102,
Currently, table-level permissions on mirrored databases in Fabric are only applied when users connect through the SQL Endpoint. When the same data is accessed through Notebooks (Spark), those SQL permissions are not enforced, which is why your users see a difference.
At this time, Fabric does not provide fine-grained table-level security for mirrored databases in Notebooks. The recommended options are:
Run queries in the Notebook through the SQL Endpoint (so your existing SQL permissions apply).
Create views with the required table or row filters and grant users access to those views.
If duplication is a concern, avoid copying into a Lakehouse and use Shortcuts or SQL Endpoint access instead.
The documents below are shared for your review and reference:
Secure mirrored data in Microsoft Fabric database - Microsoft Fabric | Microsoft Learn
Explore Data in Your Mirrored Database With Notebooks - Microsoft Fabric | Microsoft Learn
Secure Mirrored Azure Databricks Data in Fabric with OneLake security | Microsoft Fabric Blog | Microsoft Fabric
Thank you.
Hi stellahe102,
Just wanted to check regarding your question. We haven’t heard back and want to ensure you're not stuck. If you need anything else or have updates to share, we’re here to help!
Thank you.