Finish Azure Table queries by following continuation tokens

Source facts

Table Storage can return a continuation token when a query exceeds a response’s entity or execution-time limit, or crosses a partition boundary. The token lets the caller request the next segment rather than treating the current response as the whole result.

Microsoft also notes that a segment can contain fewer entities than requested while still supplying a continuation token. A short segment therefore does not by itself establish query completion. Microsoft Learn.

Applicability

Review readers that populate inventories, exports, or reports from multiple entities. Identify whether the selected client library follows continuation automatically or whether application code owns that loop; confirm behavior in the actual implementation.

DSE recommendation

DSE recommends documenting the reader’s stopping rule and preserving a stable query definition throughout retrieval. Separate a deliberately bounded business result from accidental truncation. Define how an interrupted export should resume or restart, and make an incomplete run visibly different from a completed empty or short result.

Verification

Use a known test dataset spanning several segments and partitions. Compare the completed output with expected entities, then test a response smaller than the requested page size that still carries a token. Check interruption handling and the final completion marker. Keep the dataset definition and run evidence together.

Official references

Microsoft Learn: Azure storage table design patterns. Source retrieved September 9, 2026.