web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / New March 2019 CRM API...
Microsoft Dynamics CRM (Archived)

New March 2019 CRM API Rate Limit 6000 every 300s (down from 60,000)

(5) ShareShare
ReportReport
Posted on by Tristan Reeves 10

Has anyone else noticed this silent change?

https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/api-limits

It is causing our production website that uses CRM as a backend all sorts of issues, as we now regularly get 100s of errors stating:

"Number of requests exceeded the limit of 6000 over time window of 300 seconds."

Note we regularly have 100s of users sending requests to and from CRM every minute, surely this is not beyond the scope of the product?

We have had a case open with Microsoft for weeks, and the tech guys seem perplexed that our application would ever exceed this number, and refuse to increase the limit nor provide a solution. Does Microsoft seriously think 6000 requests every 5 minutes is excessive? They clearly aren't intending CRM to have a market for enterprise scalable applications.

If this is the new hard limit we are going to have to migrate away from Dynamics CRM as a backend for our website which will be a nightmare!

*This post is locked for comments

I have the same question (0)
  • JorgenAmrudHagen Profile Picture
    JorgenAmrudHagen 30 on at

    Hi Tristan.

    We have also noticed and felt this change.

    I think it's outrageous that Microsoft can do such a massive change without any communication.

    We haven't yet try to get Microsoft to increase the limit, but as I understand from your attempts, that will be a futile exercise.

    We are using the "x-ms-ratelimit-*" headers to read how many requests we have left before reaching the threshold, but for a portal solution with Dynamics CRM as backend, that do not help much.

  • Tom Winton Profile Picture
    Tom Winton 37 on at

    Yup, Dynamics as backend for website is also killing us now.

  • Aric Levin - MVP Profile Picture
    Aric Levin - MVP 30,190 Moderator on at

    Hi,

    Yes. This was announced for the April release in some smaller forums.

    Per Microsoft the 60K number was too high and customers were not reaching that number. The actual number is not 6000, but it is 4000/user/5min. I have seen some other complaints about it, and maybe this will revert back, be a setting or a package that can be added to a subscription.

    I am not sure if there is something that you can do at this point. Keep the ticket open, and ask to escalate. Possibly something that they can adjust in the backend or Azure for your environment.

  • JorgenAmrudHagen Profile Picture
    JorgenAmrudHagen 30 on at

    Hi Aric.

    "Announced in some smaller forums" is not good practice for such a big change in functionality.

    Saying that 60k was to high and not reached, is also false, as we among others reached this limit regularly. With this new limitation our customers starts questioning Dynamics 365 as backend in larger implementations.

    I hope this isn't the first step down a path were we have to buy additional "bandwidth" in packages as you describe.

  • Aric Levin - MVP Profile Picture
    Aric Levin - MVP 30,190 Moderator on at

    Sorry, just the messenger. Don't have any details regarding the next steps on this...

  • Tristan Reeves Profile Picture
    Tristan Reeves 10 on at

    Microsoft did not provide a work around that worked, so we have cut down on our API calls for now.

    One thing we did not try but that could work was doing a load distribution of the requests between multiple application users (since you can create as many as you want), as supposedly this is a per user limit. Of course if this could be mitigated so easily by using multiple users it would make the rate limiting pointless anyway, but it is Microsoft we are dealing with so anything is possible.

  • JorgenAmrudHagen Profile Picture
    JorgenAmrudHagen 30 on at

    We've tried to distribute the load with multiple users, and that helps some, but its far from perfect.

    We still have the max concurrent requests limit, which I think is across all users. We hit that a lot, and that is a lot harder to throttle.

    The last think for us to try is batch calls, but from the documentation I'm not sure if the max 2 concurrent ExecuteMultipleRequest also applies for batch calls on the API

    We also tried Microsoft for help, but the reply was that they could not understand why this was a problem, and that we (and one other customer) was the only ones in the entire world having this problem.

    I can not understand how Microsoft can market Dynamics 365 as a "digitalization platform" for  IoT among other things, with these limits.

  • Tristan Reeves Profile Picture
    Tristan Reeves 10 on at

    Yeah i was told very similar, they must be reading from a script. There's at least 3 of us in this thread with the issue, which means Microsoft are either liars or incompetent. Not that this is likely news to anyone. I suppose they anticipated a small percentage of kickback and judged it acceptable. A colleague of mine has worked at various large organisations running CRM (such as Rolls Royce), and you can guarantee they are not suffering from this issue, but they also have far more users.

    Absent clarity from Microsoft which I'm sure we'll never get, I imagine for small sized CRM implementations with lower users this limit is here to stay.

  • Balpreetm Profile Picture
    Balpreetm 20 on at

    LATE AUG 2019 - CRM API LIMITS

    New 24 Hour Limit below

    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 

    Users who are running apps and flows without a user license through the PowerApps per app plan or the Microsoft Flow per flow plan are granted the following per-user API request entitlement.

    Add-on  Number of API requests
    PowerApps per app plan  1,000 per user pass
    Microsoft Flow per flow plan 15,000 per flow

    Here comes the bottom line/curve ball bit

    PowerApps and Microsoft Flow capacity add-on allows customers to purchase additional requests

    https://docs.microsoft.com/da-dk/power-platform/admin/api-request-limits-allocations

  • Tom Winton Profile Picture
    Tom Winton 37 on at

    This does not solve the problem (and actually adds more questions)

    The reason it doesn't solve the problem is you will note in the bottom header "Service protection limits" currently applicable it states that all of the issues raised here still apply  as it links to: docs.microsoft.com/.../api-limits

    So essentially Microsoft have created a means of gaining additional revenue from heavy using customers but those heavy using customers (most people on this thread) will still be impacted by the same limits it seems to me?

    In addition, the new charges are for all CRUD operations - it is quite vague but could mean a workflow that reads 3 records and updates one would have created 5 "requests" just in that operation?

    I actually think that this change from Microsoft is sensible but it needs to be released hand in hand with removing the API throttling. In addition, it also needs to provide customers with a means to report on the source of all of the operations that have occured. Organisation Insights is no where near detailed enough.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans