Workspace Identity not authenticating to Invoke Pipeline

[KimMW]

I have a Pipeline in a Workspace which includes an Invoke Pipeline activity to invoke another pipeline from the same workspace. When I create a new connection in setting up this activity, it offers me Workspace identity as an option. When I check the documentation of the Invoke Pipeline activity, this also indicates that Workspace identity authentication is an option (https://learn.microsoft.com/en-us/fabric/data-factory/invoke-pipeline-activity). However, when I attempt to run the pipeline, I get an error on the invoke pipeline activity with Error code 2108 - Unauthorized: The caller is not authenticated to access this resource. 

I have seen this post and have been through the troubleshooting steps provided in the accepted solution by @tayloramy ; the Workspace Identity is created for the workspace and assigned the Workspace Contributor role on this workspace (containing both the outer and the inner pipeline) and on a second workspace that is the source of some data in the inner pipeline. However, this has not resolved the issue and I still get the same error. Are there any further troubleshooting steps I can try, or is there a known limitation here?

(I have also read through this post which talks to a similar error; I find the answers here to be somewhat contradictory amongst themselves and also to contradict the post above and the documentation in saying that workspace identity authentication is not supported for this feature)

[v-echaithra]

Hi @KimMW ,

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Chaithra E.

[v-echaithra]

Hi @KimMW ,

Thank you @tayloramy  for your inputs.

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Best Regards,
Chaithra E.

[tayloramy]

Hi @KimMW, 

First, are you using the new pipeline activity and not the legacy one? The legacy one won't work for this. 

Can you send a screenshot of the workspace identity tab of the workspace settings for your workspace so we can confirm?

If the workspace identity has the contributor role, everything *should* be working. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[KimMW]

Hi @tayloramy 

Yes, I can confirm that I am using the new invoke pipeline action rather than the legacy one. 

Here is the screenshot of the workspace identity tab

[tayloramy · Accepted solution]

Hi @KimMW, 

What you're doing should be working to the best of my knowledge. 

I just tried this in my enviornment, and it works without issue. 

My setup: 
One pipeline that sends an email and triggers the second pipeline
the second pipeline just sends an email

The connection in my invoke pipeline activity looks like this: 

And this works without issue. 

Note that if the workspace identity only has viewer, I do get the error you are describing. 

But your workspace identity does have contributor, which works on my end. 

Are you able to make a new pipeline and test it? I wonder if there is something weird with your existing pipeline. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.