Power Automate per business process plan is licensed by flow and allows customers to implement critical business processes with capacity that serves teams, departments, or the entire organization without individually licensing each end user that triggers the licensed flow.
Power Automate per business process plan is great for departmental scenarios where typically, one power user sets up a flow and shares the same with the broader group. This plan alleviates the need to license each end user that knowingly/unknowingly triggers execution of the licensed flow.
Customers that need full-fledged, general purpose workflow/business process automation capabilities, should consider purchasing standalone Power Automate licenses. Licensing is supported on both a “per user” basis as well as a “per flow” basis. Both standalone licenses include the full capabilities on Power Automate. Limited Power Automate capabilities are also included within Power Apps, Office 365 and Dynamics 365 licenses. High level overview of the licensing structure is provided below.
Plan and Capabilities | Plan and Capabilities Power Automate per user plan | Power Automate per flow plan | |
---|---|---|---|
Basics | Minimum purchase | NA | 5 Units |
User license required? | Yes | ||
Execute flows | Workflows | • | • |
Business process flows | • | • | |
Connect to your data | Standard connectors | • | • |
Premium connectors | • | • | |
On premises data gateway | • | • | |
Custom connectors | • | • | |
Store and manage | Standard connectors | • | • |
Per license capacity | Common Data Service Database | 50MB | 50MB |
Common Data Service File Capacity | 200MB | 200MB | |
Daily API request limit | 5000 | 5000 |
Power Apps licenses (both “Power Apps per app plan” and “Power Apps per user plan”) include Power Automate use rights for the purpose of automating workflows associated with the Power Apps application(s).
Power Automate use within Power Apps is limited to the context of the Power Apps application. What this means is that for both triggers and actions, flows included within a Power Apps application can connect to:
If the flow is isolated and has nothing to do with the Power Apps application, then standalone Power Automate licenses will need to be purchased.
User with a standalone Power Apps license runs an app that uses SQL DB as the data source and includes flows that:
The same user (in the example above) now also wants to use a flow that updates an Oracle database, and:
This user will then require a standalone Power Automate license.
Plan and Capabilities | Power Automate use rights within Power Apps licenses | |
---|---|---|
Execute flows | Workflows | • |
Business process flows | • | |
Connect to your data | Standard connectors | • |
Premium connectors | • | |
On-premises data gateway | • | |
Custom connectors | • | |
Store and manage | Common data service use rights | • |
Dynamics 365 licenses include Power Automate use rights for the purpose of customizing and extending Dynamics 365 application(s).
Power Automate use within Dynamics 365 is limited to the context of the embedding Dynamics 365 application. For both triggers and actions, flows included within the Dynamics 365 application can connect to:
If the embedded flow is not within the context of the Dynamics 365 application, then standalone Power Automate licenses will need to be purchased.
Plan and Capabilities | Power Automate use rights within Dynamics 365 licenses | |
---|---|---|
Execute flows | Workflows | • |
Business process flows | • | |
Connect to your data | Standard connectors | • |
Premium connectors | • | |
On-premises data gateway | • | |
Custom connectors | • | |
Store and manage | Common data service use rights | • |
Office 365 licenses include Power Automate use rights for the purpose of customizing and extending Office 365 applications.
Power Automate use within Office 365 is limited to the context of the embedding Office 365 application. For both triggers and actions, flows included within the Office 365 application can connect to:
If the embedded flow is not within the context of the Office 365 application or if the embedded flow needs to connect to a premium on-premises or custom data source standalone Power Automate licenses will need to be purchased.
Plan and Capabilities | Power Automate use rights within Office 365 licenses | |
---|---|---|
Execute flows | Workflows | Unlimited |
Business process flows | - | |
Connect to your data | Standard connectors | • |
Premium connectors | - | |
On-premises data gateway | - | |
Custom connectors | - | |
Store and manage | Common data service use rights | - |
Per license capacity | Daily API Requests | 2000 |
Trial | 30 Days Free | |
All trials are all modules, multiple users. |
Buy | |||||||
|
|||||||
Select Quantity | |||||||
Add To Cart | Total= | $ |
Team User | Quantity | Per User/Mo. | ||
Read Only | $ |
Accounting | User Upgrade * | $ | ||
Quantity | Per User/Mo. | |||
New User on Power Apps * |
$ |
Time & Material Billing | User Upgrade * | $ | ||
Quantity | Per User/Mo. | |||
New User on Power Apps * |
$ |
Add To Cart | Adding = | $ |
Implementation Services | ||
Total end-to-end services are available at a cart hourly, weekly, or assured fixed package. | ||
Data migration | $60.00 | |
Project Management | $700.00 | |
Training | ||
Go-Live Support | ||
Customization | ||
Support services | ||
Solution support | ||
Emergency Support | ||
All Implementation Services |
MTC's CRM product licensing includes at no-charge a maximum of 2 non-production instance of CRM for the purposes of Development and Staging/Test. Provide these additional CRM Organization names by email to salesteam