Dataflow Gen2 authentication to Lakehouse without user dependency?

Hi Parchitect,
Thank you for reaching out to the Microsoft Fabric Communtiy.

Currently, when Dataflow Gen2 writes to a Lakehouse, only Organizational account authentication is supported, so the connection remains tied to the authenticated user.

For this specific scenario, service principal authentication is not available for the Lakehouse destination in Dataflow Gen2. As a workaround, many organizations use a dedicated non-personal service account and manage access through workspace roles to reduce dependency on individual users.

If you require fully non-user-based authentication, consider using Fabric Pipelines or Notebooks, which support service principal authentication for automation scenarios.

Workspace Identity aligns well with this requirement, but it is not currently supported for Lakehouse destination authentication in Dataflow Gen2.

For reference:

• Workspace Identity: https://learn.microsoft.com/fabric/security/workspace-identity
• Dataflow Gen2 destinations: https://learn.microsoft.com/fabric/data-factory/dataflow-gen2-data-destinations
• Service principals in Fabric: https://learn.microsoft.com/fabric/enterprise/service-principals

  
  I hope this helps. Please let us know if you have any further questions.
  
  

Hi Parchitect, 

Dataflow Gen 2 is inately user bound right now. 
THey need to be owned by a user to run, regardless of what connections they're using. As soon as you try to bind the dataflow to a service principal it will no longer be runnable. 

I hope that this is improved in the future, but it's where we're at right now. I do not recommend using dataflow gen 2 for anything that can't be owned by an individual.