Merge pull request #297118 from asergaz/dom-structure

iot-services-and-technologies new structure

Author: v-dirichards

articles/iot/TOC.yml

@@ -7,6 +7,7 @@ items:
     - name: Introduction
       href: iot-introduction.md
     - name: IoT solution components
+      expanded: true
       items:
       - name: Device development
         href: iot-overview-device-development.md
@@ -26,7 +27,7 @@ items:
         href: iot-overview-security.md
       - name: Scalability, high availability
         href: iot-overview-scalability-high-availability.md
-    - name: Azure IoT services and technologies
+    - name: Choose an Azure IoT service
       href: iot-services-and-technologies.md
 
   - name: How-to guides
@@ -110,6 +111,8 @@ items:
       href: iot-glossary.md
     - name: Azure IoT services
       items:
+      - name: Azure IoT Operations
+        href: ../iot-operations/index.yml
       - name: IoT Hub
         href: ../iot-hub/index.yml
       - name: IoT Hub Device Provisioning Service
@@ -126,6 +129,8 @@ items:
       items:
       - name: Device and Service SDKs
         href: iot-sdks.md
+      - name: Azure IoT Operations SDKs
+        href: https://github.com/Azure/iot-operations-sdks
     - name: Azure IoT Tools for VS Code
       href: https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-toolkit
     - name: Azure IoT Explorer tool

articles/iot/iot-introduction.md

@@ -199,7 +199,7 @@ If you need to migrate a device from IoT Central to IoT Hub, you can use the Dev
 
 Azure IoT Operations includes an enterprise grade, standards compliant MQTT broker. The broker enables bidirectional communication between the edge and the cloud, and powers [event-driven applications](/azure/architecture/guide/architecture-styles/event-driven) at the edge.
 
-Use the MQTT broker to implement command and control solutions that enable you to send commands to your assets either from the cloud or from other edge-based components. Connectors, such as the ONVIF connector, can use MQTT topics to listen for and respond to commands. For example, you can publish a message to a topic in the MQTT broker that's an instruction to a camera to pan left by 20 degrees. The camera can use another topic to publish a message that acknowledges the operation is complete. The [Azure IoT Operations SDKs](https://github.com/Azure/iot-operations-sdks) includes samples that show how to implement these types of command and control scenarios.
+Use the MQTT broker to implement command and control solutions that enable you to send commands to your assets either from the cloud or from other edge-based components. Connectors, such as the ONVIF connector, can use MQTT topics to listen for and respond to commands. For example, you can publish a message to a topic in the MQTT broker that's an instruction to a camera to pan left by 20 degrees. The camera can use another topic to publish a message that acknowledges the operation is complete. The [Azure IoT Operations SDKs (preview)](https://github.com/Azure/iot-operations-sdks) includes samples that show how to implement these types of command and control scenarios.
 
 For more information, see [Azure IoT Operations built-in local MQTT broker](../iot-operations/manage-mqtt-broker/overview-broker.md).
 

articles/iot/iot-overview-device-management.md

@@ -89,6 +89,8 @@ On multi-node clusters with at least three nodes, you have the option of enablin
 
 [Dapr is offered as part of MQTT broker](../iot-operations/create-edge-apps/howto-develop-dapr-apps.md), abstracting away details of MQTT session management, message QoS and acknowledgment, and built-in key-value stores, making it a practical choice for developing a highly available application.
 
+The [Azure IoT Operations SDKs (preview)](https://github.com/Azure/iot-operations-sdks) are a suite of tools and libraries across multiple languages designed to aid the development of highly available applications for Azure IoT Operations.
+
 For information on high availability across availability zones and regions for Azure Device Registry, see [Reliability in Azure Device Registry](../reliability/reliability-device-registry.md).
 
 # [Cloud-based solution](#tab/cloud)

articles/iot/iot-overview-scalability-high-availability.md

@@ -52,8 +52,9 @@ Azure IoT Operations includes an MQTT broker that routes messages from the conne
 
 The message broker is based on the [MQTT protocol](https://mqtt.org/) and supports APIs and SDKs such as:
 
+- [Azure IoT Operations SDKs (preview)](https://github.com/Azure/iot-operations-sdks)
 - [DAPR](../iot-operations/create-edge-apps/howto-develop-dapr-apps.md)
-- [MQTTnet](../iot-operations/create-edge-apps/howto-develop-mqttnet-apps.md).
+- [MQTTnet](../iot-operations/create-edge-apps/howto-develop-mqttnet-apps.md)
 
 The message broker includes a [state store](../iot-operations/create-edge-apps/overview-state-store.md) that lets you manage distributed application state across the edge cluster.
 

articles/iot/iot-overview-solution-extensibility.md

@@ -10,7 +10,7 @@ ms.date: 02/14/2025
 
 ---
 
-# Azure IoT SDKs
+# Azure IoT device and service SDKs
 
 The following tables list the various SDKs you can use to build IoT solutions.