Unanswered

NotAllowedConnectionReference - Outlook 365 Connector

(0) Share

Report

Posted on by C-Jac

I have an app, which triggers a flow, that sends an email, where send as is a shared mailbox. The service account has send as access to the shared mailbox.

Everything works great, except ONE user gets an error when clicking the button. All other users can trigger the flow just fine.

The user get's the following error:

Run failed: {"error":{"code":"xxxxxxx","message":"{\"errorCode\":\"NotAllowedConnectionReference\",\"message\":\"Connection reference 'shared_office365_1' can not be given by invoker.

- The user has Power Apps Premium license

- The Outlook Office 365 connection is using a service account

- The run as has been set to use the service account every time the flow is run

Is there something I am missing? I can't seem to find anyone else having this issue, and no matter what I try I can't seem to find the reason to this error. And the error is ONLY for ONE user.

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (0)

Michael E. Gernaey 53,960 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @C-Jac

They have the license, but can you verify that they are added to the environment and given proper roles?

I would verify their config against someone that should have equal config(s) and see whats missing.

I would even go into Power app / Environment / Users / Select them and Run Diagnostics on them

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
SC-14081350-0 2 on at

Like (0)

Report
Copy link

Link copied!

Same problem.

Connection is set to run only on service account, and is in a managed solution (so no I can't refresh the flows in the app)

I went through exact same process with same connection type in another app, and it works fine.

Was this reply helpful? Yes No