A Simplified Guide To Microsoft Power Apps, Power Automate and Power Virtual Agents Licensing
Power Apps Licensing
Customers can get access to Microsoft Power Apps by purchasing standalone licensing or though seeded licensing of Office 365 and Dynamics 365 Applications. High level overview of the licensing structure is provided below.
Entitlement Summary and Price for Power Apps
An entity within Common Data Service becomes restricted only if the Dynamics 365 application is installed on a given environment.
Power Apps and Power Automate usage will count against the API request limits provided by the Dynamics 365 license Service limits are published at http://aka.ms/platformlimits – Power Apps and Power Automate capacity add-on can be purchased to increase daily service limits.
Common Data Service database and file capacity entitlements are pooled at the tenant level.
Dynamics 365 Applications: Dynamics 365 Sales Professional, Dynamics 365 Customer Service Professional, Dynamics 365 Team Members, Dynamics 365 Operations – Activity, Dynamics 365 Human Resources Self Service, Dynamics 365 Business Central Team Members.
Dynamics 365 Enterprise Applications: Dynamics 365 Sales Enterprise, Dynamics 365 Customer Service Enterprise, Dynamics 365 Field Service, Dynamics 365 Project Service Automation, Dynamics 365 Finance, Dynamics 365 Supply Chain Management, Dynamics 365 Commerce, Dynamics 365 Human Resources, Dynamics 365 Business Central.
Embedded canvas apps within a model-driven app will not count towards the two-app limit.
A single user might be covered by multiple ‘per app’ licenses to allow the user to use multiple solutions targeted at various business scenarios, without requiring a per-user license.
Once a pool of Power Apps per app licenses are purchased, individual licenses need to be assigned to specific environments and to individual users (i.e. if the same app exists in two environments, a user would require two per app SLs to access both).
The Power Apps Per App plan is available to education customers under faculty and student pricing. Since these licenses are sold as tenant level capacity and not assigned to users in active directory, customers and partners will be responsible for ensuring that student pricing is only being applied to students. This means that when licenses are purchased with student pricing, the number of app licenses assigned to non-students (i.e. faculty) in the product may not exceed the number of faculty licenses purchased as this would indicate that student licenses have been assigned to faculty. Summarized.
Power Apps add-ons
Volume pricing available.
Each AI Builder add-on unit is a pack of 1 million service credits pooled at the tenant level.
A login provides the authenticated user with access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Think of a login as a day pass to a single Power Apps Portal
Each login provides a daily limit entitlement of 200 API calls per 24-hour period per user. Anonymous page views, which rarely interact with backend system functionality, are afforded up to 3 API calls per page view. These API calls are pooled at portal level depending on number of logins/page views assigned to portal.
Power Automate Subscriptions
General purpose Power Automate capabilities are licensed on a standalone basis. Limited Power Automate capabilities are also included within Power Apps, Office 365 and Dynamics 365 licenses. High level overview of the standalone licensing structure is provided below.
Entitlement Summary and Price for Power Automate Standalone Plans
$500/month includes 5 flows. Additional flows may be purchased for $100/month/flow.
Add-ons and data capacity licensing are same as above in the Power Apps Licensing.
Power Virtual Agents subscriptions
The Power Virtual Agents application is licensed per tenant. The administrator will need to assign user licenses through the admin portal to Power Virtual Agent users who need access to the Power Virtual Agents application. Power Virtual Agents will be charged according to the unit of ‘sessions’ (see below for definition of session).
Summary of Power Virtual Agents entitlements
A session is an interaction between the customer and the bot, and represents one unit of consumption. The session begins when an authored topic is triggered. These sessions are referred to as ‘billed sessions’ in the product. Sessions are deducted for both testing and production usage.
A topic ends in one of the following scenarios:
i. When all of the customer's questions are answered
ii. When a customer intentionally ends or closes a chat session, or
iii. When a bot is unable to answer adequately and the interaction is escalated to a live agent
Power Apps, Power Automate, and Power Virtual Agents default subscription capacities leverage the same tenant and infrastructure and will accrue across one tenant. Every tenant with a Power Apps, Power Automate or Power Virtual Agents license receives default capacity. In addition, for each Power Apps per user, Power Apps per app, Power Automate per user, and Power Automate per flow plan license there is additional capacity added to the tenant.
Common Data Service Capacity Add-ons
For more details, please refer to the Microsoft Power Apps and Power Automate Licensing Guide.