Intune auditing service limits

Request type Limit per tenant for all apps Limit per app per tenant

POST, PUT, DELETE, PATCH 200 requests per 20 seconds 100 requests per 20 seconds

Any 2000 requests per 20 seconds 1000 requests per 20 seconds





does any mean GET?



ChatGPT said:

Yes, in this context, "Any" includes GET requests as well as any other HTTP method not specifically listed (like OPTIONS, HEAD, etc.).

So the limits under "Any" apply to all requests regardless of type, including GET, while the more specific rows (POST, PUT, DELETE, PATCH) define separate limits for those write/update type requests.

To sum up:



POST, PUT, DELETE, PATCH have their own limits (e.g., 200 requests per 20 seconds per tenant)

Any covers all requests, including GET, with higher limits (e.g., 2000 requests per 20 seconds per tenant)

If you want to throttle or monitor GET requests specifically, you would look at the "Any" row limits.



You said:

whats also in any



ChatGPT said:

Great question! The term "Any" in the Intune auditing service limits typically means all HTTP request types, including but not limited to:



GET (retrieve data)

POST (create data)

PUT (update data)

PATCH (partial update)

DELETE (remove data)

OPTIONS (to check what HTTP methods are supported)

HEAD (like GET but without response body)

TRACE, CONNECT (less common, but part of HTTP)

However, since the table separates POST, PUT, DELETE, PATCH with their own limits, the "Any" limits effectively cover all methods combined, including GET and the less common ones.

So:



"Any" = all request methods combined

The special row for POST, PUT, DELETE, PATCH = applies only to those request types and has its own separate limit.

This means if you exceed the specific limits for POST, PUT, DELETE, PATCH, or the overall "Any" limits (which includes GET), you may get throttled.

In practice, "Any" mostly concerns GET and other read or auxiliary requests, while write requests have stricter limits.



You said:

bro do your maths if they are in any and also seprate rule the any rule doesnt apply



ChatGPT said:

You're totally right to call that out — let me clarify and break down the logic properly:

The limits are usually enforced like this:



There’s a specific limit for POST, PUT, DELETE, PATCH requests.

There’s a broader limit for all requests combined (Any).

How does this work in practice?

If you send POST/PUT/DELETE/PATCH requests, both limits apply:

The specific limit for these methods (e.g., 200 per 20 seconds per tenant)

And the overall "Any" limit (e.g., 2000 per 20 seconds per tenant)

For other requests (like GET), only the "Any" limit applies because there’s no separate line for GET.

So the math is:

You can’t exceed 200 POST/PUT/DELETE/PATCH requests per 20 seconds (specific limit).

And all requests together (GET, POST, PUT, DELETE, PATCH, etc.) can’t exceed 2000 per 20 seconds.

In other words:

The POST/PUT/DELETE/PATCH limit is a subset inside the overall "Any" limit.

The "Any" limit covers all requests, including POST/PUT/etc.

So, POST/PUT/DELETE/PATCH requests count toward both their specific limit and the general limit.

GET and others count only toward the general "Any" limit.

Quick example:

If you do 150 POST requests and 1900 GET requests in 20 seconds:

POST requests are under the 200 limit ✅

Total requests = 150 + 1900 = 2050 > 2000 → exceeds the "Any" limit, so throttled.

If you do 250 POST requests and 1000 GET requests:

POST requests exceed the 200 limit → throttled

Also total requests 1250 < 2000 → total okay but POST limit exceeded → throttled

So yeah, the "Any" limit always applies to total traffic, including POST/PUT/DELETE/PATCH, but the specific method limits restrict those method types further.

If your request volume exceeds either, throttling happens.

Hope that clears it up! Want me to help break down the official docs or provide example scenarios?



You said:

table what has what limit pls



ChatGPT said:

Sure! Here's a clear table summarizing the Intune auditing service request limits based on your info and the explanation:

Request TypeLimit per Tenant (all apps combined)Limit per App per TenantPOST, PUT, DELETE, PATCH200 requests per 20 seconds100 requests per 20 secondsAny (all request types, including GET)2000 requests per 20 seconds1000 requests per 20 seconds



What this means:

POST, PUT, DELETE, PATCH requests have their own stricter limits (smaller numbers).

All requests combined (Any) including GET, OPTIONS, HEAD, and also POST/PUT/DELETE/PATCH count towards the bigger “Any” limit.

POST/PUT/DELETE/PATCH requests count against both their specific limits AND the overall Any limit.

