Send Email (V2) action fails with error "You are not authorized to send mail on behalf..." however flow works fine in a different environment with the same connections

(0) Share

Report

Posted on by _sigmaNot_

Hi everyone,

I exported a PowerApps solution that includes this Flow. The Flow works as expected when I run it in the source environment (unmanaged solution), but on the test environment (managed solution) I get the error.

The Flow has a PowerApps V2 trigger however the Send Email (V2) action is configured to run with a service account which has access to email on behalf of the DO NOT reply email I need for my case.

Here's a screenshot of a successful run on the source environment

And failed run on the test environment...

As far as I understand, there should be no issues here since the actions are running with the correct account with access to send email on behalf of the account I'm trying to use.

Has anyone ran into this before?

I'm at a loss and not sure what I can try to troubleshoot this...

Any help is appreciated

Categories:

General topics

All responses (3)

Answers (0)

Sort by

Thanura09 192 on at

Like
a
(0)

Report
Copy link

Link copied!

The error code says send as denied, the message says send on behalf. I'm not experienced enough, but maybe there's something wrong with the exchange setup for the shared mailbox ? because we have two options there, 'send as' and 'send on behalf'. also worth trying after setting to 'full access'
annetoal 1,934 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

You need to talk to the person running your email service to find out whether you have "send on behalf of" privileges on the account you're configuring in the connector. Chances are you're either not using the right account, or you haven't been given privileges.

Anne
Suggested answer

_sigmaNot_ 49 on at

Like
a
(0)

Report
Copy link

Link copied!

Update on this post.

It was a matter of defining the users who can run the Flow. Setting up the connection reference is not enough, the end users who will be running the flow need to have access to the connections and they must be updated in the "Run only users" as suggested on this post.

https://community.powerplatform.com/forums/thread/details/?threadid=ceece48a-56e3-4a49-b9f0-e9e38a4aee4e