Not able to connect azure data lake storage in Power BI Desktop

[imPriti]

Hi Community,

In Power BI desktop, when I select data source as Azure data lake storage then I am getting below attached error. However if I choose blob data source then with same container URL I am able to connect without any issue.

[BhavinVyas3003 · Accepted solution]

Check Storage Type:

• Go to Azure Portal > Storage Account > Configuration
• Ensure Hierarchical namespace is Enabled (required for ADLS Gen2)

Verify Container:

• Confirm the container name (adlf-blob) exists and is correctly spelled (case-sensitive).

Use Correct Connector:

• If hierarchical namespace is not enabled, use Azure Blob Storage connector instead of ADLS.

[KonradZawel · Accepted solution]

I've hit that issue before when connecting to ADLS Gen2. One thing to double-check is whether you're using the right authentication method - sometimes switching between "Organizational account" and "Access key" makes a difference, depending on how the storage is set up.

Also, make sure the ADLS endpoint doesn’t have a firewall blocking access from Power BI. If you're working behind a VPN or proxy, that can mess things up too. Clearing Power BI's permissions cache helped me once as well

[OscarTh]

To fix the "Access forbidden" error connecting Power BI Desktop to Azure Data Lake Storage Gen2, make sure you use the correct Gen2 URL format (with dfs.core.windows.net), clear existing credentials in Power BI, and reconnect with your organizational account. Also, verify your Azure permissions include Storage Blob Data Reader, check firewall settings to allow your IP, and use the Organizational account authentication method. This usually solves the issue.

[rohit1991]

Hi @imPriti 

The error you're encountering in Power BI Desktop typically occurs when there's a mismatch between the data source type and the actual storage configuration. From the message, it looks like you're using an Azure Blob Storage URL with the Azure Data Lake Storage (ADLS) connector, which expects a different endpoint format. ADLS Gen2 requires theHierarchical Namespace (HNS) feature to be enabled in your Azure Storage account.

If HNS is not enabled, your storage behaves like regular Blob storage and should be accessed using the Azure Blob Storage connector instead. Since you're able to connect successfully with the Blob connector, it's likely that HNS is not enabled for your storage account. To resolve this, either enable HNS (if appropriate for your use case) and use the ADLS endpoint (https://<account>.dfs.core.windows.net) or continue using the Blob connector for consistent access. Also, double-check your container name for accuracy, as it's case-sensitive. Let us know if switching the connector resolves your issue.

[v-dineshya · Accepted solution]

Hi @imPriti ,

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

Thank you @BhavinVyas3003  and @KonradZawel for sharing the valuable information.

Hi @imPriti , In addition to @BhavinVyas3003 , i am adding some points.

Error indicates a mismatch between the data source you selected (Azure Data Lake Storage Gen2) and the actual endpoint or container configuration.

Please refer below things:

1. Azure Data Lake Storage Gen2 (ADLS Gen2) is built on top of Blob Storage, but not every blob container is automatically a Data Lake container unless hierarchical namespace is enabled.

2. Power BI Desktop has separate connectors for Azure Blob Storage and Azure Data Lake Storage Gen2. These connectors expect different kinds of configurations.

You're using:

https://adlfsA.blob.core.windows.net/adlf-blob

Note: This is a Blob Storage endpoint, not necessarily a Data Lake Gen2 endpoint.

Please follow below steps to fix the issue.

Step 1: Confirm HNS is Enabled

Go to the Azure Portal. Navigate to the storage account adlfsA. In the “Configuration” pane, check "Hierarchical namespace" = Enabled --> Required for ADLS Gen2. If disabled, your container is a regular blob and not usable via the ADLS connector.

Step 2: Use the Correct Connector

Depending on whether HNS is enabled:

If HNS is disabled: Use the "Azure Blob Storage" connector (as you did successfully). Do not use the ADLS connector.

If HNS is enabled: Use the "Azure Data Lake Storage Gen2" connector. Make sure to enter only the account URL, like

https://adlfsA.dfs.core.windows.net/

Note: Not the full blob URL.

Example

If you want to connect to a folder inside a Data Lake Gen2 container:

Use:

https://adlfsA.dfs.core.windows.net/adlf-blob/

Note: Only if HNS is enabled

If it's just a blob:

Use:

https://adlfsA.blob.core.windows.net/adlf-blob/
with the Blob connector.

If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.

Thank you

[v-dineshya]

Hi @imPriti ,

If my response has resolved your query, please mark it as the "Accepted Solution" to assist others. Additionally, a "Kudos" would be appreciated if you found my response helpful.

Thank you

[v-dineshya]

Hi @imPriti ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thank you.

[v-dineshya]

Hi @imPriti ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thank you.

[KonradZawel · Accepted solution]

I've hit that issue before when connecting to ADLS Gen2. One thing to double-check is whether you're using the right authentication method - sometimes switching between "Organizational account" and "Access key" makes a difference, depending on how the storage is set up.

Also, make sure the ADLS endpoint doesn’t have a firewall blocking access from Power BI. If you're working behind a VPN or proxy, that can mess things up too. Clearing Power BI's permissions cache helped me once as well

[BhavinVyas3003 · Accepted solution]

Check Storage Type:

• Go to Azure Portal > Storage Account > Configuration
• Ensure Hierarchical namespace is Enabled (required for ADLS Gen2)

Verify Container:

• Confirm the container name (adlf-blob) exists and is correctly spelled (case-sensitive).

Use Correct Connector:

• If hierarchical namespace is not enabled, use Azure Blob Storage connector instead of ADLS.