You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md
+76-26Lines changed: 76 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: patricka
6
6
ms.service: azure-iot-operations
7
7
ms.subservice: azure-data-flows
8
8
ms.topic: how-to
9
-
ms.date: 10/30/2024
9
+
ms.date: 03/20/2025
10
10
ai-usage: ai-assisted
11
11
12
12
#CustomerIntent: As an operator, I want to understand how to configure data flow endpoints for Microsoft Fabric Real-Time Intelligence in Azure IoT Operations so that I can send real-time data to Microsoft Fabric.
@@ -20,26 +20,29 @@ To send data to Microsoft Fabric Real-Time Intelligence from Azure IoT Operation
20
20
21
21
- An [Azure IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md) instance
22
22
-[Create a Fabric workspace](/fabric/get-started/create-workspaces). The default *my workspace* isn't supported.
23
-
-[Create an Event Stream](/fabric/real-time-intelligence/event-streams/create-manage-an-eventstream#create-an-eventstream)
24
-
-[Add a Custom Endpoint as a source](/fabric/real-time-intelligence/event-streams/add-source-custom-app#add-custom-endpoint-data-as-a-source)
23
+
-[Create an event stream](/fabric/real-time-intelligence/event-streams/create-manage-an-eventstream#create-an-eventstream)
24
+
-[Add a custom endpoint as a source](/fabric/real-time-intelligence/event-streams/add-source-custom-app#add-custom-endpoint-data-as-a-source)
25
25
26
26
> [!NOTE]
27
27
> Event Stream supports multiple input sources including Azure Event Hubs. If you have an existing data flow 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.
28
28
29
-
## Retrieve Custom Endpoint connection details
30
-
Retrieve the [Kafka-compatible connection details for the Custom Endpoint](/fabric/real-time-intelligence/event-streams/add-source-custom-app#kafka). You need:
29
+
## Retrieve custom endpoint connection details
31
30
32
-
:::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.":::
31
+
Retrieve the [Kafka-compatible connection details for the custom endpoint](/fabric/real-time-intelligence/event-streams/add-source-custom-app#kafka). The connection details are used to configure the data flow endpoint in Azure IoT Operations.
33
32
34
-
#### Hostname
35
-
The bootstrap server address is used for the hostname property in data flow endpoint.
36
33
37
-
#### Topic name
38
-
The event hub name is used as the Kafka topic and is of the form *es_xxxxxxx*.
39
-
40
-
#### Custom Endpoint connection string
41
-
The connection string with the primary key.
34
+
1. The connection details are in the Fabric portal under the **Destinations** section of your event stream.
35
+
1. In the details panel for the custom endpoint, select **Kafka** protocol.
36
+
1. Select the **SAS Key Authentication** section to view the connection details.
37
+
1. Copy the details for the values for the **Bootstrap server**, **Topic name**, and **Connection string-primary key**. You use these values to configure the data flow endpoint.
42
38
39
+
:::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.":::
| Bootstrap server | The bootstrap server address is used for the hostname property in data flow endpoint. |
44
+
| Topic name | The event hub name is used as the Kafka topic and is of the the format *es_aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb*. |
45
+
| Connection string-primary key | The connection string with the primary key. |
43
46
44
47
## Create a Microsoft Fabric Real-Time Intelligence data flow endpoint
45
48
@@ -49,32 +52,79 @@ Azure Key Vault is the recommended way to sync the connection string to the Kube
49
52
50
53
# [Portal](#tab/portal)
51
54
52
-
1. In the IoT Operations portal, select the **Data flow endpoints** tab.
55
+
1. In the IoT Operations experience portal, select the **Data flow endpoints** tab.
53
56
1. Under **Create new data flow endpoint**, select **Microsoft Fabric Real-Time Intelligence** > **New**.
54
57
55
-
:::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 data flow endpoint.":::
56
58
57
-
1. Enter the following settings for the endpoint:
59
+
1. Enter the following settings for the endpoint.
60
+
61
+
:::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 data flow endpoint.":::
| Host | The hostname of the Event Stream Custom Endpoint in the format `*.servicebus.windows.net:9093`. Use the bootstrap server address noted previously. |
63
-
| Authentication method |*SASL* is the currently the only supported authentication method. |
| Host | The hostname of the event stream custom endpoint in the format `*.servicebus.windows.net:9093`. Use the bootstrap server address noted previously. |
67
+
| Authentication method |*SASL* is currently the only supported authentication method. |
64
68
| SASL type | Choose *Plain*|
65
-
| Synced secret name | Enter a name for the syned secret. A Kubernetes secret with this name will be created on the cluster. |
66
-
| Username reference of token secret | Create a new or choose an existing Key Vault reference. The secret value must be exactly the text **$ConnectionString** (literal string, not an environment variable reference). |
67
-
| 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
+
| Synced secret name | Enter a name for the synced secret. A Kubernetes secret with this name is created on the cluster. |
70
+
71
+
Select **Add reference** to create a new or choose an existing Key Vault reference for the username and password references.
72
+
73
+
For **Username reference of token secret**, the secret value must be exactly the literal string **$ConnectionString** not an environmentent variable reference.
74
+
75
+
:::image type="content" source="media/howto-configure-fabric-real-time-intelligence/username-reference.png" alt-text="Screenshot to create a username reference in Azure Key Vault.":::
76
+
77
+
For **Password reference of token secret**, the secret value must be the connection string with the primary key from the event stream custom endpoint.
78
+
79
+
:::image type="content" source="media/howto-configure-fabric-real-time-intelligence/password-reference.png" alt-text="Screenshot to create a password reference in Azure Key Vault.":::
68
80
69
81
1. Select **Apply** to provision the endpoint.
70
82
71
83
# [Bicep](#tab/bicep)
72
84
73
-
Identical to [SASL instructions for the Event Hubs endpoint](/azure/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint?tabs=bicep#sasl).
85
+
Create a Bicep `.bicep` file with the following content.
86
+
87
+
```bicep
88
+
kafkaSettings: {
89
+
authentication: {
90
+
method: 'Sasl' // Or ScramSha256, ScramSha512
91
+
saslSettings: {
92
+
saslType: 'Plain' // Or ScramSha256, ScramSha512
93
+
secretRef: '<SECRET_NAME>'
94
+
}
95
+
}
96
+
}
97
+
```
98
+
99
+
Then, deploy via Azure CLI.
100
+
101
+
```azurecli
102
+
az deployment group create --resource-group <RESOURCE_GROUP> --template-file <FILE>.bicep
103
+
```
74
104
75
105
# [Kubernetes (preview)](#tab/kubernetes)
76
106
77
-
Identical to [SASL instructions for the Event Hubs endpoint](/azure/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint?tabs=kubernetes#sasl).
0 commit comments