Skip to content

Add Azure Service Bus upgrade guide for v5 to v6 #7831

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add Azure Service Bus upgrade guide for v5 to v6 #7831

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions menu/menu.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -832,6 +832,8 @@
Title: Version 6 to 7
- Title: Azure Service Bus
Articles:
- Url: transports/upgrades/asbs-5to6
Title: Version 5 to 6
- Url: transports/upgrades/asbs-4to5
Title: Version 4 to 5
- Url: transports/upgrades/asbs-3to4
Expand Down
16 changes: 16 additions & 0 deletions transports/upgrades/asbs-5to6.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
title: Azure Service Bus Transport Upgrade Version 5 to 6
summary: Migration instructions on how to upgrade the Azure Service Bus transport from version 5 to 6
reviewed: 2025-09-18
component: ASBS
related:
- transports/azure-service-bus
isUpgradeGuide: true
upgradeGuideCoreVersions:
- 9
- 10
---

## Transport Encoding Header

The `AzureServiceBusTransport.SendTransportEncodingHeader` API has been deprecated. The transport now relies on the [ContentType property](https://learn.microsoft.com/azure/service-bus-messaging/service-bus-messages-payloads#payload-serialization) of Azure Service Bus messages instead of a custom header. Remove any usage of this API.
Loading