Deployed PowerApp is Prompts for User Connection Authentication

[IPC_ahaas]

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.

[Pstork1]

When you import the solution aren't you being prompted to pick what connection to use? That's the one the connection reference is supposed to use. But you should be able to pick one setup for the service account during import.

[IPC_ahaas]

Yes, I am. It defaults to the Connection References within the Solution.

But when clicking the "..." it shows it's using my email address for each one:

but in my Dev Environment, it shows the Connection Reference is using my service account

[Pstork1]

Connection References still have underlying Connections that are specific to a single environment.  So when you import the solution to the new environment it will prompt you to make new connections or select from an existing connection. It looks like you have existing connections for your account, but not for the service account, so its defaulting to those. When you do the import you need to create connections using the service account just like you did in the original environment and make sure its using those and not the ones under your name.

[IPC_ahaas]

Then what is the point of creating a Connection Reference when I have to readd and redefine the Connection in each Environment anyway?

[Pstork1]

Because the connection reference is a logical wrapper around the connection. It allows changing the connection without having to re-edit the app. If you use a regular connection then you have to create a new one by editing the app, which may then require fixing things in the app.  The connection reference virtualizes the connection making it possible to change the connection without changing the references inside the app.

In a normal import process if there is a connection in the environment that matches the existing connection it will use that one. In your case I suspect there isn't one for the service account you used, but is one for you. So it defaults to the maker account.  If neither existed you would be prompted to create a new connection on import.  Your problem arises because you are using a non-standard connection (one with a specific account not your own) and your own account does exist as a connection in the new environment.

[IPC_ahaas]

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

[Pstork1]

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.

[Pstork1]

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.

[IPC_ahaas]

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.

[Pstork1]

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?