Invoke pipeline using Workspace Identity fails

Hi CCal,

Thank you for your follow up and patience. We apologise for any inconvenience caused.

In the new Invoke Pipeline activity, the available authentication options in the connection user interface are currently limited to Organizational Account and Service Principal. Unfortunately, the "Workspace Managed Identity (WMI)" option is not yet available in the connection dropdown, although WMI is supported for other operations in Microsoft Fabric, such as accessing Lakehouses or Warehouses. The documentation on Workspace Identity refers to general use cases but does not yet extend to pipeline invocation, which explains why this option is not visible in the UI.

At present, the Invoke Pipeline activity does not support WMI for authentication. Additionally, attempting to use Service Principal authentication results in an "Unexpected error" due to backend limitations. Hence, only Organizational Account (OAuth 2) authentication works reliably with the new Invoke Pipeline UI.

This limitation is by design, and our engineering team is aware of it. An enhancement request has been raised by the community to enable support for Workspace Identity and Service Principal authentication in Invoke Pipeline scenarios. Please find the relevant ideas forum link below for your reference:

Invoke Pipeline Task - Workspace Identity Authenti... - Microsoft Fabric Community

If enough users vote for this feature, Microsoft will prioritise its inclusion in a future release.

Until official support for WMI authentication in pipeline invocation becomes available, we recommend using the Organizational Account option in the Invoke Pipeline connection as the most stable approach.

We hope this information helps resolve your issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.