Forum Discussion
Invoke pipeline using Workspace Identity fails
Hi CCal,
Thank you for your question on the Microsoft Fabric Community Forum.
As I understand, the new Invoke Pipeline activity does not support Service Principal (Workspace Identity) authentication yet. It uses OAuth 2.0, which is based on user authentication. Because of this, when you try to invoke pipelines using workspace identity, it fails with an authentication error. This is not a bug but a limitation in the current version.
Please try the following workaround to use a non-user identity like Service Principal or Workspace Identity to invoke pipelines:
- Use a Web Activity instead of Invoke Pipeline.
- Call the Fabric REST API to start the pipeline:
POST https://api.fabric.microsoft.com/jobs/instances?jobType=Pipeline - In the Web Activity, set the authentication type to Organizational. Use a Service Principal or Managed Identity that has the correct permissions on the workspace.
Also, please check this link for more details:
Invoke pipeline activity - Microsoft Fabric | Microsoft Learn
We hope this helps you resolve the issue. If you have any more questions, please feel free to ask the Microsoft Fabric community.
Thank you.
Hello v-pnaroju-msft ,
Thank you for your reply.
However, I am not able to get this to work. When I select Auth type to Organizationl, I would not be able to enter the Service Principal credentials (TenantID, Client ID and secret).
Also, even If I select the Service Principal as Auth Type, I get "Unexpected error" and cannot save the connection.
The link unfortunately does not delve deep into the connection part.