Difference between revisions of "API requests limits"

From Power Wiki
Jump to navigation Jump to search
Line 10: Line 10:
 
== Community Resources ==
 
== Community Resources ==
 
* [https://powerplatform.se/api-per-user-limits-the-good-the-bad-and-the-ugly/ API per user limits – The good, the bad and the ugly] by Gustaf Westerlund 2019-09-03
 
* [https://powerplatform.se/api-per-user-limits-the-good-the-bad-and-the-ugly/ API per user limits – The good, the bad and the ugly] by Gustaf Westerlund 2019-09-03
 +
* [https://crmchap.co.uk/summarising-the-new-dynamics-365-customer-engagement-api-request-limits-allocations/ Summarising the New Dynamics 365 Customer Engagement API Request Limits & Allocations] by Joe Griffin
 
* [http://develop1.net/public/post/2019/09/04/how-do-the-powerplatform-api-limits-affect-model-driven-apps How do the Power Platform API Limits affect Model Driven Apps?] by Scott Durow
 
* [http://develop1.net/public/post/2019/09/04/how-do-the-powerplatform-api-limits-affect-model-driven-apps How do the Power Platform API Limits affect Model Driven Apps?] by Scott Durow

Revision as of 20:00, 18 January 2021

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 Power Apps, Power Automate, AI Builder, Power Virtual Agents, and customer engagement apps. These are refered to as Power Platform request limits.

Microsoft Dataverse API limits is a part of this. There are two categories of limits that apply for Microsoft Dataverse: Entitlement and Service protection limits.

Microsoft Resources

Community Resources