Budget every Resource Graph result page against query quota

Source facts

Microsoft directs Resource Graph SDK callers to pass the previous response’s skip token to the next paginated request and combine the pages afterward. Each of those paginated queries consumes query quota. A logical inventory operation can therefore require several quota-consuming calls. Microsoft Learn.

Applicability

Use this review for an automated Resource Graph inventory that already handles continuation tokens. Identify its expected page count, schedule and concurrent jobs. Keep quota budgeting separate from the query-shape question of whether a continuation token is available at all.

DSE recommendation

DSE recommends measuring requests per complete inventory, including continuation calls and any retries, before setting the schedule. Have the automation owner coordinate competing runs and use the service’s current throttling guidance. Retain partial results as incomplete until every expected page has been processed, and define how an interrupted run is reported.

Verification

Run a bounded inventory large enough to require multiple pages. Record each request, returned continuation token and final completion condition without exposing sensitive payloads. Confirm that the assembled result contains the intended scope and that interrupted retrieval does not appear complete. Compare the measured request count with the job’s quota assumptions before increasing frequency or concurrency.

Official references

Microsoft Learn: Guidance for throttled requests in Azure Resource Graph.