# Azure Event Hubs Listener

Learn more about this Listener type in [this article](/the-workspace/listeners/listener-integrations/collect-data-from-microsoft-products/collect-data-from-azure-event-hubs.md).

<details>

<summary>v4.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">05/07/2026</mark>

* New **Message Format** parameter to control how incoming messages are parsed.
* Then **Split Strategy** and **Custom Delimiter** fields are removed and are replaced with **Message Format** and **Format Options**.
* Parse failures now route to the **Error** port instead of being silently dropped.
* Each emitted event now carries the original partition, offset, and sequence metadata.
* Messages with an empty body after decompression are now skipped instead of emitting an event with an empty field.

</details>

<details>

<summary>v3.1.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">04/21/2026</mark>

* Improved connection strings validation and error handling.
* Resolved an issue preventing the Listener from reading events without batch mode.

</details>

<details>

<summary>v3.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">03/11/2026</mark>

* To enhance performance and resilience, we highly recommend enabling the **Client Checkpointing** option in the Listener configuration now. If it's not enabled, you must set the environment variable in your distributor with Docker Compose using `SINGLETON_LISTENER_EXECUTOR=true`. For Listener versions before `v3.0.0`, you must use the `AZURE_EVENTHUB_LISTENER_EXECUTION_ENABLED` environment variable, even if the **Client Checkpointing** option is enabled.
* Fixed the event routing to the error port under certain conditions.

</details>

<details>

<summary>v2.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">11/06/2025</mark>

Added **Starting Position** options. The starting position defines where event processing begins and can be set to a specific timestamp, sequence number, or predefined position such as the beginning or end of the stream. This setting is crucial for controlling event replay and recovery scenarios.

</details>

<details>

<summary>v1.0.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">10/09/2025</mark>

In order to use this Listener, you must activate the Environment Variable in your distributor using docker compose (`AZURE_EVENTHUB_LISTENER_EXECUTION_ENABLED`)

</details>

<details>

<summary>v1.0.0</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">10/02/2025</mark>

* New consumer group.
* Added reserved fields: `_timestamp`, `_error`, and `_worker_reception_timestamp`.
* Added the checkpoint store and partition load balancing functionalities. **Checkpoint Store:** A persistent storage mechanism that records processing progress in data streams, enabling applications to resume from the last successful point after failures, preventing data loss and duplicate processing.

  **Partition Load Balancing:** The automated distribution of data partitions across multiple processing nodes to ensure even workload distribution, maximize throughput, and maintain system performance when nodes join, leave, or fail.

</details>

<details>

<summary>v0.0.2</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">07/11/2025</mark>

* The maximum number of receivers allowed is now limited to 1 per partition in your Event Hub.
* There's a new variable (`AZURE_EVENTHUB_LISTENER_EXECUTION_ENABLED`) to indicate the distributors in which the Listener can be executed.

</details>

<details>

<summary>v0.0.1</summary>

<mark style="background-color:purple;">**Released on**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">09/20/2024</mark>

Initial version

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onum.com/listeners/azure-event-hubs-listener.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.