Forum Discussion

philip_gen2's avatar
philip_gen2
Frequent Visitor
9 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 via Organizational Account. But once we click next we get the following error message:

 

An exception occurred: DataSource.Error: Downstream service call to url 'https://wabi-north-europe-q-primary-redirect.analysis.windows.net/v1/workspaces/<workspace_id>/lakehouses' failed with status code 401. (Session ID: <session_id>, Region: europe)

 

We already tried with different users (all workspace Admins) but it always fails. The <workspace_id> id in the error references the correct workspace.

data engineering
lakehouse
  • philip_gen2's avatar
    philip_gen2
    9 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

7 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    9 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
      9 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

  • v-venuppu's avatar
    v-venuppu
    Icon for Community Support rankCommunity Support
    9 months ago

    Hi philip_gen2 ,

    Thank you for reaching out to Microsoft Fabric Community.

    Thank you Anonymous Youraj8271  for the prompt response.

    This issue is caused by a known authentication limitation in Dataflow Gen2. Even if you are a Workspace Admin, Dataflow Gen2 still requires explicit item-level permissions on the Lakehouse.

    To fix the 401 error, go to the Lakehouse --> Manage permissions --> add the user directly --> give Contributor or Admin.Once the Lakehouse has direct item permissions, the Dataflow Gen2 connection should work normally.

     

    • philip_gen2's avatar
      philip_gen2
      Frequent Visitor
      9 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

  • Youraj8271's avatar
    Youraj8271
    Icon for Resolver I rankResolver I
    9 months ago

    Thanks for sharing this issue. I am learning Fabric and Data Engineering as well, and these discussions help beginners like me understand the platform better. Hope you get a quick resolution.

  • Youraj8271's avatar
    Youraj8271
    Icon for Resolver I rankResolver I
    9 months ago

    Thanks Anonymous for breaking down the troubleshooting steps so clearly.
    As someone learning Fabric Data Engineering, it’s very useful to see what can cause 401 issues in Dataflow Gen2 and how credential + capacity settings impact Lakehouse connections.

    Really appreciate your detailed explanation.

  • v-venuppu's avatar
    v-venuppu
    Icon for Community Support rankCommunity Support
    9 months ago

    Hi philip_gen2 ,

    Thank you for confirming that the issue got solved.I would suggest accepting your approach as the solution so that it would be really helpful for others in the community who might be facing similar issues and can address them quickly.