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-mqtt-endpoint.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,7 +127,7 @@ You can also create new local MQTT broker endpoints with custom settings. For ex
127
127
| Host | The hostname and port of the MQTT broker. Use the format `<hostname>:<port>`|
128
128
| Authentication method | The method used for authentication. Choose [*Service account token*](#kubernetes-service-account-token-sat), or [*X509 certificate*](#x509-certificate)|
129
129
| Service audience | The audience for the service account token. Required if using *Service account token*. |
130
-
| X509 client certificate | The X.509 client certificate used for authentication. Required if using *X509 certificate*. |
130
+
| X509 client certificate | The X.509 client certificate used for authentication. Required if using *X509 certificate*. You can upload industry-standard multi-line X509 certificates improving device authentication management, security, and flexibility.|
131
131
| X509 client key | The private key corresponding to the X.509 client certificate. Required if using *X509 certificate*. |
132
132
| X509 intermediate certificates | The intermediate certificates for the X.509 client certificate chain. Required if using *X509 certificate*. |
133
133
@@ -372,7 +372,7 @@ For other MQTT brokers, you can configure the endpoint, TLS, authentication, and
372
372
| Host | The hostname of the MQTT broker endpoint in the format `<hostname>.<port>`. |
373
373
| Authentication method | The method used for authentication. Choose [*Service account token*](#kubernetes-service-account-token-sat), or [*X509 certificate*](#x509-certificate). |
374
374
| Service audience | The audience for the service account token. Required if using *Service account token*. |
375
-
| X509 client certificate | The X.509 client certificate used for authentication. Required if using *X509 certificate*. |
375
+
| X509 client certificate | The X.509 client certificate used for authentication. Required if using *X509 certificate*. You can upload industry-standard multi-line X509 certificates improving device authentication management, security, and flexibility. |
376
376
| X509 client key | The private key corresponding to the X.509 client certificate. Required if using *X509 certificate*. |
377
377
| X509 intermediate certificates | The intermediate certificates for the X.509 client certificate chain. Required if using *X509 certificate*. |
378
378
@@ -614,7 +614,7 @@ If you select **Create new**, enter the following settings:
614
614
| Setting | Description |
615
615
| ------- | ----------- |
616
616
| Secret name | The name of the secret in Azure Key Vault. Pick a name that is easy to remember to select the secret later from the list. |
617
-
| Secret value | The certificate, private key, or intermediate certificates in PEM format. |
617
+
| Secret value | The certificate, private key, or intermediate certificates in PEM format. You can upload industry-standard multi-line X509 certificates improving device authentication management, security, and flexibility. |
618
618
| Set activation date | If turned on, the date when the secret becomes active. |
619
619
| Set expiration date | If turned on, the date when the secret expires. |
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/howto-create-dataflow.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -313,10 +313,7 @@ When the source is an MQTT (Event Grid included) endpoint, you can use the MQTT
313
313
314
314
# [Portal](#tab/portal)
315
315
316
-
In the operations experience data flow **Source details**, select **Message broker**, then use the **Topic** field to specify the MQTT topic filter to subscribe to for incoming messages.
317
-
318
-
> [!NOTE]
319
-
> Only one topic filter can be specified in the operations experience. To use multiple topic filters, use Bicep or Kubernetes.
316
+
In the operations experience data flow **Source details**, select **Message broker**, then use the **Topic(s)** field to specify the MQTT topic filters to subscribe to for incoming messages. You can add multiple MQTT topics by selecting **Add row** and entering a new topic.
0 commit comments