Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
After you create an eventstream in Microsoft Fabric, you can route the data to different destinations. For a list of destinations that you can add to your eventstream, see Supported destinations.
Prerequisites
To add a destination to an eventstream, you need the following prerequisites:
- Access to a workspace in the Fabric capacity license mode (or) the Trial license mode with Contributor or higher permissions.
- For an Eventhouse, Lakehouse, or Fabric Activator destination, access to the workspace where the destination is located with Contributor or higher permissions.
Supported destinations
Fabric event streams support the following destinations. Use links in the table to navigate to articles about how to add specific destinations.
Note
Enhanced capabilities are enabled by default when you create eventstreams. If you have eventstreams that you created via standard capabilities, those eventstreams will continue to work. You can still edit and use them as usual. We recommend that you create a new eventstream to replace standard eventstreams so that you can take advantage of additional capabilities and benefits of enhanced eventstreams.
| Destination | Description |
|---|---|
| Custom endpoint (custom app in standard capability) | Use this destination to route your real-time events to a custom endpoint. You can connect your own applications to the eventstream and consume the event data in real time. This destination is useful when you want to send real-time data to a system outside Microsoft Fabric. |
| Eventhouse | This destination lets you ingest your real-time event data into an eventhouse, where you can use the powerful Kusto Query Language (KQL) to query and analyze the data. With the data in the eventhouse, you can gain deeper insights into your event data and create rich reports and dashboards. You can choose between two ingestion modes: Direct ingestion and Event processing before ingestion. |
| Lakehouse | This destination gives you the ability to transform your real-time events before ingesting them into your lakehouse. Real-time events are converted into Delta Lake format and then stored in the designated lakehouse tables. This destination supports data warehousing scenarios. |
| Derived stream | You can create this specialized type of destination after you add stream operations, such as Filter or Manage Fields, to an eventstream. The derived stream represents the transformed default stream after stream processing. You can route the derived stream to multiple destinations in Fabric and view the derived stream in the real-time hub. |
| Fabric Activator (preview) | You can use this destination to directly connect your real-time event data to Fabric Activator. Activator is a type of intelligent agent that contains all the information necessary to connect to data, monitor for conditions, and act. When the data reaches certain thresholds or matches other patterns, Activator automatically takes appropriate action, such as alerting users or starting Power Automate workflows. |
Note
An eventstream can support up to 11 combined sources and destinations only when using the following types:
- Source: Custom endpoint.
- Destinations: Custom endpoint and Eventhouse with Direct ingestion.
Any sources or destinations not included in the list above, and destinations not appended to the default stream, don't count toward this limit.
Manage a destination
To edit or remove an Eventstream destination, switch to Edit mode first. Then you can make changes to the destination on the canvas. After completing the required changes, publish the Eventstream to apply them.
| Destination | Description |
|---|---|
| Custom app | Use this destination to route your real-time events to a custom application. You can connect your own applications to the eventstream and consume the event data in real time. This ability is useful when you want to send real-time data to a system outside Microsoft Fabric. |
| KQL database | This destination enables you to ingest your real-time event data into a Kusto Query Language (KQL) database, where you can use the power of KQL to query and analyze the data. With the data in the Kusto database, you can gain deeper insights into your event data and create rich reports and dashboards. You can choose between two ingestion modes: Direct ingestion and Event processing before ingestion. |
| Lakehouse | This destination gives you the ability to transform your real-time events before ingesting events into your lakehouse. Real-time events are converted into Delta Lake format and then stored in the designated lakehouse tables. This ability helps with your data warehousing scenarios. To learn more about how to use the event processor for real-time data processing, see Process event data with the event processor editor. |
| Fabric Activator | You can use this destination to directly connect your real-time event data to Fabric Activator. Activator is a type of intelligent agent that contains all the information necessary to connect to data, monitor for conditions, and act. When the data reaches certain thresholds or matches other patterns, Activator automatically takes appropriate action, such as alerting users or starting Power Automate workflows. |
Note
An eventstream can support up to 11 combined sources and destinations only when using the following types:
- Source: Custom endpoint.
- Destinations: Custom endpoint and Eventhouse with Direct ingestion.
Any sources or destinations not included in the list above, and destinations not appended to the default stream, don't count toward this limit.
Manage a destination
You can edit or remove an eventstream destination through either the navigation pane or the canvas.
When you select Edit, the edit pane opens in the right side of the main editor. You can modify the configuration as you wish, including the event transformation logic, through the event processor editor.
