Announcements
I'm facing an issue in Power Apps + Power Automate that I haven't been able to resolve, even after following all known best practices.
I’ve developed a Canvas App in Power Apps that triggers a flow to upload files to a SharePoint document library.
The flow is packaged in a solution and uses a connection reference for SharePoint.
During deployment to the target environment, I explicitly bind the SharePoint connection reference to a dedicated service account (ServiceAccount@company.com) that has access to the SharePoint site.
@company.com
In the flow's run-only user settings, I’ve set it so that the app uses “this connection” (the service account) — not the run-only user's own credentials.
I repeated the previous step in the target environment
The app itself has no SharePoint connection — I’ve confirmed under View > Data Sources that SharePoint is not listed.
The flow uses the Power Apps (V2) trigger, and all SharePoint actions are configured using the correct connection reference, which is bound to the service account.
Despite all of this, end-users are still prompted to authenticate with SharePoint when opening the app or triggering the flow. The prompt asks them to log in with their own SharePoint credentials, which defeats the purpose of using the service account.
I just have another question regarding assigning run-only users. It seems that I have to add run-only users to the flow in my development environment before deploying the solution. This way, I need to add all the users in my development environment in order to be able to select them in the run-only users section, which is not an ideal option (they have nothing to do in my dev environment!). Is there a way to leave this section in the flow blank and then adjust it in my target environment after deployment? I tried once, but it didn’t work (the user is prompted to use their own credentials for SharePoint when they open the app)
How can I reset the flow in a managed env? It doesn't allow me to remove the flow from the app and add it again, as you mentioned in your previous post.
You're right about not migrating this setting from dev to prod. However, it seems that the migration happens behind the scenes, without any indication in the flow settings of the target env. It's strange, but when I set only one "run-only" user in my development environment and then deploy it to a managed env, all users the app is shared with in the target env can access the SharePoint connection I initially defined in the dev environment, without needing to be added in the "run-only" users section of the target env (I didn't modify anything in the target env!).
When I reverse the process—leaving the "run-only" users section blank in the dev environment and adding users in the target env with the same SharePoint connection—the user is prompted to authenticate with their credentials for SharePoint when they open the app.
I just don’t get it!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Vish WR 638
Haque 317
WarrenBelz 315 Most Valuable Professional
