Issues with connection references in PowerAutomates called via PowerApps

Like (1) Share

Report

Posted on 1 Jun 2023 19:54:07 by darylvogan

274

I've seen some posts similar to this issue but have not found a definitive solution. I created connection references to SharePoint and Outlook, connecting via a service account. Adding the Flow to the app works fine for me. I shared the flow to my team. However, when a coworker tries to edit the app, they get the error below. Can anyone let us know what we're doing wrong?

[{"code":"ConnectionAuthorizationFailed","message":"The caller object id is 'a290bf3e-20a7-40cb-be5a-944d6679df33'. Connection '0eff1c7a7fda4e68be02fa6de56c8877' to 'shared_office365' 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 'a290bf3e-20a7-40cb-be5a-944d6679df33'. Connection '67d6639f0c094e4783a2f1dab295b744' to 'shared_sharepointonline' 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."}]

Categories:

Connectors

All responses (4)

Answers (0)

Suggested answer

Muhammadusman12 18 on 10 Oct 2024 at 06:41:49

Like (1)

Report

Issues with connection references in PowerAutomates called via PowerApps

Please refer to the blog below; hopefully, it will resolve your issue. I faced the same problem, and it helped me.

Open Blog URL

Regards.
Suggested answer

hasnainhaider68 47 on 07 Aug 2024 at 09:51:20

Like (2)

Report

Issues with connection references in PowerAutomates called via PowerApps

For issues related to expired access token, user connections, or multi-factor authentication (MFA), please follow these steps:

1. Open an incognito window and log in as the user. This will trigger an Authenticator notification to the app, refreshing the access token.

2. Log in, navigate to the connections, and reconfigure any broken connections. Then, access Power Apps or any other solution and perform a hard refresh of the browser. The issue should be resolved.

The problem arises due to inactive or outdated tokens. Refreshing the token through the Authenticator app will resolve the issue.
Please let me know when this is complete.
darylvogan 274 on 29 Nov 2023 at 19:33:39

Like (1)

Report

Re: Issues with connection references in PowerAutomates called via PowerApps

these suggestions did not help
EddieE 4,641 Moderator on 02 Jun 2023 at 04:24:40

Like (1)

Report

Re: Issues with connection references in PowerAutomates called via PowerApps

@darylvogan

A few things to check:

1. Does the Flow have any Premium Actions? If so, then all flow users will need a Premium licence. This was my first thought

2. Does the Flow act on data that only Service Account has access to? eg a SharePoint List with restricted permissions. Users running the Flow will need to have permissions to the data if this is the case

If either of these are the case, and you don't want to get Premium licences for all and/or allow permissions to the restricted data you can setup a Helper List where everyone has the reqd permissions. This would work like

- User creates a list item

- Your current Flow trigger will then be "When an item is created or modified" in the Helper List

- this way the Flow will always run on the Service Account permissions / licences

3. The connector could simply be corrupted and just needs to be removed and re-added back to the Flow.

Have a look at these and see if they help?