Requests limits and allocations
Effective October 2019, to help ensure service levels, availability and quality, there are entitlement limits to the number of requests users can make each day across customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation), Power Apps, Power Automate, AI Builder, and Power Virtual Agents.
What is a Microsoft Power Platform request?
Requests in Microsoft Power Platform consist of various actions which a user makes across various products. At a high level, below is what constitute an API request:
Connectors – all API requests to connectors from Power Apps or Power Automate
Microsoft Power Automate – all Power Automate step actions
Common Data Service – all CRUD operations including user-driven and internal system calls required to complete CRUD transactions, as well as special operations like “share” or “assign.” These can be from any client or application and using any endpoint SOAP or REST. These include but are not limited to plug-ins, async workflows, and custom controls making the above-mentioned operations.
Note that for Common Data Service, there will be a small set of system internal operations that are excluded, such as login, logout, and system metadata operations.
This table below will describe the common requests limits as well as the allocation which a user gets based on the type of license assigned to the user.
Microsoft Power Platform requests allocations based on licenses
All the users of Microsoft Power Platform can use a certain number of requests based on the license they are assigned. The following table defines the number of requests a user can make in a 24-hour period:
|User licenses||Number of API requests / 24 hours|
|Dynamics 365 Enterprise applications1||20,000|
|Dynamics 365 Professional 2||10,000|
|Dynamics 365 Team Member||5,000|
|Power Apps per user plan||5,000|
|Power Automate per user plan||5,000|
|Office licenses (that include Power Apps/Power Automate)3||2,000|
|Application user / Non-interactive users||See Non-licensed user section below|
1Dynamics 365 Enterprise applications include Dynamics 365 Sales Enterprise, Dynamics 365 Customer Service Enterprise, Dynamics 365 Field Service, Dynamics 365 Project Service Automation, Dynamics 365 Retail, Dynamics 365 Talent, Dynamics 365 Customer Engagement plan.
2Dynamics 365 Professional includes Dynamics 365 Sales Professional, Dynamics 365 Customer Service Professional.
3See Appendix C for Microsoft 365 licenses that include Power Apps and Power Automate capabilities in the Licensing Guide.
Users who are running apps and flows without a user license through the Power Apps per app plan or flows licensed through the Power Automate per flow plan are granted the following API request entitlement.
|**Non User Licenses **||Number of API requests / 24 hours|
|Power Apps per app plan||1,000 per user pass|
|Power Automate per flow plan||15,000 per flow|
If a user has multiple plans assigned from different product lines, the total number of requests allowed would be the sum of requests allocated to each license type. For example, if a user has both a Dynamics 365 Customer Service Enterprise license as well as a Power Apps per user license , then that user will have a total of 20000 + 5000 = 25000 requests available per 24 hours.
If a user has multiple licenses allocated within the same product line, for example if a user has a Dynamics 365 Customer Service Enterprise license as the base license and a Dynamics 365 Sales Enterprise license attached, the total number of requests would be what is provided by the base license - Dynamics 365 Customer Service.
Power Apps and Power Automate capacity add-on
Power Apps and Power Automate capacity add-on allows customers to purchase additional requests. Eventually, these may be assigned to any user who has a Power Apps/Power Automate license as well as a Dynamics 365 license.
Each capacity add-on provides an additional 10,000 requests/24 hours which can be assigned to any user. Multiple capacity add-ons can also be assigned to the same user.
Power Apps and Power Automate capacity add-ons cannot be assigned to users yet. Assignment will be possible later in calendar year 2020. When supported these may be assigned to application and administrative and non-interactive users.
Non-licensed users/application users/Users with special free licenses
Common Data Service also provides the ability to have identities that do not require any user license to interact with the service. There are three types of these users:
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 these users, every tenant will get base request capacity per tenant that can only be used by these users and not by users with standard licenses.
This base request capacity is based on the type of subscription, as follows:
If a tenant has at least one Dynamics 365 enterprise subscription, they will get 100,000 requests per 24 hours.
If a tenant has at least one Dynamics 365 professional subscription, they will get 50,000 requests per 24 hours.
If a tenant has at least one Microsoft Power Apps or Power Automate subscription, they will get 25,000 requests per 24 hours.
If a tenant has multiple types of subscriptions, their base request capacity will use the subscription with the larger number of requests. For example, if a customer has both Dynamics 365 Customer Service (100,000 requests) and Power Apps per user (25,000 requests) subscriptions, their base request capacity will be 100,000 requests per 24 hours.
Base request capacity is defined at the tenant level and can only be used by non-licensed users, application users, and users who have free ($0) licenses.
After base request capacity is exhausted, customers can increase this capacity by purchasing a Power Apps and Power Automate capacity add-on.
Service protection limits currently applicable
Apart from the new daily API request limit, there are other service protection limits specific to various services that exist currently. These limits are usually much higher when compared to the daily per user entitlements for a 24-hour period. 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:
Common Data Service service protection API limits: applicable for customer engagement apps (such as Dynamics 365 Sales and Customer Service), Power Apps, and Power Automate connecting to Common Data Service/customer engagement apps
Microsoft Power Automate limits: applicable for Power Automate
Limits in connectors: applicable for Power Automate and Power Apps
Frequently asked questions
What happens if any user exceeds request capacity?
If any user exceeds their request capacity, the admin for the tenant/environment is notified. The admin can assign Power Apps and Power Automate request capacity to that user.
Users won't be blocked from using the app for occasional and reasonable overages at this point in time.
Will my integrations stop working if application users exceed base request capacity?
Currently, integrations won't be stopped for occasional and reasonable overages (see above). Administrators will be notified about overages and will be able to add Power Apps and Power Automate request capacity to be compliant. In the near future, after reporting becomes available, certain operations would be blocked when a tenant exceeds their Power Platform Request entitlements. These blocked operations will be in administration and customization areas, but not limited to these operations and could expand into other areas as well, depending on the overage scenarios.
Will there be a transition period for existing customers?
Yes, all existing customers will have a transition period until reporting is made available in the Power Platform admin center.
What tools can an admin use to monitor and analyze API requests across the platform?
Usage reports and monitoring capabilities are expected by October 2020 in the Power Platform admin center and will be the best way to monitor/analyze usage for API requests. This reporting will account for interactive and non-interactive traffic, and will also de-duplicate calls between Power Apps and Power Automate to the Common Data Service.
Can I look at the API numbers in Common Data Service Analytics section of the Power Platform Admin Center to get a sense of Power Platform request counts versus entitlements?
No, the existing API reporting includes all Common Data Service API calls, and will not include Power Apps, Power Automate, and Power Virtual Agent requests. For the Power Platform request counts, you should use the new reporting that is soon to be released. Additionally, some internal operations are not counted in the forthcoming Power Platform request report. For example, the calls to entities that are considered ‘IsPrivate’ are excluded, such as: sdkmessagerequest, solutioncomponentdefinition, and ribbonclientmetadatareporting.
Do the Power Platform request entitlements roll over from day to day or month to month?
No. All the Power Platform request entitlements are calculated on a rolling 24-hour period. If they aren't consumed, they don't roll over to the next day or next month.
Does each application user, non-interactive user, or administrative user get their own tenant-level entitlement?
No, tenant-level entitlements are shared across all application users, non-interactive users, or administrative users within the tenant.
Will the requests generated from async workflows and plug-ins in Common Data Service count against the request limits?
Yes, if these requests are making CrUD, assign, or share–type requests, they will count. However, requests generated internally from the platform aren't going to be counted.