Answered

Users being asked to sign in when flows all have Run As users

(0) Share

Report

Posted on by nksse

I'm deploying a new canvas app for users which has Power Automate flows that will run as my integration user, rather than as the users themselves.

I've set, double checked, and now triple checked that all flows have Run As users set for all connections. But when my users launch the app, they're being asked to sign into two of the five connectors themselves.

I've also tried sharing each of the flows with my own user to test if that had anything to do with it. But still I'm being asked to sign in.

What else should I check to ensure that my users won't have to sign in to any credentials when they use the app?

Categories:

Building Power Apps

All responses (9)

Answers (2)

Sort by

WarrenBelz 156,714 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @nksse ,

As you using the Power Apps V2 connection then Run Only Users then Use this connection - or are you setting it some other way ? If PA V2, also did you connect the Flow after you made these settings ?
nksse 66 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @WarrenBelz

I've set the Run As user on the Details page of each flow. In this flow, the integration user (crossed out in blue) built the flow and shared it with me (crossed out in green).
When I launch the app as the me, it wants me to sign in to create two connections.
Verified answer

WarrenBelz 156,714 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @nksse ,

The other part of the question was if you did this before you attached the Flow. If not, you need to get those connections out of the App as they will still be there. I have apps with the same settings in Flows which work fine as long as the Flow is added after the connections are configured.
nksse 66 on at

Like
a
(0)

Report
Copy link

Link copied!
Thanks @WarrenBelz.

That seems to have been the issue. The steps I think fixed the issue were:
Ensure all flows in staging have Run As users set
Refresh all flows in the canvas app (I assume this step loads the 'new' config into the app)
Export the app from staging and re-import the new version to production
nksse 66 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi again @WarrenBelz

Unfortunately this issue has reared it head again. This time I've made sure that before exporting my app from staging I:
Made sure each flow had the run as users set to my integration user
Refreshed EVERY flow in the App itself
Exported the unmanaged solution as a managed solution
Imported it into our production environment
However, after importing I noted that not all the Run As users are set in all flows; there were definitely some I had to re-add in production. But the canvas app can't be edited in production, therefore I can't try refresh the flows there.
Therefore, my suspicion is that the production app is not seeing the newly set Run As users.
Any ideas?
WarrenBelz 156,714 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @nksse ,

I must admit the Flows I have done have been connected "live" (out of business hours with the fall-back of versioning and flow backup) for probably the reason you are experiencing.
nksse 66 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks again @WarrenBelz.
Verified answer

nksse 66 on at

Like
a
(1)

Report
Copy link

Link copied!

Hey @WarrenBelz

Thought I'd share my success. I found a forum post (that I can't find again) which mentioned that only Flows triggered by the Flow button for mobile works with Run As users.

I had been using the Power App (V2) trigger. I changed my flows, refreshed them in the app, deployed the new version of the Solution to Production and it works!
WarrenBelz 156,714 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @nksse ,

Interesting - how exactly do you use the manual trigger in this process - I assume you switch back to Power Apps V2 before you deploy ?