diff --git a/articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md b/articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md
index aa21be15bad0a..efe09ffd786fc 100644
--- a/articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md
+++ b/articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md
@@ -62,7 +62,8 @@ Azure Key Vault is the recommended way to sync the connection string to the Kube
     | Host                  | The hostname of the Event Stream Custom Endpoint in the format `*.servicebus.windows.net:9093`. Use the bootstrap server address noted previously. |
     | Authentication method | *SASL* is the currently the only supported authentication method. |
     | SASL type             | Choose *Plain* |
-    | Synced secret name    | Create or select a Key Vault secret where the secret's value is exactly the text **$ConnectionString** (literal string, not an environment variable reference). |
+    | Synced secret name    | Enter a name for the syned secret. A Kubernetes secret with this name will be created on the cluster. |
+    | 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). |
     | 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. |
 
 1. Select **Apply** to provision the endpoint.
@@ -83,4 +84,4 @@ The advanced settings for this endpoint are identical to the [advanced settings
 
 ## Next steps
 
-To learn more about data flows, see [Create a data flow](howto-create-dataflow.md).
\ No newline at end of file
+To learn more about data flows, see [Create a data flow](howto-create-dataflow.md).