Our Blog

where we write about the things we love

01

Oct

The new Power Platform API limits – a massive over-reaction?

In the wake of the controversial new Microsoft Power Platform request limits and allocations to take effect from October 2019 there has been a lot of speculation as to the impact this will have on our customers and the projects we are working on. The news hasn’t been greeted favourably. But I suspect, that may be an over-reaction.

The new Power Platform API limits

Were we spoilt for too long?

Like spoilt only children, to date we’ve had very little throttling with regards to API usage. In the past we were limited to 4000 API requests, per user, per organisation instance, over a five-minute sliding window.

Theoretically, that meant we could make up to 1,152,000 API requests in 24 hours. That is a lot for the average user. But this also means that it could be abused.

The new rules

So, what are Microsoft’s new rules? There will be a limit to the number of API requests a user can make on the Power Platform in a 24-hour period. This limit will be based on the specific licence assigned to the user.

User licenses

Number of API requests / 24 hours

Dynamics 365 Enterprise applications

20,000

Dynamics 365 Professional

10,000

Dynamics 365 Team Member

5,000

PowerApps per user plan

5,000

Microsoft Flow per user plan

5,000

Office licenses (that include PowerApps/Microsoft Flow)

2,000

It’s worth noting that if a user has multiple plans assigned from different product lines, then their API limit will be the sum of the requests allocated to each plan.

But if a user has multiple licences allocated within the same product line, then their API limit will be what is allocated to the base license.

In Dynamics blogger Scott Durrow’s new post regarding the subject, he does a little experiment and determines that an average user will consume ~10 API requests when opening a Dynamics 365 Unified Client Contact form (assuming no customisations have been made that make additional API calls).

If the user has a Dynamics 365 Professional license, giving him 10,000 API requests a day, they would have to open ~2 contact records every minute, for eight hours straight before they would hit their limit. This is more than enough for an average user.

New ways to play

The new API limits should not have a large impact on the average user. However, we do need to be aware of the new limits when developing Model Driven Apps and try to keep API requests to a minimum.

But shouldn’t we have been doing that all along?

There will most definitely be scenarios where a user will exceed their API limit. A capacity add-on will be available to add an additional 10,000 requests per 24 hours to any user.

Is it just a cash grab by Redmond? Maybe, but Microsoft’s cloud offerings are maturing and LDD (License Driven Development) is becoming even more important as the Power Platform evolves.

This will inevitably influence the pricing model. We need to make sure that we mature along with it, designing and building solutions that bridge the capability of the platform and our customer’s needs.

Yes, this will prove to be a challenge in certain circumstances. But we enjoy this line of work and we like solving new types of problems. Don’t forget that!

Sharing our toys

The Power Platform is a shared platform, and it was only a matter of time before Microsoft introduced some new rules to play by to ensure quality of service for everyone on the platform.

We collectively use the Power Platform, and having it guarded against malicious and noisy behaviour is probably not a bad thing.

Posted by: Ryan James, Senior Developer | 01 October 2019

Tags: Dynamics 365, Microsoft Power Platform, API, Application Programming Interface


Blog archive

Stay up to date with all insights from the Intergen blog