What are Business Events?
A Business Event represents a significant occurrence or change-in-state that matters to the business. Unlike raw telemetry or diagnostic data, Business Events are intentionally modeled around business outcomes: driving critical decisions, automating workflows, triggering alerts, enabling analytics, and providing real-time context to AI.
Official documentation
For the complete API reference and platform overview, see the Business Events documentation on learn.microsoft.com.
The core idea
In most data platforms, workloads communicate through direct calls: one service invokes another, waits for a response, and fails if the other is unavailable. This creates tight coupling that makes systems fragile and hard to evolve.
Business Events introduce a different model. Any publisher (a Notebook, a User Data Function, an Eventstream, or Activator) can emit a named, schema-defined event to Real-Time Hub the moment something meaningful happens. Any number of consumers (Activator or Eventhouse) react to that event independently, without the publisher knowing who is listening or how many are subscribed.
This means you can add new consumers, change how alerts are delivered, or route the same event to an analytics store, all without touching the code that published the event.
flowchart LR
subgraph Publishers
NB[Notebook]
UDF[User Data Function]
ES[Eventstream]
ACT1[Activator]
end
subgraph RTH[Real-Time Hub]
BE([Business Event])
end
subgraph Consumers
ACT2[Activator]
EH[Eventhouse]
end
NB --> BE
UDF --> BE
ES --> BE
ACT1 --> BE
BE --> ACT2
BE --> EH
Key concepts
Schema-first design Every Business Event has a defined schema before any data flows. The schema uses a record format with typed fields, ensuring consumers always know what to expect.
Decoupled architecture Publishers do not know who consumes their events. Consumers do not know who publishes. This means you can add new consumers without changing any publisher code.
Real-time delivery Events are delivered to consumers in real time through Microsoft Fabric Real-Time Hub infrastructure.
Next steps
- Architecture Overview: understand how the pieces fit together
- Event Schema: learn the schema format and field types
- Decision Guide: when to use Business Events vs alternatives