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

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Gallery / Power Automate - Webinars and Video Gallery / Impersonate Power Automate ...

Impersonate Power Automate actions when flows are called from Power Apps

Views (1422)
RezaDorrani Profile Picture Posted by RezaDorrani 12,145

Hello everyone,

 

👉 Did you know there is a way to set Run-As permissions for connectors in flows called from Power Apps❓

This opens up scenarios to run actions with "elevated permissions". Similar to the "Impersonation Step" feature in SharePoint Designer Workflows.

Scenario: User has Read access on SharePoint List but can Create Items via Power App.

 

The new Power Apps (V2) trigger in flow gives us Run-as capabilities in Power Automate & opens up possibilities of SharePoint Security/permission impersonation by elevating user access in Power Apps.

The magic is in the "Run only users" setting of Power Automate flows triggered from Power Apps using the V2 connector.

 

Video includes the following:

✅ PowerApps Security with data connections & Sharing

✅ Power Apps run based on Permissions of data source

✅ Call Power Automate from Power Apps

✅ Run Power Automate actions with elevated permissions (different user account)

✅ Call flow from Power Apps to run under elevated security.

 

#PowerApps #PowerAutomate #SharePoint #Permissions #ElevatedAccess


Thanks,
Reza Dorrani, MVP
YouTube
Twitter

 

Categories:

Comments

  • eetech65 Profile Picture eetech65
    Posted at
    Impersonate Power Automate actions when flows are called from Power Apps

    @Anonymous Were you able to find a work around for this?

  • Community Power Platform Member Profile Picture Community Power Pla... Microsoft Employee
    Posted at
    Impersonate Power Automate actions when flows are called from Power Apps

    Based on my own experience, this functionality only works with non-solution aware apps and flows. If you try triggering the flow from an app that's within a managed solution, an error will occur and the flow will not trigger.