Merge pull request #262586 from kgremban/jan5-mqttevents

Consolidate event grid state reporting info

Author: prmerger-automator[bot]

articles/iot-hub/iot-hub-event-grid.md

@@ -7,7 +7,7 @@ author: kgremban
 ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
-ms.date: 01/22/2022
+ms.date: 01/05/2024
 ms.author: kgremban
 ms.custom: [amqp, mqtt, 'Role: Cloud Development']
 ---
@@ -178,10 +178,7 @@ For device telemetry events, IoT Hub will create the default [message route](iot
 
 Device connected and device disconnected events are available for devices connecting using either the MQTT or AMQP protocol, or using either of these protocols over WebSockets. Requests made only with HTTPS won't trigger device connection state notifications.
 
-* For devices connecting using Java, Node, or Python [Azure IoT SDKs](iot-hub-devguide-sdks.md) with the [MQTT protocol](../iot/iot-mqtt-connect-to-iot-hub.md) will have connection states sent automatically. 
-* For devices connecting using the Java, Node, or Python [Azure IoT SDKs](iot-hub-devguide-sdks.md) with the [AMQP protocol](iot-hub-amqp-support.md), a cloud-to-device link should be created to reduce any delay in accurate connection states. 
-* For devices connecting using the .NET [Azure IoT SDK](iot-hub-devguide-sdks.md) with the [MQTT](../iot/iot-mqtt-connect-to-iot-hub.md) or [AMQP](iot-hub-amqp-support.md) protocol won’t send a device connected event until an initial device-to-cloud or cloud-to-device message is sent/received.
-* Outside of the Azure IoT SDKs, in MQTT these operations equate to SUBSCRIBE or PUBLISH operations on the appropriate messaging [topics](../iot/iot-mqtt-connect-to-iot-hub.md). Over AMQP these equate to attaching or transferring a message on the [appropriate link paths](iot-hub-amqp-support.md).
+For information about monitoring device status with Event Grid, see [Monitor device connection status](./monitor-device-connection-state.md#event-grid).
 
 ### Device connection state interval
 

articles/iot-hub/monitor-device-connection-state.md

@@ -6,7 +6,7 @@ author: kgremban
 ms.author: kgremban
 ms.topic: reference
 ms.service: iot-hub
-ms.date: 10/18/2022
+ms.date: 01/05/2024
 ---
 
 # Monitor device connection status
@@ -56,15 +56,12 @@ Device connection state events are available for devices connecting using either
 
 Outside of the Azure IoT SDKs, in MQTT these operations equate to SUBSCRIBE or PUBLISH operations on the appropriate messaging topics. Over AMQP these operations equate to attaching or transferring a message on the appropriate link paths.
 
-IoT Hub doesn't report each individual device connect and disconnect, but rather publishes the current connection state taken at a periodic 60-second snapshot. Receiving either the same connection state event with different sequence numbers or different connection state events both mean that there was a change in the device connection state during the 60-second window.
-
 ### Event Grid limitations
 
 Using Event Grid to monitor your device status comes with the following limitations:
 
 * Event Grid doesn't report each individual device connect and disconnect event. Instead, it polls for device status every 60 seconds and publishes the most recent connection state if there was a state change. For this reason, state change reports may be delayed up to one minute and individual state changes may be unreported if multiple events happen within the 60-second window.
-* Devices that use MQTT start reporting device status automatically. However, devices that use AMQP need [cloud-to-device link](iot-hub-amqp-support.md#invoke-cloud-to-device-messages-service-client) before they can report device status.
-* The IoT C SDK doesn't have a connect method. Customers must send telemetry to begin reporting accurate device connection states.
+* Devices that use AMQP need [cloud-to-device link](iot-hub-amqp-support.md#invoke-cloud-to-device-messages-service-client) before they can report device status.
 * Event Grid exposes a public endpoint that can't be hidden.
 
 If any of these limitations affect your ability to use Event Grid for device status monitoring, then you should consider building a custom device heartbeat pattern instead.