Error using direct lake: don't have permission to view the content of a Direct Lake Table

[alfBI]

Hi,

We have developed a model connected by Direct lake to a lakehouse (model A)

User A has been granted with Read & read all rights on the lakehouse.

A report has been created on top of the model and a application has been created adding the report A as content

User A has been granted with view access to the app.

And with all that stuff in place following error message does appear when the app is loaded by the user A

What are we missing?

Note: All items on same workspace. User A is not member of workspace. The model A created is not the default one provided by the Lakehouse, it's a custom one.

Thx

[amolt]

Hello @Flash777 , 

Perhaps this will help:

Solved: Re: Turn off Explore this Data feature - Microsoft Fabric Community

[amolt]

Hi @Arlo ,

Thanks for your workaround.
It works perfectly.
In my case I had to add the service principal as the workspace “viewer” BEFORE creating the new connection. After creating the new connection, you also have to select this new connection to use it in the model.

 

[MatthewH]

but do you think that is because of this error or because that's just how you need to do it. I'm reluctant to give people access to the entire lake house because that lake house is my serving layer. my understanding was that from that serving layer, we could create semantic models and provide different audiences access to those

[Arlo]

Fabric is GA but it is definitely still Beta. I see the team add buttons to stuff while I'm in the middle of working, new unannounced preview features just show up sometimes. My best guess is that Microsoft is racing and following a product strategy of "just get it into their hands so they can play with it". The only part of that that bugs me is that we're paying for a GA product with SLAs that they can't ever meet.

[enerkat]

Honestly I don't know but it would be great if it would work giving access only to the semantic model instead of the entire lakehouse. Maybe someone from microsoft can clear this up. @Anonymous 

[Anonymous]

Hi @alfBI ,

I need to know more information about the problem you are having, are you getting this error when viewing the semantic model or is the error occurring when a user accesses Lakehouse in Direct Lake using a fixed identity setup. Is it intermittent or persistent. Is there a detailed error message or a full screenshot of the error popup.
This helps us to better understand and resolve your issue.

Best Regards,

Ada Wang

[alfBI]

Hi Ada, 

The problem might be reproduced following next steps

1) Create a lakehouse with some tables

2) Create a semantic model on top of it (developed on the service)

3) Create a Power BI report using direct lake against previous semantic model (developed on the service)

4) Embed the report on an app

5) Grant user access to app

6) Grant user access to Lakehouse content (Read/read all)

7) User tries access report on the app

Regards,

Alfons

[enerkat]

Hi Ada,

sorry for inserting myself into the conversation here but I have exactly the same situation as alfBI. The error is persistent and happens when a user accesses the App and is trying to view a report created using direct lake mode. The user has been given Read and ReadAll access to the corresponding lakehouse. We have tested this with 2 different users and the get the same error.

This is the full error message we get:

Thanks for your help.

[Anonymous]

Hi @alfBI ,

We have reported this issue and submitted it to the product team.
They have been aware of the issue and the engineers will do their best to resolve it. I will update here if there is any progress, so please be patient. 

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[alfBI]

Many Thanks

[Anonymous]

Hi @alfBI ,
We have reported this issue and submitted it to the product team. They have been aware of the issue and fixed it. Please check it later.

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[alfBI]

Do you have any update about the topic?  Me and other users are still facing the same issue than before

Regards

[alfBI]

Hi,

We have tested and problems remains. Do you know if some additional change is required on our side to make this work?

Thx

[enerkat]

Hi Ada,

You say the product team has fixed it but I am still having the same problem. Do you know when we can expect it to work?

Thanks.

[alfBI]

Not

[tharunkumarRTK]

@alfBI - Is there any RLS implemented on your model?

[alfBI]

no

[tharunkumarRTK]

Ok, I hope this issue is not user specific. If yes then contact the Microsoft support team. Otherwise, try elevating the user permissions.