Is it possible to restrict table-level access for users in Microsoft Fabric Lakehouse?

[mohita98]

Hi community,

I’m working on a solution in Microsoft Fabric using the Lakehouse architecture. I want to implement fine-grained access control so that when a user logs into Fabric and tries to access certain tables within the Lakehouse, access is denied based on their permissions.

My questions are:

1. Is it currently possible to restrict access to specific tables within a Lakehouse for certain users?

2. If yes, what’s the best way to implement such access control—using Fabric permissions, OneLake security, or any other method?

The goal is to ensure that some users can see only specific tables (or views) and are completely restricted from others, even when they have general access to the Lakehouse workspace.

Any documentation links or best practices would be greatly appreciated.

Thanks in advance!

[Akash_Varuna · Accepted solution]

@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.

[v-echaithra]

Hi @mohita98 ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,
Chaithra.

[v-echaithra]

Hi @mohita98 ,

We wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,
Chaithra.

[v-echaithra]

Hi @mohita98 ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,
Chaithra.

[mohitkumawat · Accepted solution]

Hi you can try OLS 

https://learn.microsoft.com/en-us/fabric/security/service-admin-object-level-security?tabs=table

[Akash_Varuna]

Hi @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

[mohita98]

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 · Accepted solution]

@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.