Power Platform Community Forum Thread Details

I have a few scenario

First my basic understanding is that when they say pricing is per bot/month, the definition of a bot in this context is one VM, not one automated process. If that is correct, I could have one process that I want to kick off, it would need to run on one VM for about 1 hour. Then I have other processes that run similar duration at different times. That would all be one Unattended license.

Before any more, is that correct?

Assuming it is, if I had 50 users that have access to trigger Web flows that have back-end Desktop flows. At any given time I want the ability to have up to 5 running at any time. My assumption is there is a way to Pool 5 VMs each with an unattended license (so 5 unattended licenses) and have them waiting for calls.

Is that possible? Any links on how to Pool VMs in that manner?

Adding to that scenario, what would happen if a 6th process was called? Would it fail? Would it queue?

Lastly, If I wanted to have the 5 unattended licenses dedicated to this process during work hours (say 8 AM-8 PM), but then take 3 and use them to run other processes, how would that be done? Would you have to remove them from the pool? Or just send jobs to them from other processes and the fact that they are busy takes them out of the pool by default?

Thank you,

John

Categories:

Power Automate Desktop

Before any more, is that correct?

- VMs and procesesses are both often called bots, which can be confusing. One VM and one Unattended RPA add-on will never give any issues. The scenario is correct.

You would need to have 5 unattended licenses, but you don't necessarily need to have a matching set of VMs. Could be 10 or 50 VMs with different configurations optimized for other desktop flows.

Is that possible? Any links on how to Pool VMs in that manner?

Yes, they're called machine groups.

Manage machine groups - Power Automate | Microsoft Docs

Adding to that scenario, what would happen if a 6th process was called? Would it fail? Would it queue?

Queue.

Desktop flows will be queued until unattended licenses are available. Flow priorities can be used to control this.

One thing to bear in mind is that once a VM is part of a machine group, it can not be targeted individually.