Connectors
Azure Event Hub integration
High-throughput event streaming integration with Azure Event Hub for real-time data ingestion and processing.
Updated 2026-08-11
Overview
The Azure Event Hub integration provides high-throughput event streaming capabilities for real-time data ingestion and processing. This integration enables seamless connection to Azure Event Hub namespaces, allowing you to stream and process large volumes of events with low latency and high reliability.
Prerequisites
- Azure subscription with appropriate permissions
- Azure Event Hub namespace
- Azure Storage account
- Event Hub with consumer groups configured
- Bloo platform access credentials
Configuration Steps
1. Create Azure Event Hub Namespace
- Sign in to the Azure Portal
- Select All services on the left navigational menu
- Select Event Hubs in the Analytics section
- Click + Create to create a new Event Hub namespace
- Configure the following settings:
- Subscription: Select your Azure subscription
- Resource Group: Create new or select existing resource group
- Namespace name: Enter a unique namespace name
- Location: Select the appropriate region
- Pricing tier: Choose Standard (recommended) or Premium
- Throughput units: Set based on your requirements (1-20 for Standard tier)
- Click Review + Create and then Create
- Wait for deployment to complete and navigate to your namespace
2. Create Azure Storage Account
- In the Azure Portal, navigate to Storage accounts
- Click + Create to create a new storage account
- Configure the following settings:
- Subscription: Select your Azure subscription
- Resource Group: Use the same resource group as Event Hub
- Storage account name: Enter a unique name
- Location: Select the same region as Event Hub
- Performance: Standard (recommended)
- Redundancy: LRS (Locally-redundant storage)
- Click Review + Create and then Create
3. Create Container
- Navigate to your storage account in the Azure Portal
- In the left menu, scroll to Blob service section
- Select Containers
- Click + Container button
- Configure the container:
- Name: Enter a lowercase name (e.g., "eventhub-bookmarks")
- Public access level: Set to "Container" for proper access
- Click OK to create the container
4. Create Event Hub
- On the Event Hubs Namespace page, select Event Hubs in the left menu
- Click + Event Hub at the top
- Configure the Event Hub:
- Name: Enter a descriptive name
- Partition count: Set based on your throughput requirements
- Message retention: Set retention period (1-7 days)
- Click Review + Create and then Create
5. Enable Event Capture
- Click on your newly created Event Hub
- Click Capture events in the Event Hub page
- Enable capture and select the container created in step 3
- Configure capture settings as needed
6. Configure Diagnostic Settings
- Navigate to your Azure resource (e.g., Azure solution)
- In the left menu, search for "Monitoring"
- Click Diagnostic settings
- Click + Add diagnostic setting
- Configure diagnostic settings:
- Name: Enter a descriptive name
- Category details: Select log types to ingest
- Destination details:
- Check Stream to an event hub
- Select your subscription
- Select your Event Hub namespace
- Select your Event Hub name
- Select RootManageSharedAccessKey policy
7. Get Connection Strings
Azure Storage Connection String
- Navigate to your storage account
- Under Security + Networking, select Access keys
- Copy the Connection string value under key1
Event Hub Connection String
- Navigate to your Event Hub namespace
- Select Shared Access Policies in the left menu
- Select RootManageSharedAccessPolicy (or create a new policy)
- Copy the Connection string-primary key
Bloo Platform Configuration
Connector Setup
- Log in to your Bloo platform
- Navigate to Integrations > Connectors
- Click Add New Connector
- Configure the following fields:
| Field Name | Description |
|---|---|
| Connector Name | Enter a descriptive name for your connector |
| Connector Type | Select "Azure EventHub connector" |
| Azure Storage Connection String | Paste the storage connection string from step 7 |
| Azure Connection String | Paste the Event Hub connection string from step 7 |
| Event Hub Name | Enter the Event Hub name created in step 4 |
| Container Name | Enter the container name created in step 3 |
- Click Save to create the connector
Validation
- Navigate to Collection Status screen
- Verify your Azure Event Hub connector appears with Active status
- Confirm data ingestion is working by checking the data flow
Features
- High Throughput: Process millions of events per second
- Low Latency: Real-time event processing with minimal delay
- Scalability: Automatically scale based on demand
- Reliability: Built-in redundancy and fault tolerance
- Consumer Groups: Support for multiple consumer applications
- Partition Management: Distribute load across multiple partitions
- Message Retention: Configurable retention periods
- Diagnostic Integration: Seamless integration with Azure diagnostic settings
Troubleshooting
Common Issues
Connection Failed
- Verify connection strings are correct
- Check network connectivity to Azure
- Ensure proper permissions are granted
No Data Ingestion
- Verify Event Hub is receiving data
- Check diagnostic settings configuration
- Ensure consumer group is properly configured
Performance Issues
- Increase throughput units if needed
- Optimize partition count
- Check message size limits
Support
For additional support and troubleshooting:
- Check Azure Event Hub documentation
- Review Bloo platform logs
- Contact Bloo support team
Security Considerations
- Use managed identities when possible
- Implement proper access controls
- Enable encryption in transit and at rest
- Regularly rotate access keys
- Monitor access patterns and usage
Best Practices
- Namespace Design: Use separate namespaces for different environments
- Partition Strategy: Choose partition count based on expected throughput
- Consumer Groups: Use separate consumer groups for different applications
- Monitoring: Set up proper monitoring and alerting
- Retention: Configure appropriate message retention periods
- Security: Follow Azure security best practices
- Cost Optimization: Monitor usage and optimize costs regularly
Related
Was this page helpful?