{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/", "slug": "dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility", "url": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/" }, "title": "Use Queue peek operations for observation without changing message visibility", "summary": "DSE recommends classifying the operation before running the queue client method.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "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-17T16:33:32+00:00", "modified_at": "2026-09-17T16:38:46+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 206, "potentially_affected": "This guide applies to a PowerShell-based Azure Queue Storage investigation where the operator needs to decide whether to observe a message or take part in its processing.", "dse_recommendation": "DSE recommends classifying the operation before running the queue client method.", "primary_source": { "name": "How to use Azure Queue Storage from PowerShell - Azure Storage | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/queues/storage-powershell-how-to-use-queues", "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": "

Source facts

\n

Microsoft explains that Peek previews messages without dequeuing them or increasing DequeueCount. Receive temporarily hides a message from other processes for the visibility timeout. Permanent deletion requires both the message identifier and its pop receipt. Microsoft Learn

\n

Applicability

\n

This guide applies to a PowerShell-based Azure Queue Storage investigation where the operator needs to decide whether to observe a message or take part in its processing.

\n

DSE recommendation

\n

DSE recommends classifying the operation before running the queue client method. For inspection, choose the documented peek path and restrict the displayed content to what the investigation needs. For a processing test, use a designated test message and document the visibility interval and deletion decision. Keep routine troubleshooting separate from message consumption so the investigator understands which actions can affect the worker’s view of the queue.

\n

Verification

\n

Record which method was called and inspect the resulting message metadata. During a controlled processing test, compare visibility and deletion behavior with the intended sequence. Do not describe a received message as permanently removed unless the delete operation succeeded. Preserve unexpected results with the message identifier while avoiding unnecessary disclosure of message contents.

\n

Official references

\n", "content_text": "Source facts\nMicrosoft explains that Peek previews messages without dequeuing them or increasing DequeueCount. Receive temporarily hides a message from other processes for the visibility timeout. Permanent deletion requires both the message identifier and its pop receipt. Microsoft Learn\nApplicability\nThis guide applies to a PowerShell-based Azure Queue Storage investigation where the operator needs to decide whether to observe a message or take part in its processing.\nDSE recommendation\nDSE recommends classifying the operation before running the queue client method. For inspection, choose the documented peek path and restrict the displayed content to what the investigation needs. For a processing test, use a designated test message and document the visibility interval and deletion decision. Keep routine troubleshooting separate from message consumption so the investigator understands which actions can affect the worker’s view of the queue.\nVerification\nRecord which method was called and inspect the resulting message metadata. During a controlled processing test, compare visibility and deletion behavior with the intended sequence. Do not describe a received message as permanently removed unless the delete operation succeeded. Preserve unexpected results with the message identifier while avoiding unnecessary disclosure of message contents.\nOfficial references\n\nMicrosoft: How to use Azure Queue Storage from PowerShell – Azure Storage | Microsoft Learn", "content_markdown": "## Source facts\n\nMicrosoft explains that Peek previews messages without dequeuing them or increasing DequeueCount. Receive temporarily hides a message from other processes for the visibility timeout. Permanent deletion requires both the message identifier and its pop receipt. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/queues/storage-powershell-how-to-use-queues)\n\n## Applicability\n\nThis guide applies to a PowerShell-based Azure Queue Storage investigation where the operator needs to decide whether to observe a message or take part in its processing.\n\n## DSE recommendation\n\nDSE recommends classifying the operation before running the queue client method. For inspection, choose the documented peek path and restrict the displayed content to what the investigation needs. For a processing test, use a designated test message and document the visibility interval and deletion decision. Keep routine troubleshooting separate from message consumption so the investigator understands which actions can affect the worker’s view of the queue.\n\n## Verification\n\nRecord which method was called and inspect the resulting message metadata. During a controlled processing test, compare visibility and deletion behavior with the intended sequence. Do not describe a received message as permanently removed unless the delete operation succeeded. Preserve unexpected results with the message identifier while avoiding unnecessary disclosure of message contents.\n\n## Official references\n\n- [Microsoft: How to use Azure Queue Storage from PowerShell – Azure Storage | Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/queues/storage-powershell-how-to-use-queues)" }, "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-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/", "url": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Use Queue peek operations for observation without changing message visibility", "item": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/", "url": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/", "headline": "Use Queue peek operations for observation without changing message visibility", "description": "DSE recommends classifying the operation before running the queue client method.", "abstract": "DSE recommends classifying the operation before running the queue client method.", "articleBody": "Source facts\nMicrosoft explains that Peek previews messages without dequeuing them or increasing DequeueCount. Receive temporarily hides a message from other processes for the visibility timeout. Permanent deletion requires both the message identifier and its pop receipt. Microsoft Learn\nApplicability\nThis guide applies to a PowerShell-based Azure Queue Storage investigation where the operator needs to decide whether to observe a message or take part in its processing.\nDSE recommendation\nDSE recommends classifying the operation before running the queue client method. For inspection, choose the documented peek path and restrict the displayed content to what the investigation needs. For a processing test, use a designated test message and document the visibility interval and deletion decision. Keep routine troubleshooting separate from message consumption so the investigator understands which actions can affect the worker’s view of the queue.\nVerification\nRecord which method was called and inspect the resulting message metadata. During a controlled processing test, compare visibility and deletion behavior with the intended sequence. Do not describe a received message as permanently removed unless the delete operation succeeded. Preserve unexpected results with the message identifier while avoiding unnecessary disclosure of message contents.\nOfficial references\n\nMicrosoft: How to use Azure Queue Storage from PowerShell – Azure Storage | Microsoft Learn", "datePublished": "2026-09-17T16:33:32+00:00", "dateModified": "2026-09-17T16:38:46+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/" }, "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-20260917-088-use-queue-peek-operations-for-observation-without-changing-message-visibility/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Use Queue peek operations for observation without changing message visibility" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 206, "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": "How to use Azure Queue Storage from PowerShell - Azure Storage | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/queues/storage-powershell-how-to-use-queues" } } ] } }