Stratara.Outbox.AzureServiceBus
4.6.0
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Outbox.AzureServiceBus --version 4.6.0
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 4.6.0
<PackageReference Include="Stratara.Outbox.AzureServiceBus" Version="4.6.0" />
<PackageVersion Include="Stratara.Outbox.AzureServiceBus" Version="4.6.0" />
<PackageReference Include="Stratara.Outbox.AzureServiceBus" />
paket add Stratara.Outbox.AzureServiceBus --version 4.6.0
#r "nuget: Stratara.Outbox.AzureServiceBus, 4.6.0"
#:package Stratara.Outbox.AzureServiceBus@4.6.0
#addin nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.6.0
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.6.0
Stratara.Outbox.AzureServiceBus
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Azure Service Bus implementation of Stratara.Abstractions.Messaging.IMessageBus. Publishes JSON-serialized messages to topics and exposes a subscription helper that wires up a Service Bus processor with per-message exception classification:
- success →
CompleteMessageAsync ConcurrencyException→AbandonMessageAsyncuntilMessageRetry:MaxConflictRequeuesredeliveries (default 100) have not resolved it, thenDeadLetterMessageAsyncwith reasonconflict- any other exception →
AbandonMessageAsyncuntilMessageRetry:MaxDeliveryAttemptsdeliveries (default 3) have failed, thenDeadLetterMessageAsyncwith reasonfailureand the exception in the description
The subscription's own MaxDeliveryCount must leave room for the bounds; a subscription created with Service Bus defaults allows 10 deliveries. Where the host can read the subscription, the bus lowers the bounds for it to fit and logs 108_111.
System-level errors (connection drops, auth failures) arrive via ProcessErrorAsync and are logged; the Service Bus client owns the reconnect / retry policy for those.
A subscription that stops closes its processor, which takes no further message and waits for its running handler — as long as the host's shutdown timeout allows while the application stops, twenty seconds otherwise; the host waits for that before it counts as stopped. A handler that gives up because the subscription stops has its message abandoned rather than dead-lettered by the framework; the broker counts that delivery like any other. A handler's outcome is settled whatever the subscription's own cancellation says, and a handler that failed because its save committed but could not publish has its message completed, not delivered again.
Install
dotnet add package Stratara.Outbox.AzureServiceBus
Register the bus in your DI composition — one call wires the ServiceBusClient, the envelope
options and the IMessageBus implementation:
// Connection string:
builder.Services.AddAzureServiceBus(builder.Configuration.GetConnectionString("ServiceBus")!);
// Or, preferred in Azure — managed identity, no secret in configuration:
builder.Services.AddAzureServiceBusWithManagedIdentity("my-namespace.servicebus.windows.net");
The AzureServiceBusBus implementation is internal; register it through these extensions rather
than by naming the type.
The explicitly-chosen transport wins.
AddAzureServiceBusreplaces theIMessageBusregistration, so it takes effect even when the RabbitMQ umbrella (builder.AddMessaging(), which the worker composites call) already claimed the slot. Still use one transport per host — calling both is a configuration smell — but an explicitAddAzureServiceBuswill no longer be a silent no-op behind a composite.
Notes
Pre-3.0 this implementation lived inside Stratara.Outbox.RabbitMQ. As of 3.0 the two transports are separate packages so a consumer who only wants RabbitMQ does not drag the Azure Service Bus SDK into the dependency tree (and vice versa).
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Azure.Identity (>= 1.21.0)
- Azure.Messaging.ServiceBus (>= 7.21.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Options (>= 10.0.13)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.13)
- Stratara.Abstractions (>= 4.6.0)
- Stratara.Shared (>= 4.6.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 103 | 11/6/2026 |
| 4.7.1 | 97 | 11/5/2026 |
| 4.7.0 | 106 | 10/30/2026 |
| 4.6.1 | 105 | 10/29/2026 |
| 4.6.0 | 102 | 10/28/2026 |
| 4.5.0 | 107 | 10/28/2026 |
| 4.4.10 | 103 | 10/26/2026 |
| 4.4.9 | 98 | 10/26/2026 |
| 4.4.8 | 100 | 10/24/2026 |
| 4.4.7 | 102 | 10/23/2026 |
| 4.4.6 | 97 | 10/22/2026 |
| 4.4.5 | 108 | 10/14/2026 |
| 4.4.4 | 107 | 10/10/2026 |
| 4.4.3 | 111 | 10/10/2026 |
| 4.4.2 | 113 | 10/2/2026 |
| 4.4.1 | 107 | 9/29/2026 |
| 4.4.0 | 109 | 9/27/2026 |
| 4.3.1 | 116 | 9/25/2026 |
| 4.3.0 | 113 | 9/23/2026 |
| 4.2.0 | 123 | 9/18/2026 |
An erasure shreds every key that names the subject, and nothing stopped the next encryption for that subject
from creating a new one: a key store asked for a scope it does not hold creates a first version. A job, a request
in flight or a second process that encrypted for an erased subject afterwards got a fresh key, and what it wrote
stayed readable for good. The key store now records an erased subject and refuses to create a key for it again.
### Added
- **`IKeyStore.MarkSubjectErasedAsync(KeySubject)`** records that a tenant or user has been erased. It has a
default implementation that throws `NotSupportedException`, so an existing key store still compiles.
- **`KeySubject`** names the tenant or user, and `KeySubject.Covers(KeyScope)` states which keys belong to its
erasure: for a tenant, a key of any level that names it; for a user, a user-level key that names it.
- **`KeyScopeErasedException`** (an `InvalidOperationException`) is what a key store throws for such a scope. It
carries the refused `Scope`.
### Changed
- **An encryption for an erased subject fails.** After a subject's erasure, `GetOrCreateCurrentKeyAsync` and
`RotateAsync` throw `KeyScopeErasedException` for every scope the subject covers, whether or not it ever held a
key, and create nothing. The blob encryptor, the encrypting settings store and the field-encrypting serializer
pass it through. Code that erased a subject and then wrote encrypted data for it again now sees the exception;
the mark is permanent and cannot be lifted. Revoking every version of a scope is not an erasure and marks nothing.
- **`ISubjectEraser` marks the subject before it sweeps any plane**, so an encryption racing the erasure
either creates its key first, and that key is shredded with the rest, or is refused. A key store that cannot mark
a subject leaves the erasure as before and logs `SubjectNotMarkable` (112009).
- **The file-backed key store writes format version 2**, which holds the marks, and refuses to open a file in a
newer format than it knows. `InMemoryKeyStore` refuses an erased subject as the file store does; `DummyKeyStore`
refuses to mark one, as it refuses every erasure operation.
**Upgrading:**
- **Upgrade every process that shares a key store file in one step.** A process on an earlier release reads a
version-2 file, ignores the marks, creates keys for an erased subject and drops the marks the next time it writes
the file. A version-1 file needs no migration. Rolling back is possible but loses the marks on the first write.
- **Map `KeyScopeErasedException` to your answer for data that is gone**, if a request can reach an encryption for
a subject after its erasure.
- **A key store of your own implements `MarkSubjectErasedAsync`**, refusing in `GetOrCreateCurrentKeyAsync` and
`RotateAsync` every scope a marked subject `Covers`. Without it the erasure warns and the gap stays open.