Azure IoT Developer (AZ-220) key terms

A managed Azure service that acts as a central message broker between devices and back-end applications, supporting bidirectional device-to-cloud and cloud-to-device communication, per-device identity, and multiple protocols.

A helper service for IoT Hub that enrolls devices automatically and assigns each one to the correct hub without manual registration, using enrollment groups or individual enrollments.

A JSON document stored by IoT Hub that holds desired properties set by the solution back end, reported properties sent by the device, and read-only metadata such as tags and connection state.

The portion of a device or module twin that the back-end solution writes to declare target configuration, which the device reads and applies, then acknowledges through reported properties.

The portion of a device or module twin that the device writes to describe its current state, such as firmware version or active settings, so back-end systems can observe it.

A twin document that exists for each module running on a device, letting the back end configure and observe individual modules independently of the device-level twin.

A request-response invocation that a back end sends to a connected device or module, which must respond within a timeout, commonly used for immediate actions such as rebooting or opening a valve.

A one-way message sent from a solution back end to a device over the IoT Hub service-facing endpoint, delivered at least once and optionally acknowledged by the device.

Telemetry or event data that a device sends to IoT Hub through its device-facing endpoint, where it becomes available to built-in routing, event streams, or custom endpoints.

A feature that sends device messages to built-in endpoints or custom endpoints such as storage, Service Bus, or Event Hubs, selected by queries written over message and twin properties.

The addition of static or dynamic key-value annotations, such as a tenant identifier or a value from the device twin, to messages as they pass through IoT Hub routing.

A named set of permissions, such as registry read, registry write, service connect, or device connect, that governs what a SAS token holder may do against an IoT Hub endpoint.

A signed string derived from a shared access key, a resource URI, and an expiry that grants time-limited access to an IoT Hub endpoint without exposing the underlying key.

A digital certificate used to authenticate devices to IoT Hub or the provisioning service, typically with a self-signed device certificate chained to a registered root or intermediate certificate authority.

The proof-of-identity method a device uses during provisioning, such as an X.509 certificate, a symmetric key, or a trusted platform module endorsement key.

A provisioning service entry that applies shared configuration, such as initial twin state and target hub, to any device that proves identity through a common root certificate or symmetric key.

A provisioning service entry tied to one specific device, allowing unique registration settings and higher per-device control than a group enrollment provides.

A device registered in IoT Hub that runs the IoT Edge runtime and hosts modules, acting as a gateway that can filter, aggregate, or forward data from downstream leaf devices.

A containerized unit of business logic deployed to an IoT Edge device, defined in a deployment manifest with an image, registry credentials, restart policy, and desired properties.

A JSON document that declares which modules run on an IoT Edge device, how they are created and routed, and which target devices or device groups receive the deployment.

The IoT Edge runtime module responsible for installing, starting, monitoring, and reporting the status of the other modules according to the deployment manifest and its twin.

The IoT Edge runtime module that provides a local message broker and routing fabric between modules and downstream devices, buffering messages when upstream connectivity is lost.

A leaf device that does not connect directly to IoT Hub but instead connects to an IoT Edge device acting as a transparent or protocol-translation gateway.

A real-time analytics service that runs SQL-like queries over streaming inputs such as IoT Hub, producing outputs to storage, functions, or Power BI for hot-path processing.

A custom routing endpoint that exposes IoT Hub device messages through an Event Hubs-compatible interface, letting consumers read the stream with standard Event Hubs SDKs.

A serverless compute service that runs event-driven code, commonly triggered by IoT Hub events through Event Grid or an Event Hubs connection to process or enrich device data.

A publish-subscribe event routing service that delivers IoT Hub lifecycle events, such as device created or connected, to subscribers like functions, Logic Apps, or webhooks.

A workflow automation service with connectors for IoT Hub and many other systems, used to orchestrate business processes triggered by device events or schedules.

Platform measurements such as telemetry messages sent, twin reads, and throttling errors that can be charted in the portal or exported to Log Analytics for alerting.

Optional IoT Hub log records for categories such as connections, device identity operations, and routes, which are routed to Log Analytics, storage, or Event Hubs for analysis.

A testing approach that generates synthetic telemetry from one or many simulated device identities to validate routing, scaling behavior, and back-end processing before real hardware exists.

A per-unit cap on operations such as identity registry writes or message throughput that IoT Hub enforces, causing errors when exceeded and requiring scale-up or backoff handling.

The IoT Hub store of device and module records, each with credentials and enabled or disabled status, queried and modified through the registry manager APIs.

The use of automatic device configurations to apply twin desired properties and device settings to large groups of devices based on a target condition query.

A recurring configuration that assigns a deployment manifest to edge devices whose twin properties match a target condition, supporting layered deployments and priority ordering.

A direct method invocation addressed to a specific module on an edge device, often routed locally through Edge Hub rather than sent to the cloud.

A family of client libraries for languages such as C#, Java, Node.js, and Python that wrap IoT Hub protocols and handle connection, retry, and twin operations for devices and services.

Platform-level records emitted by an Azure resource and routed to a destination; for IoT Hub they include route and connection diagnostics useful for troubleshooting delivery failures.