You’re offline. This is a read only version of the page.
My PowerApp has a Flow attached to it. I am using a service account for the connections to send an Email and access a SharePoint Site. I expected the app to maintain this when I published it to another Environment, but it's prompting the user at startup.
How do I avoid this? The user shouldn't be prompted to use their account for connections I purposefully setup to use a service account.
I deleted the Connections from the Dev Environment, created new Connection References and re-created the Connections, then deleted the old Connection References and relinked the Steps to use the new Connection Refences. I republished all customizations and redeployed it to the Beta Environment. Same issue.
I have an open request with Microsoft to get to the bottom of this. Very frustrating.
I didn't share anything with the user running the app other than the app itself. I did share the app directly with the user instead of using a security group, but I don't think that should make a difference. The actual connection in that environment is owned by me as the maker.
Any possibility that an earlier version of the app used those connections directly and then they were removed and a flow with connections was used instead? It may be an old ghost connection that is causing the security prompt.
Could it be that I need to share the Connections in the new Environment?
If I have to add users to the Environment, and assign Security Role, and Share the app, and Share the tables, maybe I have to share the connections? Completely absurd that I need to share each piece of this pie, but I wouldn't put it past Microsoft at this point.
In the last screenshot if you click on the ellipses menu next to the SharePoint and the Outlook connection reference do those also have a connection using jarvis?
These screenshots are without changing anything.
2)
3)
5)
6)
7) Shared the app with a Security Group that has my test user in it.
Security Group:
My test user (Tony Stark) still gets prompted to use their account.
I just did a quick test and was able to use a different account on the connection and the user was not prompted for permissions in the production environment. Here are the steps
In the Dev environment
1) Created a Solution with an App, a Flow, and a Connection Reference
2) Set the Connection Reference to point to a connection with a different account "jdoe@acmeman.com"
3) Set the Run Only users setting to use that connection for the connection reference.
4) Published all Customizations and Exported Solution as a Managed Solution
In the Production environment
5) Created a connection using "jdoe@acmeman.com"
6) Imported the Managed Solution. During Import I picked the existing Jdoe@acmeman.com for the Connection reference Connection
7) Shared the app with e1test@acmeman.com.
😎 Logged in as e1test in a private browser session and ran the app. No Prompt for connections.
#3, #5, and #6 are the key steps I believe. #6 will default to the makers connection if one exists in the production environment.
Let me do some testing. It may just not work when using a connection in the connection reference set for a service account. I haven't tried that scenario.
Deleted and reimported the App again. This time I choose the service account for the Connection Refences.
The Flow now shows the service account.
The App STILL prompts me to use my account
#1
WarrenBelz
791
Most Valuable Professional
#2
MS.Ragavendar
410
Super User 2025 Season 2
#3
mmbr1606
275
Super User 2025 Season 2
Share
Report
All responses (
Answers (
