<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure-Service-Bus on PowerShell.org - Welcome Automaters!</title><link>https://powershell.org/tags/azure-service-bus/</link><description>Recent content in Azure-Service-Bus on PowerShell.org - Welcome Automaters!</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://powershell.org/tags/azure-service-bus/index.xml" rel="self" type="application/rss+xml"/><item><title>Reordering an Unordered Azure Service Bus Stream with PowerShell</title><link>https://powershell.org/articles/2026/09/reordering-an-unordered-azure-service-bus-stream-with-powershell/</link><pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate><guid>https://powershell.org/articles/2026/09/reordering-an-unordered-azure-service-bus-stream-with-powershell/</guid><description>&lt;p&gt;Azure Service Bus sessions are the natural choice when a consumer must process related messages in order. But what if the messages already arrive through a non-session subscription, while a downstream consumer still expects an ordered, session-aware stream?&lt;/p&gt;
&lt;p&gt;This article explores one possible bridge between those two models. The idea is to use message deferral as a broker-backed buffer and session state as a small index that remembers which deferred messages can be released later.&lt;/p&gt;</description></item></channel></rss>