06 Power Platform Licensing Guide January 2023 PDF
06 Power Platform Licensing Guide January 2023 PDF
Licensing Guide
January 2023
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | November 2022
Table of Contents
How to buy ............................................................................................................................................................................................. 2
Licensing Programs ...................................................................................................................................................................... 2
How to license ....................................................................................................................................................................................... 2
Multiplexing ................................................................................................................................................................................... 2
Licensing Requirements for External Users ............................................................................................................................ 3
Power Apps ............................................................................................................................................................................................. 3
Power Apps..................................................................................................................................................................................... 3
Power Apps per app plan ........................................................................................................................................................... 3
Power Apps per user plan ........................................................................................................................................................... 4
Power Apps per app pay-as-you-go plan............................................................................................................................... 5
Power Automate ................................................................................................................................................................................... 9
Power Automate ........................................................................................................................................................................... 9
Power Automate per user plan................................................................................................................................................. 11
Power Automate per user with attended RPA plan ............................................................................................................ 11
Power Automate per flow plan ................................................................................................................................................ 11
Power Automate unattended RPA add-on .......................................................................................................................... 12
Power Automate hosted RPA add-on ................................................................................................................................... 13
Power Virtual Agents ....................................................................................................................................................................... 19
Power Pages ........................................................................................................................................................................................ 22
Power Pages authenticated users plan.................................................................................................................................. 22
Power Pages anonymous users plan...................................................................................................................................... 23
Power Platform Dataverse Capacity ........................................................................................................................................... 25
Dataverse default subscription capacity ............................................................................................................................... 25
Dataverse capacity for Power Platform pay-as-you-go environments.........................................................................26
Dataverse capacity meters ........................................................................................................................................................26
Capacity add-ons............................................................................................................................................................................... 27
Dataverse (Common Data Service) capacity ........................................................................................................................ 27
AI Builder capacity add-on ....................................................................................................................................................... 27
Power Virtual Agents capacity add-on ..................................................................................................................................29
Trial and Implementation ............................................................................................................................................................... 29
Power Platform Service Support.................................................................................................................................................. 29
Pricing .................................................................................................................................................................................................... 30
Appendix A: Terminology and Custom Tables ...................................................................................................................... 31
Appendix B: Dynamics 365, Microsoft/Office 365, and Windows licenses that include Power Platform
capabilities ........................................................................................................................................................................................... 33
Appendix C: Change Log ................................................................................................................................................................ 36
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | November 2022
Using This Guide
Use this guide to improve your understanding of how to license Microsoft Power Apps, Power Automate,
Power Virtual Agents and Power Pages.
This guide is not intended to influence the choice of Microsoft products and services. The examples
presented in this guide are illustrative. Microsoft reserves the right to review or update this document at
any time without notice.
This document applies for users with Power Apps, Power Automate, Power Virtual Agents and Power
Pages licenses.
To facilitate understanding of licensing requirements this guide is structured as follows:
1) How to buy 3) Capacity add-ons
2) How to license (product licensing) 4) Notes: Change log
For help determining the right technology solution for any given organization, including the license requirements
for a specific product or scenario, consult with your Microsoft account team or your Microsoft Certified Partner.
This guide does not supersede or replace any of the legal documentation covering use rights.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |1
How to buy
Licensing Programs
Licensing programs are channels through which you can buy Power Apps, Power Automate, Power Virtual Agents and
Power Pages licenses. You can license these Power Platform products through the Microsoft Volume Licensing (VL), Cloud
Solution Provider program (CSP), and/or Web Direct (MOSP) programs. In Volume Licensing, Power Apps, Power
Automate, Power Virtual Agents and Power Pages 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 Platform licensing channels and segment availability, refer to the Product 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.
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 with Power Apps, Power Automate, Power Virtual Agents and
Power Pages services. Multiplexing does NOT reduce the number of subscription licenses of any type required to access
the Power Apps, Power Automate, Power Virtual Agents and Power Pages apps. Any user or device that accesses Power
Apps, Power Automate, Power Virtual Agents and Power Pages apps, directly or indirectly must be properly licensed.
Power Apps, Power Automate, Power Virtual Agents and Power Pages services can only be accessed with Power Apps,
Power Automate, Power Virtual Agents and Power Pages licenses. Similarly, Power Apps, Power Automate, Power Virtual
Agents and Power Pages, licenses are required for users that input data into, query, or view data from the Power Apps,
Power Automate, Power Virtual Agents and Power Pages apps through a pooling device. With Power Platform services,
pooled connections use a non-interactive user account that can access the system but only via the web service layer.
Internal users accessing Power Platform services indirectly through a portal or via an API to a separate service such as
Microsoft Outlook must also be properly licensed, regardless of whether they are set up as a Power Apps, Power
Automate, Power Virtual Agents and Power Pages user in the app, for example:
• Internal users that access Power Apps, Power Automate, Power Virtual Agents and Power Pages services must still
be properly licensed for Power Apps, Power Automate, Power Virtual Agents and Power Pages.
• Any user that accesses Power Apps, Power Automate, Power Virtual Agents and Power Pages services made
available through an automated process requires a Power Apps, Power Automate, Power Virtual Agents and
Power Pages license.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |2
• The number of tiers of hardware or software between with Power Apps, Power Automate, Power Virtual Agents
and Power Pages apps and the users or devices that ultimately use Power Apps, Power Automate, Power Virtual
Agents and Power Pages services indirectly does not affect the number of User SLs required.
For additional information about multiplexing refer to the Microsoft Multiplexing Overview.
For additional information on external guest user access please see here.
Power Apps
Power Apps
Service Overview
Power Apps is a low code/no code application platform that allows enterprises to
digitize business operations by easily building line of business applications and
customizing existing Dynamics 365 and Microsoft/Office 365 applications. For more
details, please visit https://powerapps.microsoft.com/.
Licensing overview
General purpose, full Power Apps capabilities are licensed on a standalone basis. Additionally, limited Power Apps
capabilities are included within select Dynamics 365 and Microsoft/Office 365 licenses. For more information, please see
the sections titled Power Apps use rights included with Dynamics 365 licenses and Power Apps use rights included with
Microsoft/Office 365 licenses later in this document.
High-level overview of the licensing structure is provided below.
Per user, per app Per user
Licensing scheme Per user, per app Per user
Note:
• Embedded canvas apps within a model-driven app will not count towards the one-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 is purchased, individual licenses need to be assigned to specific
environments and to individual users (i.e., if the same app or website exists in two environments, a user will
require two per app User SLs to access both).
• The Power Apps per app plan is available to qualified education customers under faculty and student pricing.
Since these licenses are sold as tenant level capacity and are not assigned to users in Active Directory, customers
and partners will be responsible for ensuring that student pricing is applied to students only. When licenses are
purchased with student pricing, the number of app licenses assigned to nonstudents (i.e., faculty) may not exceed
the number of faculty licenses purchased, as this would indicate that student licenses have been assigned to
faculty.
Store and manage data Create and access custom tables (includes complex tables) 1
⚫
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |4
Per user offer summary
SKU Name Power Apps per user plan
License type User license
Store and manage data Create and access custom tables (includes complex tables)1 ⚫
Power Apps per app pay-as-you-go meter definition: A measure of the number of unique, active users who open a single
pay-as-you-go enabled app in an environment one or more times in a month.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |5
Entitlement Summary for Power Apps per app pay-as-you-go meter
Power Apps
Plans and capabilities per app pay-as-you-
go plan
Custom apps Run one custom app (canvas or model driven) 1 app
Standard connectors ⚫
Store and manage data Create and access custom tables (includes complex tables) 1
⚫
1 GB per pay-as-you-
Dataverse Database capacity5
go environment
Per license capacity
1 GB per pay-as-you-
Dataverse File capacity5
go environment
AI Builder AI Builder service credits
1
For exceptions to Dynamics 365 Field Service use rights for Power Apps users, refer to the Dynamics 365 Licensing Guide.
2
For a full list of restricted tables and exceptions for Case tables, see Restricted tables requiring Dynamics 365 licenses.
3
Power Automate use rights included with Power Apps standalone plans do not include RPA functionality, which requires a separate purchase of Power
Automate per user with attended RPA plan.
4
When Managed Environments is activated in a specific environment, all Power Apps, Power Automate, Power Virtual Agents, and Power Pages usage in
that environment requires standalone licenses. Please see Power Platform Managed Environments for details.
5
Dataverse Database, File and Log capacity are available with pay-as-you-go as alternatives to the existing capacity add-ons for overages, above and
beyond the standard entitlement of 1GB of Dataverse Database and 1GB of Dataverse File storage for each pay-as-you-go environment. With these
meters customers simply pay for the amount of storage they use rather than purchasing add-on licenses in advance. Please see Pay-as-you-go meters -
Power Platform for more information.
Please review http://aka.ms/platformlimits for more details.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |6
Power Apps use rights with Dynamics 365 applications
Dynamics 365 Dynamics 365 Enterprise
Capabilities
Applications1 Applications2
Within same environment(s) as
Run standalone apps (canvas/model driven) licensed Dynamics 365
Custom apps / websites application(s)3
Within same environment(s) as
Access websites licensed Dynamics 365
application(s)
Standard connectors ⚫ ⚫
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |7
Power Apps use rights with Office 365 licenses
Capabilities Office 365
Run custom apps (canvas apps) Unlimited
Custom apps / websites Run custom apps (model driven apps)
Access custom websites
Standard connectors ⚫
Power Apps
Power Apps Power Apps
Plans and capabilities per app meter Select
per app plan per user plan Select
Select D365 D365
$10 per M/O365
$5 per $20 per licenses1 Enterprise
active user/ licenses
user/month user/month licenses1
app/month
Unlimited Within
Run custom apps 1 app or same Unlimited
apps
Run custom environ. as
apps / 1 app licensed
websites 1 custom Unlimited D365
Run custom websites
website websites application
s
Standard connectors ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
Connect to
your data Premium and custom
⚫ ⚫ ⚫ ⚫ ⚫
connectors
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |8
On premises data
⚫ ⚫ ⚫ ⚫ ⚫
gateway
Dataverse
Utilize Dataverse ⚫ ⚫ ⚫ ⚫ ⚫ for Teams
only
Store and
Create and access
manage data ⚫ ⚫ ⚫ 15 per app ⚫
custom tables2
D365 restricted
Read only Read only Read only (CRUD) (CRUD)
tables access3
Run apps in a
Managed Managed
⚫ ⚫ ⚫
Environments Environment.
Manage at scale.4
Cloud flows
(Automated, instant,
and scheduled Within app Within app Within app Within app Within app
Execute flows
flows)5 context context context context context
Business process
flows
Dataverse Database 1
50 MB6 250 MB6 $ $
Per license capacity (accrued) GB/environment7
capacity Dataverse File 1
400 MB6 2 GB6
capacity (accrued) GB/environment7
AI Builder service
AI Builder 250 credits 500 credits
credits8
1
Use of Power Apps capabilities included with Dynamics 365 licenses must be only within the context of the licensed Dynamics 365 application.
2
For exceptions to Dynamics 365 Field Service use rights for Power Apps users, refer to the Dynamics 365 Licensing Guide.
3
For a full list of restricted tables and exceptions for Case tables, see Restricted tables requiring Dynamics 365 licenses.
4
When Managed Environments is activated in a specific environment, all Power Apps, Power Automate, Power Virtual Agents, and Power Pages usage in
that environment requires standalone licenses. Please see Power Platform Managed Environments for details.
5
Power Automate use rights included with Power Apps standalone plans do not include RPA functionality, which requires a separate purchase of the
Power Automate per user with attended RPA plan.
6
Dataverse Database and Database File capacity entitlements are pooled at the tenant level.
7
Dataverse Database and Dataverse File capacity are applied to each environment with pay-as-you-go billing enabled and are not granted for each
monthly active user.
8
Cap on accrued capacity: 1,000,000 credits. If more service credits are needed, use the AI Builder capacity add-on.
Please review http://aka.ms/platformlimits for more details.
Power Automate
Power Automate
Service Overview
Power Automate allows enterprises to implement automated workflows and business processes
and achieve operational efficiencies. For more details, please visit
https://powerautomate.microsoft.com/.
Licensing overview
General purpose Power Automate capabilities are available on a standalone basis. Limited Power Automate capabilities are
also included within Power Apps, Dynamics 365, and Microsoft/Office 365 and Windows licenses. For more information,
please see the sections titled Power Automate use rights included with Power Apps/Dynamics 365/Office 365/Windows
licenses later in this document.
A high-level overview of the licensing structure is provided below.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e |9
Per user with
Power Automate Per user Per flow
attended RPA
Per flow
Licensing scheme Per user Per user (Minimum initial purchase requirement of 5
flows)
Allows licensed user
Allows licensed user to create and run
to create and run unlimited cloud flows
unlimited cloud using DPA, plus
Allows users within an organization to
flows and automate automate legacy
Description implement cloud flows using DPA with
cloud apps, services apps on a desktop
reserved capacity.
and data with Digital through Robotic
Process Automation Process Automation
(DPA). (RPA) in attended
mode, and AI.
Standard connectors ⚫ ⚫ ⚫
Enterprise management
Applies to flows included ⚫ ⚫ ⚫
and security
Dataverse Database capacity 250MB5 250MB5 50MB5
Per license capacity
Dataverse File Capacity 2GB5 2GB5 200MB5
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 10
instance.
3
Desktop flow connector included (This desktop flow connector is not included in Windows licenses).
4
When Managed Environments is activated in a specific environment, all Power Apps, Power Automate, Power Virtual Agents, and Power Pages usage in
that environment requires standalone licenses. Please see Power Platform Managed Environments for details.
5
Dataverse Database and Dataverse File subscription capacity is accrued at the tenant level. Additional Dataverse Database, Dataverse File and Dataverse
Log subscription capacity can be purchased in increments of 1GB.
6
Additional AI Builder capacity can be purchased per 1M service credits for $500/month.
Please review http://aka.ms/platformlimits for more details.
Note:
• Desktop flow authoring, bot orchestration and management 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
process (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 at the tenant level.
Please review http://aka.ms/platformlimits for more details.
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 can purchase the “Power
Platform Requests add-on” license.
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.
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 at 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 Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 12
Power Automate hosted RPA add-on
Hosted RPA extends desktop-based automation by enabling a bot to run autonomously, i.e., independent of a user.
Unattended bots can be deployed on a virtualized machine or in a virtualized environment. Each hosted RPA add-on
provides capacity for a single Microsoft-hosted bot machine. The Power Automate per user with attended RPA plan or the
Power Automate per flow plan are qualifying base licenses for the hosted RPA add-on. Multiple hosted RPA add-on
licenses can be added with a single qualifying base license.
Note: Power Automate hosted RPA is licensed by bot. Concurrent instances of a singular process require an additional
unattended bot for each instance.
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.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 13
Power Automate use rights included with Power Apps plans
If the embedded flow is not within the context of the Dynamics 365 application, then standalone Power Automate licenses
will need to be purchased.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 14
Summary of Power Automate use rights with Dynamics 365 licenses
Dynamics 365 Enterprise
Plans and capabilities Dynamics 365 Applications2
Applications3
Cloud flows (Automated, instant, and
Execute flows1 scheduled flows) Within app context Within app context
Business process flows
Standard connectors ⚫ ⚫
Power Automate use within M/O365 is limited to the context of the embedding M/O365 application. For both triggers and
actions, flows included within the M/O365 application can connect:
• To any data source within the use rights of the M/O365 application.
• Directly with the M/O365 application (via built in trigger/action).
If the embedded flow is not within the context of the M/O365 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 Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 15
Summary of Power Automate use rights with Microsoft/Office 365 licenses
Power Automate use rights within
Plans and capabilities
M/O365 licenses
Cloud flows (Automated, instant, and scheduled flows) ⚫
Execute flows Business process flows
Desktop flows M365 Business Premium, M365 F3, E3, E5
Standard connectors ⚫
Connect to your data Premium and custom connectors1
On-premises data gateway
Utilize Dataverse for Teams
Select M/O365 licenses
(use for flows in Teams only)2,3,4
Store and manage data
Dataverse (formerly Common Data Service) use rights
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 16
Summary of Power Automate use rights with Windows licenses
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 17
Summary of Power Automate use rights
Power Automate paid offers Power Automate use rights included with:
Standard connectors ⚫ ⚫ ⚫ ⚫ ⚫2 ⚫2
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 18
1
See technical documentation for definitions of each flow type.
2
Within app context - For both triggers and actions, flows included within an embedding application, can connect to any data source
within the use rights of the embedding application and directly with the embedding application.
3
Via Power Automate desktop only; a free application not intended for business-critical functions; there is no SLA or Microsoft
support. Cloud flows, standard and premium connectors, orchestration (scheduled or automatic triggers for desktop flows, attended
or unattended, combined cloud flows + desktop flows in a single automation), sharing desktop flows, developing in a different
environment than the default, Automation Lifecycle Management (ALM), monitoring and execution logs are not included.
4
Unattended RPA scenarios require the Power Automate unattended RPA add-on license, the Power Automate hosted RPA license or
the Power Automate Unattended desktop flow run meter. For the unattended RPA add-on license and hosted RPA add-on licenses,
qualifying base licenses include the Power Automate per user with attended RPA plan or Power Automate per flow plan. Multiple
unattended RPA add-ons can be applied against a single qualifying base license. Concurrent instances of a singular process require
an additional unattended bot for each instance.
5
Desktop flow connector is included. (This desktop flow connector is not included in Windows licenses.)
6
When Managed Environments is activated in a specific environment, all Power Apps, Power Automate, Power Virtual Agents, and
Power Pages usage in that environment requires standalone licenses. Please see Power Platform Managed Environments for details.
7
Dataverse Database and Dataverse File subscription capacity is accrued at the tenant level. Additional Dataverse Database,
Dataverse File and Dataverse Log subscription capacity can be purchased in increments of 1GB.
8
Additional AI Builder capacity can be purchased per 1M service credits for $500/month via the AI Builder capacity add-on.
Please review http://aka.ms/platformlimits for more 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 (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.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 19
Summary of Power Virtual Agents entitlements
Plans and capabilities Power Virtual Agents entitlements
Cloud flows (Automated, instant and Within the context of Power Virtual Agents
Create flows scheduled flows) bots
A billed session is an interaction between the user and the bot and represents one unit of consumption. The billed
session begins when a user topic is triggered and ends when one of these conditions is met—either: The user's
questions are answered; or the conversation exceeds 60 minutes or 100 turns*. There is no end user experience
impact when exceeding 60 minutes or 100 turns; this simply counts as another billed session for reporting
purposes.
*A turn is defined as one exchange between the user and the bot (i.e., the user sends a message to the bot and the bot
responds or vice versa). One billed session usually contains multiple turns.
Reference this link for details.
Licensing structure
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 20
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 Microsoft/Office 365 licenses
Power Virtual Agents for Teams enables customers with select M/O365 licenses to build and deploy
custom chatbots directly within Teams, using Dataverse for Teams. For a complete list of M/O365 licenses
that include Power Virtual Agents for Teams use rights, please refer to Appendix B.
Summary of Power Virtual Agents for Teams use rights included with Microsoft/Office 365 licenses
Power Virtual Agents for Teams use
Plans and capabilities
rights with M/O365 licenses
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 21
Please review http://aka.ms/platformlimits for more details.
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 refer to the Dynamics 365 Licensing Guide for
information related to these entitlements.
Power Pages
Service Overview
Power Pages delivers a secure, enterprise-grade platform for
creating, hosting and administering modern external facing
business websites. For more details, please visit
https://powerpages.microsoft.com/
Licensing overview
Power Pages licensing is based on two user types, authenticated users per website/month and
anonymous users per website/month. Each end user that accesses a Power Pages website needs to be
licensed appropriately.
• Authenticated users definition: Power Pages authenticated users are users who obtain secure access
to a website by logging in through an authentication provider on the website.
• Anonymous users definition: Power Pages anonymous users are users who access a website and do
not log in.
Customers should purchase the necessary number of capacity pack licenses to cover the anticipated
number of authenticated users that will access each Power Pages website over a monthly period. Unused
capacity does not carry over to the next month.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 22
Note: Authenticated user capacity packs do not need to be assigned to individual users. These capacities
are assigned to an environment.
For example, a customer requiring Power Pages access to a single website for 20,000 anonymous
users/month can purchase 40 Power Pages anonymous user capacity packs at Tier 2 pricing.
Power Pages anonymous user subscription plan offers
Customers should purchase the necessary number of capacity pack licenses to cover the anticipated
number of anonymous users that will access each Power Pages website over a monthly period. Unused
capacity does not carry over to the next month.
Note: Anonymous user capacity packs do not need to be assigned to individual users. These capacities are
assigned to an environment.
Power Pages use rights included with Power Apps and Dynamics 365 licenses
Power Pages use rights within Power Apps and Dynamics 365 Enterprise Apps are limited to the context
of the Power Apps and Dynamics Enterprise Apps. Dynamics 365 Enterprise Apps are granted use rights
for Power Pages, however, restricted tables and the associated Dynamics 365 license requirements for
users who create, update, or delete data stored within these tables remain in place. For a full list of
restricted tables, see Restricted tables requiring Dynamics 365 licenses.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 23
1
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
2
Dynamics 365 Sales Enterprise, Dynamics 365 Sales Premium, Dynamics 365 Customer Service Enterprise, Dynamics 365 Field
Service, Dynamics 365 Finance, Dynamics 365 Supply Chain Management, Dynamics 365 Project Operations, Dynamics 365
Commerce, Dynamics 365 Human Resources, Dynamics 365 Business Central, Dynamics 365 Intelligent Order Management
Please review http://aka.ms/platformlimits for more details.
Within same
Create, access, host
1 app or 1 environ. as
Custom websites and administer ⚫ ⚫ ⚫
website licensed
websites
D365 app
Standard connectors ⚫ ⚫ ⚫ ⚫ ⚫
Connect to your data Premium and
⚫ ⚫ ⚫ ⚫ ⚫
custom connectors
Utilize Dataverse ⚫ ⚫ ⚫ ⚫ ⚫
Dynamics 365
Read
restricted tables Read only Read only Read only CRUD
only
access2
Dataverse Database
Default capacity 5 GB3 5 GB3 5 GB4 10 GB4
capacity
Dataverse Database
Accrued capacity 2 GB5 500 MB5 20 GB4 20 GB4
capacity
Per pay-as-you-go
Dataverse Database
environment
capacity
(Default)
Per pay-as-you-go
Dataverse File capacity environment
(Default)
Run websites in a
Managed Environ.
Managed Environments ⚫ ⚫ ⚫ ⚫ ⚫
Manage Power
Platform at scale. 6
1
For exceptions to Dynamics 365 Field Service use rights for Power Apps users, refer to the Dynamics 365 Licensing Guide.
2
For a full list of restricted tables and exceptions for Case tables, see Restricted tables requiring Dynamics 365 licenses.
3
Shared entitlement per tenant
4
Per license capacity
5
Per capacity pack
6
When Managed Environments is activated in a specific environment, all Power Apps, Power Automate, Power Virtual Agents, and
Power Pages usage in that environment requires standalone licenses. Please see Power Platform Managed Environments for details.
Please review http://aka.ms/platformlimits for more details.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 24
Power Platform Dataverse Capacity
Dataverse default subscription capacity
Power Apps, Power Automate, Power Virtual Agents and Power Pages default subscription capacities
leverage the same tenant and infrastructure and will accrue across one tenant. Every tenant with a Power
Apps, Power Automate, Power Virtual Agents and Power Pages license receives default capacity. In
addition, for each Power Apps per user, Power Apps per app, Power Automate per user, Power Automate
per flow plan and Power Pages license there is additional accrued capacity added to the tenant. For
capacity and service limits regarding Dataverse for Teams, please refer to the public documentation here.
Default Default Accrued Accrued
Power Apps Default Capacity per tenant
per user per app per user per app
Dataverse Database capacity 10GB 5GB 250MB 50MB
Dataverse File capacity 20GB 20GB 2GB 400MB
Dataverse Log capacity 2GB 2GB
Note, customers may have as many flows as needed with the per-flow plan. Each flow will increase
capacity limits.
Default
Power Virtual Agents Default Capacity per tenant
per tenant
Dataverse Database capacity 10GB
Dataverse File capacity 20GB
Dataverse Log capacity 2GB
Accrued Accrued
Default Default entitlement entitlement
Power Pages Default Capacity entitlement entitlement per authenticated per anonymous
per tenant per tenant user capacity user capacity
pack pack
Dataverse Database capacity 5GB 5GB 2GB 500MB
Dataverse File capacity 16GB 4GB
Power Apps, Power Automate, Power Virtual Agents, Power Pages and Dynamics 365 Sales, Customer
Service, and Field Service applications leverage the same tenant and infrastructure. Dataverse capacity
(Dataverse Database, Dataverse File, and Dataverse 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 for the web, as well as the Dynamics 365
Licensing Guide for information related to other entitlements.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 25
Database Stores and manages table definitions and data
Stores attachments to notes or emails in Dynamics 365 Sales, Customer Service, and Field Service
File applications and Power Apps. These include documents, image files, videos, PDF files and other
crucial files needed in an organization.
Records table and column data changes over time for use in analysis and reporting purposes. Log
Log
capacity is designed to help organizations meet their auditing, compliance, and governance policies.
The first Power Apps OR Power Automate OR Power Virtual Agents OR Power Pages OR Dynamics 365
Sales, Customer Service, and Field Service subscription 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 assume 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):
Default/ Total Tenant
Default and Accrued Capacity Allocation Accrued/10 Enterprise USL
tenant wide capacity
Dataverse Database capacity 10GB 10*250MB + 20*50MB = 3.5GB 10GB + 3.5GB = 13.5GB
Dataverse File capacity 20GB 10*2GB + 20*400MB = 28GB 20GB+28GB = 48 GB
Dataverse Log capacity 2GB NA 2GB
Included per
Pay-as-you-go environments pay-as-you-go
environment
Dataverse Database capacity 1GB
Dataverse File capacity 1GB
Dataverse Log capacity
Meter definition: Amount of capacity used in the environment beyond any entitled amounts (1GB
database capacity and 1GB of file capacity per environment).
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 26
Dataverse Capacity/environment Additional Increment
Dataverse Database capacity 1GB
Dataverse File capacity 1GB
Dataverse Log capacity 1GB
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 the 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.
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
step up to standalone Power Apps, Power Automate, Power Virtual Agents or Power Pages plans for
additional capacity).
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.”
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 27
Offer Details
SKU Name AI Builder capacity add-on
License type Tenant wide capacity license
Entitlement 1 million monthly service credits
Power Apps,1 Power Automate2 and Dynamics 365
Qualifying base licenses
licenses3
1
Power Apps per app 250 service credits, per user – 500 service credits. Cap on accrued capacity is 1,000,000 credits.
2
Users licensed with Power Automate per user with attended RPA plan are granted 5,000 AI Builder service
Credits/month.
3
Please see the Dynamics 365 Licensing Guide for more information.
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.
AI Builder rate card
Each AI builder capability consumes service credits at different rates. A calculator is available to help
estimate AI Builder Capacity add-on units to be purchased based on the anticipated usage of various AI
Builder services. Administrators can download an Excel capacity consumption report for the tenant here.
Service Credit
Capability Operation Type
Consumption Rate
Business Card Reader Real-time Prediction Prebuilt 100 credits/Card
Training Custom Free
Forms Processing
Real-time Prediction Custom 500 credits/Page
ID reader Real-time Prediction Prebuilt 100 credits/Page
Training Custom Free (Performed on-premises)
Image Classification
Real-time Prediction Custom 4 credits/Image
Invoice Processing Real-time Prediction Prebuilt 500 credits/Page
50 credits/Image (Standard - First 500
images)
Training Custom 400 credits/Image (Domains - First 500
Object Detection images)
10 credits/Image (After 500 images)
Real-time Prediction Custom 20 credits/Image (Standard and Domains)
Training Custom Free
Prediction Scheduled Prediction Custom 1 credit/5 rows
Real-time Prediction Custom 10 credits/1 row
Receipt Scanning Real-time Prediction Prebuilt 100 credits/Page
Training Custom Free
Text Analysis
Real-time Prediction Custom 20 credits/1k chars
Category Classification, Entity Extraction
Real-time Prediction Prebuilt 20 credits/1k chars
Text Analysis
Real-time Prediction Prebuilt 20 credits/1k chars
Key Phrase Extraction, Language Detection, Sentiment
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 28
Capacity enforcement
For AI Builder capacity add-on SKUs, purchased capacity is enforced monthly and unused service credits
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, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 29
Pricing
Power Apps, Power Automate, Power Virtual Agents and Power Pages price lists are located here:
• Power Apps: https://powerapps.microsoft.com/en-us/pricing/
• Power Automate: https://powerautomate.microsoft.com/en-us/pricing/
• Power Virtual Agents: https://powervirtualagents.microsoft.com/en-us/pricing/
• Power Pages: https://powerpages.microsoft.com/en-us/pricing/
Resource Link
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 30
Appendix A: Terminology and Custom Tables
Administration: Administration is critical in order to establish boundaries and policies around the use of
Power Apps in organizations
• Manage environments – space to store, and manage, and share data, apps, and flows
• Data policies – create and enforce policies that define how data can be shared
App (definition of Power Apps per app): An “app” is a combination of Power Platform assets that solves a
specific business scenario
• Each “per app” license provides use rights to run 1 custom app (canvas or model driven), or
access 1 custom website.
• No limits on other components (e.g., forms, dashboards, etc.).
Application Program Interface (API): Any form of application programming interface that provides access
to a Microsoft service and any associated tools, including sample code that enables interactions with
Microsoft's services, and documentation that Microsoft makes available under these TOU, and includes all
elements, components, and executables of such API.
Application Types:
• Canvas Apps: Design and build a business application from a canvas in Microsoft Power Apps
without writing code in a traditional programming language. Design the application by dragging and
dropping elements onto a canvas, the designer has complete control over app layout.
• Model-driven Apps: Design is a component-focused approach to app development based on data
model and business processes. Unlike canvas app development where the designer has complete
control over application layout, with model-driven apps much of the layout is determined for you
and largely designated by the components you add to the application.
Connector: It provides a way for users to connect their business data and leverage a set of pre-built
actions and triggers to build their applications and workflows. Examples of connections: Dataverse
(formerly Common Data Service), SharePoint, SQL, OneDrive, Excel, Dynamics 365.
• Standard Connector: Data sources within the Microsoft 365 ecosystem. Examples: Excel, Outlook,
SharePoint, LinkedIn. A list of standard connectors is located here.
• Premium Connector: Business systems beyond Microsoft 365. Examples: DocuSign, Zendesk, Jira
Software.
• Custom Connector: To support more tailored scenarios, users can build custom connectors with
their own triggers and actions. These connectors are function-based; data is returned based on
calling specific functions in the underlying service. Example: Services that are not available as
prebuilt connectors.
• On-premises Connector: Accesses on-premises data using a gateway. Example: Microsoft SQL
Server.
CRUD: Create, read, update, and delete operations.
Dataverse (formerly Common Data Service): Dataverse lets you store and manage data that is used by
business applications.
Dataverse for Teams, built atop Dataverse, delivers a built-in low code data platform for Microsoft Teams,
and provides relational data storage, rich data types, enterprise grade governance, and one-click solution
deployment.
Dataverse is designed to be used in any application (not just Teams) and includes additional security
features such as auditing, sharing, column level and hierarchical security. For a detailed comparison on
Dataverse for Teams and Dataverse capabilities, please refer to the public documentation here.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 31
Desktop flow: A feature in Power Automate targeting the RPA market by enabling legacy apps to be
automated via GUI vs API.
• Processes executed via desktop flows can be contained within a broader API-based automation
scenario or exist standalone.
Flow (definition of flow within app context): For both triggers and actions, flows included within an
embedding application can connect
• To any data source within the use rights of the embedding application
• Directly with the embedding application (via built in trigger/action)
Robotic Process Automation (RPA): A market for process automation that encompasses the use of an
application's graphical user interface (GUI), where a user records a series of steps/actions/tasks for the
automation technology to then perform as a process by repeating directly in the GUI.
RPA robot or "bot": A GUI-based process running on a desktop or virtualized environment
• Attended bot: Triggered by an explicit user action on their workstation, i.e., a local or remote
desktop
o Must operate concurrently with the user on the same workstation
o Can run more than one discrete process, but each process must be serialized to run
sequentially
• Unattended bot: Runs autonomously without requiring user actuation
o Can be deployed on a local or remote desktop, or other virtualized environment
o Can run more than one discrete process, but each process must be serialized to run
sequentially
o Concurrent instances of a singular process require an additional unattended bot for each
instance
Tables: A set of records used to store data, similar to how a table stores data within a database. Tables let
users model business data for use within an organization’s business applications. Examples of tables:
Account, Contact, Lead, Opportunity.
• Standard tables: Dataverse (formerly Common Data Service) provides business tables, out of the
box, that represent most commonly used tables across business applications. Examples: Account,
Appointment, Contact, Email, etc.
• Custom tables: Tables that are created by the customer/partner for a specific business need. For
example, type of machine is not a standard table, so it can be created as a custom table.
• Restricted tables: Tables that requires a Dynamics 365 license for full access. Examples: Case, SAL,
Knowledge Articles. For list of restricted tables click here.
• Complex tables: These are tables that use complex server-side business logic. Any table (whether
standard or custom) becomes complex once the customer/partner associates the table with the
custom business logic. Example: any table that uses a real-time workflow or code plug-in.
Workflows:
• Background workflows: Task automation across systems and services. Runs in the background.
• Real-time workflows: Task automation across systems and services. Runs in a real time manner.
• Business process flows: Structured stateful human interactive workflows which are composed of
multiple steps, allows branching/stage gating, and includes process KPIs and reporting.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 32
Appendix B: Dynamics 365, Microsoft/Office 365, and
Windows licenses that include Power Platform capabilities
Dynamics 365
Limited Use Rights Included with Qualifying
License
Qualifying License
Power
Power Apps Power Pages
Automate
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 33
Microsoft 365*, Office 365, and Windows
Limited Use Rights Included with Qualifying License
Power
Qualifying License Power Automate Virtual Dataverse
Power
Agents for
Apps
for Teams
Cloud Desktop
Teams
flows flows
Office 365 E1 ○ ○ ○ ○
Office 365 E3 ○ ○ ○ ○
Office 365 E5 ○ ○ ○ ○
Office 365 F3 ○ ○ ○ ○
Microsoft 365 F1
Microsoft 365 F3 ○ ○ ○ ○ ○
Microsoft 365 E3 ○ ○ ○ ○ ○
Microsoft 365 E5 ○ ○ ○ ○ ○
Windows 10 Pro ○
Windows Enterprise E3 ○
Windows Enterprise E5 ○
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 34
Office 365 A1 ○ ○
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 35
Appendix C: Change Log
Page Topic Change Action Date
12, 17 Power Automate New Hosted RPA January 2023
Various Power Platform New Managed Environments January 2023
Various Power Pages New Power Pages Nov 2022
24 AI Builder Updated Image Classification added to rate card June 2022
Various Power Platform Clarified Minor clarifications May 2022
Service credit consumption rates by
24 AI Builder New April 2022
capability and operation listed
Power Virtual Agents for
20 Clarified Chat sessions per user/24 hours April 2022
Teams
5 Power Apps New Power Apps per app pay-as-you-go plan March 2022
Power Platform pay-as-you-go Dataverse
22, 23 Dataverse New March 2022
capacity
Power Apps and Power Rebranded as Power Platform Requests
10, 17 Rebranded Feb 2022
Automate capacity add-on add-on
4, 5 Power Apps New AI Builder service credits Dec 2021
Dynamics 365 Field Service use rights for
5 Power Apps New Dec 2021
work orders
Various Power Platform requests Updated Updated footnotes Nov 2021
Dynamics 365 Intelligent Order
28 Appendix B Updated Oct 2021
Management added
3, 4 Power Apps per app Updated Entitlements updated Oct 2021
Various WinAutomation Updated End of support Oct 2021
8 Power Apps Portals Updated Channels for per login add-on June 2021
11, 17 Power Automate New Process Advisor June 2021
Terminology change from entities to
Various Microsoft Dataverse Updated May 2021
tables
Power Virtual Agents use rights included
19 Power Virtual Agents New May 2021
with Dynamics 365 applications
Various Subscription capacity Updated Power Apps and Power Automate May 2021
Various Daily API request limit Rebranded Rebranded as Power Platform requests May 2021
Various Power Virtual Agents Clarified Daily API request limit April 2021
7 Power Apps portals Clarified End user type March 2021
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2023 P a g e | 36