The Power BI Report doesn't have permission to read data Lakehouse (Direct Lake table permission)

[Quang]

I am currently experiencing issues related to obtaining Lakehouse data permissions from the chart. The chart is unable to establish a connection with the dataset and is displaying the following error. I have the ability to access the Lakehouse and query data.

My workspace role is set as Contributor, and my permissions include Read, Write, Execute, ReadAll, and ViewOutput.

It's worth noting that this issue has only arisen today; it was functioning correctly yesterday.

Could you please assist me in resolving this matter?

[Quang · Accepted solution]

This issue has been fixed by the Microsoft Developer Team after I created the support ticket.

Thanks

[deanbeane]

Hi @Quang, sorry to hear you are still struggling. My setup is I have a DEV workspace with all my Fabric artefacts, and I then make a subset of non-Fabric artefacts (dashboards, reports, semantic models/datasets) available in a Premium per-user workspace for end-user consumption. I am not entirely sure why this works - it just does in my case. I will steer clear of addressing your particular region constraints as I'm not familiar with your admin settings. Sorry I cant be of more help...

[deanbeane]

I had the same issue. Changing the licence type of the worskspace which hosts the report to 'Premium Per-user' solved the problem. 'Workspace Settings' -> 'Premium' -> 'Premium per-user'

[Quang]

Hi @deanbeane ,

I have tried to change the License type of the workspace to Premium User. I got the error below.

My workspace is using Fabric resources, Is that affect my workspace report if I remove Fabric?

I found that the issue permission is only for external users who do not have the same domain as the workspace admin.

[gtacchini]

Same issue here!!

[Quang]

Hi @GilbertQ , I already have gotten this issue for more than 1 day in my time zone , Still not fixed yet

[GilbertQ]

Hi @Quang 

I would then try something else, because it is in preview I do not think that support can help at the moment.

[GilbertQ]

Hi @Quang 

It might just be a temporary bug that might be fixed tomorrow?