Overview
Azure Event Hubs is Microsoft's managed event-streaming service – Kafka-compatible, big-data ingest. The Automize Event Hubs connector covers event publishing, consumer groups, and partition listing.
- Regions: Each namespace lives in one Azure region. Geo-DR via paired namespaces.
- Plans: Basic, Standard, Premium, Dedicated tiers. Kafka surface available on Standard+.
Setting up the connection
Auth type: Bearer Token.
- Azure Portal → Event Hub Namespace → Shared Access Policies → create policy with Send/Listen claims.
- Copy SAS connection string OR use Entra ID with Azure Event Hubs Data Sender/Receiver roles.
- In Automize → Settings → Connectors → Azure Event Hub. Paste credentials + namespace + event hub name.
Find your credentials at https://portal.azure.com/.
Rate limits
Throughput Units (Standard) or Processing Units (Premium) determine ingress + egress capacity. 1 TU = 1 MB/s ingress, 2 MB/s egress.
Data model
Streaming primitives:
Namespace ─── Event Hubs (topics) ─── Partitions ─── Events
└─ Consumer Groups (independent read positions)Available operations
7 operations available. Click any row to jump to its detail.
| Operation | Category | What it does |
|---|---|---|
| Create Consumer Group | General | Create a consumer group |
| Delete Consumer Group | General | Delete a consumer group |
| Get Partition | General | Get partition runtime information |
| List Consumer Groups | General | List consumer groups for an event hub |
| List Partitions | General | List partitions for a consumer group |
| Send Event Batch | General | Send a batch of events |
| Send Event | General | Send an event to an event hub |
Operations
Create Consumer Group
Create a consumer group
| Parameter | Required | Type | Description |
|---|---|---|---|
Event Hub Name event_hub_name | Yes | text | |
Consumer Group Name consumer_group_name | Yes | text |
Delete Consumer Group
Delete a consumer group
| Parameter | Required | Type | Description |
|---|---|---|---|
Event Hub Name event_hub_name | Yes | text | |
Consumer Group Name consumer_group_name | Yes | text |
Get Partition
Get partition runtime information
| Parameter | Required | Type | Description |
|---|---|---|---|
Event Hub Name event_hub_name | Yes | text | |
Consumer Group consumer_group | Yes | text | |
Partition Id partition_id | Yes | text |
List Consumer Groups
List consumer groups for an event hub
| Parameter | Required | Type | Description |
|---|---|---|---|
Event Hub Name event_hub_name | Yes | text |
Tips
- Each consumer group has its own offsets per partition.
List Partitions
List partitions for a consumer group
| Parameter | Required | Type | Description |
|---|---|---|---|
Event Hub Name event_hub_name | Yes | text | |
Consumer Group consumer_group | Yes | text |
Tips
- Returns partition IDs + their current sequence numbers.
Send Event Batch
Send a batch of events
| Parameter | Required | Type | Description |
|---|---|---|---|
Event Hub Name event_hub_name | Yes | text |
Send Event
Send an event to an event hub
| Parameter | Required | Type | Description |
|---|---|---|---|
Event Hub Name event_hub_name | Yes | text |
Tips
- body: JSON or binary. Partition Key for ordering within a partition.
- Batch send: pass array of events.
FAQ
- Event Hubs vs Service Bus?
- Event Hubs: high-throughput append-log, multiple readers, ideal for analytics/IoT. Service Bus: enterprise messaging, queues + pub-sub, transactional.
- Kafka compat – fully?
- Standard+ exposes a Kafka 1.0+ surface – use any Kafka client. Topics map to Event Hubs.