Outlook365 connector

(0) Share

Report

Posted on by uwenagel

382

Hi there

We have an app that is sending an email using the Office365Outlook.SendEmailV2(...) method which is working in principle.

Now we want to use a dedicated account for that mail, not the one that is currently logged in. This way the mail would always come from a service user.

We are thus trying to set up the connector with the other account.

In the connections section it is shown with the current users account:

In the three dots there is a possibility to change the account, however when doing that, it is not changed at all!!

What is the correct way to set up a Outlook365 connector with a different account?

Categories:

Building Power Apps

I have the same question (0)

All responses (9)

Answers (0)

WarrenBelz 153,034 Most Valuable Professional on at

Like (0)

Report

Hi @uwenagel ,

You can use the From: parameter when sending mail, providing the user has access to the account the mail is being sent from. You cannot change the account in the way you describe as the whole purpose of connector authentication is that the logged-in user has the appropriate licence to use the connector. There is a Flow workaround possible requiring a dummy list with the parameters (then it would come from the service account)

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

Was this reply helpful? Yes No
WarrenBelz 153,034 Most Valuable Professional on at

Like (0)

Report

Hi @uwenagel ,

Just checking if you got the result you were looking for on this thread. Happy to help further if not.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

Was this reply helpful? Yes No
uwenagel 382 on at

Like (0)

Report

Unfortunately this is not what I was looking for. I have to say that we had this functionality (connector with different users) but for any reason this is gone and cannot be reproduced. The workaround with Automate will probably eventually lead to the same problem.

So the problem still exists!

Was this reply helpful? Yes No
WarrenBelz 153,034 Most Valuable Professional on at

Like (0)

Report

Hi @uwenagel ,

I am not sure what you had before as this has never been possible to my knowledge.

Was this reply helpful? Yes No
uwenagel 382 on at

Like (0)

Report

But we have the same situation with another connector (Office 365 Users)! See the attached list of connections! The one starting with svc... is the service user.

Was this reply helpful? Yes No
WarrenBelz 153,034 Most Valuable Professional on at

Like (0)

Report

Hi @uwenagel ,

When using the Office365Outlook.SendEmail connector, it authenticates on the connection of the logged-in user (it has to determine whether they actually have a licence for an Outlook connector) and the mail comes from them unless you use the From: parameter (then they need Send access to that mailbox).

Was this reply helpful? Yes No
rb 835 Super User 2024 Season 1 on at

Like (0)

Report
Hey, one way I can think of solving this is by invoking a Flow which has Run-As configuration set by your desired 'Send-As' user, which will force all emails coming from your PowerApp to be sent through that user's Outlook connector.

The main difficulty setting this up is that "Run-As" is only available for Instant flows, not PowerApps Triggered flows. As such, I needed to call the Instant as a child flow. (Now we've moved the functionality from PowerApps to two layers down: PowerApps -> PowerApps Flow -> Instant Flow........... not sure if this is ideal, but it works 😉)

Create Svc-Email "Instant" Flow
Create an "Instant Flow" in your Solution
Set up any dynamic properties as input arguments (in my example I am only using Subject and Body)
Feed arguments to "Send an email (V2)"
Ensure you have at least one response-type action

Create Svc-Email "PowerApps Triggered" Flow
Create a "PowerApps Triggered" Flow in your Solution.
Call child Instant flow, assigning dynamic properties to "Ask in PowerApps"
Save Flow, then add to your PowerApp

Set Run-As
Make sure your Send-As account has "Office 365 Outlook" connection created
Open the Instant Flow details
Under "Run only users" assign your Send-As account's Connector and Save the setting
Run from PowerApps!

I required similar functionality when using Office Scripts - it was easier to set up Run-As from one account which has access to the script instead of all users requiring access to the script. I found it could be a bit awkward during development though, as I use my own account to edit the Flow, then have to re-set the Run-As everytime I make a change to the Child Flow.

Hope this helps!

Was this reply helpful? Yes No
WarrenBelz 153,034 Most Valuable Professional on at

Like (0)

Report

Thanks @metsshan ,

You can actually do it a lot easier than that with a Flow using a "dummy" list, creating a new record in it with all your parameters and then triggering the Flow from "When a record is created". This thread was questioning why a Flow needs to be used.

Was this reply helpful? Yes No
rb 835 Super User 2024 Season 1 on at

Like (0)

Report

Ahh, I see now. I thinnk that would require some kind of Implicity Shared Outlook connector, which to my knowledge does not exist.

Was this reply helpful? Yes No