Settings

The Settings tab contains device-specific platform settings that control how the device is provisioned, sends data, and receives deployments.

Settings tab on device configuration

Management Endpoint

Defines where the device connects for management and provisioning (e.g., to receive configuration and deployments).

• Name – The name of the management endpoint (typically an IoT Hub).

• Location – The region or geographic location of the endpoint.

The Provision Device button opens a dialog to provision or reprovision the device to a management endpoint. This sets up the device’s identity and credentials so it can connect securely. See the Provisioning documentation for details.

Ingestion Endpoint

Controls how the device sends measurement and telemetry data to the cloud.

• Ingestion Endpoint – The name of the endpoint that receives uploaded data (e.g., telemetry, logs).

• Upload Mode – Defines whether cold-path data should be uploaded as a single file, or as one file per Tag. If shown as “Platform Default,” the device inherits the default mode from platform-level settings.

• Upload Frequency – Defines how often cold-path data should be sent (e.g., every 10 seconds, every 5 minutes). Also inherits platform defaults unless specified.

The Change Ingestion button opens a dialog where you can select a different ingestion endpoint and adjust upload behavior (mode and frequency).

Setting Ingestion endpoint for a device

Deployment

Defines how the device receives and applies deployments.

• Deployment Method – Choose between available deployment types. Options are:

  • Direct (default), meaning that the full configuration is sent as a single, complete manifest directly to the device. The deployment is applied immediately, but there are no subsequent checks for configuration drift (if the deployment is altered).

  • Managed : The deployment is sent to the device as one or more layered configurations. This means that the deployment is set as a desired state, and the Management Endpoint will continuously ensure that the desired configuration remains intact.

Use Managed deployment if is important to avoid configuration drift, of if a very large number of devices are targeted.