Dataflows in "private" workspaces visible to everyone

[stephenpavely]

I'm having an issue whereby a dataflow configured in a private app workspace appears to be accessible to everyone in the tenant (or at least those with a Power BI Pro licence) via Power BI Desktop. I have tried setting up two both the old and new style workspaces as provate workspaces, with only myself as a member (Admin) and creating dataflows in each one:

The dataflows are then accessible via Power BI Desktop to other users, which in this case needs to be restricted in our organisation:

Have I configured the something incorrectly or is this a security issue? It seems to me like when you select the private option for a workspace that "only approved members can see what's inside" should prohibit this kind of access?

Many thanks in advance,

Stephen

[v-cherch-msft]

Hi @stephenpavely 

I cannot reproduce it.If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

Regards,

[stephenpavely]

Thanks for your reply. I have just raised a ticket so I will update with the outcome.

[stephenpavely · Accepted solution]

I've just had a screenshare with Microsoft and this does seem to be an issue with Power BI Desktop (I'm using the latest version - May 2019 at present).

It seems the application is caching user credentials specifically for connecting to Dataflows in "C:\Users\Stephen\AppData\Local\Microsoft\Power BI Desktop\User.zip" and is not clearing them when switching users in Power BI Desktop. The issue is (mostly) resolved by deleting the User.zip file, which prompts the user to sign in again inside the application and prompts an additional dialog box asking whether to use those credentials to connect to the dataflow service.

This is clearly still a security issue though, so I would beware of user-switching in desktop if using dataflows. The support rep informed that the issue has been passed on to the product team.

[v-cherch-msft]

Hi @stephenpavely 

Thanks for sharing,please accept your reply as solution, that way, other community members will easily find the solution when they get same issue.

Regards,