Forum Discussion

Manu002's avatar
Manu002
Frequent Visitor
1 year ago
Solved

Lakehouse SQL endpoint access

Hi Experts,   I'm facing a problem. I give access to only one lakehouse in a workspace to a user via SQL Endpoint. Unexpectedly, That user has access also to other lakehouse in that workspace. I ve...
  • burakkaragoz's avatar
    1 year ago

    Hi Manu002 ,

     

    This behavior is expected in Microsoft Fabric. Currently, SQL Endpoints are shared at the workspace level, not per individual Lakehouse. That means if a user has access to the SQL Endpoint, they can query all Lakehouses within that workspace.

    To manage access more granularly:

    • Consider separating Lakehouses into different workspaces if isolation is required.
    • Use row-level security (RLS) within the Lakehouse to restrict data access.
    • Only admins can manage certain permissions like ReadData, so if you're just a member, you may not see or assign all access levels.

    Hopefully, Microsoft will introduce more granular SQL Endpoint controls in future updates.

  • v-menakakota's avatar
    1 year ago

    Hi Manu002 ,

    Thank you for reaching out to us on the Microsoft Fabric Community Forum.

     

    Thank you burakkaragoz for providing possible solution. SQL Endpoints are scoped at the workspace level, not at the individual Lakehouse level. So if a user has access to the workspace SQL Endpoint, they will be able to query all Lakehouses within that workspace.
    To manage access more securely, create separate workspaces and Use Row-Level Security (RLS) to control data visibility within a shared Lakehouse.

    If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily