> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/destinations/destinations-catalog/azure-event-hub.md).

# Azure Event Hub

[Azure Event Hubs](https://azure.microsoft.com/en-us/products/event-hubs) is a massively scalable data ingestion service capable of handling millions of events per second, allowing you to process and analyze the enormous volumes of data generated by your connected devices and applications. After data flows into an event hub, it can be transformed and stored using any real-time analytics platform or batching/storage adapter.\
Using this destination you can leverage [Azure Event Hubs REST API](https://learn.microsoft.com/en-us/rest/api/eventhub/) to send events to [your Azure Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create).

## Key features

The Azure Event Hub destination provides the following key features:

* **Events structure**: our [Events reference](https://doc.commandersact.com/developers/tracking/events-reference) model covers [Azure Event Hubs's event structure](https://learn.microsoft.com/en-us/rest/api/eventhub/send-batch-events), meaning that your data is properly bridged to the expected fields in an optimized way.
* **Property mapping**: send all properties in your event or select the ones to include. See `Send All Properties` and `Custom Event Properties` in [Configuration](#configuration).

## Destination setup

{% hint style="info" %}
Ensure you do the following steps before configuring your destination:\
**1.** Create an [Event Hub](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-create). \
**2.** Generate a [Shared Access Signature (SAS)](https://learn.microsoft.com/en-us/azure/event-hubs/authenticate-shared-access-signature#generate-a-shared-access-signature-token).\
The `Shared Access Policy` must have at least the `Send` permission.
{% endhint %}

### Configuration

<table><thead><tr><th width="300">Settings</th><th>Description</th></tr></thead><tbody><tr><td><code>Shared Access Policy Name</code></td><td><em><strong><code>Required</code></strong></em><br>Shared access policy name that grants write access to the event hub (E.g. <code>WriteSharedAccessKey</code> ).</td></tr><tr><td><code>Shared Access Policy Key</code></td><td><em><strong><code>Required</code></strong></em><br>Shared access policy primary key (E.g. <code>123ABCabc......efg=</code> ).</td></tr><tr><td><code>Event Hub Namespace</code></td><td><em><strong><code>Required</code></strong></em><br>Event hub namespace that contains the event hub resource to use (E.g. <code>my-namespace</code> ).</td></tr><tr><td><code>Event Hub Name</code></td><td><em><strong><code>Required</code></strong></em><br>Event hub to which events will be sent (E.g. <code>my-hub</code> ).</td></tr><tr><td><code>Send All Properties</code></td><td>Flag this option to send all properties in your event (after <a href="https://doc.commandersact.com/features/destinations/advanced-mapping#transform-data-before-it-gets-to-the-destination">Properties Transformations</a>) to the <code>Azure Event Hub</code>.</td></tr><tr><td><code>Custom Event Properties</code></td><td>Map your event properties to specific propery names in Azure. Set <code>Azure property name</code> to specify the property name in Azure, and <code>Your value</code> for its value.</td></tr></tbody></table>

## Field mappings

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Commanders Act Properties</th><th>Azure Properties</th></tr></thead><tbody><tr><td><code>[Any property name]</code></td><td><code>[Any property name]</code> <strong>[1]</strong></td></tr></tbody></table>

{% hint style="info" %}
**1.** See <mark style="color:blue;">`Custom Event Properties`</mark> in [Configuration](#configuration). You can also flag <mark style="color:blue;">`Send All Properties`</mark> to send all properties in your events with the same original names and values.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://doc.commandersact.com/features/destinations/destinations-catalog/azure-event-hub.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.