Licensing in Microsoft Power Apps and Power Automate
This article discusses:
- Power Apps and Power Automate Add-on Licensing
- Use cases that do not require add-on licensing
- Use cases that require add-on licensing
Cases that do not require add-on licensing
- Microsoft 365 (M365) Power Apps and Power Automate add-on licenses are not needed to support the use of Canvas Power Apps applications and Power Automate flows involving standard connectors. This use case is covered by the Microsoft A3 and A5 licenses if daily transaction limits are not exceeded. In general, M365 workflows that stay within the environment of licensed Microsoft applications (i.e., only utilize other Microsoft applications) are covered by the A3 and A5 licenses.
- If your department has a Power Apps application that triggers a Power Automate flow involving premium connectors, you do not need to license users for both the application and flow separately. You only need to license your users for the application.
- Exception: If the same flow is triggered separately from the application by another non-Microsoft business process, then you would need to license the flow separately.
Case that requires add-on licensing
- If a Power Apps application or a Power Automate flow uses a premium connector, then you will need to license all developers and users with at least one of the add-on licenses. See “Add-on Licensing Options per Use Case” below.
- If you have a student or campus-wide use case that requires licensure, please seek a Cloud Consultation with Collaborative Computing Solutions (CCS) to discuss your use case. Microsoft is willing to work with educational institutions on special pricing around these types of use cases.
Add-on Licensing Options by Use Case
- Developers working with premium connectors should be licensed with the “Power Apps per user plan”, the “Power Automate per user plan”, or both.
- For users, there are several options based on number of applications or flows involving premium connectors:
- When using one or two Power Apps applications involving premium connectors, the department should seek the “Power Apps per app plan” license.
- When using one Power Automate flow involving premium connectors, the department should seek the “Power Automate per flow” license.
- Any other use case involving premium connectors should use the “Power Apps per user plan” or the “Power Automate per user plan” licenses as appropriate.
- The only caveat to the above statements is:
For a list of standard and premium connectors, refer to this Microsoft Documentation page List of all connectors published by Microsoft.
Top of Page
Microsoft 365 license ordered not accessible
Microsoft Documentation List of Microsoft-published Standard and Premium Connectors
Top of Page