These docs are for v7.1.0. Click to read the latest docs for v7.6.0.

Azure IoT Connection

Overview

This section provides a guide on connecting an ESF device to the Microsoft Azure IoT platform. This guide covers the usage of the ESF Cloud Connector for

  • Microsoft Azure IoT Hub (DPS Individual Enrollment, DPS Enrollment Group, IoT Hub Direct)
  • Microsoft Azure IoT Central (Individual Enrollment, Enrollment Group)

Prerequisites

In order to connect to the Azure IoT Hub, the following prerequisites must first be met:

Azure IoT Connector

The ESF Gateway Administrative Console exposes all the services necessary to configure a connection to Microsoft Azure IoT Hub or Microsoft Azure IoT Central.

🚧

In case of connection to Azure IoT Central, please follow the instruction on the Create a Device in IoT Central Applications page before connecting devices directly to Azure Iot Central or via Azure IoT Plug and Play

Available Connections:

ESF can connect to the Microsoft Azure IoT Hub or Microsoft Azure IoT Central using any of the three endpoints by following one of the custom connections below:

DataService

In order for ESF to connect to the Azure IoT Services on startup, the option connect.auto-on-startup must be set to true in DataService. If this value is changed from false to true, ESF will immediately begin the connection process. It is recommended that the CloudService and MqttDataTransport are configured before setting the connect.auto-on-startup option to true.

🚧

Changing the value of connect.auto-on-startup from true to false will not disconnect the client from the broker. This setting simply implies that ESF will not automatically connect on the next start of the framework.

Connect/Disconnect

The status panel can be used to manually connect or disconnect the client while ESF is running. The main button toolbar has a connect and disconnect button that may be used to control connectivity.

🚧

Connecting or disconnecting the client via the status panel has no impact on ESF automatically connecting at startup. This capability is only controlled via the connect.auto-on-startup DataService setting.