Forum Discussion
Lakehouse SQL Endpoint permissions
Anonymous
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!
Anonymous
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
|