Types of Power Automate add-ons

Entitlements to use Power Automate capabilities (standard connectors, premium connectors, attended RPA, etc.) are obtained via licenses and add-ons. This article focuses on add-ons (for details on licenses, visit the types of Power Automate licenses page).

The Power Automate add-ons are categorized as follows:

• capacity add-ons
• consumptive add-ons
• storage add-ons

Add-on type	Description
Capacity add-on	A capacity add-on is allocated to a Power Automate object (cloud flow, machine, and more.). It provides the object autonomous entitlements (the same way a user license provides entitlements to a user).
Consumptive add-on	A consumptive add-on provides a monthly quantity of units (AI builder credits, Power Platform requests), which are consumed and destroyed after usage.
Storage add-on	Storage add-ons provide data storage space to support scaling of various Power Automate operations.

You can purchase those add-ons on the Power Automate Pricing page or from your Microsoft 365 Admin Center (if you're an admin). Learn more on purchasing.

Tip

• As alternative to capacity add-ons, an organization can enable its environments to use the Pay-as-you-go model and get started building flows without any license requirement or upfront costs.
• Within a Pay-as-you-go environment all premium capabilities (including RPA) are available

Extra details on the Power Platform licensing model can be found in the Microsoft Power Platform Licensing Guide.

Power Automate capacity add-ons

A capacity add-on is object-centric: it's allocated to a Power Automate object (cloud flow, machine, hosted machine, hosted machine group) and it provides this object specific autonomous entitlements (regardless of the user licenses owned by persons interacting with the object). Its role is exactly identical to a capacity license.

There are two Power Automate (legacy) capacity add-ons:

Unattended RPA add-on (legacy)

Important

• The Power Automate Process license has replaced the Unattended RPA add-on (same price with more entitlements).
• The already purchased Unattended RPA add-ons are considered legacy and shouldn't be renewed but instead replaced by Power Automate Process licenses.
• The existing Unattended RPA add-ons have however been upgraded to align on the Process license: once assigned to an environment, they now have exactly the same role as Process licenses and those two SKUs can be used interchangeably (allocated to cloud flows or machines).

The Unattended RPA add-on provides the unattended RPA entitlement needed to trigger a desktop flow in unattended mode on a standard machine (unattended mode refers to a desktop flow execution without human supervision).

	Standard machine (physical or virtual)
Scenario description	When allocated to a machine, an Unattended RPA add-on becomes an unattended bot. Each unattended bot on a machine entitles the machine to carry one unattended desktop flow run at a time1.
Unattended bot allocation	Unattended bots can be manually allocated to machines or automatically allocated to them at runtime2. Discover how to allocate an unattended bot to a machine.
Unattended bot release	Unattended bots need to be manually deallocated from the machine.
Unattended bot settings	Each machine - depending on its OS - can support a maximum number of unattended bots (equal to the maximum number of Windows sessions the machine can concurrently open). For example, some Windows server can open 10 Windows sessions at the same time and can therefore be allocated up to 10 unattended bots.
Scenario benefits	- Unattended mode enablement on the machine3 - Multi-session management through multi-allocation - Reduced machine management through auto-allocation at desktop flow runtime

1. When an unattended run is triggered through an unattended bot, Power Automate securely signs into the user's machine on user's behalf, executes the desktop flow actions on the target applications, and then signs out of the device.

2. Unattended bot can be auto-allocated at desktop flow unattended runtime if the machine setting 'Enable auto-allocation' is ON and the machine needs an extra bot to perform the run.

3. A standard machine with no unattended bot can't run unattended except when the user has a Trial license.

Unattended RPA scenarios, without human interaction, are applicable for example, to scenarios such as processing invoices and entering them into a legacy application automatically or scheduled financial reconciliation across multiple systems that can only be automated by clicking user interfaces.

As the Unattended RPA add-on was upgraded to align on the Process license, learn about its extra-capabilities (to cover cloud flows invoking the machine with unattended bot(s) / to be allocated to a cloud flow directly) on the Process license documentation.

Hosted RPA add-on (legacy)

Important

• The Power Automate Hosted Process license has replaced the Hosted RPA add-on (same price with more entitlements)
• The existing Hosted RPA add-ons have been automatically converted into Power Automate Hosted Process licenses: no action needs to be taken

The Hosted RPA add-on provides the hosted RPA entitlement enabling RPA with zero infrastructure (= no physical machine management on the user side).

The add-on is needed to provision a Microsoft hosted machine in the two following scenarios:

• Individual hosted machine
• Hosted machine group

At provisioning of any hosted machine (individual or within a group), a Hosted RPA add-on is auto-allocated to it and becomes a hosted bot.

	Hosted machine	Hosted machine group
Scenario description	A hosted machine enables developers to build, test, and run automation on a constantly active (= turned-on) hosted machine.	A hosted machine group enables developers to run automation on an auto-scaling group of hosted machines. It's continuously adjusting the number of hosted machines turned-on to the desktop flow workload.
Hosted bot allocation	One hosted bot is automatically pulled from the available hosted pool1 and allocated to the individual hosted machine at its creation.	One hosted bot is automatically pulled from the available hosted pool1 and temporarily allocated to the hosted machine group when it scales up: any new hosted machine turned-on in the group consumes one extra hosted bot.
Hosted bot release	The hosted bot is automatically released to the available hosted pool1 at manual deletion of the hosted machine.	The hosted bot is automatically released to the available hosted pool1 by the hosted machine group when it scales down (= when one of its hosted machines is turned-off).
Hosted bot settings	None	A hosted machine group has two scaling settings: - Max bots: the maximum number of hosted bots it can auto-allocate itself to turn-on hosted machines. - Committed bots: the guaranteed number of hosted bots it can immediately auto-allocate itself when required.
Scenario benefits	- Hosted machine constantly turned-on - Reaction time	- Auto-scalability delivering high processing parallelization and reacting to demand spikes - Load balancing2 across multiple hosted machine groups, which optimizes the hosted bot utilization rate

1. The available hosted pool supports all hosted machine groups auto-scaling operations: the hosted machine groups pull hosted bots from it when they scale up and are throttled (= can't scale-up) when the available hosted pool is empty

2. Load balancing refers to the ability of multiple hosted machine groups to scale-up and down at different moments using the same available hosted pool. The load balancing governance is managed through the max bots and committed bots scaling settings.

Each hosted bot can carry one unattended desktop flow run at a time (and so can be seen as an unattended bot too). Individual hosted machines also support attended runs if the user has a Power Automate Premium license or a Trial license.

As the Hosted RPA add-ons was converted into Hosted Process licenses, learn about their extra-capabilities (to cover cloud flows invoking hosted machines / to be used as Process licenses) on the Hosted Process license documentation.

Power Automate consumptive add-ons

A consumptive add-on provides a monthly quantity of consumptive units, which are consumed by flow runs and destroyed after usage (AI builder credits, Power Platform requests entitlement).

AI builder capacity add-on

AI Builder is licensed as an add-on to standalone Power Apps and Power Automate licensing and to Dynamics 365 licenses. AI Builder is licensed on a capacity basis. AI Builder capacity is expressed as service credits. Service credits serve as the single (common) currency across all the scenarios supported by AI Builder. The available service credits decrease when you use AI Builder services. Different scenarios (for example, forms processing, prediction, etc.) use service credits at different rates. Purchase the appropriate number of AI Builder capacity add-on units based on anticipated usage across all scenarios.

Each unit of AI Builder capacity add-on includes 1 million service credits per month. For example, a customer who requires 4.7 million service credits per month (based on anticipated usage), should purchase five units of AI Builder capacity add-on.

Note

• Purchased service credits can be used from AI Builder models included within Power Automate, Power Apps, and Dynamics 365 applications.
• Service credits are deducted / consumed for both training and production usage
• Service credits are pooled across the tenant.

FAQs about the AI builder add-on

I have a Power Automate per user with RPA plan and I got AI builder credits as part of the plan. Can I transfer the credits to someone else?

No. AI builder service credits are pooled at the tenant level and can't be assigned to a particular user. So, any user who runs a flow that needs AI builder service credits needs to use credits from the pool.

Power Platform requests add-on

Power Apps and Power Automate capacity add-ons increase the daily Power Platform requests limits for workloads that need more usage capacity than their allocation. These add-ons provide an extra 50,000 daily Power Platform requests per unit for $50/month. Unused Power Platform requests don't carry over from day to day. You can purchase these add-ons at any time and they remain part of the subscription for the remainder of the subscription term.

You can't assign Power Platform requests capacity add-on packs to users or flows during the transition period. However, Microsoft recommends that you purchase these add-ons to remain within your license terms and to be prepared for when the transition period ends.

If Power Automate is throttling your flows, try Pay-as-you-go to ensure that none of the flows in the environment are throttled. If you can't use Pay-as-you-go, purchase add-ons and create a Microsoft support ticket with the flow details and add-on details so that the support team can provide exceptions for your throttled flows.

Power Automate storage add-ons

Storage add-ons provide data storage space to support scaling of operations.

Process Mining add-on

The Process Mining add-on is a tenant wide add-on that is available with the Power Automate Premium license. It offers:

• Additional 100 GB of process mining capacity to the capacity pool, from which users with the Power Automate Premium license can consume.
• Additional 2 GB of Dataverse database capacity.
• Additional 1 TB of Dataverse file capacity.

Get Power Automate pricing details at Power Automate pricing. For inquiries about add-on capability licensing, contact Microsoft Process and Task Mining Questions.

Dataverse storage capacity add-on

Data volume continues to grow exponentially, as businesses advance their digital transformation journey and bring data together across their organization. Modern business applications need to support new business scenarios, manage new data types, and help organizations with the increasing complexity of compliance mandates.

To support the growing needs of today's organizations, Dataverse storage capacity add-ons can support scaling of Power Automate operations. Learn more in How to add storage capacity to Power Platform.