Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Author: Roberto Cervantes Rivero - Senior Product Manager
Business Events in Microsoft Fabric Real-Time Hub give organizations a way to define, publish, discover, and act on meaningful business signals across their data platform.
Today we are expanding that capability: Fabric Eventstream now supports Business Events as a native destination, letting teams publish governed, discoverable business signals directly from the Eventstream canvas with no code.
Business Events are schema-defined, discrete signals that represent meaningful changes in the business. Unlike raw telemetry, they carry organizational meaning—a defined name, a registered schema, and a contract between the producer and every consumer.
Teams can browse Real-Time Hub, find the events being published across the organization, understand their structure, and subscribe to them without needing to understand the infrastructure behind them.
Previously, publishing a Business Event typically meant using a Fabric Notebook with notebookutils.businessEvents.publish() or a User Data Function for custom code scenarios. Those options remain the right fit when you need fine-grained control: complex transformations, custom ML scoring, multi-stream joins, or business logic that goes beyond what a no-code pipeline can express.
With this release, Eventstream adds a built-in Business Events destination for scenarios where the logic is already well understood, and the priority is moving from signal to action quickly. Teams can filter, aggregate, apply thresholds, and publish reusable business signals directly from the Eventstream canvas, all from the same streaming pipeline they already use to process and route real-time data.
This gives teams a governed, no-code path to publish Business Events without building point-to-point integrations or extra custom publishing components.
Figure: Eventstream provides a built-in Business Events destination for scenarios where the logic is clearly defined, and the primary goal is to move from signal to action as quickly as possible.
Scenario: A stadium operator wants to keep fans moving safely through four entrance gates—North, South, East, and West—each instrumented with turnstile sensors that emit telemetry on every passage.
The challenge: Hundreds of arrive every minute across all gates. The challenge is not simply noticing that a line already exists, but recognizing early that congestion is building so operations can redirect staff, open overflow lanes, or rebalance arrivals before fan safety and entry experience are affected.
Goal: Detect emerging congestion at the gate level in real time, publish it as a Business Event, and trigger downstream actions such as notifying operations or starting an escalation workflow.
Business objective: Give stadium operations earlier awareness so they can intervene before crowding becomes a safety issue or wait times start to degrade the fan experience.
How Business Events help: By publishing congestion as a Business Event in Real-Time Hub, the signal becomes reusable across teams. Operations can receive a Teams alert, analytics can subscribe for reporting, and future consumers such as workflows, dashboards, or escalation systems can respond without changing the original pipeline. Watch the demo video to see it in action.
Because Business Events are published against a defined schema in Real-Time Hub, producers and consumers can work from a shared contract regardless of who built the publisher.
A single Business Event can support multiple consumers without forcing producers to build tightly coupled integrations.
Learn more about Business Events in Eventstream by exploring the overview.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.