Requests limits and allocations
Refrence 1
Power Platform Request limits exist to help ensure service levels, availability, and quality of the platform. There are limits to the number of requests users can make each day across Power Apps, Power Automate, Power Virtual Agents, and Dynamics 365 applications.
What is a Microsoft Power Platform request?
Requests in Microsoft Power Platform consist of various actions that a user makes across various products. At a high level, below is what constitutes an API request:
- Power Apps – all API requests to connectors and Microsoft Dataverse.
- Power Automate – all API requests to connectors, process advisor analysis, HTTP actions, and built-in actions from initializing variables to a simple compose action. Both succeeded and failed actions count towards these limits. Additionally, retries and other requests from pagination count as action executions as well. For more information, see What counts as Power Platform request?
- Power Virtual Agents - API requests (or calls) to Power Automate flows from within a chatbot conversation.
- Dataverse – all create, read, update, and delete (CRUD), assign, and share operations including user-driven and internal system requests required to complete CRUD transactions, and special operations like share or assign. These can be from any client or application (including Dynamics 365) and using any endpoint (SOAP or REST). These include, but aren't limited to, plug-ins, classic workflows, and custom controls making the earlier-mentioned operations.
Note
For Dataverse, there is a small set of system internal operations that are excluded from limits, such as login, logout, and system metadata operations.
The sections below describe the request types and the limits established for each.
Licensed user request limits
All the users of Microsoft Power Platform have limits on the number of requests based on the license they're assigned. The following table defines the number of requests a user can make in a 24-hour period:
| Products | Requests per paid license per 24 hours |
|---|---|
| Paid licensed users for Power Platform (excludes Power Apps per App, Power Automate per flow, and Power Virtual Agents) and Dynamics 365 excluding Dynamics 365 Team Member1 | 40,000 |
| Power Apps pay-as-you-go plan, and paid licensed users for Power Apps per app, Microsoft 365 apps with Power Platform access, and Dynamics 365 Team Member2 | 6,000 |
| Power Automate per flow plan3, Power Virtual Agents base offer, and Power Virtual Agents add-on pack4 | 250,000 |
| Paid Power Apps Portals login | 200 |
1 This category includes paid licenses for Power Apps per user plan (which includes the previous Power Apps Plan 1 and Power Apps Plan 2 licenses), Power Automate per user plan (which includes the previous Flow Plan 1 and Flow Plan 2 licenses), Dynamics 365 Sales Premium, Dynamics 365 Sales Enterprise, Dynamics 365 Sales Professional, Dynamics 365 Customer Service Enterprise, Dynamics 365 Customer Service Professional, Dynamics 365 Field Service, Microsoft Relationship Sales, Microsoft Industry Cloud, Dynamics 365 Project Service Automation, Dynamics 365 Commerce, Dynamics 365 Human Resources, Dynamics 365 Finance, Dynamics 365 Project Operations, Dynamics 365 Supply Chain Management, Dynamics 365 Customer Engagement plan, Dynamics 365 Unified Ops plan, Dynamics 365 Plan, Dynamics 365 for Operations Device, Dynamics 365 for Operations Activity, Dynamics AX Online Device, Dynamics AX Online Task, Dynamics CRM Online Enterprise, and Dynamics CRM Online Professional.
2 This category includes the Power Apps pay-as-you-go plan, and paid licenses Power Apps per app plan, Dynamics 365 Team Member, Dynamics CRM Online Basic, Dynamics CRM Online Essential, Dynamics AX Self-Serve, Microsoft 365 licenses, and Microsoft Project Online (Plan 1, Plan 3, and Plan 5). See Appendix B in the Licensing Guide for Microsoft 365 licenses that include Power Apps and Power Automate capabilities.
3 The Power Automate per flow plan allows capacity to be specifically reserved for a single flow, irrespective of the owner of the flow. This doesn't use the non-licensed user request limits at the tenant level.
4 Power Virtual Agents requests are counted from Power Automate flows triggered from a Power Virtual Agents chatbot. Power Virtual Agents initial sessions pack and additional sessions pack both receive the same daily Power Platform Request limits.
Other details
Power Platform Request limits are only included with paid base licenses in the Dynamics 365 'base + attach' licensing model. Attach licenses don't include separate limits. For example, if a user has a Dynamics 365 Customer Service Enterprise as the base license and Dynamics 365 Sales Enterprise as an attach license, the total request limit would be what is provided by the base license - Dynamics 365 Customer Service Enterprise.
If a user has multiple paid licenses assigned to them, the total number of requests allowed would be the sum of requests allowed for each license. For example, if a user has both a Dynamics 365 Customer Service Enterprise base license and a Power Apps per user license then that user will have a total of 40,000 + 40,000 = 80,000 requests available per 24 hours.
Power Virtual Agents requests are counted from Power Automate flows triggered from a Power Virtual Agents chatbot. Power Virtual Agents initial sessions pack and additional sessions pack both receive the same daily Power Platform Request limits.
Non-licensed user request limits
A separate limit is established for certain activities(for example: A background process that migrates data between databases) that don't require a user to interact with the service. These limits are defined and pooled at the tenant level. Dataverse enables you to have identities that don't require any user to interact with the service. These include:
Additionally, there are special free ($0) licenses, which are used to interact with Dynamics 365 applications like Dynamics 365 Marketing. See How Marketing is licensed for more details.
For these non-licensed identities, every tenant will get an initial base request limit per tenant determined by what paid licenses are on the tenant, plus accrued limits determined by the quantity of paid Dynamics 365 Enterprise and Professional licenses.1 This pool can only be used by these non-licensed users and not by users with assigned interactive user licenses.
| Products | Pooled non-licensed tenant-level requests per 24 hours |
|---|---|
| Dynamics 365 Enterprise & Professional applications1 | 500,000 base requests + 5,000 requests accrued per USL1 up to 10,000,000 max2 |
| Power Apps (all licenses) | 25,000 base requests with no per-license accrual for the tenant |
| Power Automate (all licenses) | 25,000 base requests with no per-license accrual for the tenant |
1 This category includes licenses for Dynamics 365 Sales Premium, Dynamics 365 Sales Enterprise, Dynamics 365 Sales Professional, Dynamics 365 Customer Service Enterprise, Dynamics 365 Customer Service Professional, Dynamics 365 Field Service, Microsoft Relationship Sales, Dynamics 365 Project Service Automation, Dynamics 365 Commerce, Dynamics 365 Human Resources, Dynamics 365 Finance, Dynamics 365 Project Operations, Dynamics 365 Supply Chain Management, Dynamics 365 Customer Engagement plan, Dynamics 365 Unified Ops plan, Dynamics 365 Plan, Dynamics CRM Online Enterprise, and Dynamics CRM Online Professional. Power Platform Request accrued non-licensed tenant-level limits are only granted with paid base licenses in the Dynamics 365 'base + attach' licensing model.
2If you anticipate exceeding the non-licensed user limits, reach out to your reseller or Microsoft Account team to discuss a custom solution.
Additional details
Certain products operate in the concept of a service principal and will have their limits accrued to the non-licensed user pool. This is the best way to align limits with how the product operates on the platform.
If a tenant has multiple types of subscriptions, their non-licensed user request capacity will use the product line subscription with the larger number of requests. For example, if a customer has both Dynamics 365 Customer Service Enterprise base license subscriptions (500,000 minimum requests + accrued limits) and Power Apps per user subscriptions (25,000 requests/day), their pooled tenant-level request capacity will be 500,000 minimum requests + accrued limits per 24 hours.
What happens if a licensed or non-licensed user exceeds limits
Power Platform Request limits have been updated and substantially increased in late 2021 to be at levels that are significantly higher than typical usage for most customers. With the updated limits, expectations are that very few users would exceed the documented limits. If you anticipate exceeding the non-licensed user limits, reach out to your reseller or Microsoft Account team to discuss a custom solution.
Any possible high usage enforcement won't happen until six months after Power Platform Request usage reporting has been generally available in the Power Platform Admin Center.
Microsoft reserves the right to enforce limits for overages. If a customer encounters high usage enforcement, they can expect some form of throttling. Customers can purchase additional capacity to avoid high usage enforcement or move their environment to pay-as-you-go and pay for actual usage above daily limits.
Power Platform Request capacity add-on
Customers that observe in reporting that they're frequently using more requests than limits can avoid high usage enforcement by purchasing the Power Platform Request capacity add-on. This add-on allows customers to increase the limits for specific high usage licensed users or high usage non-licensed users. Each capacity add-on raises the request limit by another 50,000 per 24 hours. Multiple capacity add-ons can be assigned to increase limits.
You cannot assign Power Platform requests capacity add-on packs to users or flows during the transition period. However, Microsoft recommends that you purchase these add-ons to remain within your license terms and to be prepared for when the transition period ends.
If your Power Automate flows are being throttled, try Pay-as-you-go to ensure none of the flows in the environment are throttled. If you cannot use Pay-as-you-go, purchase add-ons and create a Microsoft support ticket with the flow details and add-on details so that the support team can provide exceptions for your throttled flows.
Note
Currently, capacity add-ons cannot be assigned to users (including application, administrative, and non-interactive users). The functionality for assignment of capacity add-ons will be aligned to the timing of high usage enforcement.
Other applicable limits
Apart from the daily Power Platform Request limits, there are other service protection limits specific to each service. As with the daily request limits, these limits help maintain the quality of service by protecting the service from malicious or noisy behavior that would otherwise disrupt service for all customers.
Review the following resources for information about current service protection limits for each service:
- Dataverse limits: applicable for model-driven apps and customer engagement apps (such as Dynamics 365 Sales and Customer Service), Power Apps, and Power Automate connecting to Dataverse/customer engagement apps
- Power Automate limits: applicable for automated, scheduled, and instant flows
- Limits in connectors: applicable for Power Automate and Power Apps
View detailed Power Platform request usage information in the Power Platform admin center (preview)
To view the consumption of Power Platform requests for licensed users, non-licensed users, and per flow licensed flow runs.
Sign in to the Power Platform admin center.
Select Capacity in the left-side navigation pane.
On the Summary tab, select Download reports in the Add-ons section.
Select New from the menu.
Select Microsoft Power Platform requests in the Choose a report box.
Select the required type of report and then select Submit.
Once the report is ready, select Download to download the report as an Excel CSV file.
Note
These reports are currently in preview. There are two limitations with the Licensed User preview report.
- The entitlements for Licensed Users are showing up in the reporting per user per day per environment. The limits should apply at the per user per day level. When looking at reporting, understand that the limits are per user per day, using the entitlement quantity only one time per day, not summing entitlements for the same user potentially multiple times.
- The Licensed User report will not show correct entitlements for users licensed via the Power Apps per app license or Power Apps per app pay-as-you-go meter. Entitlements for such users will be shown as 0 when in fact they should be shown as 6000 (request per 24-hour period as outlined above).
Licensed User report
The Licensed User report shows the Power Platform request usage per user per day and the users entitled quantity. The downloadable report contains the following fields:
| Field | Description |
|---|---|
| Environment ID | The unique Power Platform environment identifier. |
| Environment Name | The display name of environment. |
| Caller ID | The unique identifier of the calling identity which maps to Active Directory ID. This can be null or empty. |
| Caller Type | The type of caller identity. Applicable value for licensed user report is User. |
| Usage Datetime | The date and time of when the usage was captured (UTC). |
| Entitled quantity | The total of any Power Platform request limits for the user. |
| Total consumed quantity | The total usage across all the types of Requests (Dataverse, Power Apps, and Power Automate). |
| Dataverse Requests | Number of Power Platform requests originating from Dataverse. |
| Power Automate Requests | Number of Power Platform requests originating from Power Automate. |
| Power Apps Requests | Number of Power Platform requests originating from Power App. |
Here's a sample of a detailed usage report:
Non-licensed User report
The Non-licensed User report shows the Power Platform request usage per day for non-licensed users and the total entitlement for non-licensed users for that tenant. The downloadable report contains the following fields:
| Field | Description |
|---|---|
| Power platform request entitlement for this tenant | The total daily entitlement for non-licensed power platform requests for this tenant. |
| Environment ID | The unique Power Platform environment identifier. |
| Environment Name | The display name of environment. |
| Caller ID | The unique identifier of the calling identity. This can be null or empty. |
| Caller Type | The type of caller identity. Applicable values are System, Non-Interactive/Application. |
| Resource Type | The type of resource. Applicable values are Dataverse, Power Apps, and Power Automate. |
| Resource ID | The unique resource identifier. Based on the Resource Type, this could be an app ID, Dataverse Organization ID, or Power Automate Flow ID. This can be null or empty. |
| Meter Category | The top level meter in this case Power Platform request. |
| Meter Subcategory | The detailed classification of what generated the request. This can be Dataverse, Power Apps, or Power Automate. |
| Usage Datetime | The date and time of when the usage was captured (UTC). |
| Consumed Quantity | Usage of Power Platform requests. |
Here's a sample of a detailed usage report:
Per Flow report
The Per Flow Licensed Flows downloadable report contains the following fields:
| Field | Description |
|---|---|
| Environment ID | The unique Power Platform environment identifier. |
| Environment Name | The display name of environment. |
| Environment Region | Not available during preview. |
| Caller ID | The unique identifier of the Flow. This can be null or empty. |
| Caller Type | The type of caller identity. Applicable values are Flow. |
| Usage Datetime | The date and time of when the usage was captured (UTC). |
| Entitled Quantity | The value of any included entitlement for the flow. |
| Consumed Quantity | Usage of Power Platform requests. |
Here's a sample of a detailed usage report:
Frequently asked questions
What tools can I use to monitor and analyze Power Platform requests across the platform?
Reporting for Power Platform Request usage in preview is available in the Power Platform admin center.
What are the timelines for Power Platform Request limits?
The concept of limits was first introduced in late 2019 and documented limits were substantially increased in late 2021. Public preview reporting for Power Platform Requests rolled out in June 2022. Following a public preview period, the reports will move to general availability. There is no current ETA for when this will happen. Any potential high usage enforcement won't start until at least six months after reports have been made generally available. However, note that Power Automate will continue to throttle at transition limits until enforcement. See FAQs.
What account's limits are used for classic workflows or Power Automate flows?
It depends if the process is run on-demand or in the background. Instant flows, which are run on-demand, will use the limits of the account who started the process. On the other hand, workflows or automated/scheduled flows that run in the background will always use the limits of the owner of the process irrespective of why the process started or what accounts are used for connections inside of the process. See Whose Power Platform request limits are used by the flow?.
Do the Microsoft Power Platform request limits roll over from day to day or month to month?
No. All the Microsoft Power Platform requests exist for a 24-hour period. If they aren't consumed, they don't roll over to the next day nor do they accumulate within a month.
Does each application user, non-interactive user, administrative user, or SYSTEM user get their own tenant-level limit?
No. Tenant level limits are shared across all application users, non-interactive users, administrative users, or SYSTEM user within the tenant.
Do the requests generated from classic Dataverse workflows and plug-ins in Dataverse count against the request limits?
Yes, if these requests are making CRUD, assign, or share–type requests, they'll count. In the case of classic workflows, this includes actions such as checking conditions, starting child workflows, or stopping workflows. However, requests generated internally from the platform aren't counted, such as: sdkmessagerequest, solutioncomponentdefinition, and ribbonclientmetadatareporting.
Should I use a third-party data integration tool instead of Power Automate to avoid hitting my limits?
No, third-party data integration tools are subject to the exact same limits as scheduled, instant, or automated flows. Thus, there's no difference whether you choose to use Power Automate or a third-party tool. Moreover, requests from Power Automate to the Dataverse aren't double-counted, a flow that calls one action will only count as one request against their limit, not two.
No comments:
Post a Comment