It's not possible to run a Dataflow Gen2 as Service Principal.
This is documented here: Background Jobs - Run On Demand Execute - REST API (Dataflow) | Microsoft Learn
It would be great if it was possible to run Dataflow Gen2 as a Service Principal.
The ability to run Dataflow Gen2 as Service Principal would enable:
- identity isolation between environments
- using dedicated service principals per dev/test/prod environments
- avoid reliance on user accounts
- users may leave the project, so we want to avoid reliance on user accounts
7 Comments
- YevgenyM
Advocate IV
As bernhard0614 wrote this feature is practically unusable in high frequency deployment cicd...
We need this feature to connect to many sources where pipelines (copy data) still doesn't provide good support for.
miguel yaronprigal
Is there any ETA for this? - Thanks bernhard0614 for linking my issue - it's a daily thing for me right now - whenever I deploy using git refresh or fabric cicd using the service principal, I get this pipeline SPN issue, so having to go in and manually toggle it off and on is just so disruptive to my workflow especially when doing a lot of deployments
- Hi, Dataflows are completly unusable for use without Service Principal support. We want to rely on workspace identities / service principals rather than user accounts. Bug has also been filed for fabric cicd library: https://github.com/microsoft/fabric-cicd/issues/971 Do we have a rough timeline for this? Thanks, Bernhard
- Causing a lot of issues with deployment with fabric cicd right now - needs to be fixed
- This is an absolute need for us too. Officially supporting the fabric-cicd project, recommending SP as a deployment entity and disabling Organizational User authentication for deploying makes it a must have feature that I expected to be implemented since OA deployment was deprecated/disabled.
- miguel
Community Admin
Status changed:NewtoUnder Review - This is very much needed. We have a lot of dataflows in use - when we deploy to higher environments via fabric-cicd, the dataflows deploy successfully but are useless because the SPNs that deploy them are not able to run them via the activator triggers we have.
