Azure Message Broker Connector
Setup and configuration of Azure Event Hub and authentication infrastructure must be available, according to the Azure documentation.
eventHubNamespace) {your-namespace}.servicebus.windows.net
This value is available in the Azure portal.
eventHubName) This value is available in the Azure portal.
authentication) Dependending on the setup and available infrastructure, different methods may suit better. Refer to the individual plugin documentation for further explanations.
If authentication with Microsoft Entra ID is not possible, consider using a "Connection String" for direct access.
For successful authentication, ensure that the necessary certificates are available when a custom truststore is used with IAM.
For integration or if necessary, additional logging regarding connections to Azure can be enabled in the Log4J configuration. IAM documentation explains custom logging configuration.
Adjust the log levels for "com.azure", "com.azure.core.amqp", "com.microsoft.azure.proton.transport.proxy" or other libraries to your needs.
connectionString) Alternative service authentication method if general authentication with Microsoft Entra ID is not possible.
An Azure connection string contains all information required for an application to securely authenticate with and connect to an Azure Event Hub. It includes the service endpoint, authentication credentials (Shared Access Key), and an optional entity path (Event Hub name).A namespace-level connection string grants the specified permissions (manage, read, or write) for all Event Hubs within the namespace.
An Event Hub–level connection string (ends with ;EntityPath=<EventHubName>) grants the specified permissions only for that specific Event Hub.
Connection strings should only be used when authentication with Microsoft Entra ID is not available or for integration.
It is recommended to rotate connection strings regularly.
For successful authentication, ensure that the necessary certificates are available when a custom truststore is used with IAM.
For integration or if necessary, additional logging regarding connections to Azure can be enabled in the Log4J configuration. IAM documentation explains custom logging configuration.
Adjust the log levels for "com.azure", "com.azure.core.amqp" or other libraries to your needs.
transportType) AMQP is the default transport type and is recommended for most scenarios. Outbound connections use port 5671.
AMQP over Web Sockets is useful for environments where networking is restrictive or when a proxy configuration must be used. Outbound connections use port 443.
proxyHost) If this property is left empty, no proxy will be used.
proxyPort) proxyAuthenticationType) - None: The proxy requires no authentication. Configuration of a proxy login user and password is ignored.
- Basic Authentication: Uses a username and password sent in plaintext (Base64 encoded but not encrypted).
- Digest Authentication: Uses a username and password with challenge-response hashing for improved security.
proxyLoginUser) proxyLoginPassword) partitionKey) A partition key is used to map event data into specific partitions for data organization.
It enables keeping related events together in the same partition and in the exact order in which they arrived.
The partition key is derived from the application context and identifies the interrelationship of the events.
The partition key is used for all events sent to the event hub by this message broker connector.
type: AzureMessageBrokerConnector
id: AzureMessageBrokerConnector-xxxxxx
displayName:
comment:
properties:
authentication:
connectionString:
eventHubName:
eventHubNamespace:
partitionKey:
proxyAuthenticationType: NONE
proxyHost:
proxyLoginPassword:
proxyLoginUser:
proxyPort:
transportType: AMQP