Connector permission

[Anonymous]

I don't think I've seen this asked before. I've created connectors in my powerapps and flows, and I thought they were using the specific user who created them as the authenticator. But when a user goes to access the power apps, it puts in their name as the authenticating user.

Where this is a problem for me is 2 fold. I have a flow that sends an email. I want the emails to go out as the person who created the flow (in this case its a noreply email account). But when the user authenticates, then the emails go out as that end user instead of the noreply account.

In that same vain, i want a file to be saved to a central onedrive location - the noreply users onedrive folder. But when the end user authenticates, it stores the file in their onedrive folder instead.

Is there away to explicity call out which user I want to use for the email send (without having to allow all users the Send on Behalf permission for the No Reply) or the onedrive folder (without sharing the folder)? it would seem if I could explicitly say which user those connectors were to run under, then I wouldn't have to fidgit with the send on behalf of or sharing the folder.

[v-yamao-msft · Accepted solution]

Hi @Anonymous,

How is your flow created? Is it triggered by a PowerApps button?

Have you shared the app with group members?

I assume that you have added that flow on an app button.

Per my certain knowledge, if you share an app that includes a flow, users who run the app will be prompted to confirm or update any connections on which the flow relies, which means that the flow will run based on the end user’s account info. Send an email from end user’s email account, save the file in their OneDrive folder.

If you would like to send out the email on the account of the flow creator, please consider removing the trigger PowerApps button and using a different trigger instead. In another word, save the data from PowerApps to SharePoint list, then trigger the flow with “SharePoint – When an item is created”, then the email will be sent out only from the user who set up the flow.

Hope this could be your reference.

Best regards,

Mabel

[Anonymous]

Ah ok. 

I do think it would be best if it allowed the connections to be run as a specific person, but knowing that there is a work around makes sense. 

I'll give that a try and see where I get.

[DonKirkham]

To be clearer, the connector in the flow (when set up with a SharePoint trigger) uses the account used to setup the connector. In most cases, this is the user that is creating the flow, but you can add a connection with a different user, like a Service Account.  Then make sure the service account has the correct permissions for the data accessed by the connector. For example, a flow might access a SharePoint list, look up User profile information that is not included in SharePoint and send an email. This involves 3 connectors (SharePoint, O365 Users for profile info, and Office 365 connector for sending the email.)  Each of these can use a Service account to accomplish what you need.