Skip to content

Commit 6bb2104

Browse files
committed
Glossary updates
1 parent 1c51ee6 commit 6bb2104

1 file changed

Lines changed: 37 additions & 1 deletion

File tree

articles/iot/iot-glossary.md

Lines changed: 37 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: dobett
66
ms.service: azure-iot
77
services: iot
88
ms.topic: conceptual
9-
ms.date: 02/03/2026
9+
ms.date: 03/09/2026
1010
ai-usage: ai-assisted
1111

1212
# Generated from YAML source.
@@ -366,6 +366,18 @@ Casing rules: Always lowercase.
366366

367367
Applies to: Azure IoT Operations
368368

369+
### Dataset
370+
371+
In [Azure IoT Operations](#azure-iot-operations---enabled-by-azure-arc), a dataset is a logical grouping of [data points](#data-point) collected from an [asset](#asset). A dataset defines which telemetry values belong together and how they're routed to a destination MQTT topic. A single asset can have multiple datasets to group telemetry by purpose, such as process monitoring or energy monitoring. Data points can't exist independently outside a dataset.
372+
373+
Connectors that use datasets include OPC UA, REST/HTTP, MQTT, and SSE.
374+
375+
See also [event group](#event-group), [management group](#management-group).
376+
377+
Casing rules: Always lowercase.
378+
379+
Applies to: Azure IoT Operations
380+
369381
### Default component
370382

371383
All [IoT Plug and Play device](#iot-plug-and-play-device) [models](#model) have a default [component](#component). A simple [device model](#device-model) only has a default component - such a model is also known as a no-component [device](#device). A more complex model has multiple components nested below the default component.
@@ -702,6 +714,18 @@ Casing rules: Always lowercase.
702714

703715
Applies to: Azure IoT Operations
704716

717+
### Event group
718+
719+
In [Azure IoT Operations](#azure-iot-operations---enabled-by-azure-arc), an event group is a logical container for related [events](#event-azure-iot-operations) from an [asset](#asset). An event group defines which events belong together and the destination MQTT topic where event data is published. Event groups are the event equivalent of [datasets](#dataset) — events within a group can carry metadata such as trigger time, severity, and sensor ID. Events can't exist independently outside an event group.
720+
721+
Connectors that use event groups include OPC UA, ONVIF, and SSE.
722+
723+
See also [dataset](#dataset), [management group](#management-group).
724+
725+
Casing rules: Always lowercase.
726+
727+
Applies to: Azure IoT Operations
728+
705729
### Event Hubs-compatible endpoint
706730

707731
An [IoT Hub](#iot-hub) [endpoint](#endpoint) that lets you use any Event Hubs-compatible method to read [device](#device) messages sent to the hub. Event Hubs-compatible methods include the [Event Hubs SDKs](../event-hubs/event-hubs-programming-guide.md) and [Azure Stream Analytics](../stream-analytics/stream-analytics-introduction.md).
@@ -1019,6 +1043,18 @@ Applies to: IoT Hub, Device Provisioning Service
10191043

10201044
## M
10211045

1046+
### Management group
1047+
1048+
In [Azure IoT Operations](#azure-iot-operations---enabled-by-azure-arc), a management group is a logical grouping of management actions that can be invoked against an [asset](#asset). Each action has a target URI and an action type: read, write, or call. Management actions can't exist independently outside a management group. Management groups let you organize and secure related control and configuration operations together.
1049+
1050+
Connectors that use management groups include OPC UA, ONVIF, and MQTT.
1051+
1052+
See also [dataset](#dataset), [event group](#event-group).
1053+
1054+
Casing rules: Always lowercase.
1055+
1056+
Applies to: Azure IoT Operations
1057+
10221058
### Model
10231059

10241060
A definition of a type of entity in your physical environment, including its [properties](#properties), telemetries, and [components](#component). Models are used to create [digital twins](#digital-twin) that represent specific physical objects of this type. Models are written in the [Digital Twins Definition Language](#digital-twins-definition-language).

0 commit comments

Comments
 (0)