AMA: Use cases for Power Automate per flow licensing

[sedolan]

Thank you for providing this Community AMA session.  My question is around applicable use cases/scenarios around Power Automate per flow licensing.  I understand when per user licenses would be most relevant/applicable, but can you provide some real-world examples/scenarios where per flow licenses makes more sense for a customer organization?  When would a customer choose to go with per flow over per user, and why?  Thanks!

[KlausF]

We use the per Flow licensing for our CoE tool kit. we have too much data for the normal license, so we run always in API limits. with this flow license we have 250 k API and the flow runs with higher priority.

[FlowHawk]

One scenario I've had is that we built a Power Apps Portal that would receive a CSV from a user. We had a flow in the background that would parse the CSV and take a variety of actions. We licensed this flow with the per flow license because of the reserved capacity (to further ensure we wouldn't hit any call limits for such a critical flow), because there were premium connectors, and because the rest of the organization didn't have per user licenses. You can think of it this way:

If you create a flow with premium connectors for your whole org of 1000 people (where the users will be running the flow in their own context, like from a SharePoint site or Power App), you can either license everyone with a per user license (1000 * $15 = $15,000) or license this one flow with a per flow license ($100). But also note the addition of the reserved capacity as an added bonus.

[ChrisGarty · Accepted solution]

@sedolan , 

@KlausF has a great example.

Candidate flows would include:

1. any flow that is heavily used and draining a user's daily request limit: Requests limits and allocations - Power Platform | Microsoft Docs

2. any flow that is bumping into performance limits, since the flow will then execute with the High performance profile: Limits and configuration - Power Automate | Microsoft Docs