# Configuring Azure Event Hub for Data Export

> Use this guide to configure Azure Event Hub as a destination for UiPath Data Export. Azure Event Hub supports event-based (JSON) exports for Orchestrator Events and Audit Logs.

Use this guide to configure Azure Event Hub as a destination for UiPath Data Export. Azure Event Hub supports event-based (JSON) exports for Orchestrator Events and Audit Logs.

## Prerequisites

- An active Azure Event Hub account.
- A connection string scoped to a specific Event Hub instance (not a namespace-level connection string).
- The Azure Shared Access Signature (SAS) policy must include at minimum the **Send** and **Listen** permissions.
- Organization Administrator access in UiPath Test Cloud.

## Security recommendation

To restrict access without exposing your network to all external traffic, configure static IP allowlisting in your Azure Event Hub. Go to **Settings** > **Networking** > **Public access** > **Firewall** > **Address range** and add the UiPath static export IP address. Contact UiPath Support to obtain the current IP address.

![Azure Event Hub Networking — Firewall settings](https://dev-assets.cms.uipath.com/assets/images/data-export/AzureAcessPolicy-9d1bd124.webp)

## Configuring Azure Event Hub

1. In UiPath Test Cloud, go to **Admin** and select **Data Export**.
2. Select **+ Add**.
3. Choose the tenant for this export, then select **Next**.
4. Select the data sources to export (for example, **Orchestrator Events** or **Audit Logs**), then select **Next**.
5. Select **Azure Event Hub** as the destination and enter the connection string.

   The connection string must target a specific Event Hub instance. The following is an example of a valid format:

   ```
   Endpoint=sb://xxxx.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxxxxxxxxxxxx;EntityPath=xx
   ```

   To verify connectivity before saving, select **Test Connection**. This sends a test event to the destination.

6. Review the configuration, then select **Save**.

**Result:** The new configuration appears in the **Data Export** table. The **Status** column reflects whether data is being delivered successfully.