Forum Discussion
Dataflows Storage can't connect to ADLS Gen2
Hi,
I am struggling with connecting my PBI Tenant to my Dataflow storage. I have set up everything based on MS doc, so it means:
- I am using ADLS Gen2 with the correct region, Hot performance/access tier, Hierarchical namespaces
- Created a BLOB container with "powerbi" name
- Added access rights directly in MS Azure Storage Explorer to - Power BI Service, Premium and Power Query Online plus to Other added Execution rights
- In Azure Portal on storage in Access Control (IAM) I am the owner of the resource (not inherited from subscription) and I have added Power BI Service as a Reader and data access role
Then when I try to connect it in PBI Service in Admin portal and put there correct connection details I receive:
A few months ago I already set up storage with PBI, but then I wanted to change it. So I disconnected the previous storage and wanted to add a new one. Even though I followed all the videos, blogs, and docs I can't make it work. I would be pleased with any kind of help.
Thanks.
Pavel
bh56 you have a little bit different issue. You have to set correct access roles in IAM (access control) in Azure Portal. You have to be the owner of the resource (not inherited one).
My problem was solved via MS Support - the only thing was that I had to delete a container (named powerbi) that I had in my ADLS Gen2. The mechanism behind creates this container automatically. Now everything works for me.
Let me know whether you need some additional assistance.
11 Replies
Hi PavelR ,
Here is someone who had the same problem with you and has solved it. Please refer to Unable to connect to Azure Data lake Gen2 storage on Power BI to use DataFlow.
Before you can configure Power BI with an Azure Data Lake Storage Gen2 account, you must create and configure a storage account.
Best Regards,
Yingjie LiIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
When I remove Power BI Service in the role of a Reader from Access Control (IAM) in my storage account, then I get the "Can't connect to storage account"
When I add it back, then I am again stuck with the error message that I have shown in the first post.
Does anybody know how to overcome those issues?
Based on the documentation limits of the integration of ADLS and PBI, you are only able to integrate once at least as implemented within the preview. This is probably why you are having the issue even though you were able to unlink it. I suggest opening up a ticket and see if they can clear anything in the backend that is probably preventing it from integrating.
There is an upcoming feature that is integrate an ADLS at the workspace level slated for preview in July 2020. Maybe by then either the limiation from above can be cleared out or the integration at the workspace level will help resolve your issue.
Thanks for your response michaelm91 Yeah, I am about to open a support ticket.
Did you ever find out what your issue was? I'm having the same issue.
Can't connect to storage account
We couldn't connect to the storage account because you don't have the required role-based-access-control (RBAC) permissions. Make sure you're assigned the "Reader and Data Access Role" for this storage account, and try again.
bh56 you have a little bit different issue. You have to set correct access roles in IAM (access control) in Azure Portal. You have to be the owner of the resource (not inherited one).
My problem was solved via MS Support - the only thing was that I had to delete a container (named powerbi) that I had in my ADLS Gen2. The mechanism behind creates this container automatically. Now everything works for me.
Let me know whether you need some additional assistance.
@PaveIR Thanks for getting back to me. I did add the roles under IAM.
Do you have your storage defined as "hierarchical namespace enabled". I do, wondering if that is my issue.
It's unclear to me at this point if this is needed to leverage ADLS Gen2 storage or not.
As an owner of your Azure Storage account, you are not automatically assigned permissions to access data. You must explicitly assign yourself an RBAC role for Azure Storage. You can assign it at the level of your subscription, resource group, storage account, or a container or queue.
You cannot assign a role scoped to a container or queue if your storage account has a hierarchical namespace enabled.
