Re: Power Apps License Change - API limits

DanW · ‎09-02-2019

I did not see anything about this in the blog post on the license changes, but the announcement just hit and it has new API limits in it. In March, Microsoft went from an API limit of 60k to 4000 calls every 5 minutes per user. With this new announcement, if you are using the Per App plan, it is limited to 1,000 calls per user, per 24 hours. So a potential, 1.1m calls per day down to 1k per day. Am I reading this right? This is a massive reduction and will destroy an app I have spent the better part of a year building and getting our organization to adopt. I am already going to have to ask my company to spend more just to support the new licensing model.

Reference https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations

iAm_ManCat · ‎09-03-2019

Hi,

It looks like it's advising that the total calls are cumulative per license, so if you have a Per App and they already have an Office365 license, then it will be 2000 + 1000.

Is your App making the calls or the Flow behind it? if it's the Flow then you could get a Per Flow license that would give you 15k +2k (for Office365 license), so 17k calls/user/day. This works out to one every 5.08 seconds in 24hours, or 1 every 1.69s in an 8Hour workday, which may be a throttling limit if your App runs for that entire 8 hour period..

Cheers,

ManCat

@iAm_ManCat

My blog

Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!

Thanks!
You and everyone else in the community make it the awesome and welcoming place it is, keep your questions coming and make sure to 'like' anything that makes you 'Appy
Sancho Harker, MVP

DanW · ‎09-03-2019

The ones I am referring to are not being called from flow, they are being called from JS web resources inside a model driven app. I understand the need for rate limiting. But going from 4k every 5 minutes, to 1k every 24 hours isn't rate limiting.

iAm_ManCat · ‎09-04-2019

Yeah, I do agree that it's a biit of an 'arrow to the knee' - I was only trying to see if there was any way we could come up with a workaround 🙂

@iAm_ManCat

My blog

Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!

Thanks!
You and everyone else in the community make it the awesome and welcoming place it is, keep your questions coming and make sure to 'like' anything that makes you 'Appy
Sancho Harker, MVP

cepjc · ‎11-11-2020

I am considering a model-driven app + CDS solution, but this API limit is really a killer (https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations ). This has been a massive reduction of the API request limits by Microsoft. (by the way, the allocations you get do not even roll-over day-to-day or month-to-month; check the Q&A in the link above... 🤐)

We are currently testing a Proof-of-Concept and I already surpass the 5k daily API calls, and trust me; I don't have much of a complex/fancy solution. As feedback provider to my organization who is evaluating to use (or not) PowerApps, probably I will highlight this as a negative point.

I really hope Microsoft listens to us -customers-, reconsider and step-up this limitation! I am not sure how many members this community has, but this is a topic that we all should be aware off. I am surprised there is not much discussion around it.

For those of you with significant experience in the platform: Is there are recommendation on best practices on how to keep the API calls to the minimum in a model-driven app?