Fabric Pipeline should run as workspace identity

[pellitteris]

Currently, Microsoft Fabric pipelines run under the identity of the last user who modified them, which can cause disruptions when tenant administrators make changes to security policies, such as enabling MFA or Conditional Access Policy, or when the user is disabled or worse, deleted.
It would be desirable for an enterprise platform like Fabric to run scheduled processes as system user (workspace identities) and independent of the user who developed, updated or deployed it.

[dcsearle]

Totally agree. Fabric is not enterprise grade until you can protect objects from breaking when user account issues arise - this recently happened to us when "something changed" which resulted in us having to touch each pipeline and save it before it would work again. This happened to us on 1st April so not sure if this coincides with when you wrote this post and maybe is why you wrote this post! I would hazard a guess that Microsoft can even cause issues like this themselves when they tweak default settings (like additional security and tenant-level settings which are introduced as features) - so I wouldn't state that this is totally something with our control as admins.

[Liszet]

Totally agree! We recently had a developer quit, and everything they have worked on has stopped working. The identity of the pipeline was one of the issues.