---
title: "How to configure Azure (for Event Hubs)"
slug: "how-to-configure-azure-for-event-hubs"
description: "Unlock powerful data integration with the Data Activation connector for Azure, enhancing marketing and analytics through real-time, secure data management."
updated: 2026-02-27T13:22:29Z
published: 2026-02-27T13:25:42Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.supermetrics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to configure Azure (for Event Hubs)

The Data Activation data connector for Microsoft Azure unlocks powerful data integration and processing capabilities, enabling you to harness the full potential of your customer data. By bridging the Data Activation with Azure's cloud infrastructure and services, you can enhance your marketing and analytics efforts through scalable and secure data management.

This article describes how to set up Azure Event Hubs for use with the Data Activation. You can use this connector as an audience or journey Server-to-server connector or as an event

- The [Azure Event Hubs audience and journey connector](/v1/docs/azure-event-hubs-setup-for-data-activation) can be used in an audience or journey and notifies you of all added, modified, or removed events of profiles.
- The [Azure Event Hubs event connector](/v1/docs/azure-event-hubs-event-connector-setup-for-data-activation) forwards the raw events collected by the Data Activation to your Azure Event Hubs instance. You can use this information in Azure for different purposes such as reporting.

## Key benefits

- **Scalable data processing**: Use Azure's powerful cloud infrastructure to handle large volumes of customer data efficiently, enabling you to execute complex analytics and audience segmentation with ease.
- **Seamless data integration**: Connect with Azure services like Azure Data Lake, Azure Synapse Analytics, and Azure Machine Learning to consolidate and analyze data from multiple sources for deeper insights.
- **Real-time activation**: Enable real-time data flow between the Data Activation and Azure, ensuring your campaigns and customer interactions use the most current and relevant data.
- **Enhanced data security**: Benefit from Azure's enterprise-grade security measures to ensure the safe transfer, storage, and processing of customer data.
- **Streamlined personalization**: Use Azure's AI and machine learning capabilities alongside your customer data to power advanced personalization across your marketing campaigns.
- **Cross-platform connectivity**: Integrate with Azure's extensive ecosystem of tools and applications, enabling unified workflows and a cohesive approach to data-driven marketing.

## Quick connector overview

| Property | Value |
| --- | --- |
| **Platform type** | DSP |
| **Needs cookie sync** | No |
| **Connecting protocol** | Azure |
| **Real-time data sync** | Yes |
| **Syncs data on** | Add, Modify, Remove |
| **Multiple connectors allowed** | Yes |

## Before you begin

Before using the Azure Event Hubs connector, ensure you have:

- An active Microsoft Azure account
- Permission to create Event Hubs and namespaces

## Instructions

### Create a namespace

1. Go to **Microsoft Azure**.
2. Open **Home → Event Hubs**.
3. Click **Create Namespace**.

Create a new resource group or select an existing one. Specify the namespace details:

- Name
- Location
- Pricing tier

Click **Review + create** and confirm creating the new namespace.

### Create an event hub

1. Select the namespace you want to use, for example, the one you created earlier.
2. Click **+ Event hub**.

The name you select here is also the `entityPath` which you need later for the connection string.

Specify the name of your hub and click **Create**.

### Get the connection string

1. Select your hub.
2. Find **Shared access policies** in the left-hand menu.
3. Click **Shared access policies**.
4. Click the **+ Add** button.
5. Select the **Send** checkbox and save.

Copy the **Connection string-primary key** or **Connection string-secondary key**. You use this string to create your new Azure connector.

> [!NOTE]
> Important
> 
> Ensure the policy name is included at the end of the connection string with `EntityPath`. ,
> 
> 
> 
> You should obtain a string like this:
> 
> ```plaintext
> Endpoint=sb://my-namespace-1.servicebus.windows.net/;SharedAccessKeyName=access-key-name;SharedAccessKey=YourAccesskey;EntityPath=my-event-hub
> ```

Take the connection string from the event hub, not from the Event Hubs instance (the parent level). The parent-level connection string does not work.

## More resources

- [How to build audiences](/v1/docs/how-to-build-audiences)
- [How to build journeys](/v1/docs/how-to-build-journeys)
- [How to measure goals and outcome signals](/v1/docs/how-to-measure-goals-and-outcome-signals)