Note
Access to this page requires authorization. You can try signing in or .
Access to this page requires authorization. You can try .
How to use process capacity
Note
Process capacity and Unattended RPA capacity have been combined in a single capacity pool and can be used interchangeably within the Power Automate platform. They have exactly the same value and role.
Within the Power Automate portal:
- Process capacity is based on a purchased Process license.
- Legacy Unattended RPA capacity is based on an Unattended RPA add-on.
Process capacity or legacy Unattended RPA capacity can be allocated to a machine or to a cloud flow.
Allocate Process capacity to a machine
When Process capacity is allocated to a machine, it becomes an unattended bot. Each unattended bot on a machine can carry one unattended desktop flow run at a time. So if a machine needs to execute multiple unattended runs simultaneously, it needs as many unattended bots as it has simultaneous unattended runs to perform.
To allocate Process capacity to a machine, go to the machine details page and select Settings.
👁 Screenshot of the machine page showing no unattended bot allocated.
Use the Unattended bots slider to allocate some process capacity to the machine and save.
👁 Screenshot of the machine page settings with one unattended bot added.
You now have a machine that can perform unattended RPA.
Note
- Machine max bot supported depends on your machine and its OS. The maximum value this parameter can reach is 10 (for some Windows Servers).
- Available capacity in the environment shows how many unattended bots can still be created. Keep in mind that the process capacity is a shared resource between all users within an environment and so use only what you need.
- Enable auto-allocation lets unattended bots be automatically allocated to a machine when an unattended run requires it. Multiple unattended bots can be auto-allocated for simultaneous unattended runs. Once auto-allocated, the unattended bots remain on the machine until manually deallocated.
- For a global overview of how process capacity is used within the environment, select the Manage capacity utilization link. It also provides an option to request more capacity.
Allocate process capacity to a cloud flow
When a Process license is allocated to a cloud flow, the flow's plan changes to Process plan in the portal. This licenses the cloud flow to run premium actions independently from the user license, with a daily entitlement of 250,000 actions (shown as Power Platform Requests in admin center reports). Every trigger and action execution counts as one action. Actions inside a loop run once per iteration, so loops multiply your action count.
To allocate process capacity to a cloud flow, go to the cloud flow details page and select Edit.
👁 Screenshot of the cloud flow details page showing the option to change the plan.
Note
At creation, a cloud flow is by default based on the user plan.
Change the plan used by the flow to Process plan and save.
👁 Screenshot of the cloud flow page settings showing the process plan allocation.
The cloud flow is now independent from the user license.
Important
Only solution flows (flows that are in a Dataverse solution) can have Process capacity assigned or stacked. To add an existing flow to a solution, go to Solutions > select a solution > Add existing > Automation > Cloud flow. Admins can add flows in bulk via PowerShell.
Stack multiple Process licenses on a cloud flow
Multiple Process licenses can be allocated to a single cloud flow to increase its daily action entitlement. Each additional Process license adds 250,000 actions per day.
| Process licenses | Daily action entitlement |
|---|---|
| 1 | 250,000 |
| 2 | 500,000 |
| 3 | 750,000 |
| 5 | 1,250,000 |
| 10 | 2,500,000 |
| 10+ | N × 250,000 |
Up to 10 Process licenses can be stacked on a single cloud flow.
Currently, each Process license must be directly assigned to the flow that uses it. Flow groups (sharing a single pool of Process capacity across multiple related flows) and automatic capacity inheritance from parent flows are planned but not yet available.
Estimate your daily usage: (actions per run) × (runs per day) = daily actions. If this exceeds 250,000, stack additional Process licenses to match your expected daily volume.
Note
- Some older environments in the Europe region might have capacity limitations that reduce the effectiveness of stacking above 3 licenses. If you encounter this, consider creating a new environment.
- To try Process licenses before purchasing, admins can provision a free 30-day admin-managed trial from the Microsoft 365 admin center. Trial Process licenses have the same entitlements as paid licenses and can be stacked.
Related information
Feedback
Was this page helpful?