Forum Discussion
Is it possible to restrict table-level access for users in Microsoft Fabric Lakehouse?
mohita98 You could try enforcing Row-Level and Column-Level Security (RLS/CLS) within the Lakehouse to restrict data access during query execution.You could also enforce Delta Lake’s ACLs or use scoped views with permissions applied at the source, so unauthorized users cannot access hidden tables even indirectly.
Super UserHi mohita98 Yes, it’s possible to restrict table-level access in a Fabric Lakehouse using OneLake security and workspace roles. Use Delta Lake’s security features or create scoped shortcuts/views with permissions for specific users.
If this post helped please do give a kudos and accept this as a solution
Thanks In Advance
Thanks for the response!
I did try using OneLake security to restrict access, and while it hides the tables successfully, I’ve noticed that when building a new semantic model, I'm still able to see and use all the tables from the Lakehouse—even those I’m not supposed to have access to.
This means that restricted users can still include those hidden tables in semantic models and build Power BI reports on top of them, which bypasses the intended access controls.
Is there a way to ensure that restricted tables are completely inaccessible, not just hidden, during semantic model creation as well?
Appreciate any additional guidance on this!
- Akash_Varuna
mohita98 You could try enforcing Row-Level and Column-Level Security (RLS/CLS) within the Lakehouse to restrict data access during query execution.You could also enforce Delta Lake’s ACLs or use scoped views with permissions applied at the source, so unauthorized users cannot access hidden tables even indirectly.