Hello All,
I'm facing a bit of a weird issue when calling a flow triggered by Power app.
I have a flow with Power app trigger.
This flow has only one action - send an email V2 office 365 outlook
Email is sent to "user A". I'm User A
Connection used for this action is a service account "user B".
Power app button on select runs the above flow.
Now when any user clicks on the button, flow sends the email from current user who triggered the power app.
I'm expecting the flow to send email from service account User B.
I'm have troubleshooting this issue but I haven't found a solution yet.
Things I have tried.
1. Change the Trigger from powerapp to say SharePoint. Emails gets send from user B.
2. Tried creating new app or new flow, the issue exists.
3. I have two existing flows which have powerapp Trigger and both of them are able to send email from connection reference that is user B.
4. Any new app or flow fails always sends email from current user and ignores the connection reference.
Interesting bit is when I as user A triggers the flow then the email is sent from service account user B.
This is happening across different environments.
Any idea on how to further troubleshoot the issue?
Hi Guys, can you use the advanced property in the SendEmail V2 action, and set the Sender email.
Easy...
Hi,
I am also experiencing this inconsistency between a flow that is triggered automatically and a flow that is fired directly from Power Apps. From Power Automate, the flow sends an email using the connection reference, from Power Apps, it is the user context that prevails, making the email sent from the user address.
Is there anything i can try to fix it?
Many thanks.
Thank you Warren for your help on this one.
I guess my source of truth was wrong. The two existing flows and one app (all part of same solution) still uses connection reference rather than current user context triggering the flows.
These were done atleast 6-8 months in past and there might have been some issue at that time so I'm assuming it is just working as is by chance or due to some bug.
Since this existing apps or flows have not been updated since then I feel they continue to work.
Any new apps or flow do run by current user context.
Even new app calling the existing flows run in current user context.
The issue might be with the existing app.
For now, i believe we can agree on the fact the Flow triggered from a power app runs on current user context and not the connection.
Thank you and really appreciate your help.
Hi @AK06 ,
Firstly I so not use PowerAppsV2, so that may be the issue. By "personal tenancy", do you mean my user environment? I just re-checked the Sent Items of my Service Account (it owns all Apps, Lists and Flows) and all emails in there are non-power apps triggered (we have a lot triggered by submitted forms) . As I mentioned earlier all photos are created by users in the field (the Flow is Power Apps triggered).
Update to this
Asked a colleague to create a new app and flow. Email gets sent out from current user account.
I'm just wondering, could it be related to IAM within our tenancy?
@WarrenBelz if you have some time, would you mind testing out this scenario in one of your personal tenancies, if you have one?
Hey,
So i ran few test cases
didn't work = Sent from current user account instead of connection account
worked = Sent from connection account instead of current user account
1. PowerApps v2 - new app, new flow, new environment - Result didn't work
2. New App calling existing flow sending emails - didn't work
3. Testing on existing app and existing flow - It works as it used to
4. Personal tenancy - new app , new flow - It works. It is sending emails from connection account and not user account.
My next step would be to get a colleague in my tenancy to create an app and flow to test the experience. It looks like the issue is with my account when i create new connection for O365 outlook send email action
@AK06 ,
Please post how this goes - you may have found a bug or change. I know mail always is sent by the connected user (we send hundreds of emails in our apps and would have picked this up quickly if different). I have also just checked a Library with hundreds of photos done each day and they are all created by the user.
you and I have different experience.
Check the flow screenshot - create item creates the item in list with connection account and not the user who triggered the powerapp.
Send an email sends the email with current user account and not the connection account.
My other existing flows, sends email with connection account.
I'm going to try two things now.
Use powerapp V2 trigger to see if there is any difference.
Create a POC in my personal tenancy to rule out any account issues.
Would be helpful if anyone reading this can give it a try and share their experience.
Thanks in advance.
@AK06 ,
Always from the current connection. If I want one from the Flow connection, I use "when an Item is created" in SharePoint as the trigger and write the parameters to a new record in a "dummy" list.
And just to add, if I use a different connector like SharePoint create an item in the flow triggered by Power app - item is created by connection and not by current user
WarrenBelz
637
Most Valuable Professional
stampcoin
570
Super User 2025 Season 2
Power Apps 1919
473