I have built a PowerApp that will get a SharePoint list and display each list item in a dropdown menu.
You can select one of the list items then click Submit and it will call a Flow and pass it: User().FullName, User().Email, DataCardValue1 (The dropdown selected value)
The flow will go and manipulate a load of different SharePoint lists and documents and once finished it will send an email as confirmation.
The 'Send Email' block is using a no-reply user as a connection so therefore should send from firstname.lastname@example.org.
This works fine for myself or my colleague who helped build the Flow and PowerApp. However, I have shared this PowerApp with end-users and if they go to submit the PowerApp, the confirmation email will always come from their email and not the email@example.com email.
I've narrowed it down to the PowerApp permissions when the end-user first loads the app. If I switch the accounts when you give the PowerApp permissions from the end-users outlook connection to the no-reply user, the flow will send emails as the correct address. However, this is not scalable as we cannot give out service account credentials to end-users.
Why is the Send Email block in the flow not using the firstname.lastname@example.org connection? Surely the PowerApp should not be asking for an outlook connection as the email is not being sent from the PowerApp.
Has anyone else experience this or know how to work around this issue?
The PowerApp does not have an Outlook connection, please see below screenshot:
We call an MS flow from the PowerApp when it's submitted.
Office365Users is used to get the submitting users details such as name and email address.
The Sharepoint connection is running as an integration user that has appropriate permissions to all relevant lists/document libraries.
In regards to how we are sharing the app, we are sharing as just users of the app. The only users who are co-owners are those who help develop the solution.