# Budget every Resource Graph result page against query quota

> A paginated inventory consumes more than one query operation.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-059-budget-every-resource-graph-result-page-against-query-quota/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:34:01+00:00
- Modified: 2026-09-17T16:38:45+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 1 minutes

## What you need to know

A paginated inventory consumes more than one query operation.

## Potentially affected

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.

## Article

## 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](https://learn.microsoft.com/en-us/azure/governance/resource-graph/concepts/guidance-for-throttled-requests).

## 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](https://learn.microsoft.com/en-us/azure/governance/resource-graph/concepts/guidance-for-throttled-requests).

## Primary reference

- Name: Guidance for throttled requests in Azure Resource Graph - Azure Resource Graph | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/governance/resource-graph/concepts/guidance-for-throttled-requests
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Budget every Resource Graph result page against query quota,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-059-budget-every-resource-graph-result-page-against-query-quota/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.