Adjust known issues text for MQTT broker

Author: dominicbetts

articles/iot-operations/manage-mqtt-broker/howto-configure-brokerlistener.md

@@ -20,6 +20,9 @@ To customize the network access and security use the *BrokerListener* resource.
 
 Each listener port can have its own authentication and authorization rules that define who can connect to the listener and what actions they can perform on the broker. You can use *BrokerAuthentication* and *BrokerAuthorization* resources to specify the access control policies for each listener. This flexibility allows you to fine-tune the permissions and roles of your MQTT clients, based on their needs and use cases.
 
+> [!TIP]
+> You can only access the default MQTT broker deployment by using the cluster IP, TLS, and a service account token. Clients connecting from outside the cluster need extra configuration before they can connect.
+
 Listeners have the following characteristics:
 
 - You can have up to three listeners. One listener per service type of `loadBalancer`, `clusterIp`, or `nodePort`. The default *BrokerListener* named *listener* is service type `clusterIp`.

articles/iot-operations/manage-mqtt-broker/overview-iot-mq.md

@@ -39,6 +39,8 @@ MQTT broker focuses on the unique edge-native, data-plane value it can provide t
 
 MQTT broker builds on top of battle-tested Azure and Kubernetes-native security and identity concepts making it both highly secure and usable. It supports multiple authentication mechanisms for flexibility along with granular access control mechanisms all the way down to individual MQTT topic level. 
 
+> [!TIP]
+> You can only access the default MQTT broker deployment by using the cluster IP, TLS, and a service account token. Clients connecting from outside the cluster need extra configuration before they can connect.
 
 ## Azure Arc integration
 

articles/iot-operations/troubleshoot/known-issues.md

@@ -32,8 +32,6 @@ This article lists the known issues for Azure IoT Operations Preview.
 
 ## MQTT broker
 
-- You can only access the default deployment by using the cluster IP, TLS, and a service account token. Clients outside the cluster need extra configuration before they can connect. <!-- Prereq?? by design -->
-
 - You can't update the Broker custom resource after the initial deployment. You can't make configuration changes to cardinality, memory profile, or disk buffer.
 
   As a workaround, when deploying Azure IoT Operations with the [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command, you can include the `--broker-config-file` parameter with a JSON configuration file for the MQTT broker. For more information, see [Advanced MQTT broker config](https://github.com/Azure/azure-iot-ops-cli-extension/wiki/Advanced-Mqtt-Broker-Config) and [Configure core MQTT broker settings](../manage-mqtt-broker/howto-configure-availability-scale.md).