Canvas App - Unable to add flow because of co-worker connection permissions

[ramonahyde]

Hello dear community,

I want to add an owned Power Apps V2 flow to some Power App that is using co-worker's connection reference (which is also co-owner of the flow) but then I've encountered this error message:

The details are:

[{"code":"ConnectionAuthorizationFailed","message":"The caller object id is 'some_id'. Connection 'some_id' to 'shared_onedriveforbusiness' cannot be used to activate this flow, either because this is not a valid connection or because it is not a connection you have access permission for. Either replace the connection with a valid connection you can access or have the connection owner activate the flow, so the connection is shared with you in the context of this flow."},{"code":"ConnectionAuthorizationFailed","message":"The caller object id is 'some_id'. Connection 'some_office365_connection' to 'shared_office365users' cannot be used to activate this flow, either because this is not a valid connection or because it is not a connection you have access permission for. Either replace the connection with a valid connection you can access or have the connection owner activate the flow, so the connection is shared with you in the context of this flow."}]

FYI I'm using the new Power Automate experience. With the old one, I get some generic message something like "Request HTTP error".

I tried to follow the tip "have the connection owner activate the flow, so the connection is shared with you in the context of this flow". So my co-owner turned off then on the flow but the error message is still there (even after refreshing Power Apps studio)... Perhaps it isn't the right procedure? Or we have to wait some time before it's recognized as "shared" with my account ?

I don't know what to do because the account I'm using (who is the main owner of the flow) can't create a connection ref to Office 365 Users (nor OneDrive which is also used in the flow) because of his current license (it's a service account) for now. 

'Could find similar issues in the internet, but there were no replies at all 😒... So thank you in advance if this issue can be solved!

[ramonahyde · Accepted solution]

As a workaround, all connection references in the flow must be owned by my co-worker and she has to add the flow herself in the Power App (so she must be co-owner of it too). She does not have to be flow's main owner.
If I ever refresh or remove/add this flow, I still get the message so avoid doing this for god's sake! But I can still update the app without issue.

Cumbersome, but this does the job.

EDIT 12/29/2022 : Actually you can add a flow with your connections (you must be the owner) even though they reference another account. But you must create the connection inside the reference yourself (so if you want to use another account, you must authenticate it, someone else cannot do that for you). Then you can add the flow and you are the only one to be able to do so.

Also I couldn't find any feature in the UI to change an owner of some connection reference, so instead I replaced it with another one for each flow (tedious task).

[techsan20]

ramonahyde

I am having the same issue.  My co-worker created a flow that had a manual trigger.  I am creating a power app that will use that flow.  I updated the flow to use a power app trigger.  Went to power app to add it and got the message you got which I assume has to do with the connections within the flow my co-worker created.

I am getting from  your solutions post and edit:

- My co-worker could go into the power app and should be able to add the power automate flow to the app no problem.   Is that correct?

- I am not following your 12/29 edit to your solution post.   Are you saying that I have to change the connections/connection references in the flow to my account and then I can add.  

From what I get is that in the end is the user that created the connections in the flow that can add to power app?  Any thoughts on ways to develop a flow in future to get around this?

[darylvogan]

Has there been a fix for this, or does the original creator really have to be the one adding flow to the app? This seems illogical, as the original creator might not exist anymore.

[Abhishek_Kunder]

Having similar issue, let us know if any fix exists without creating new connection.

[Dajaran]

This issue is still in the System 😞

Even being co-owner of the flow, does not give me the permissions to add the Flow back in.

In my Case we did deploy the App / Flow with a dedicated Service Account which I don't have access to. So whenever I need to update the Flow to incorporate changes, I loose the Flow inside the App.

Someone has to login as that Service Account again and add the Flow back into the App, very annoying.

[darylvogan]

Thanks, very unfortunate

[mdc1111]

Getting same type of error if there is a solution please update ..!!

[darylvogan]

BUMP: how is this possibly still an issue by MS? What is the proper set of procedures to avoid this issue? Is everyone experiencing this?

[Spirytus]

Yes, it's still an issue.

(and yes, I'm a coowner of the flow that I just tried to add to the app myself)

The workaround mentioned by ramonahyde still works but it's most definitely a nuisance.