eMail sent from PowerApp - can it use the running users email credentials?

[TGrounds]

I have a PowerApp solution that writes information to a data source for a survey to be sent.  I have a Flow that is triggered when a new record is written to the data source.  In that flow it sends an e-mail constructed from the data elements of the data source.  That all is working as expected.

Question:  How do I have the connection to Outlook or Office365 use the credentials of the person running the PowerApp rather than my credentials associated with the shared flow?  There is a community of users using the PowerApp but all the survey e-mails appear to be coming from me rather than the PowerApp user.

Thanks - 

Tom.

[v-monli-msft]

Hi @TGrounds,

To let other PowerApps users run the flow, you would need to share your Flow with Owner permission to these users. By default, the connections inside the shared flow would use your credentials. But you could let the users to change to their own credentials. Just navigate to the Team flows > Edit flow > select the "..." in send an email action, and switch to their own credentials:

Regards,

Mona

[ericonline]

Hello @v-monli-msft and @TGrounds. I have a similar issue I'm working through. Maybe it can apply and you could use it / help. 

I had our Active Directory team set me up with a powerapps@mycompany.com email address. Is there a way to set this "user" up with permissions so that things like Flows have a more generic "From" email address? 

Its kind of annoying when all PowerApp emails across our organization have my pretty face on them!

[RusselThomas]

Hi ericonline,

If the powerapps@mycompany.com is a different user account, then you just need "Send As" or "Send on behalf of" permissions for that account to use it in your Flows.  If it's just an alias on your mailbox, then I'm not sure it will change anything.

I usually set up a dedicated user account for a business area to house their departmental apps and flows.

This is often referred to as a "service account" in most organisations, but the reference can be misleading - IT departments (and especially security) use service accounts for running system or server services - they usually have non-expiring passwords and are also given the "log on as a service" privilege and have the "log on interactively" privilege removed by IT as part of the creation process. 

This is not what you're looking for 🙂

So for now, let's refer to it as the 'origin' account.

Here, you're looking for a normal 'user' account, whose passwords and connections you will have to manage manually unless your business has some sort of account Vault service which can help manage this.  The vault helps secure it as you can log on as the 'origin' account, create and share your apps and flows with your normal user account, then log off the 'origin' account and edit apps and flows from your normal user account.  Anyone wanting to access the 'origin' account to create more apps/flows would then need to go through the vault process to do so.

It's also useful to manage staff turnover and handover, considering a key business process and app built on Flow and PowerApps can grind to a halt if the person who built it leaves the company and has their account disabled.

Hope this helps,

RT