What you’re seeing
- Errors returning HTTP status 429 or "Too Many Requests" partway through a tenant-wide script.
- A report that finishes in seconds for a handful of users takes hours, or never completes, across the whole organization.
- Responses include a Retry-After value telling the script to wait before trying again.
- Output files are missing users or mailboxes because some requests failed silently.
- Other admin tools or integrations in the same tenant also slow down while the script is running.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- Microsoft Graph enforces per-app and per-tenant request limits, and the script sends calls faster than those limits allow.
- The script makes one request per user or per item instead of using batching, filtering or paging efficiently.
- Retry logic ignores the Retry-After guidance and retries immediately, which prolongs the throttling.
- Several scripts or third-party tools share the same app registration and compete for the same request budget.
- Some Graph endpoints, such as those for mail, reports or audit logs, have tighter limits than the general API.
Why it matters
Graph throttling usually hits the jobs that matter most at scale: license audits, security reviews, offboarding sweeps and compliance exports. A script that quietly skips throttled users produces reports that look complete but are not, which can lead to missed inactive accounts, wrong license counts or gaps in an audit trail. Repeated heavy load can also slow other integrations in the tenant, affecting backup tools or sync services that your business depends on.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Is Microsoft blocking our account?
No. Throttling is a normal, temporary limit that protects the service. Requests start succeeding again once the volume drops, but the script needs to respect the limits to finish reliably.
Can we trust the reports this script already produced?
Not fully if throttling errors occurred during the run. An engineer can check for gaps and confirm whether any users or items were skipped.
Does buying more licenses raise the limit?
Generally not in a way that solves this. The lasting answer is a more efficient script, which an engineer can usually rework remotely.