API Request Allocations for Microsoft Dynamics 365, Power Apps and Power Automate

By 23rd October 2019 November 8th, 2019 Product Updates

Microsoft have announced that as from October 2019, there will be new limits and allocations applied to requests made on the Power Platform; we take a look at how this may affect users of Microsoft Dynamics 365, Power Apps and Power Automate.

What is a Power Platform Request?

It’s important to clarify what constitutes a request when referring to these new limits and allocations. A request (also referred to as an API Call) is:

  1. The creating, reading, updating and deleting (often abbreviated to CRUD) of a record in the Common Data Service. In addition to these CRUD actions, the sharing or assigning of a record also counts as a request.
  2. Any Step Action within Microsoft Power Automate.
  3. Any API calls to Connectors from within a Power App or Power Automate.

Request Allocations

Each user is allocated requests, the number of which is dependent on the licence(s) they have been assigned

User Allocations

Licence TypeNo. of Requests per 24-Hour period
Dynamics 365 Enterprise App20,000
Dynamics 365 Professional App10,000
Dynamics 365 Team Member5,000
Power Apps Per User Plan5,000
Microsoft Power Automate Per User Plan5,000
Office 365 (that include Power Apps/Power Automate)2,000

If a user has access to more than one licence, the allocations from each licence are totalled up into one allocation.

Per App and Per Flow Allocations

Requests made by Power Apps or Power Automate that are part of Per App and Per Flow licences have different allocations:

Licence TypeNo. of Requests per 24-Hour period
Power Apps Per App Plan1,000 Per User Pass
Microsoft Power Automate Per Flow Plan15,000 Per Flow

For Power Apps or Power Automate Flows, should the allocations above be insufficient, additional Power App/Flow capacity can be purchased in blocks of 10,000.

Special User Types and Allocations

The Common Data Service also has special system user types do not require licences: Application Users, Non-Interactive Users and Administrative Users. For these user types, a base allocation of requests is provided, depending on the subscriptions within the tenant.

Subscription TypeNo. of Requests per 24-Hour period
At least one Dynamics Enterprise Subscription100,000
At least one Dynamics Professional Subscription50,000
At least one Power Apps/Flow Subscription25,000

Frequently Asked Questions

What happens if a user/app/flow exceeds the Request allocation?

Should this happen, the tenant administrator will be notified, directing them to assign additional Power Apps and Microsoft Power Automate request capacity to that user/app/flow. Currently there are no technical restrictions in place to prevent the overuse of the allocations, but these may be introduced in the future.

Is there a transition period for existing customers to this new allocation model?

Yes. All existing customers will have a transition period until October 1, 2020 or the expiration of their current subscription term, whichever is longer.

How can we keep track of our request usage?

Usage reports and monitoring capabilities will be made available in the Power Platform Admin Centre soon.

Summary

These new allocations have been introduced to discourage excessive numbers of API requests being made that have a negative impact on Microsoft’s platform for other customers and users. However, as the allocations for each licence type are generous, they should not affect the vast majority of Dynamics 365 and Power Platform users. All the same, it is still useful to be aware of these limits when planning large-scale or frequent record processing to avoid falling foul of the new limits.

Should you have any questions on the above changes, feel free to contact one of our team to discuss them.

Related Links