Unable to access one folder of a datalake

[frenchphil]

Hi, 

I have a very strange problem with accessing one of the folder of my datalake, I explain ..

From PowerBI Desktop, I can access without any problem at all folders of my Azure Datalake (with oAuth2 authentification). 

I'd like to parameter a dataflow on powerbi service connecting the datasource to the same URL I use in PowerBI Desktop but, after authentification, I have the message: "Informations d'identification non valide. (ID de session : 0e0e8a7f-1979-458b-aa6c-fdaf3ba6fd23, région : europe)"

How can we explain a difference of access between PBI Desktop and PBI service in this case ? Is there a cache of something in PBI Service? Any idea ?

Thanks for your help

Philippe

[otravers]

in PQO you have to connect to your container, not a subfolder:

Subfolder or file not supported in Power Query Online

Currently, in Power Query Online, the Azure Data Lake Storage Gen2 connector only supports paths with container, and not subfolder or file. For example, https://<accountname>.dfs.core.windows.net/<container> will work, while https://<accountname>.dfs.core.windows.net/<container>/<filename> or https://<accountname>.dfs.core.windows.net/<container>/<subfolder> will fail.

 https://docs.microsoft.com/en-us/power-query/connectors/datalakestorage

[frenchphil]

Thanks for your message

Actually, in theory, it doesn't work but I have noticed PQO sucess connecting to a subfolder. In my case, I have 1 container with 2 subfolders. PQO can access to one of them but not both. An another case, I have 1 container with 2 subfolders and it's successful connecting both.

I noticed that connecting to a subfolder was the only method to allow automatic refresh with oAuth2 authentification (despite what Microsoft documentation indicates as a limitation). I don't know why but, when you put the subfolder in the datasource (https://<accountname>.dfs.core.windows.net/<container>/<subfolder>), the refresh works (we have been tested this configuration since one week without any fail!)

[otravers]

It's possible that the documentation is out of date, or that loading a subfolder directly sometimes works but is not supported. Have you tried authenticating with the Account Key instead of the organizational account? 

[frenchphil]

I can't have access to the Account key because I am not the owner of the Datalake and it is a "shared" datalake with several customers.... I hope, MS will implement the token authentification in this case, that would be more secure.