web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Power Apps → Power Aut...
Power Apps
Suggested Answer

Power Apps → Power Automate not respecting “Use this connection” (Dataverse permission issue)

(0) ShareShare
ReportReport
Posted on by

Hi everyone,

I’m facing an issue with a Power Apps → Power Automate → Dataverse setup, where the flow does not seem to respect the configured connection and instead runs under the caller’s context.

Scenario

- A Power App triggers a Power Automate flow (Power Apps trigger)
- The flow performs operations in Dataverse (Create/Update records)
- All Dataverse actions are configured with “Use this connection” (service account)
- The service account has full permissions on the tables

Problem

When the flow is executed from Power Apps, I get permission errors in Power automate, as if the flow is running under the end user’s context, not the service account.
Example error:

 

Categories:
I have the same question (0)
  • Suggested answer
    TechFreak Profile Picture
    149 on at

    Hi,

    Yeah, this is a pretty common point of confusion when working with Power Apps → Power AutomateMicrosoft Dataverse.

    What’s happening is that when a flow is triggered from Power Apps using the Power Apps trigger, it runs in the caller’s context (end user) by default, not strictly under the service account—even if your Dataverse actions are configured with “Use this connection”.

    So even though you selected a service account connection, Dataverse still enforces security based on the invoking user, which is why you’re seeing permission errors.

    Why this happens


    • Power Apps → Flow uses the user’s identity to invoke the flow

    • Dataverse applies row-level and table-level security

    • “Use this connection” does not fully override the execution context for Dataverse in this scenario
     

    What you can do

    Option 1: Grant proper permissions to users (simplest)

    Make sure the users running the app have:


    • Required security roles in Dataverse

    • Access to the tables/records being updated
     

    This is the most straightforward fix if acceptable.

    Option 2: Use a child flow (recommended pattern)

    Split your logic into two flows:

    Parent Flow


    • Trigger: Power Apps

    • Pass required parameters
     

    Child Flow


    • Trigger: “Run a child flow”

    • All Dataverse actions configured with service account connection
     

    This pattern ensures:


    • The child flow runs using its own connections

    • Dataverse actions execute under the service account context
     

    Option 3: Use an HTTP-triggered flow (advanced)


    • Create a flow with When an HTTP request is received

    • Call it from Power Apps

    • Use service account connections inside
     

    This fully decouples the user context, but requires premium setup and security handling.

    Quick check

    Also confirm:


    • You don’t have any dynamic connections accidentally switching to “Run-only user”

    • The flow’s Run-only users settings are not overriding connections
     

    Summary


    • Power Apps-triggered flows run in user context by default

    • Dataverse enforces security even if a service connection is selected

    • Use child flows or proper permissions to resolve this cleanly

    Best regards,
    Satyam Pandey

     

    ✅ If this helped solve your issue, please mark it as Accepted Solution so others can find it quickly.

    ❤️ If it was helpful, please click Yes on “Was this reply helpful?” or give it a Like.

    🏷️ For follow-ups, feel free to tag @TechFreak

    💼 LinkedIn

    ▶️ YouTube

  • Suggested answer
    11manish Profile Picture
    3,333 on at
    When a Power Automate flow is triggered from Power Apps, it runs in the caller’s context, and the platform enforces that the user must have permission to use
     
    the configured connections—even if “Use this connection” is selected.
     
    This is why you see the ConnectionAuthorizationFailed error. The recommended solution is to either share the connection with users, configure run-only
     
    permissions correctly, or (best practice) move the Dataverse operations into a child flow that runs fully under a service account.

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.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 424

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
11manish Profile Picture

11manish 290

Last 30 days Overall leaderboard