Stratara.Outbox.AzureServiceBus
4.7.0
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Outbox.AzureServiceBus --version 4.7.0
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 4.7.0
<PackageReference Include="Stratara.Outbox.AzureServiceBus" Version="4.7.0" />
<PackageVersion Include="Stratara.Outbox.AzureServiceBus" Version="4.7.0" />
<PackageReference Include="Stratara.Outbox.AzureServiceBus" />
paket add Stratara.Outbox.AzureServiceBus --version 4.7.0
#r "nuget: Stratara.Outbox.AzureServiceBus, 4.7.0"
#:package Stratara.Outbox.AzureServiceBus@4.7.0
#addin nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.7.0
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.7.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.7.0)
- Stratara.Shared (>= 4.7.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 |
A release for one person who belongs to several tenants — and, sharing one identity store, to several applications.
### Added
- **`MembershipStatus.Former`** records a member who has left. It confers nothing — no role, permission or
cross-tenant access, never the tenant at sign-in, never a selection — and stays listed until the user's or the
tenant's erasure removes it.
- **`AddCheckedMembershipTenantClaim<TUser>()`**, a third tenant-claim mode: the claim is stamped at sign-in, kept when
the security-stamp validator refreshes a cookie sign-in, and checked on every request. A request whose user is no
longer an active member of the carried tenant loses the claim and resolves to the reserved default tenant, without
another tenant substituted. Only principals ASP.NET Identity issued are checked; an API key or a token the host
mints keeps its tenant. The tenant changes only when the host re-issues the sign-in. Combining it with
`AddMembershipTenantClaimsTransformation()` throws, and a claims transformation of the host's own registered
beside it is refused at start. Use it where several applications share one identity store:
`active_tenant` holds one selection per account, so live resolution moves every open session when any of them
switches.
- **`EventSubject.ForUser(userId)`** and **`EventSubject.NamesAnOwner`**: a stream can be created for a user alone,
for data that belongs to a person rather than to any of their tenants. It is recorded under the reserved default
tenant, keeps that owner for every later event whatever tenant the session names, and its encrypted fields — at
every level — are keyed to the person: shredded by the person's erasure, untouched by any tenant's.
`KeySubject.User` covers those keys too, so nothing is encrypted for the person again after the erasure.
- **`StrataraIdentityStore`, an identity store several hosts can share on PostgreSQL**, with its migrations shipped
in `Stratara.EventSourcing.EntityFrameworkCore`. It holds ASP.NET Identity's tables, passkeys included, and the
tenant directory in the fixed schema `stratara_identity`, with the history in
`stratara_identity.__stratara_identity_migrations`. `AddStrataraIdentityStore()` registers it on the connection
string `identitydb` (falling back to `defaultdb`, never through a tenant-routing `IDbResolver`) with the
directory's stores over it, and refuses a host that turns on `Stores.ProtectPersonalData`;
`MigrateStrataraIdentityStoreAsync()` creates the database where needed and applies the migrations — hosts that
migrate at once take turns. The account type is `IdentityUser` and cannot be extended, and the store fixes the
ASP.NET Identity schema version and key lengths, so every host's model matches the shipped migrations. Within a
major version the schema changes only additively. Moving an existing identity store onto it means replacing it and
seeding with the same user and tenant ids; the new guide *Shared Identity Store* describes it.
### Changed
- **Setting a membership to a status other than `Active` clears a selection that pointed at it**, as removing it
already did.
- **An explicit subject that names a user and no tenant is accepted** by `AppendOnBehalfOfAsync` and
`CreateOnBehalfOfAsync`; one that names neither is refused as before. A session whose tenant resolved to the
reserved default still gives an event no owner.
- **BREAKING (behaviour): an event or aggregate type marked `[EncryptData]` as a whole stops the host from starting.**
`EncryptionMetadataDriftGuard` refuses every registered aggregate, and every event type a registered aggregate
applies, that carries the attribute on the type; an event type no aggregate applies is refused when it is appended,
before anything is written. Once its subject was erased such a payload had nothing left to deliver, and a replay or
rebuild stopped there for good. Mark the properties instead; payloads already written as a whole are still read.
Commands and other types may still be marked as a whole.
### Fixed
- **A user's erasure shreds their own data through a key store that cannot list its scopes.** The eraser names the
user's keys under the reserved default tenant itself, at every level; until now only a listing reached the
user-level one.