Skip to content

Azure Service Bus Polymorphic dispatch behavioral breaking change #8164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ramonsmits merged 3 commits into from
Apr 9, 2026
Merged

Azure Service Bus Polymorphic dispatch behavioral breaking change #8164

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1cc87b7
Polymorphic dispatch behavioral change
ramonsmits Apr 8, 2026
b574074
🐛 Fix broken links in ASB 4-to-5 upgrade guide
ramonsmits Apr 9, 2026
fc4b67b
Feedback from Mauro
ramonsmits Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion transports/upgrades/asbs-4to5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,20 @@ upgradeGuideCoreVersions:

Upgrading Azure Service Bus transport from version 4 to version 5 is a major upgrade and requires careful planning. Read the entire upgrade guide before beginning the upgrade process.

## Polymorphic dispatch

[Polymorphic dispatch using message type inheritance](/nservicebus/messaging/dynamic-dispatch-and-routing.md) no longer auto subscribes to all descendant types. Polymorphic dispatch is still supported but requires that each descendant type in the inheritance tree [is configured with an explicit type subscription on the topology object](/transports/azure-service-bus/topology.md#subscription-rule-matching-interface-based-inheritance).


## Topologies

Version 5 of the transport introduces the concept of choosing a topic topology. The following two topologies are supported:

- Migration topology
- Topic-per-event type topology

The topology selection must be explicitly passed into the constructor of the transport when the transport is being created.

## Topologies

### Topic-per-event type topology

Expand Down