Attaching a flow to a Power App fails when the flow contains an Outlook 365 email action. The error received is "Failed during http send request." This occurs when the credentials used when the email action was added to the flow are different from the credentials of the user who is editing the Power Apps. Example, User A is editing the Power App and is trying to attach a flow that was created by User B. The email action in the Flow is using User B's credentials. The Power App and the Flow are shared to User A and User B as co-owners. The only way to get the flow attached to the power app is if User B opens the app for editing and attaches the Flow. User A can't attach the Flow.
One quick step could be the user who has the flow created to save it as a template.
The user who will be attaching the flow to the App can then leverage the template and rebuild the flow - thereby all connections would be under their account.
Also, please note when a Power App calls a flow all the connections in the flow run under the context of the user running the Power App.
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.
The problem is that when you trigger a flow manually using a Power App the flow will then run in the context of the user running the Power App. So when you attach your flow to the Power App it tries to run the Send an Email action in User A's context, not User B's context. If User A doesn't have the authority to send the email it will fail. That's the way Power Apps and Power Automate are designed to work. You have to make sure that User A can create a connection to do all the actions required in the flow or it won't work.
As Pstork said, if User A doesn't ave permission the flow will fail. You could also set up send as permissions for each user who would run this flow, but each user would have to be set up individually so depending on how many users would have access this might not be preferable.
Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
In our scenario, the user simply needs to have permission to send an email via Outlook 365. All our developers have this permission. If User A creates the Flow and attaches the Flow to the Power App, User B is able to run that app because (as was mentioned in the replies) the Flow runs under the credentials of the user.
Given this, then why can't User B attach the same Flow (created by User A) to a Power App that User B owns when both the App and the Flow are shared? This same issue doesn't exist for other types of connectors such as SQL and CDS.
Seems like a bug with the Outlook 365 connector since it applies this restriction when other connectors don't.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Join us for the next call on June 15, 2022 at 8am PDT.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.