In in my previous post, Overreacting to the new Power Platform API limits, I argued that the new Power Platform API limits are justified to maintain quality of service for all of us. My argument still stands. Microsoft have updated their Requests limits and allocations documentation to explain how the new licensing and API limit changes affect non-licensed users and it’s looking positive.
How do the API limits affect non-licensed users
Each Common Data Service tenant will have a base API request capacity that can only be consumed by its non-licensed users. These non-licensed include non-interaction users, application users and administrative users. Essentially there will be a pool of API requests that all non-licensed users in a tenant will collectively consume.
The base request capacity is based on the type of subscription:
|Subscription||API requests per 24 hours|
|Dynamics 365 enterprise||100,000|
|Dynamics 365 professional||50,000|
Points worth noting
If a tenant has multiple subscriptions, their base API request capacity will be the max of two subscriptions. I’m assuming that the two subscriptions in question will be the two with the highest API request capacity.
The base API request capacity can be increased by purchasing PowerApps and Microsoft Flow capacity add-ons.
If the limits are occasionally and reasonably exceeded, the users will not be blocked. However, administrators will receive notifications about overages.
The base API request capacity can only be consumed by non-licensed users.
The future is not as bleak as it seemed a few weeks ago. The API request limits for non-interactive users are generous and should be enough for integration and 3rd party access to Dynamics 365 and Common Data Service.
Microsoft could have made this a little clearer when they first announced the new API limits to stave off some of the hysteria.