Edit

Azure Event Hubs - Client SDKs

  • Article

This article provides following information for the SDKs supported by Azure Event Hubs:

  • Location of package that you can use in your applications
  • GitHub location where you can find source code, samples, readme, change log, reported issues, and also raise new issues
  • Links to quickstart tutorials

Client SDKs

The following table describes all the latest available Azure Event Hubs runtime clients. The core focus of these libraries is to send and receive messages from an event hub.

Language Package Reference
. NET Standard Azure.Messaging.EventHubs
Azure.Messaging.EventHubs.Processor
Java azure-messaging-eventhubs
azure-messaging-eventhubs-checkpointstore-blob
Python azure-eventhub
azure-eventhub-checkpointstoreblob-aio
JavaScript azure/event-hubs
azure/eventhubs-checkpointstore-blob
Go azure-event-hubs-go
C azure-event-hubs-c

The following table lists older Azure Event Hubs runtime clients. While these packages may receive critical bug fixes, they aren't in active development. We recommend using the latest SDKs listed in the above table instead.

On 30 September 2026, we'll retire the Azure Service Bus SDK libraries WindowsAzure.ServiceBus, Microsoft.Azure.ServiceBus, and com.microsoft.azure.servicebus, which don't conform to Azure SDK guidelines. We'll also end support of the SBMP protocol, so you'll no longer be able to use this protocol after 30 September 2026. Migrate to the latest Azure SDK libraries, which offer critical security updates and improved capabilities, before that date.

Although the older libraries can still be used beyond 30 September 2026, they'll no longer receive official support and updates from Microsoft. For more information, see the support retirement announcement.

Language Package Reference
. NET Standard Microsoft.Azure.EventHubs (legacy)
Microsoft.Azure.EventHubs.Processor (legacy)
. NET Framework WindowsAzure.Messaging (legacy)
Java azure-eventhubs (legacy)

Management SDKs

Here's a list of currently available management-specific libraries. None of these libraries contain runtime operations, and are for the sole purpose of managing Event Hubs entities.

.NET packages

Client libraries

  • Azure.Messaging.EventHubs: It's the current version of the library, conforming to the unified Azure SDK design guidelines and under active development for new features. It supports the .NET Standard platform, allowing it to be used by both the full .NET Framework and .NET Core. There's feature parity at a high level with Microsoft.Azure.EventHubs, with details and the client hierarchy taking a different form. This library is the one that we recommend you to use.
  • Microsoft.Azure.EventHubs: It was the initial library to break out Event Hubs into a dedicated client that isn’t bundled with Service Bus. It supports the .NET Standard 2.0 platform, allowing it to be used by both the full .NET Framework and .NET Core. It's still the dominant version of the library with respect to usage and third-party blog entries, extensions, and such. The baseline functionality is the same as the current library, though there are some minor bits that one offers and the other doesn’t. It's currently receiving bug fixes and critical updates but is no longer receiving new features.
  • Windows.Azure.ServiceBus: It was the original library, back when Event Hubs was still more entangled with Service Bus. It supports only the full .NET Framework, because it predates .NET Core. This library offers some corollary functionality that isn’t supported by the newer libraries.

Management libraries

  • Microsoft.Azure.Management.EventHub: It's the current GA version of the management library for Event Hubs. It supports the .NET Standard 2.0 platform, allowing it to be used by both the full .NET Framework and .NET Core.

Next steps

You can learn more about Event Hubs by visiting the following links: