# Finish Azure Table queries by following continuation tokens

> Test completion against continuation state, not merely the number of entities returned in one response.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:31:35+00:00
- Modified: 2026-09-10T00:32:00+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

Test completion against continuation state, not merely the number of entities returned in one response.

## Potentially affected

Applications retrieving multiple entities from Azure Table Storage.

## DSE recommendation

Make continuation handling an explicit acceptance test for every multi-entity Table Storage reader.

## Article

## 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](https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns).

## 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](https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns). Source retrieved September 9, 2026.

## Primary reference

- Name: Azure storage table design patterns | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Finish Azure Table queries by following continuation tokens,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/
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.