Power Platform Community Forum Thread Details

Hi,

Originally posted this on the powerapps board but its probably more a powerautomate question. I would like to know if the below is how flow is meant to function when using a single cloud account in an instant flow.

We have a flow that is being triggered from powerapps and has a basic outlook send email (v2). The email action is linked to one of our cloud email accounts in the connection reference as all our staff still have on prem accounts.

When clients attempt to run the flow the email action gives this error indicating the action is running using their personal on prem accounts and not the account specified on the action:

REST API is not yet supported for this mailbox. This error can occur for sandbox (test) accounts or for accounts that are on a dedicated (on-premise) mail server.
clientRequestId: 2e91c2c5-75ab-4b7e-954c-f452dbd12805
serviceRequestId: f2d2e90e-3ece-45f1-4b4e-14d1a838c449

Our testing:

Created a canvas app, added a button, created a new flow by going to the actions menu for the button within the canvas app, pressed PowerAutomate then create flow.

Within that flow I add a PowerApps trigger and an outlook send email v2 action. I tell the email action to use the cloud outlook account via connection references.

I save the flow, publish the power app.

I share the app to colleague's involved in the test.

Results:

If I run the app and push the button the email triggers
If I open the flow editor and manually run the flow the email triggers
If a colleague pushes the button in the app the flow errors
If a colleague opens the flow editor and manually runs the flow the email action errors
- On the error there is the option for my colleague to fix permissions. If the colleague signs into the cloud account the flow works in both the app and manual testing

It appears the email action does not use the cloud account unless staff manually log into the cloud account individually which is not workable as the account password is not meant to be shared like this.

It also appears inconsistent on whether staff simply playing the app even receive the option to fix permissions on the outlook action when they receive the screen to "Allow" access to their own accounts.

Is this normal behaviour?

We have other apps and flows working with the same cloud account in the outlook action. The only difference in process we can think of is with those apps the flow's are automated flows and not instant flows. So its not the user running the app that's triggering the flow but the change at the data source so we are assuming the system's run the flow using a different account.

Any advice is appreciated, from what I can see an organisation that has not moved its staff accounts into the cloud is unable to utilise the outlook actions for instant flows in a workable manner despite having specific cloud accounts created to run the actions.

Any advice appreciated.

Ben

Categories:

Building flows