Hello, I am setting up an integration between VTSCADALight and [the Azure Event Grid MQTT Broker](https://learn.microsoft.com/en-us/azure/event-grid/mqtt-overview). I have provisioned a certificate and an Event Grid namespace, and demonstrated using [MQTTX](https://mqttx.app/) that I am able to connect with the certificate from my host to the Event Grid's MQTT Broker and send messages. Doing so requires specifying mqtts:// as the protocol, 8883 as the port, and using the SAN value in the cert as both the Client ID and Username of the MQTT connection request. Between the TCP/IP Port tag's configuration, which specifies the broker's address and 8883 port, as well as specifies the same cert for use in mutual authentication, and the MQTT Client driver which specifies the Client ID and Username, these properties seem to be achieved. However, in the Tag Browser, the Port's value is 260 (intermittently 0), while the MQTT Client Driver's value alternates between 5 and 9. Further, when I try to Plot the TCP/IP Port's value, the chart shows up empty. I know from the [MQTT Client Driver](https://www.vtscada.com/help/Content/D_Tags/D_MQTT_ErrMsg.htm?tocpath=Reference%7CTag%20Reference%7CCommunication%20Driver%20Tags%7CMQTT%20Client%20Driver%7C_____3) documentation that 5 means an Authorization Error and 9 means Timeout waiting for CONNACK. And, I know from the [TCP/IP Port Tags](https://www.vtscada.com/help/Content/D_Tags/Dev_TCPPort.htm) documentation that 260 means the connection was lost. This leads me to the following questions: - Other than plotting the history of these error codes and using WireShark to inspect traffic at a lower level, what can I do to see more clearly what the integration issue is? - Are there any limitations of the MQTT Client Driver that would make it incompatible with the Event Grid MQTT Broker? - Has anyone successfully made that integration work? Thanks for your help!