Request - Insight in number and type of API calls

[Marijn]

We have on-premise backup of M365 and we're currently having an issue where we are being throttled by Microsoft. ( Veeam case: 07878518 )

It would really help us if we were able to have an insight from Veeam into the amount of api-calls being made and of which type. so how many REST and how many Graph calls for job x, overal, etc.
This would also help us determine if it is even Veeam/VBO that is using up most api-resources or if maybe someone else from within our organisation is doing api-calls.

Even better would be if we could limit them for the overal environment so that we could do a QoS on our sharepoint environment. I want to prevent thottling other users by doing too many API-calls.
So just like the backup window but then for API-calls.
i.e. Say we can do 5000 api resource per minute for our license-volume. I'd like to be able to use 4800 api resource by night and only 2000 api resources during business hours.

Also i'm asuming the development team is working very hard to move every api call available over to graph API if possible as those types of calls are "charged" less api-resources compared to an equivalent rest api-call.

[DaStivi]

This issue, "application throttling" is since one of the last 8.1 updates and also in the 8.2 update...

Had a customer that had a case and got some hotfix for it but for my service provider environment it didn't helped ...

Good you opened a case on this issue! The veeam team needs to made aware of sich issue obviously something is odd there.. i do have to open a case on this topic too, but all the case handling is very time consuming

[Marijn]

Well, it's a good thing Veeam made a private fix allready. That usually indicates there's improvements in the pipeline for us all.

Secondly i've been in a quite a few calls with Microsoft about this as I would like them to tell me how I am using these api-resources. Unsurpisingly, they're unable/unwilling to tell me. I have the feeling that they've simply increased the api-resource cost for REST calls and as VBO is still using these quite a lot you simply run out of api-resources a lot sooner.
Veeam will have to re-write the code to make use of the Graph api calls wherever they can to get this working again.

[Polina]

@Marijn

I'm a bit surprised that Microsoft asks you for the requests count, while to the best of knowledge they're perfectly capable to identify all requests coming from Veeam or from a specific application by its ID.

The issue with throttling impact is indeed getting worse from what I'm seeing the last months. There're a few changes planned on our side that should improve the situation; at the same time our conversations with Microsoft on how to achieve better efficientcy within the current lanscape are ongoing.

Thanks!