Power Automate Premium Per User licenses in approval flows that use Premium connectors
Hi, I have a Power Automate approval flow (specifically, instant type) in SharePoint Online that uses Premium connectors. It is correct that only page’s Authors who start the approval flow needs an Premium Per User license because the flow runs in their context? On the other hand, isn’t it required that flow’s Approvers also have a Premium Per User license? In particular, this is what is meant here when in the Faq for terms “runs”:
Instant flows (button, hybrid triggers) run in the context of the user who invokes them, regardless of the connections used in the flow. If an automated or scheduled flow uses a premium connector, only the owner needs to have a Premium license.
If an instant flow has premium connectors, every user who runs the flow needs a Power Automate Premium license. In such cases, instead of licensing every user, you can license the flow with a Process license.
For complete official faq:
Thanks, John,
Hi, I have a Power Automate approval flow (specifically, instant type) in SharePoint Online that uses Premium connectors. It is correct that only page’s Authors who start the approval flow needs an Premium Per User license because the flow runs in their context? On the other hand, isn’t it required that flow’s Approvers also have a Premium Per User license? In particular, this is what is meant here when in the Faq for terms “runs”:Instant flows (button, hybrid triggers) run in the context of the user who invokes them, regardless of the connections used in the flow. If an automated or scheduled flow uses a premium connector, only the owner needs to have a Premium license.If an instant flow has premium connectors, every user who runs the flow needs a Power Automate Premium license. In such cases, instead of licensing every user, you can license the flow with a Process license.For complete official faq:https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/faqs#who-needs-to-purchase-a-premium-license? Thanks, John, Read More