Talk to our team

Explore Uplyst

Esc

Popular places to start

platformEnterprise intelligence for the way you work.

Uplyst connects operational data, business relationships and real time events to support decisions across your enterprise.

integrationsConnect your enterprise systems.

Explore Uplyst integrations across business applications, data platforms, databases, event streams and industrial systems.

DocumentationTechnical guides for connected systems

Guides to enterprise architecture, semantic models, integration contracts, security and operations.

resourcesEnterprise intelligence in practice

Architecture, integration and governance guidance for connecting enterprise data with operational decisions.

Azure Event Hubs integration

Bring Azure events into the context of your business. Uplyst links telemetry and application activity with the assets, customers and operations they affect.

How it connectsDiscuss your integration
Independent consumers, shared operational events
  1. Event HubsPartitioned event streams from Azure applications and devices
  2. Consumer groupsSeparate views and processing positions for each application
  3. Uplyst business contextEvents linked to assets, customers and operational processes

Connect Azure events with business records

Azure Event Hubs is a managed streaming service supporting Kafka, AMQP and HTTPS. Uplyst connects approved event streams with its enterprise intelligence layer, bringing together event activity and records from operational systems.

Consumer groups let applications read the same stream independently. The integration's event selection and business mappings define how source activity relates to entities such as equipment, accounts and orders.

Consumer progress and replay

Consumers track their positions within each partition. Checkpoints preserve completed progress so processing can resume after a restart, while configured retention determines which events remain available for replay.

Business event identifiers and timestamps help relate replayed data to existing operational history. Source position and business identity together support investigation of delayed or repeated updates.

One partition. Independent progress.Partition 2
payments.operationsRetained sequence begins at 10420
  1. 10480Payment captured
  2. 10481Settlement opened
  3. 10482Fee allocated
  4. 10483Settlement posted
  5. 10484Account updated
financial-contextSettlement and account intelligence
Saved checkpoint
10482
Next retained event
10483
compliance-reviewIndependent transaction review
Saved checkpoint
10480
Next retained event
10481
Each consumer resumes from its own progress.

The bars show progress through the five events above. Both next events remain in retention. Advancing one group does not advance the other. If Blob Storage holds checkpoints, its access is configured separately.

Microsoft Entra identities and roles

Event Hubs supports authorization through Microsoft Entra ID and Azure role assignments. The Azure Event Hubs Data Receiver role provides permissions to receive events within its assigned scope.

When a consumer stores checkpoints in Blob Storage, storage access is configured separately. The event stream and the checkpoint store serve different purposes and have their own permissions.

Microsoft Entra access

Event Hubs
Receive permitted eventsThe Azure Event Hubs Data Receiver role supports event consumption.
Blob Storage, when used
Store consumer checkpointsStorage permissions are separate from event access.

Partitions and independent consumers

Event Hubs partitions allow a stream to be consumed in parallel. Each consumer group maintains its own view of the stream, so operational analysis can run alongside other applications using the same events.

Ordering is local to a partition. Business processes that span several sources also rely on entity relationships and event time to understand the sequence of activity.

Operational monitoring across Azure

Equipment telemetry, application logs and transaction events can reveal changes that matter beyond the source application. Uplyst connects those changes with business records to support maintenance, service operations and financial analysis.

This context helps teams investigate the affected asset, customer or process when event delivery slows or a source stops reporting.

Related integrations

Azure Blob Storage integrationApache Kafka integration

Connect your systems
with Uplyst.

Talk with our team about the systems you use and the decisions they need to support.

Discuss an integration