Power Automate Process license

[Tony101]

Hi ,

I'm new to Power Automate & trying to understand the licensing & costs for our organization to use PA.

With the new Power Automate Process license can that bot run more than one flow? 

If we had, say 20 flows in total,  how many Power Automate Process licenses would we need?

We have ~ 200 user licenses so it's hard for us, currently, to justify the per user licensing.

Thank you

Tony

[BCBuizer]

Hi @Tony101 ,

Are the 20 flows you are talking about desktop flows or cloud flows?

If they are desktop flows, should they run in attended mode or unattended mode? 

If they are cloud flows, do you ant users to be able to use premium connectors?

What existing licenses do the users already have as these may already enable them to do what's required?

All the above are needed to be able to give a better informed advice. In case you wish to have a look yourself, have a look at the Power Platform Licensing guide (page 6) to find more details.

[Tony101]

Thanks @BCBuizer  I do have the guide... thx.

We have M365 E1 licenses .
They 20 flows aren't developed yet. we're just doing a few to better  understand the process.
Most would start with a form and with or without an approval process do the following

• Update a list
• Update a user profile
• Send the results in an email
  
  Basic stuff I know but it's a start.
  
  As we have only an E1 license on-prem AD sync to Azure AD is only unidirectional. Someone had mentioned that there is a connector that can update on-prem AD but I haven't explored that yet. If there is that could become part of the work flow.
  So I would guess desktop flows as a start.
  
  If one Power Automate Process bot can process multiple cloud flows that would be appealing. I'm assuming here that the bot's are for cloud flows, so correct me if I'm wrong
  We've only recently moved everything from on-prem to M365 so we have a lot of education on the go in many areas .:) 
  
  tia

[BCBuizer]

Hi @Tony101 ,

In line with the discussion in this article it seems the solution is to create desktop flows to make changes in the on-prem AD. Those desktop flows require process licenses, but maybe you wont need 20 licenses, depending on the workload as per this article. 

In turn the desktop flows can be triggered by cloud flows, which can be triggered from Power Apps. For this part the E1 license should be enough to cover.