Forum Discussion

philip_gen2's avatar
philip_gen2
Frequent Visitor
11 months ago
Solved

DataSource.Error (401) when trying to connect to Lakehouse from within a Dataflow Gen2

We have a workspace connected to an F2 capacity. Within this workspace we want to read tables from a lakehouse via a Dataflow Gen2. When setting up a lakehouse connection, we can successfully sign in...
data engineering
lakehouse
  • philip_gen2's avatar
    philip_gen2
    11 months ago

    Hello v-venuppu ,

    thanks for your support. While your solution did not fix my problem it motivated me to try one more thing, which finally solved to problem:

    I think my issue is related to my company having muliple tenants and the tenant where the fabric capacity/workspace is located in is not the native tenant of my user. We now created a new native user within the fabric tenant and gave it admin permissions to the workspace. When I log in with this user I can create connections to lakehouses. After sharing the connections, I can re-use them also with my normal user

Anonymous's avatar
Anonymous
Not applicable
11 months ago

Hi philip_gen2 ,

Please try below things to fix the issue.

 

1. Re‑authenticate the connection: Go to Manage Connections and Gateways in Power BI Service/Fabric, delete the Lakehouse connection, and re‑add it using Organizational Account. Several users found that refreshing credentials restored proper authentication.

 

2. Check Fabric licensing/capacity: Ensure your workspace is on a supported Fabric capacity (F64 or higher is recommended for Lakehouse + Dataflow Gen2). F2 is very limited and may block certain downstream calls.

 

3. Merge data sources privacy setting: In Dataflow Gen2, enable “Merge data sources” under privacy settings. This allows the mashup engine to perform cross-source operations without isolation errors.

 

4. Confirm that all users have at least Contributor rights on the Lakehouse item itself, not just Admin rights on the workspace.

 

If my response as resolved your issue please mark it as solution and give kudos.

 

Thanks,

Dinesh

philip_gen2's avatar
philip_gen2
Frequent Visitor
11 months ago

Hello Anonymous,

thanks for helping, but unfortunately your suggestions do not solve the issue:

  1. Refreshing or deleting+re-creating connections does not help, we tried multiple times with different lakehouses and users.
  2. I am working on an F2 capacity for a client in a different tenant and we do not have any problems connecting to lakehouses, so I would rule out capacity size as the root cause.
  3. Enabling the following setting did not seem to have any effect: "Allow combining data from multiple sources. This could expose sensitive or confidential data to an unauthorized person"
  4. The user accounts we used to test connections have all available permissions on the lakehouse

Best regards,

Philip