Merge pull request #312835 from dominicbetts/aio-datasets-management-groups-event-groups

AIO: Improve management groups

Author: prmerger-automator[bot]

articles/iot-operations/discover-manage-assets/howto-configure-opc-ua.md

@@ -658,6 +658,12 @@ This command shows you what changes would be made to your Azure resources withou
 
 ---
 
+## Add management groups and actions
+
+A management group is a logical grouping of actions that you can invoke against an OPC UA asset, such as writing a value to a tag or calling a method. Actions must belong to a management group.
+
+To create a management group and define actions for it, see [Control OPC UA servers](howto-control-opc-ua.md). That article explains the different types of actions (simple writes, complex writes, and method calls) and the MQTT topics you use to invoke them.
+
 ## Update an asset
 
 # [Operations experience](#tab/portal)
@@ -871,6 +877,7 @@ To delete individual resources by using Bicep, see [Deployment stacks](/azure/az
 ## Related content
 
 - [Manage asset and device configurations](howto-use-operations-experience.md)
+- [Control OPC UA servers](howto-control-opc-ua.md)
 - [Connector for OPC UA overview](overview-opc-ua-connector.md)
 - [az iot ops ns asset](/cli/azure/iot/ops/ns/asset)
 - [az iot ops ns device](/cli/azure/iot/ops/ns/device)

articles/iot-operations/discover-manage-assets/howto-use-sse-connector.md

@@ -178,17 +178,30 @@ To define an asset that publishes events from the SSE endpoint, follow these ste
 
 1. Add any custom properties you want to associate with the asset. For example, you might add a property to indicate the manufacturer of the camera. Select **Next** to continue.
 
-1. On the **Datasets** page, create any datasets required and define the data points.
+A dataset defines where the connector sends the data it collects from a collection of data points. An SSE asset can have multiple datasets. To create a dataset:
 
-1. On the **Event groups** page, create an event group to define the events to publish to the MQTT broker.
+1. Select **Create dataset**.
 
-1. In the event group, select **Add event** to add an event for the asset. For example:
+1. Enter the details for the dataset such as its name, data source, and destination. For SSE assets, the data source is the path on the SSE endpoint. The destination is either an MQTT topic or a [broker state store](../develop-edge-apps/overview-state-store.md) key.
 
-    :::image type="content" source="media/howto-use-sse-connector/add-event.png" alt-text="Screenshot that shows how to add an event for SSE source." lightbox="media/howto-use-sse-connector/add-event.png":::
+1. Select **Create and next** to create the dataset.
+
+    > [!TIP]
+    > Use the **Manage default settings** option to configure default dataset settings.
+
+An event group defines where the connector sends the data it receives from a collection of events. An SSE asset can have multiple event groups. To create an event group:
+
+1. Select **Create event group**.
+
+1. Enter a name for the event group and the destination MQTT topic.
 
-    Add details for each event to publish to the MQTT broker.
+1. Select **Create and next** to create the event group and go to the events page.
 
-    Select **Next** to continue.
+1. Select **Add event** to add an event to the group. For example:
+
+    :::image type="content" source="media/howto-use-sse-connector/add-event.png" alt-text="Screenshot that shows how to add an event for SSE source." lightbox="media/howto-use-sse-connector/add-event.png":::
+
+    Add details for each event to publish to the MQTT broker. Select **Next** to continue.
 
 1. On the **Review** page, review the details of the asset and select **Create** to create the asset. After a few minutes, the asset is listed on the **Assets** page:
 
@@ -202,6 +215,10 @@ Run the following command:
 az iot ops ns asset sse create --name mysseasset --instance {your instance name} -g {your resource group name} --device sse-connector-cli --endpoint sse-connector-0
 
 az iot ops ns asset sse dataset add --asset mysseasset --instance {your instance name} -g {your resource group name} --name weatherdata --data-source "/api/weather" --dest topic="azure-iot-operations/data/erp" retain=Never qos=Qos1 ttl=3600
+
+az iot ops ns asset sse event-group add --asset mysseasset --instance {your instance name} -g {your resource group name} --name alerts --data-source "" --dest topic="azure-iot-operations/events/mysseasset" retain=Never qos=Qos1 ttl=3600
+
+az iot ops ns asset sse event add --asset mysseasset --instance {your instance name} -g {your resource group name} --event-group alerts --name temperaturethreshold --data-source "/events/temperaturethreshold" --dest topic="azure-iot-operations/events/mysseasset" retain=Never qos=Qos1 ttl=3600
 ```
 
 To learn more, see [az iot ops ns asset sse](/cli/azure/iot/ops/ns/asset/sse).
@@ -260,6 +277,31 @@ resource asset 'Microsoft.DeviceRegistry/namespaces/assets@2025-10-01' = {
         ]
       }
     ]
+
+    eventGroups: [
+      {
+        name: 'alerts'
+        eventGroupConfiguration: '{}'
+        events: [
+          {
+            name: 'temperaturethreshold'
+            dataSource: '/events/temperaturethreshold'
+            eventConfiguration: '{}'
+            destinations: [
+              {
+                target: 'Mqtt'
+                configuration: {
+                  topic: 'azure-iot-operations/events/mysseasset'
+                  qos: 'Qos1'
+                  retain: 'Never'
+                  ttl: 3600
+                }
+              }
+            ]
+          }
+        ]
+      }
+    ]
   }
 }
 ```

articles/iot-operations/discover-manage-assets/overview-manage-assets.md

@@ -136,6 +136,24 @@ Connectors include:
 
 - **Custom connectors**. Services that you create to connect to other data sources and publish data to the MQTT broker. Use the Azure IoT Operations SDKs to create custom connectors that meet your specific requirements.
 
+Each connector organizes asset data using one or more of the following types:
+
+- **Datasets**: A logical grouping of telemetry data points that defines what data is collected and routes it to a destination MQTT topic.
+- **Event groups**: A logical container for related discrete events from an asset, such as state changes or alerts, routed to a destination MQTT topic.
+- **Management groups**: A logical grouping of read, write, or call actions that can be invoked against an asset.
+- **Streams**: A continuous flow of media data, such as video or audio, from an asset such as a camera.
+
+The following table summarizes which data types each connector supports.
+
+| Connector       | Datasets | Event groups | Management groups | Streams |
+|-----------------|:--------:|:------------:|:-----------------:|:-------:|
+| OPC UA          | Yes      | Yes          | Yes               |         |
+| ONVIF           |          | Yes          | Yes               |         |
+| Media           |          |              |                   | Yes     |
+| HTTP/REST       | Yes      |              |                   |         |
+| SSE             | Yes      | Yes          |                   |         |
+| MQTT (preview)  | Yes      |              | Yes               |         |
+
 #### Discovery
 
 You can use Akri services to automatically discover physical devices and assets. Akri services also help operational technology (OT) users set up devices and assets in the operations experience web UI. The connectors described earlier all use the framework that Akri services provide to implement their core capabilities.

articles/iot/iot-glossary.md

@@ -6,7 +6,7 @@ ms.author: dobett
 ms.service: azure-iot
 services: iot
 ms.topic: conceptual
-ms.date: 02/03/2026
+ms.date: 03/09/2026
 ai-usage: ai-assisted
 
 # Generated from YAML source.
@@ -366,6 +366,18 @@ Casing rules: Always lowercase.
 
 Applies to: Azure IoT Operations
 
+### Dataset
+
+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.
+
+Connectors that use datasets include OPC UA, REST/HTTP, MQTT, and SSE.
+
+See also [event group](#event-group), [management group](#management-group).
+
+Casing rules: Always lowercase.
+
+Applies to: Azure IoT Operations
+
 ### Default component
 
 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.
 
 Applies to: Azure IoT Operations
 
+### Event group
+
+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.
+
+Connectors that use event groups include OPC UA, ONVIF, and SSE.
+
+See also [dataset](#dataset), [management group](#management-group).
+
+Casing rules: Always lowercase.
+
+Applies to: Azure IoT Operations
+
 ### Event Hubs-compatible endpoint
 
 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
 
 ## M
 
+### Management group
+
+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.
+
+Connectors that use management groups include OPC UA, ONVIF, and MQTT.
+
+See also [dataset](#dataset), [event group](#event-group).
+
+Casing rules: Always lowercase.
+
+Applies to: Azure IoT Operations
+
 ### Model
 
 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).