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-endpoint.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,9 +168,9 @@ fabricOneLakeSettings:
168
168
169
169
The following authentication methods are available for Microsoft Fabric OneLake dataflow endpoints. For more information about enabling secure settings by configuring an Azure Key Vault and enabling workload identities, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
170
170
171
-
Before you create the dataflow endpoint, assign workspace *Contributor* role to the IoT Operations extension that grants permission to write to the Fabric lakehouse.
171
+
Before you create the dataflow endpoint, assign workspace *Contributor* role to the IoT Operations extension that grants permission to write to the Fabric lakehouse. You can find the extension name in the Azure IoT Operations instance overview page under **Essentials** > **Arc extension**.
172
172
173
-

173
+

174
174
175
175
To learn more, see [Give access to a workspace](/fabric/get-started/give-access-workspaces).
| Host | The hostname of the Kafka broker in the format `<NAMEPSACE>.servicebus.windows.net:9093`. Include port number `9093` in the host setting for Event Hubs. |
62
-
| Authentication method| The method used for authentication. Choose *System assigned managed identity*|
61
+
| Host | The hostname of the Kafka broker in the format `<NAMESPACE>.servicebus.windows.net:9093`. Include port number `9093` in the host setting for Event Hubs. |
62
+
| Authentication method| The method used for authentication. Choose *System assigned managed identity*, *User assigned managed identity*, or *SASL*. |
63
+
| Client ID | The client ID of the user-assigned managed identity. Required if using *User assigned managed identity*. |
64
+
| Tenant ID | The tenant ID of the user-assigned managed identity. Required if using *User assigned managed identity*. |
65
+
| SASL type | Choose `Plain`. |
66
+
| Synced secret name | Enter a name of the Kubernetes secret that contains the connection string. Required if using *SASL*. |
67
+
| Username reference or token secret | The reference to the username or token secret used for SASL authentication. Either pick it from the Key Vault list or create a new one. The value must be `$ConnectionString`. |
68
+
| Password reference of token secret | The reference to the password or token secret used for SASL authentication. Either pick it from the Key Vault list or create a new one. The value must be in the format of `Endpoint=sb://<NAMESPACE>.servicebus.windows.net/;SharedAccessKeyName=<KEY-NAME>;SharedAccessKey=<KEY>`. |
63
69
64
70
1. Select **Apply** to provision the endpoint.
65
71
@@ -234,7 +240,7 @@ To configure a dataflow endpoint for non-Event-Hub Kafka brokers, set the host,
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/howto-configure-mqtt-endpoint.md
+11-6Lines changed: 11 additions & 6 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: 11/11/2024
9
+
ms.date: 11/14/2024
10
10
ai-usage: ai-assisted
11
11
12
12
#CustomerIntent: As an operator, I want to understand how to understand how to configure dataflow endpoints for MQTT sources and destinations in Azure IoT Operations so that I can send data to and from MQTT brokers.
@@ -126,8 +126,8 @@ You can also create new local MQTT broker endpoints with custom settings. For ex
| Host | The hostname of the MQTT broker endpoint in the format `<hostname>.<port>`. |
369
-
| Authentication method | The method used for authentication. Choose *System assigned managed identity*, *User assigned managed identity*, or *Service account token*. |
370
-
| Service audience | The audience for the service account token. Required if using service account token. |
374
+
| Authentication method | The method used for authentication. Choose *System assigned managed identity*, *Kubernetes service account token*, or *None*. |
375
+
| Service audience | The audience for the service account token. Required if using Kubernetes service account token. |
371
376
| Client ID | The client ID of the user-assigned managed identity. Required if using *User assigned managed identity*. |
372
377
| Tenant ID | The tenant ID of the user-assigned managed identity. Required if using *User assigned managed identity*. |
373
378
| Access token secret name | The name of the Kubernetes secret containing the SAS token. Required if using *Access token*. |
0 commit comments