Device connectivity in Microsoft IoT Central
This article introduces key concepts relating to device connectivity in Microsoft IoT Central.
Every device that connects to your Microsoft IoT Central application, connects to the endpoints that are exposed by the IoT hub Microsoft IoT Central uses. IoT Hub enables scalable, secure, and reliable connections from your connected devices.
The Azure Device SDKs offer the easiest way for you implement the code on your devices that connects to your Microsoft IoT Central application. The following device SDKs are available:
- Azure IoT SDK for C
- Azure IoT SDK for Python
- Azure IoT SDK for Node.js
- Azure IoT SDK for Java
- Azure IoT SDK for .NET
Each device connects using a unique connection string that identifies the device. A device can only connect to the IoT hub where it is registered. When you create a real device in your Microsoft IoT Central application, the application generates a connection string for you to use.
SDK features and IoT Hub connectivity
All device communication with IoT Hub uses the following IoT Hub connectivity options:
The following table summarizes how Microsoft IoT Central device features map on to IoT Hub features:
|Microsoft IoT Central||Azure IoT Hub|
|Measurement: Telemetry||Device-to-cloud messaging|
|Device properties||Device twin reported properties|
|Settings||Device twin desired and reported properties|
To learn more about using the Device SDKs, see one of the following articles for example code:
- Connect a generic Node.js client to your Microsoft IoT Central application
- Connect a Raspberry Pi device to your Microsoft IoT Central application
- Connect a DevDiv kit device to your Microsoft IoT Central application.
The Device SDKs support the following network protocols for connecting to an IoT hub:
For information about these difference protocols and guidance on choosing one, see Choose a communication protocol.
If your device can't use any of the supported protocols, you can use Azure IoT Edge to do protocol conversion. IoT Edge supports other intelligence-on-the-edge scenarios to offload processing to the edge from the Microsoft IoT Central application.
All data exchanged between devices and your Microsoft IoT Central is encrypted. IoT Hub authenticates every request from a device that connects to any of the device-facing IoT Hub endpoints. To avoid exchanging credentials over the wire, a device uses signed tokens to authenticate. For more information, see, Control access to IoT Hub.
Currently, devices that connect to Microsoft IoT Central must use SAS tokens. X.509 certificates are not supported for devices that connect to Microsoft IoT Central.
Now that you have learned about device connectivity in Microsoft IoT Central, here are the suggested next steps: