Migrating Azure Servicebus

Azure Service Bus Migration

Overview

Migrate from the legacy WindowsAzure.ServiceBus package to the modern Azure.Messaging.ServiceBus SDK. The new SDK uses a single ServiceBusClient as the entry point, with dedicated ServiceBusSender, ServiceBusReceiver, and ServiceBusProcessor types replacing the old per-entity clients. Message handling shifts from OnMessage callbacks to async event handlers on the processor. AMQP is the only transport protocol (NetMessaging is removed).

Package Reference Changes

Old Reference (Remove)

<PackageReference Include="WindowsAzure.ServiceBus" Version="{old-version}" />

New Reference (Add)

<PackageReference Include="Azure.Messaging.ServiceBus" Version="{version}" />

Optionally add Azure.Identity for Azure AD–based authentication instead of connection string keys.

Workflow

Migration Progress:
- [ ] Step 1: Detect legacy Service Bus usage
- [ ] Step 2: Update project file references
- [ ] Step 3: Replace client creation
- [ ] Step 4: Migrate message sending
- [ ] Step 5: Migrate message receiving
- [ ] Step 6: Build and verify

Step 1: Detect Legacy Service Bus Usage

Scan the project for:

• using Microsoft.ServiceBus; and using Microsoft.ServiceBus.Messaging; statements
• Client types: QueueClient, TopicClient, SubscriptionClient, MessagingFactory
• BrokeredMessage usage
• OnMessage / OnMessageAsync callback registrations
• NamespaceManager for queue/topic administration

Step 2: Update Project File References

Remove WindowsAzure.ServiceBus and add Azure.Messaging.ServiceBus (see "Package Reference Changes" above).

Step 3: Replace Client Creation

The new SDK uses ServiceBusClient as the single entry point, then creates senders, receivers, or processors from it:

// Old
var factory = MessagingFactory.CreateFromConnectionString(connectionString);
var queueClient = factory.CreateQueueClient("my-queue");

// New
await using var client = new ServiceBusClient(connectionString);
var sender = client.CreateSender("my-queue");
var receiver = client.CreateReceiver("my-queue");

ServiceBusClient and its child types are thread-safe and reusable — create one client per application and share it.

Step 4: Migrate Message Sending

All send operations are async-only in the new SDK.

Step 5: Migrate Message Receiving

Replace OnMessage callbacks with ServiceBusProcessor event handlers:

// Old
queueClient.OnMessage(message =>
{
    var body = message.GetBody<string>();
    message.Complete();
});

// New
var processor = client.CreateProcessor("my-queue");
processor.ProcessMessageAsync += async args =>
{
    string body = args.Message.Body.ToString();
    await args.CompleteMessageAsync(args.Message);
};
processor.ProcessErrorAsync += async args =>
{
    // Handle errors
};
await processor.StartProcessingAsync();

Step 6: Build and Verify

1. Build the project:

   dotnet build
   

2. Test message send/receive against a Service Bus namespace (or use the local emulator)
3. Verify message completion, dead-lettering, and error handling work correctly
4. Confirm scheduled messages use DateTimeOffset instead of DateTime

Troubleshooting

Missing ProcessErrorAsync Handler

ServiceBusProcessor requires both ProcessMessageAsync and ProcessErrorAsync to be assigned before calling StartProcessingAsync(). The error handler is mandatory — omitting it throws an InvalidOperationException.

Message Body Deserialization

BrokeredMessage.GetBody<T>() used DataContractSerializer by default. ServiceBusReceivedMessage.Body is a BinaryData instance — use Body.ToObjectFromJson<T>() for JSON or Body.ToArray() for raw bytes. If the old messages used DataContractSerializer, deserialize with DataContractSerializer manually from Body.ToStream().

Connection String Format

The connection string format is the same between both SDKs. However, if code used MessagingFactory.Create(address, tokenProvider) with separate endpoint and credentials, replace with new ServiceBusClient(fullyQualifiedNamespace, new DefaultAzureCredential()) using Azure.Identity.