What’s new for Business Events and real-time events in Microsoft Fabric
Microsoft Fabric helps teams react when those moments happen. Real-Time Hub provides a common place to discover event sources, connect consumers, and move from a signal to an action. With Business Events now generally available and new Fabric Events capabilities arriving in the September 2026 release, organizations can connect business meaning and platform operations through one event-driven model. One model, three outcomes Publish a governed signal once, let operational teams react independently, and retain the same event for real-time and historical analysis. Turn business meaning into a governed event (Generally Available) A Business Event represents a meaningful occurrence or state change that matters to the organization. It is not raw telemetry or a diagnostic record. It captures business intent: a payment failed, a cold-chain shipment is at risk, inventory fell below a threshold, or an approval is required. Every Business Event follows a versioned schema in an Event Schema Set. Publishers and consumers agree on the event name, fields, data types, and meaning before they integrate. This contract reduces point-to-point dependencies because the publisher does not need to know which teams will react, and consumer teams can add or change their responses without modifying publisher code. Use the Fabric experience closest to the business logic Business Events meet teams where their detection logic already runs. A notebook can publish the result of analytics or machine learning. A User Data Function can emit an event from reusable domain logic after validating an application request. Activator can convert a condition detected in Power BI, a Real-Time Dashboard, KQL, or a warehouse query into a governed signal. This flexibility keeps ownership clear. The team that understands the business condition owns when the event is published. The Event Schema Set owns the shared contract. Downstream teams own how they respond. The following animation follows a cold-chain shipment risk event through Real-Time Hub. It shows how a user opens the governed event, reviews its schema and connected consumers, publishes representative data, and verifies the event flow before relying on production logic. By bringing the event contract, publishers, consumers, and validation tools into one experience, Real-Time Hub gives teams a shared view of how an event moves through the system. Teams can use that visibility to confirm that the event structure and connections work as expected before the production publisher is ready. Validate integrations before production code is ready A faster inner loop is one of the most practical advantages of the new experience. The sample publisher generates a JSON payload from the selected schema, so teams can replace the values or upload a representative file and publish an event in seconds. Data preview then shows recent payloads for each publisher and consumer together with event metadata and the active schema version. Teams can publish a sample Business Event, inspect Business Events data, and verify the contract, permissions, subscription, and routing before connecting the live publisher. This removes temporary test code and gives both sides of the integration direct evidence that the expected payload arrived. For application-oriented scenarios, the guided User Data Function publisher experience prepares the Fabric connection and sample publisher code from Real-Time Hub. Developers can focus on the business condition and payload instead of integration plumbing. Process, act, and analyze without changing the publisher After an event is published, independent consumers can choose the response that matches their responsibility. Activator can send notifications, start workflows, or invoke downstream logic. Eventhouse can retain every event in a dedicated Kusto Query Language (KQL) table for operational monitoring, historical analysis, Real-Time Dashboards, anomaly detection, and AI or machine learning scenarios. React immediately to a high-severity condition with an alert or automated action. Route and transform the signal for downstream destinations through Eventstream. Retain durable evidence for audit, trends, service-level analysis, and continuous improvement. Eventstream as a Business Events consumer is in Preview. It can filter, enrich, transform, route, and fan out an existing governed signal while the original publisher remains independent. Teams can add Business Events from an Eventstream or start from the event in Real-Time Hub through a prepopulated consumer flow. Review the Eventstream consumer guidance for configuration details. For the generally available paths, learn how to publish Business Events from Activator and analyze Business Events in Eventhouse. Monitor capacity health as events occur (Generally Available) Capacity Overview Events include two event types. Capacity Summary events provide a recurring high-level view of utilization and health, while Capacity State events identify changes such as pause, resume, and throttling-related conditions. Capacity administrators no longer need to rely only on periodic checks to discover that action may be required. These signals can drive no-code alerts in Activator, automated workflows, or Eventstream processing. They can also land in Eventhouse for KQL analysis, historical retention, and dashboards that help teams recognize patterns before users are affected. Follow the capacity health monitoring tutorial and review the Capacity Overview Events schema to get started. Find the operations driving capacity pressure (Preview) Capacity Operation Events extend capacity visibility from overall health to operation-level root cause. Fabric emits an event for each operation that consumes capacity, with details such as the workspace and item, capacity unit consumption, duration, throttling delay, status, and smoothing-window attribution. Administrators can identify which refreshes consumed the most capacity, which operations were throttled, and where repeated failures originate. Activator can respond when an expensive operation crosses a threshold, while Eventstream and Eventhouse support routing, chargeback analysis, governance, and longer-term optimization. or troubleshooting utilization, throttling, and failures. Review the Capacity Operation Events documentation for the complete schema. React to item deletion and recovery (Generally Available) Real-Time Hub now includes workspace item lifecycle events for soft-delete and recovery operations. Teams can subscribe when an item is moved into the recovery state, when recovery succeeds, or when either operation fails. These events make item lifecycle activity available to the same alerting and stream-processing tools already used for other Fabric Events. A workspace administrator can receive an alert when a critical item is accidentally soft deleted, trigger a governance workflow, or retain the event for audit and historical analysis. Because the new events use the existing workspace item event model, teams can extend current consumers instead of building a separate monitoring path. Explore the Fabric workspace item events documentation for event names and schema details. See how Business Events accelerate discount approvals In the Protect the Margin with Business Events in Fabric demonstration, a sales application sends proposal details to a User Data Function. The function applies discount and margin policies, then publishes the governed Sales.Deals.DiscountApprovalRequired event only when manager or executive approval is required. The team first creates the event contract, connects Eventstream, publishes representative samples, and confirms delivery with Data preview. It then connects the production function and submits a live proposal through the same validated path. Eventstream remains independent from the sales application and can send the event to a Spark notebook for scoring, enrichment, or approval analytics. Watch the end-to-end demonstration Watch Protect the Margin with Business Events in Fabric to see how a business signal connects sales policy, real-time validation, and independent downstream processing. Get started Start with one event that is easy to explain and costly to miss. Define the contract, publish a representative sample, verify delivery, and add one consumer that produces a measurable operational or analytical outcome. Once the pattern is proven, additional teams can subscribe without changing the original publisher. Choose the event path that matches your scenario: explore the Business Events overview to publish governed business signals, or the Fabric Events and Azure Events overview to react to changes across Fabric or bring Azure resource events into Fabric. Visit the Fabric Events developer site for architecture guidance, end-to-end scenarios, and samples, and use the Real-Time Hub overview to connect your first event to an action, a stream-processing path, or durable analytical history.
From factory floor to Fabric: Securely stream private data with Eventstream
Bring private operational data into Real-Time Intelligence Real-time operational data is often generated in places that are intentionally isolated from the public internet. Factory MQTT brokers, enterprise Kafka clusters, database change data capture sources, and messaging systems may live in an on-premises network, an Azure virtual network, or a private environment in another cloud. Microsoft Fabric Eventstream virtual network and on-premises support gives streaming connectors a managed path to approved private sources. The source stays behind its network boundary while Eventstream retrieves events for transformation, routing, analytics, and action. Network teams continue to control connectivity, and data teams use a shared network reference in Fabric instead of exposing a public endpoint. A manufacturing industry data scenario Consider a manufacturing environment where sensors, machines, and vehicles publish events every second to an MQTT broker in the factory network. Operations teams want to monitor equipment health, detect production issues, and respond to changing conditions. The analytics team wants to route those events through Eventstream to Eventhouse and Lakehouse, then use them in real-time dashboards and alerts. The MQTT broker is private by design. The security team doesn't permit inbound access from the public internet, and the broker has no publicly routable endpoint. The data team needs a connection model that reaches the broker through the organization's approved network path. A challenge shared across industries The challenge is common across industries. Valuable operational sources often live in on-premises networks, Azure virtual networks, or private environments in other clouds because those systems were intentionally designed not to be publicly accessible. Eventstream virtual network and on-premises support provide a secure, managed pathway for connecting those sources to Fabric. Network administrators retain control of the network boundary, while data engineers can use the approved streaming virtual network data gateway when creating Eventstream connections. Use an Azure virtual network as the controlled bridge Rather than making the MQTT broker public, data team partners with the networking team to use a customer-owned Azure virtual network as an intermediary bridge. This is the core of the Eventstream virtual network architecture. The team registers the Microsoft.MessagingConnectors resource provider, creates an Azure virtual network, and prepares a subnet delegated to Microsoft.MessagingConnectors. Because the MQTT broker is in the factory network, the networking team connects that network to Azure through the organization’s private connectivity approach, such as VPN or Azure ExpressRoute. Before moving forward, the team verifies that a client in the Azure virtual network can reach the MQTT broker. The broker remains private, but the Azure virtual network now has a secure route to it. Enable Fabric permission to use the network The private route now exists, but Eventstream still needs permission to use the Azure virtual network. Data team then works with Fabric admin to enable the workspace identity for the Fabric workspace that contains the Eventstream. The Azure administrator then grants the workspace identity the Network Contributor role on the Azure virtual network. Think of this as authorizing fabric to use approved network path. The network team created the bridge. The role assignment authorizes the Fabric workspace to use the prepared Azure VNet for connector injection. Bring the network reference into Fabric Inside Fabric, data team creates a streaming virtual network data gateway from Manage connections and gateways. The gateway represents the Azure virtual network and subnet resources within Fabric and passes the network information needed for streaming connector virtual network injection. The streaming virtual network data gateway is not a traditional gateway server. It is a Fabric reference to the Azure network resources already prepared by the networking team. d selects the prepared Azure VNet and delegated subnet. Connect and publish the MQTT source With the gateway available, data engineer returns to Eventstream and adds an MQTT source. During connection setup, select the streaming virtual network data gateway, supply the MQTT connection information and credentials, complete the source configuration, and publish the Eventstream. When the Eventstream is published, Fabric injects the streaming connector into the delegated subnet. The connector makes an outbound connection through the private route to retrieve MQTT events. No inbound public endpoint is required on the factory broker. Eventstream can then transform and route the events to Fabric destinations. Turning factory signals into real-time intelligence Once the Eventstream is running, factory telemetry starts flowing into Fabric. Data engineering team can transform and route the events to Eventhouse for real-time analytics, persist data in Lakehouse, create operational dashboards, and configure alerts for important conditions. The factory systems remain behind the company’s network boundary while the analytics team gains access to the operational signals needed for timely decisions. Plan for operational boundaries This connection model manages connector placement, but it doesn't replace the organization's network design. Teams still own private routing, DNS resolution, firewall rules, source credentials, certificates, and source availability. The same model applies to many supported streaming sources, including Apache Kafka, Azure Service Bus, Amazon Kinesis Data Streams, Google Cloud Pub/Sub, HTTP, and several CDC connectors. Connector-specific authentication and network requirements still apply. For prerequisites and the complete configuration sequence, follow the Eventstream streaming connector virtual network and on-premises support guide. Next steps Review the architecture with your networking and Fabric administrators, then identify one private streaming source for a controlled validation. Confirm network reachability before configuring Eventstream, document the delegated subnet and workspace permissions, and verify the complete event path after publishing. If you find this blog helpful, please give it a thumbs-up! Have ideas for what you'd like to see next? Drop us a comment or reach out to [email protected] — we'd love to hear what real-time scenarios you're building and what topics you'd like us to cover in future posts. To suggest improvements or additional scenarios, submit feedback through Fabric Ideas.From Business Events, Fabric Events, and Azure Events to Real-Time Hub
Welcome to the eighth and final post in our Business Events, Fabric Events, and Azure Events series for Microsoft Fabric. This series takes you from foundational event-driven concepts to practical implementation patterns that help teams turn meaningful business moments into trusted signals, decisions, and actions across Fabric.Designing scalable Business Events in Microsoft Fabric
Welcome to the seventh post in our Business Events, Fabric Events, and Azure Events series for Microsoft Fabric. This series takes you from foundational event-driven concepts to practical implementation patterns that help teams turn meaningful business moments into trusted signals, decisions, and actions across Fabric.Five Business Event scenarios and the pattern they share
Welcome to the sixth post in our Business Events, Fabric Events, and Azure Events series for Microsoft Fabric. This series takes you from foundational event-driven concepts to practical implementation patterns that help teams turn meaningful business moments into trusted signals, decisions, and actions across Fabric.Reacting to Business Events with Activator and Eventhouse
Welcome to the fifth post in our Business Events, Fabric Events, and Azure Events series for Microsoft Fabric. This series takes you from foundational event-driven concepts to practical implementation patterns that help teams turn meaningful business moments into trusted signals, decisions, and actions across Fabric.Publishing Business Events from Fabric workloads
Welcome to the fourth post in our Business Events, Fabric Events, and Azure Events series for Microsoft Fabric. This series takes you from foundational event-driven concepts to practical implementation patterns that help teams turn meaningful business moments into trusted signals, decisions, and actions across Fabric.Design a Business Event schema that consumers can act on
Welcome to the third post in our Business Events, Fabric Events, and Azure Events series for Microsoft Fabric. Whether you're new to event-driven architectures or building enterprise-grade event-driven solutions, this series takes you from foundational concepts to real-world implementation patterns across Microsoft Fabric.Choose the right event pillar in Microsoft Fabric: Business Events, Fabric Events, and Azure Events
Welcome to the second post in our Business Events, Fabric Events, and Azure Events series for Microsoft Fabric. Whether you're new to event-driven architectures or looking to build enterprise-grade event-driven solutions, this series will take you from foundational concepts to real-world implementation patterns across Microsoft Fabric.Build event-driven architectures in Fabric with Real-Time Hub
Learn the fundamentals of event-driven architecture in Microsoft Fabric. Explore Real-Time Hub, understand the three Fabric event pillars, and discover how Business Events enable workloads to react to meaningful business signals in real time.
