Microsoft Dataverse API limits overview

Dataverse API limits help ensure service levels, availability, and quality. Dataverse API limits are part of the Power Platform Request limits and allocations. This article will introduce limits specifically for Dataverse applicable for Power Apps, Power Automate, and customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation) connecting to Dataverse.

For information about limits for all areas within Power Platform, see Power Platform Request limits and allocations.

There are two categories of limits that apply for Dataverse: Entitlement and Service protection limits as summarized below.

Service Protection limits Power Platform Request (API Entitlement) limits
Immediately return 429 Too Many Requests when limits are exceeded. Enforced for Power Automate flows but will have provisions for occasional overages on Dataverse, when enforced
Evaluated in a 5-minute sliding window. Evaluated in a 24-hour period.
Applies to all external requests to Dataverse web services. Applies to all compute operations and analytics originating from internal or external requests.
Developer is responsible for avoiding conditions that can cause errors and managing retry when they occur. Administrator is responsible to manage assigned capacity. They can purchase capacity add-ons to increase limits.
Enforced today within the product. - Will be enforced after preview report, available today for administrators to track and estimate usage, is made generally available.
-Preview reports are available now.
More information: More information:

Entitlement limits

These limits represent the number of requests users are entitled to make each day. The allocated limit depends on the type of license assigned to each user.

If any user exceeds their request entitlement, the administrator would be notified and would be able to assign Power Apps and Power Automate request capacity to that user. Users won't be blocked from using apps for occasional and reasonable overages at this point of time.

For Dataverse, API requests include all data operations that interact with table rows where rows are created, retrieved, updated, or deleted (CRUD). Special operations such as share and assign are included because they're considered updates. These requests can be from any client or application and using any endpoint. These include, but aren't limited to, operations performed by plug-ins, async workflows, custom controls, and $batch (ExecuteMultiple) operations. There's a small set of system internal operations that are excluded, like sign in, sign out, and system metadata operations.


Power Platform API request allocations include use of Power Automate, AI Builder, and Connector APIs. All requests through a connector that result in a Dataverse request will represent 1 Power Platform request.

For details on these entitlement limits, see Microsoft Power Platform requests allocations based on licenses.

For information about viewing and allocating capacity add-ons, see Capacity add-ons.

For information about purchasing individual capacity add-ons see the Power Apps and Power Automate Licensing Guide.

Service protection limits

To ensure consistent availability and performance for everyone we apply some limits to how APIs are used with Dataverse. Service protection API limits help ensure that users running applications can't interfere with each other based on resource constraints. The limits won't affect normal users of the platform. Only applications that perform a large number of API requests may be affected. The limits provide a level of protection from random and unexpected surges in request volumes that threaten the availability and performance characteristics of the Dataverse platform.

We limit the number of concurrent connections per user account, the number of API requests per connection, and the amount of execution time that can be used for each connection. These metrics are evaluated within a five-minute sliding window. When one of these limits is exceeded, an exception will be thrown by the platform.


Service protection limits apply to all external web service requests, not only the CRUD operations on tables counted against entitlement limits.

Service protection API limits aren't applied against API calls made within workflows, custom workflow activities, or plug-in code. These operations are invoked internally.

Service protection limits are only encountered by applications that perform a high volume of data operations. We recommend that developers building applications that perform a high volume of data operations apply patterns to retry operations after a period of time when these exceptions are returned. Applying these patters will allow the application to respond to exceptions the service sends and reduce the total number of requests and achieve the highest possible throughput.

For information about the specific errors that can be returned and how developers can apply patterns to respond to these errors, see Service Protection API Limits.

See also

Administer Power Platform / Licensing and license management / Requests limits and allocations
Developer / Work with data using code / Service Protection API Limits