Change pipeline ownership to Service Principle

[Ayush05-gateway]

Hi Community members,

Looking for a solution to the problem with ownership of pipelines: I’m using Microsoft Fabric and would like to update the ownership of pipelines (or switch the Run As account to a service principal). The reason is that one of our team members, who owned several pipelines, has left the organization and was removed from the Fabric AD group. As a result, all pipelines owned by them failed to execute. 

Reassign Pipeline Ownership to other user is a temporary solution so looking for a strategic solution.

The connections used by these pipelines are mostly Web2 (Rest API) connections to 3rd party applns. that only authenticate using anonymous mode or have a defined user/pwd.

Thanks.

[tayloramy · Accepted solution]

Hi @Ayush05-gateway, 

No - you can’t set a Fabric data pipeline’s owner to a service principal today. Ownership can be taken over by a user (via the item’s “Take over” action), but there’s no UI or documented API to assign ownership to a service principal. Pipelines then run under the owner’s/scheduler’s user context. See Microsoft’s docs on taking ownership and run identity: Take ownership of Fabric items and Notebook/pipeline run security context.

I recommend submitting an idea for this so the CAT team can put this on their roadmap. https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideas

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.