Power Apps, Power Automate and Power Virtual Agents Licensing Guide-June 2021
Power Apps, Power Automate and Power Virtual Agents – How to Buy
Licensing programs are channels where you can buy Power Apps, Power Automate and Power Virtual Agents. You can license Power Apps, Power Automate and Microsoft Power Virtual Agents through Microsoft Volume Licensing (VL), Cloud Solution Provider program (CSP), and/or Web Direct (MOSP) programs. In Volume Licensing, Power Apps and Power Automate are available through:
• Enterprise Agreement (EA)
• Enterprise Agreement Subscription (EAS)
• Server and Cloud Enrollment (SCE)
• Enrollment for Education Solutions (under the Campus and School Agreement) (EES)
Additional channels:
• Microsoft Online Government
• Microsoft Products and Services Agreement (MPSA). More information on MPSA is available here.
• Microsoft Online Subscription Program (Web Direct/MOSP)
For more information on Power Apps, Power Automate, and Power Virtual Agents licensing channels and segment availability, refer to the Product Terms and the Online Service Terms.
Participating in a Volume Licensing program typically involves signing an agreement and/or enrollment,meeting a minimum purchase requirement, and ordering licenses through a Microsoft Reseller. Visit the Microsoft Volume Licensing website to learn more about how to buy through Volume Licensing, find a reseller partner, and more helpful information.
Power Apps, Power Automate and Power Virtual Agents – How to license
Multiplexing
Multiplexing refers to the use of hardware or software that a customer uses to pool connections, reroute information, or reduce the number of users that directly access or use the Power Apps, Power Automate and Power Virtual Agents service. Multiplexing does NOT reduce the number of SLs of any type required to access the Power Apps, Power Automate and Power Virtual Agents apps. Any user or device that accesses the Power Apps, Power Automate and Power Virtual Agents app —whether directly or indirectly—must be properly licensed.
Power Apps, Power Automate and Power Virtual Agents service can only be accessed if you have a Power Apps, Power Automate or Power Virtual Agents license. Similarly, Power Apps, Power Automate and Power Virtual Agents licenses are required for users that input data into, query, or view data from the Power Apps, Power Automate and Power Virtual Agents apps through a pooling device. Pooled connections use a non-interactive user account in Power Apps, Power Automate and Power Virtual Agents that can access the system but only via the web service layer. Internal users accessing Power Apps, Power Automate and Power Virtual Agents service indirectly through a portal or via an API to a separate service such as Microsoft Outlook must also be properly licensed, regardless of if they are set up as a Power
Apps, Power Automate and Power Virtual Agents user in the app, for example:
• Internal users that access the Power Apps, Power Automate and Power Virtual Agents service must still be properly licensed for Power Apps, Power Automate and Power Virtual Agents.
• Any user that accesses Power Apps, Power Automate and Power Virtual Agents service that is made available through an automated process requires a Power Apps, Power Automate and Power Virtual Agents license
• The number of tiers of hardware or software between the Power Apps, Power Automate and Power Virtual Agents apps and the user or devices that ultimately use Power Apps, Power Automate and Power Virtual Agents service indirectly does not affect the number of SLs required.
For additional information about multiplexing refer to the Microsoft Volume Licensing Brief Multiplexing—Client Access License (CAL) Requirements. Note, this document is intended to provide general multiplexing guidance that can be used for online as well as on-premises situations.
Licensing Requirements for External Users
External users must be appropriately licensed to access Power Platform services and data. Applicable
licensing includes:
• An appropriate Power Platform USL
• Seeded licensing capabilities from Office or Dynamics 365 USLs
• Power Portal login or page view capacity
• Accessing via an appropriately licensed Power Automate Per Flow workflow
Users must be appropriately licensed whether they are accessing directly or indirectly per multiplexing guidelines.
Power Apps Subscriptions
Licensing overview
General purpose, full Power Apps capabilities are licensed on a standalone basis. Additionally, limited Power Apps capabilities are included within various Office 365 and Dynamics 365 licenses; for more information, please see the sections titled Power Apps use rights included with Dynamics 365/Office 365 licenses later in this document.
High level overview of the licensing structure is provided below.
Standalone Power Apps licensing
Customers that need general purpose and full capabilities of the platform should license Power Apps on a
standalone basis. Licensing is supported on both a “per user” basis as well as a “per user, per app” basis.
Both standalone licenses are fully featured. Details follow.
Power Apps per app plan
Power Apps per app plan allows organizations to get started with the platform at a lower entry point.
Customers on the per app plan typically start with 1-2 leading use case scenarios before adopting the
platform more broadly. Power Apps per app plan is also an attractive licensing option to license end users
that run only a few apps.
Power Apps per app plan allows individual users to run 2 custom applications (be it canvas or model or
both) and access 1 custom portal based on the full capabilities of Power Apps.
Note:
• 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.
Power Apps per user plan
Power Apps per user plan allows licensed users to run unlimited custom applications based on the full capabilities of Power Apps.
Power Apps use rights included with Dynamics 365 licenses
Limited Power Apps use rights are included within the same environment(s) as the licensed Dynamics 365 application(s) to allow users to customize & extend Dynamics 365 applications. Use of Power Apps capabilities included with Dynamics 365 licenses must be only within the context of the licensed Dynamics 365 application. Further, the specific use rights vary by Dynamics 365 license type.
Power Apps use rights included with Office 365 licenses
Limited Power Apps use rights are included with select Office 365 licenses to allow users to customize and extend Office 365 for productivity scenarios, and to deliver a comprehensive low-code extensibility platform for Microsoft Teams. For a complete list of Office 365 licenses that include Power Apps and Dataverse for Teams use rights, please refer to Appendix B.
Azure API Management. Customers with eligible Office 365 licenses that include Dataverse for Teams can use these connectors for
custom applications, flows, and chatbots running in Teams and to connect Azure backend services, not on-premises or 3rd party
clouds. Please see Azure API Management page and technical documentation here. 2Dataverse for Teams is a built-in flexible datastore that provides data storage and a one-click solution for app deployment in
Teams. For a complete list of Office 365 licenses that include Dataverse for Teams use rights, please refer to Appendix B. 3Each Dataverse for Teams environment uniquely maps (1:1) to a Teams team and can store up to 1,000,000 records based on typical
usage. Please refer to the public link here for the details on Dataverse for Teams capacity and service limits. 4Dataverse for Teams does not grant additional entitlements with standalone Power Platform licenses but supports premium
functionality that comes with corresponding license. Example: In a given Dataverse for Teams environment, accessing premium
connectors in the context of an app requires all users accessing the app to be licensed either by the Power Apps per app or per user
plans depending on the customer scenario/needs. 5Dataverse database and file capacity entitlements are pooled at the tenant level. 6Usage capacity is across Power Apps, Power Automate, and Power Virtual Agents; “Power Apps and Power Automate capacity add-
on” can be purchased to increase daily service limits.
Power Apps Portals
Licensing overview
Provisioning a Power Apps Portals instance
Power Apps Portals instances can be provisioned by customers on-demand. Provisioning a portals instance draws 1GB from available (unused) Dataverse database capacity. Thus, provisioning additional portals instances is only capped by available Dataverse database capacity.
Usage of a Power Apps Portals instance
Each end user that accesses a Power Apps Portals instance needs to be licensed appropriately. The table below outlines the end user types.
Per login model
For Power Apps Portals instances that implement authenticated external user scenarios, appropriate login capacity, based on anticipated usage volumes, should be purchased. Customers should purchase necessary capacity of logins across all Portals instances that cater to authenticated external user scenarios.
Each unit provides 100 logins/month. Volume tiers and corresponding SKUs differ based on minimum purchase requirements. For each of the tiers, once the minimum purchase requirement is met, additional units can be purchased in units of 1. For example, a customer requiring 5,500 logins/month can purchase 55 units of “Power Apps Portals login capacity add-on tier-3”.
Capacity enforcement
For Power Apps Portals login capacity add-on SKUs, purchased capacity is enforced monthly. Unused logins do NOT carry over from one month to another. Customers should purchase appropriate capacity aligned with peak monthly anticipated usage.
Overage handling
While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
Assignment of purchased capacity
The minimum assignment capacity per Power Apps Portal instance is 100 logins/month. Once the minimum capacity of 100 logins/month is assigned, additional logins can be added in terms of 1 login.
Per page view model
For Power Apps Portals instances that implement anonymous access scenarios, appropriate capacity of page views, based on anticipated usage, should be purchased. Customers should purchase necessary page views capacity across all Portals instances that cater to anonymous access scenarios.
Each unit provides 100,000-page views per month. For example, a customer requiring 570,000-page views per month, should purchase 6 units of “Power Apps Portals page view capacity add-on”.
Capacity enforcement
For Power Apps Portals pageview capacity add-on SKUs, purchased capacity is enforced monthly. Unused page views do NOT carry over from one month to another. Customers should purchase appropriate capacity aligned with peak monthly anticipated usage.
Overage handling
While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
Assignment of purchased capacity
The minimum assignment capacity per Power Apps Portal instance is 50,000-page views/month. Once the minimum capacity is assigned, additional page views can be added in terms of 1-page view.
Power Apps Portals – Use rights for Internal users
For internal users i.e. users licensed with Power Apps or Dynamics 365 licenses, the use rights for Portals which are essentially custom portals aligned with use rights to custom Power Apps.
Power Platform requests for Power Apps portals
Each login provides a daily limit entitlement of 200 Power Platform requests per 24-hour period per user.
Anonymous page views, which rarely interact with backend system functionality, are afforded up to 3 Power Platform requests per page view.
These Power Platform requests are pooled at portal level depending on number of logins/page views assigned to portal.
Power Automate Subscriptions
Licensing overview
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; for more information, please see the sections titled Power Automate use rights included with Dynamics 365/Office 365 licenses later in this document.
High level overview of the licensing structure is provided below.
Standalone Power Automate licensing
Customers that need full-fledged, general purpose workflow, business process automation or Robotic Process Automation (RPA) capabilities, should consider purchasing standalone Power Automate licenses.
Licensing is supported on both a “per user” basis as well as a “per flow” basis. All standalone licenses include the full capabilities on Power Automate with the exception of RPA functionality which is only included in Power Automate per user with attended RPA plan.
Power Automate per user plan
Power Automate per user plan equips individual users to create and run unlimited workflows and business processes based on their unique needs. The per user plan is intended to support the broad adoption of an automation culture in an organization. Should the entire organization be licensed with the Power Automate per user plan, admins will have minimal overhead with tracking how many flows are being activated/used within the organization.
“Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits.
Power Automate per flow plan
The Power Automate per flow 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 flow 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.
Note:
• All types of enabled top-level flows need to be licensed (scheduled flows, automated flows, instant flows and business process flows). Flows that are only used as “child” flows (triggered by another flow) do not need to be additionally licensed
• Should customers wish to license more top-level flows, they should purchase more units of the “Power Automate per flow plan”
• Should customers only wish to license more usage capacity for currently licensed flows, they may purchase “Power Apps and Power Automate capacity add-on”.
Note, scheduled flows may be configured to trigger every minute, irrespective of license type. There are no limits on the frequency of flow runs beyond what the connector supports.
Power Automate per user with attended RPA plan
Power Automate per user with attended RPA plan spans legacy and modern applications, allowing individual users to create unlimited flows for API-based automation plus automate legacy applications with desktop flows through Robotic Process Automation (RPA) and AI. This plan builds on the Power Automate per user plan with the ability for users to run an attended RPA bot on their workstation.
Additionally, attended RPA includes access to AI Builder capacity in support of scenarios like forms processing, object detection, prediction, text classification and recognition, and more.
Please note running an RPA bot in an unattended scenario requires the addition of the Power Automate unattended RPA add-on – learn more.
Note:
• Desktop flow authoring, bot orchestration and management are included in the offer.
• WinAutomation client capabilities are included in the offer.
• The bot must operate concurrently with the user on the same workstation; the bot can run more than one discrete processes (desktop flows), but each process must be serialized to run sequentially.
• Additional AI Builder capacity can be purchased per 1M service credits for $500/month; AI Builder service credit capacity is pooled on the tenant level.
• “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits.
Power Automate unattended RPA add-on
The Power Automate unattended RPA add-on extends desktop-based automation by enabling a bot to run autonomously, i.e. independent of a user. Unattended bots can be deployed on a local or remote desktop, or other virtualized environment. The Power Automate per user with attended RPA or Power Automate per flow plans are eligible base offers for the unattended RPA add-on.
Note, the Power Automate unattended RPA add-on is licensed by bot. Concurrent instances of a singular process require an additional unattended bot for each instance – multiple unattended RPA add-ons can be applied against a qualifying base license.
Note:
• One unattended RPA add-on license includes the rights to one unattended RPA bot, as well as all necessary functions tied to desktop flow authoring, bot orchestration and management.
• Running the unattended RPA bot in a VM requires the separate purchase of any necessary compute resources.
• Additional AI Builder capacity can be purchased per 1M service credits for $500/month; AI Builder service credit capacity is pooled on the tenant level.
• Any services or applications the unattended bot accesses must be licensed separately. For instance, if the bot is accessing Windows or Office, the Microsoft 365 – Unattended License must also be purchased in addition to the Power Automate unattended RPA add-on.
Power Automate use rights included with Power Apps licenses
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:
• Any data source within the use rights of the Power Apps application
• Directly with the Power Apps application (via built in trigger/action)
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.
Example of Power Automate use within Power Apps application context:
User with a standalone Power Apps license runs an app that uses SQL DB as the data source and includes flows that:
• Read from OR write to SQL DB
• Use a built-in Power Apps trigger and/or action – e.g., Send a push notification to the app
Example of Power Automate use outside of Power Apps application context:
The same user (in the example above) now also wants to use a flow that updates an Oracle database, and:
• Is completely unrelated to the Power Apps app
• Does not interact in any way with the Power Apps app (or its data sources)
This user will then require a standalone Power Automate license.
Power Automate use rights included with Dynamics 365 licenses
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:
• Any data source within the use rights of the Dynamics 365 application
• Directly with the Dynamics 365 application (via built in trigger/action)
If the embedded flow is not within the context of the Dyn
Dynamics 365 application, then standalone Power Automate licenses will need to be purchased.
Power Automate use rights included with Office 365 licenses
Limited Power Automate use rights are included with select Office 365 licenses to allow users to customize and extend Office 365 for productivity scenarios, and to deliver a comprehensive low-code extensibility platform for Microsoft Teams. For a complete list of Office 365 licenses that include Power Automate and Dataverse for Teams use rights, please refer to Appendix B.
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:
• Any data source within the use rights of the Office 365 application
• Directly with the Office 365 application (via built in trigger/action)
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.
Power Automate use rights included with Windows licenses
Limited Power Automate use rights are included with select Windows licenses to create and execute personal desktop automation for attended RPA capabilities in Power Automate Desktop. This expands the digital workforce’s ability to automate legacy tasks that can slow down their workflows, empowering Windows users to start automating redundant and time-consuming tasks with low-code automation through RPA. For a complete list of Windows licenses that include these use rights, please refer to Appendix B.
Power Automate use within Windows is available for all applications and websites (across all web browsers). Enterprise automation and administrative rights are not available in Windows.
login and create desktop flows. This application should not be utilized for business-critical functions as there is no SLA or Microsoft
support. If Power Automate is business critical, you should purchase the appropriate Power Automate license which includes
support. 4 Reference http://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be
purchased to increase daily service limits. 5 Desktop flow connector included (it is not included in Windows licenses)
6 Additional Dataverse Database/File/Log capacity can be purchased in increments of 1GB. Dataverse Database and File capacity are
pooled tenant wide. 6 Reference http://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be
purchased to increase daily service limits. 7 Additional AI Builder capacity can be purchased per 1M service credits for $500/month; AI Builder service credit capacity is pooled
on the tenant level.
Note, scheduled flows may be configured to trigger every minute, irrespective of license type. There are no limits on the frequency of flow runs beyond what the connector supports
Power Virtual Agents subscriptions
EWith Power Virtual Agents, customers can publish bots to engage with their customers on multiple platforms or channels. These include live websites, mobile apps, and messaging platforms like Microsoft Teams. Please refer to this public documentation on channel details.
Licensing overview
The Power Virtual Agents application is licensed per tenant. Power Virtual Agents will be charged according to the unit of ‘billed sessions’1 (see below for definition).
A user license (called Power Virtual Agent User License) is required for each user authoring bots with Power Virtual Agents. Available at no additional cost, the license can be assigned to users by the administrator in the admin portal. We recommend acquiring the tenant license (with capacity add-on if needed) and user licenses as part of a single transaction to simplify onboarding to Power Virtual Agents.
Capacity enforcement
All Power Virtual Agents purchased capacity is enforced monthly and unused sessions do not carry over month to month.
Overage handling
While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
Comprehensive monitoring, reporting and alerting mechanisms will be instituted to assist customers with managing Power Virtual Agents capacity. More stringent technical enforcement (including service denial) will result for usage that is significantly over the purchased capacity
Power Virtual Agents for Teams use rights included with Office 365 licenses
Power Virtual Agents for Teams enables customers with select Office 365 licenses to build and deploy custom chatbots directly within Teams, using Dataverse for Teams. For a complete list of Office 365 licenses that include Power Virtual Agents for Teams use rights, please refer to Appendix B.
Power Virtual Agents use rights included with Dynamics 365 licenses
Select Dynamics 365 licenses include limited Power Virtual agents use rights and session capacity for the purpose of extending Dynamics 365 application(s). Please Dynamics 365 Licensing Guide for information related to these entitlements.
Subscription Capacity
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 ser, 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 is being rebranded as Microsoft Dataverse. For capacity and service limits regarding Dataverse for Teams, please refer to the public documentation here.
Power Apps, Power Automate, Power Virtual Agents and Dynamics 365 Sales, Customer Service, and Field Service applications leverage the same tenant and infrastructure. Dataverse capacity (database, file and log formats) is pooled across the tenant and shared amongst relevant application workloads.
There are additional Microsoft subscriptions beyond Power Platform that grant Dataverse capacity entitlements. Please see this page for details related to Project Online, as well as the Dynamics 365 Licensing Guide for information related to other entitlements.
Dataverse allows integration with Outlook and SharePoint.
The first subscription of Power Apps OR Power Automate OR Power Virtual Agents OR Dynamics 365 Sales, Customer Service, and Field Service provides the one-time default capacity entitlement for the tenant. For example, if a new customer purchases “Power Apps per user plan”, the tenant will receive 10GB of default Dataverse Database capacity. Additional subscriptions do not add to the tenant’s default capacity.
When additional subscriptions are added to the tenant, additional Dataverse capacity may accrue to the tenant.
Example:
Let’s assumed that a new customer starts by purchasing 10 Power Apps per user licenses and 20 Power Apps per app licenses. In this case, the total tenant wide pooled capacity will be as follows (note 1GB = 1,024MB):
Capacity Add-ons
If additional subscription capacity (such as additional database or file capacity) is required, these optional add-on licenses can be added to your subscriptions. Subscription add-ons apply across tenant and are not tied to a specific user. Subscription add-ons can be purchased at any time and remain a part of the subscription for the remainder of the subscription term.
Dataverse (Common Data Service) Capacity Add-ons
Apps or flows utilizing Dataverse (formerly Common Data Service) will consume varying quantities of Database Capacity, File Capacity, and Log Capacity and may require different kinds of Power Apps and Power Automates environments. Apps may utilize flows, or flows may be run separately from apps.
Each type of per user license (Office 365, Dynamics 365 applications, standalone Power Apps and Power Automate Plan licenses) include capacities of one or more of these basic resources. These entitlements are pooled, and shared across users, at the customer tenant level.
Please note that Dataverse (formerly Common Data Service) capacity add-ons do not apply to Dataverse for Teams scenarios (i.e. when a Dataverse for Teams environment reaches its limit, customers need to tep up to standalone Power Apps, Power Automate, or Power Virtual Agents plans for additional capacity).
AI Builder capacity add-on
Service overview
AI Builder helps empower everyone – regardless of their technical experience to work with ArtificialIntelligence (AI). This solution helps easily add AI capabilities to both apps and business processes. AI Builder supports various scenarios such as predictions, business card, and many more. For more information on AI Builder, please visit https://PowerApps.microsoft.com/ai-builder/
Licensing overview
AI Builder is licensed as an add-on to standalone Power Apps and Power Automate licensing as well as Dynamics 365 licenses.
AI Builder is licensed on a capacity basis. AI Builder capacity is expressed in the form of “service credits”.
Service credits serve as the single (common) currency across all the scenarios supported by AI Builder.
Available service credits are deducted when AI Builder services are used. Different scenarios (for example, forms processing, prediction, etc.) burn down service credits at different rates.
Customers should 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 requiring 4.7 million service credits per month (based on anticipated usage), should purchase 5 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
Capacity enforcement
For AI Builder capacity add-on SKUs, purchased capacity is enforced monthly and unused service credit do not carry over month to month.
Overage handling
While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
Comprehensive monitoring, reporting and alerting mechanisms will be instituted to assist customers with managing AI Builder capacity. More stringent technical enforcement (including service denial) will result for usage that is significantly over the purchased capacity.
Assignment of purchased capacity
Assignment of purchased capacity to appropriate Power Automate, Power Apps applications and Dynamics 365 workloads is managed in product. Assignment helps ensure capacity for critical AI models.
The minimum capacity to be assigned is 1 service credit.
Power Apps and Power Automate capacity add-on
Power Apps and Power Automate capacity add-on increases the daily Power Platform requests for Power Apps, Power Automate, Power Virtual Agents, and Dynamics 365 users/workloads that need more usage capacity than their allocation. For more details on service limits and to learn about daily service limits applicable to various licenses, please visit http://aka.ms/platformlimits
Capacity enforcement
For Power Apps and Power Automate capacity add-on SKUs, purchased capacity is enforced daily and unused/unassigned Power Platform requests do not carry over from day to day. Also, the assigned capacity is specific to a user/flow
Overage handling
While occasional and reasonable overages will be tolerated, customers exceeding licensed capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
Assignment of purchased capacity
Upon purchase of the add-on subscription, the tenant admin will need to assign the purchased capacity to specific users and/or flows. Minimum capacity that needs to be assigned is 1,000 daily Power Platform requests.
Power Virtual Agents capacity add-on
Power Virtual Agents capacity add-on increases the number of chat bot sessions and daily Power Platform requests per tenant.
For more informations download the document:
(© Microsoft Corporation. All rights reserved.)