Currently, the Fabric Data Factory Invoke Pipeline task uses the user's credentials who saved the pipeline to then authenticate to the Azure Data Factory to execute the ADF pipeline. When that user'...
We face the same problem. Our use case: multiple workspaces, each of them orchestrated by their own 'slave' pipelines within those workspaces. Workspaces are interdependent and thus are orchestrated by a 'master' orchestrator pipeline in separate ws. Dependency on SSO makes the solution less reliable and less secure, as pipeline owner's principal must be granted at least CONTRIBUTOR access on all 'slave' workspaces. Workspace Identities could solve this. Furthermore, one would naturally expect workspace identities behaving as OP has mentioned. We are actively looking forward to this improvement. Keep up the good work and thanks!
