{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/",
        "slug": "dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/"
        },
        "title": "Finish Azure Table queries by following continuation tokens",
        "summary": "Test completion against continuation state, not merely the number of entities returned in one response.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-10T00:31:35+00:00",
        "modified_at": "2026-09-10T00:32:00+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 1,
        "word_count": 218,
        "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.",
        "primary_source": {
            "name": "Azure storage table design patterns | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>Table Storage can return a continuation token when a query exceeds a response&#8217;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.</p>\n<p>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. <a href=\"https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends documenting the reader&#8217;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.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Azure storage table design patterns</a>. Source retrieved September 9, 2026.</p>",
        "content_text": "Source facts\nTable 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.\nMicrosoft 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.\nApplicability\nReview 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.\nDSE recommendation\nDSE 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.\nVerification\nUse 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.\nOfficial references\nMicrosoft Learn: Azure storage table design patterns. Source retrieved September 9, 2026.",
        "content_markdown": "## Source facts\n\nTable 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.\n\nMicrosoft 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).\n\n## Applicability\n\nReview 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nUse 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.\n\n## Official references\n\n[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."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Finish Azure Table queries by following continuation tokens",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/",
                "headline": "Finish Azure Table queries by following continuation tokens",
                "description": "Test completion against continuation state, not merely the number of entities returned in one response.",
                "abstract": "Test completion against continuation state, not merely the number of entities returned in one response.",
                "articleBody": "Source facts\nTable 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.\nMicrosoft 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.\nApplicability\nReview 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.\nDSE recommendation\nDSE 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.\nVerification\nUse 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.\nOfficial references\nMicrosoft Learn: Azure storage table design patterns. Source retrieved September 9, 2026.",
                "datePublished": "2026-09-10T00:31:35+00:00",
                "dateModified": "2026-09-10T00:32:00+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-021-finish-azure-table-queries-by-following-continuation-tokens/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Finish Azure Table queries by following continuation tokens"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 218,
                "timeRequired": "PT1M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Azure storage table design patterns | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns"
                }
            }
        ]
    }
}