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.
Hi v-pnaroju-msft,
I was facing similar issue where I am trying to inovke pipeline from same workspace. The workspace ID has Workspace Admin access but still I am getting "Unauthorized Error" even though in auth Workspace ID is selected
- v-pnaroju-msft10 months agoCommunity Support
Hi Dark_Aria,
Based on my understanding, the Unauthorized error you are encountering when invoking a pipeline using Workspace Identity occurs because Workspace Identity is not yet supported for the Invoke Pipeline activity even within the same workspace. Although Workspace Identity functions for other Fabric operations such as Lakehouses and Warehouses, it has not been integrated for pipeline authentication. Consequently, authorization fails even if your account has Workspace Administrator privileges.
At present, only Organizational Account (OAuth 2.0) authentication is supported. Please switch your connection authentication to Organizational Account.
This limitation is by design, and the engineering team is aware of it. A request to enhance the service and enable support for Workspace Identity and Service Principal authentication in Invoke Pipeline scenarios has been raised by the community. For your reference, please see the relevant Microsoft Fabric Community ideas forum link:
Invoke Pipeline Task - Workspace Identity Authenti... - Microsoft Fabric CommunityIf a sufficient number of users vote for this feature, Microsoft will consider prioritising it for a future release.
We hope this information helps to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.