|
| 1 | +--- |
| 2 | +title: Configure dataflow endpoints for Microsoft Fabric Real-Time Intelligence |
| 3 | +description: Learn how to configure dataflow endpoints for Microsoft Fabric Real-Time Intelligence in Azure IoT Operations. |
| 4 | +author: PatAltimore |
| 5 | +ms.author: patricka |
| 6 | +ms.service: azure-iot-operations |
| 7 | +ms.subservice: azure-data-flows |
| 8 | +ms.topic: how-to |
| 9 | +ms.date: 10/30/2024 |
| 10 | +ai-usage: ai-assisted |
| 11 | + |
| 12 | +#CustomerIntent: As an operator, I want to understand how to configure dataflow endpoints for Microsoft Fabric Real-Time Intelligence in Azure IoT Operations so that I can send real-time data to Microsoft Fabric. |
| 13 | +--- |
| 14 | + |
| 15 | +# Configure dataflow endpoints for Microsoft Fabric Real-Time Intelligence |
| 16 | + |
| 17 | +To send data to Microsoft Fabric Real-Time Intelligence from Azure IoT Operations, you can configure a dataflow endpoint. This configuration allows you to specify the destination endpoint, authentication method, topic, and other settings. |
| 18 | + |
| 19 | +## Prerequisites |
| 20 | + |
| 21 | +- An [Azure IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md) instance |
| 22 | +- A [configured dataflow profile](howto-configure-dataflow-profile.md) |
| 23 | +- [Create a Fabric workspace](/fabric/get-started/create-workspaces). The default *my workspace* isn't supported. |
| 24 | +- [Create an Event Stream](/fabric/real-time-intelligence/event-streams/create-manage-an-eventstream#create-an-eventstream) |
| 25 | +- [Add a Custom Endpoint as a source](/fabric/real-time-intelligence/event-streams/add-source-custom-app#add-custom-endpoint-data-as-a-source) |
| 26 | + |
| 27 | +> [!NOTE] |
| 28 | +> Event Stream supports multiple input sources including Azure Event Hubs. If you have an existing dataflow to Azure Event Hubs, you can bring that into Fabric as shown in the [Quickstart](../get-started-end-to-end-sample/quickstart-get-insights.md#ingest-data-into-real-time-intelligence). This article shows you how to flow real-time data directly into Microsoft Fabric without any other hops in between. |
| 29 | +
|
| 30 | +## Retrieve Custom Endpoint connection details |
| 31 | +Retrieve the [Kafka-compatible connection details for the Custom Endpoint](/fabric/real-time-intelligence/event-streams/add-source-custom-app#kafka). You need: |
| 32 | + |
| 33 | +:::image type="content" source="media/howto-configure-fabric-real-time-intelligence/event-stream-kafka.png" alt-text="Screenshot in Microsoft Fabric that has the Custom Endpoint connection details."::: |
| 34 | + |
| 35 | +#### Hostname |
| 36 | +The bootstrap server address is used for the hostname property in Dataflow endpoint. |
| 37 | + |
| 38 | +#### Topic name |
| 39 | +The event hub name is used as the Kafka topic and is of the form *es_xxxxxxx*. |
| 40 | + |
| 41 | +#### Custom Endpoint connection string |
| 42 | +The connection string with the primary key. |
| 43 | + |
| 44 | + |
| 45 | +## Create a Microsoft Fabric Real-Time Intelligence dataflow endpoint |
| 46 | + |
| 47 | +To configure a dataflow endpoint for Microsoft Fabric Real-Time Intelligence, you need to use Simple Authentication and Security Layer (SASL) based authentication. |
| 48 | + |
| 49 | +Azure Key Vault is the recommended way to sync the connection string to the Kubernetes cluster so that it can be referenced in the dataflow. [Secure settings](../deploy-iot-ops/howto-enable-secure-settings.md) must be enabled to configure this endpoint using the operations experience Portal. |
| 50 | + |
| 51 | +# [Portal](#tab/portal) |
| 52 | + |
| 53 | +1. In the IoT Operations portal, select the **Dataflow endpoints** tab. |
| 54 | +1. Under **Create new dataflow endpoint**, select **Microsoft Fabric Real-Time Intelligence** > **New**. |
| 55 | + |
| 56 | + :::image type="content" source="media/howto-configure-fabric-real-time-intelligence/event-stream-sasl.png" alt-text="Screenshot using operations experience to create a new Fabric Real-Time Intelligence dataflow endpoint."::: |
| 57 | + |
| 58 | +1. Enter the following settings for the endpoint: |
| 59 | + |
| 60 | + | Setting | Description | |
| 61 | + | --------------------- | ------------------------------------------------------------------------------------------------- | |
| 62 | + | Name | The name of the dataflow endpoint. | |
| 63 | + | Host | The hostname of the Event Stream Custom Endpoint in the format `*.servicebus.windows.net:9093`. Use the bootstrap server address noted previously. | |
| 64 | + | Authentication method | *SASL* is the currently the only supported authentication method. | |
| 65 | + | SASL type | Choose *Plain* | |
| 66 | + | Synced secret name | Name of secret that will be synced to the Kubernetes cluster. You can choose any name. | |
| 67 | + | Username reference of token secret | Create a new or choose an existing Key Vault reference. The secret value must be the literal string *$ConnectionString*. It isn't an environment variable. | |
| 68 | + | Password reference of token secret | Create a new or choose an existing Key Vault reference. The secret value must be the Custom Endpoint connection string noted earlier. | |
| 69 | + |
| 70 | +1. Select **Apply** to provision the endpoint. |
| 71 | + |
| 72 | +# [Bicep](#tab/bicep) |
| 73 | + |
| 74 | +Identical to [SASL instructions for the Event Hubs endpoint](/azure/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint?tabs=bicep#sasl). |
| 75 | + |
| 76 | +# [Kubernetes (preview)](#tab/kubernetes) |
| 77 | + |
| 78 | +Identical to [SASL instructions for the Event Hubs endpoint](/azure/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint?tabs=kubernetes#sasl). |
| 79 | + |
| 80 | +--- |
| 81 | + |
| 82 | +## Advanced settings |
| 83 | + |
| 84 | +The advanced settings for this endpoint are identical to the [advanced settings for Azure Event Hubs endpoints](howto-configure-kafka-endpoint.md#advanced-settings). |
| 85 | + |
| 86 | +## Next steps |
| 87 | + |
| 88 | +To learn more about dataflows, see [Create a dataflow](howto-create-dataflow.md). |
0 commit comments