Power Platform Community Forum Thread Details

I am configuring all of my agents according to the instructions and even tried all other options. Seems like there is a bug. Please assist as I am sure I am not the only one.

Cannot integrate flows regardless of many options, tried teams, outlook, gmail, and regular mail.

Error:

Flow client error returned with status code "Forbidden" and details "{"error":{"code":"ConnectionAuthorizationFailed","message":"The caller object id is '4621873d-1391-4bb6-af3d-7c68cb08544b'. Connection 'new_sharedgmail_27ae5' to 'shared_gmail' 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:

Calling actions from Copilot Studio

Hello

If i read correclty you r post : the message say that 'forbidden' about using "gmail" as a connection.

for the next part of my answer : I assume you'r making the test on a professionnal tenant, manage by an IT administrator. So if not the case, sorry :) i don't want to offend , english is not my native language.

In professionnal environnement : "IT pro" block nearly always the capacity to use "not microsoft" tool like gmail with power platform or agent, it's a security mesure (many time people who steal user account, used those connector to send outside data with agent and/or power platform).

If you need a gmail connexion in a professionnal use case, you can ask you'r IT admin to allow the connector to you. It's possible to make exception in certain condition (depend on the company policy and governance of your company, not alway possible)

For others like Teams, etc etc, if the message is "forbidden" too : it's probably nearly the same : IT Administrator could block everything (often the case in default governance in company, they want you to ask and explain why you need the connexion, very often the case in real world : it's call "apply DLP " by IT admin.)

So no solution to avoid an IT administrator security law, i hope this explaination help you understand this not a bug but intented to be block by security administrator.

I hope this help :)