GET and other request types count only towards the overall Any limit.

If you want, I can help make this into a more visual chart or explain how this affects your API calls practically!



You said:

Any (all request types, including GET) WHATS IN THERE



ChatGPT said:

Got it! You want a clear list of what’s included in “Any (all request types)” for Intune auditing service limits.



What’s included in Any (all request types)?

All HTTP methods, for example:



GET — retrieve data (most common for reading info)

POST — create data

PUT — update data (full replacement)

PATCH — update data (partial)

DELETE — delete data

OPTIONS — ask which methods are allowed

HEAD — like GET but only headers, no body

TRACE — diagnostic, rarely used

CONNECT — establish network tunnels (rare in APIs)

Important:

The table shows POST, PUT, DELETE, PATCH have a separate limit.

However, all these requests still count towards the “Any” limit, which is a global limit for all requests combined.

So “Any” = literally every request regardless of method.

Summary:

MethodCounted in specific limit?Counted in “Any” limit?GETNoYesPOSTYesYesPUTYesYesPATCHYesYesDELETEYesYesOPTIONSNoYesHEADNoYesTRACENoYesCONNECTNoYes



So “Any” means literally all requests your tenant sends, no matter the HTTP method.

If you want, I can help you design a usage strategy based on these limits!



You said:

HOW CAN IT BE IN ANY LIMIT AND SPEFICI



ChatGPT said:

I see where the confusion is—let me explain it clearly:

How can requests be in both the specific limit and the "Any" limit?

Think of the limits like two layers of rules working together:



Specific Method Limit (POST, PUT, DELETE, PATCH):



This is a stricter limit just for those specific write/update requests. You cannot send more than this number of those requests in a time window.

Overall "Any" Limit:



This is a broader limit that counts all requests combined, including GET, POST, PUT, PATCH, DELETE, OPTIONS, etc. It caps the total traffic to prevent overload.

Why both?

The specific limit ensures you don’t overwhelm the system with heavy write/change operations.

The "Any" limit prevents too much total traffic regardless of method, protecting the system’s overall performance.

Visualization with a bucket analogy:

Imagine two buckets collecting water drops:

Bucket A: Only drops labeled POST/PUT/DELETE/PATCH go here; max 200 drops per 20 sec.

Bucket B: All drops (including those in Bucket A plus GET, OPTIONS, etc.) go here; max 2000 drops per 20 sec.

If you pour 150 drops of POST and 1900 drops of GET:



Bucket A: 150 drops (under 200 limit) → OK

Bucket B: 150 + 1900 = 2050 drops (over 2000 limit) → Throttled

If you pour 250 drops POST and 500 drops GET:



Bucket A: 250 drops (over 200 limit) → Throttled immediately

Bucket B: 250 + 500 = 750 drops (under 2000 limit) → OK overall, but still throttled because of Bucket A

TL;DR:

POST/PUT/DELETE/PATCH requests count twice: once in their own stricter limit, and once in the overall traffic limit ("Any").

GET and other request types only count in the overall "Any" limit.

If you want, I can help you build a monitoring or throttling strategy that respects both these limits. Does that help?



You said:

how does it know in which limit post is????



ChatGPT said:

Great question! Here's how the system knows which limit to apply to a POST (or any) request:

How does Intune (or any API service) distinguish request types and apply limits?

HTTP Method in the Request:



Every HTTP request includes a method in its header—such as GET, POST, PUT, DELETE, PATCH, etc.

The API Gateway / Throttling Layer:



When your request reaches the Intune service endpoint, the API gateway or throttling system inspects the HTTP method.

Apply the Rules Based on Method:

If the method is POST, PUT, DELETE, or PATCH, the system tracks that request against both:

The specific limit for that method group

The overall “Any” limit for total requests

If the method is GET or others (OPTIONS, HEAD), the system tracks only against the overall “Any” limit.

Technically:

Each request hits the server with a method, e.g.

POST /api/audit HTTP/1.1

The throttling component counts this request in two counters:

One counter for POST/PUT/DELETE/PATCH requests (incremented by 1)

One counter for all requests (incremented by 1)

If either counter hits the limit in the time window, your request will be throttled.

Summary:

It “knows” because the HTTP method is explicit in the request.

It maintains separate counters for:

Specific method group (POST, PUT, DELETE, PATCH)

All requests combined (Any)

Let me know if you want a simplified diagram or code example to show how this counting works!





help me... it doesnt understand my issue... can you help me?