Invoke pipeline using Workspace Identity fails

Hi CCal,

Thank you for the followup.

As per my understanding, the new Invoke Pipeline activity in Microsoft Fabric supports Workspace Identity; however, it does not currently facilitate Service Principal authentication through the GUI. Since you are invoking a pipeline within the same or another workspace, the simplest and most secure approach is to utilise Workspace Managed Identity (WMI), which requires no secrets or client IDs.

Kindly follow the steps outlined below to resolve the issue:

1. In Microsoft Fabric, navigate to your workspace settings and confirm that Workspace Managed Identity is enabled.
2. In the Azure Portal, go to the Target Workspace's Resource Group and access the Access Control (IAM) settings. Assign the Contributor role (or higher) to the Workspace Managed Identity of the outer pipeline. You can identify this Managed Identity by its name format: Microsoft Fabric - <Workspace Name>.
3. In the outer pipeline, open the Invoke Pipeline activity and create a new connection. For the Authentication type, select Workspace Managed Identity. Please do not select OAuth 2.0. If the connection was previously saved with OAuth 2.0 and cannot be changed, delete the existing connection and create a new one from scratch using Workspace Identity.

Additionally, please refer to the following links for further information:
Workspace identity - Microsoft Fabric | Microsoft Learn
Authenticate with Microsoft Fabric workspace identity - Microsoft Fabric | Microsoft Learn

We hope that the above information will assist in resolving the issue. Should you have any further queries, please feel free to reach out to the Microsoft Fabric community.

Thank you.