Lakehouse SQL Endpoint permissions

[PetyrBaelish]

Hi, I'm struggling to grant permissions to a lakehouse, so that end users can connect in Power BI Desktop.

I'm expecting users to open Power BI Desktop, select OneLake Data Hub -> Lakehouses -> search for the lakehouse name, and then "Connect to SQL Endpoint". But users are unable to find the lakehouse.

In Fabric, when I go to Manage Permissions on the lakehouse, my "all staff" group has Read permission on it.

When I go to Manage Permissions on the SQL endpoint, my "all staff" group has Read and ReadData permissions.

As a workspace admin it works for me.

What else do I need to do to enable my all staff group to connect to the SQL endpoint in Power BI Desktop (or any other tool)?

[tharunkumarRTK · Accepted solution]

@PetyrBaelish 

When you gave read all sql analytics endpoint permissions that is essentially mean you are allowing your users to read the tables through SQL analytics endpoint. 

So ideally you need to share the sql endpoint details with your end users and they should be able to connect.

This level of permissions will not allow them to access delta parquet files and also the other files stored within the lakehouse.
I guess this is the reason why your users not able to see the tables when they were trying to access from 
Power BI desktop -> One lake data hub -> lakehouse. 

Since you gave read permissions on the sql analytics endpoint only, that might be the reason why it is appearning under

Power BI Desktop -> one lake datahub -> warehouse 

if you want your users to be able to find it under lakehouse then give "Read all Apache Spark"

Need a Power BI Consultation? Hire me on Upwork

Connect on LinkedIn

Did I answer your question? Mark my post as a solution!
If I helped you, click on the Thumbs Up to give Kudos. Proud to be a Super User!

[PetyrBaelish]

Something else to add... if my users connect selecting warehouse (OneLake Data Hub -> Warehouses -> Search for table name -> Connect to SQL Endpoint), this works.

So I really don't know why choosing Lakehouse means my users can't find the table, but selecting warehouse they can. The table is stored in a lakehouse.

[Anonymous]

Hi @PetyrBaelish 

You might notice the Filter(n) dropdown box in the OneLake data hub window. When you select OneLake Data Hub -> Lakehouses, it checks only Lakehouse option by default. So you need to check "SQL analytical endpoint" option at the same time to see the SQL endpoint of the shared lakehouse. 

However when you select OneLake Data Hub -> Warehouses, it checks both SQL analytical endpoint and Warehouse options by default, so you will see that SQL endpoint. 

When you use the OneLake Data Hub connector, the navigation window is always the same, the only difference is the default checked options for filtering OneLake items. So your users don't see them as the filter option is not checked. 

Hope this would be helpful. 

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!

[PetyrBaelish]

just to add - the users I'm testing withcan successfully connect to the semantic model (they have read & build permissions)