Merge pull request #293255 from dominicbetts/iot-diagram-comments

IoT: Add comments pointing to art library

Author: prmerger-automator[bot]

articles/iot/iot-introduction.md

@@ -24,6 +24,8 @@ The following two sections give a high-level view of the components in typical c
 
 A **cloud-based solution** is an integrated set of IoT devices, components, and services, that addresses a business need and that connects devices directly to the cloud. An example of a cloud-based solution is a fleet of delivery trucks that send telemetry data to the cloud for analysis and visualization:
 
+<!-- Art Library Source# ConceptArt-0-000-025 -->
+
 :::image type="content" source="media/iot-introduction/iot-cloud-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture for cloud-based solutions." border="false":::
 
 You can build cloud-based solutions with services such as [IoT Hub](../iot-hub/iot-concepts-and-iot-hub.md), [Device Provisioning Service](../iot-dps/about-iot-dps.md), and [Azure Digital Twins](../digital-twins/overview.md).
@@ -35,6 +37,8 @@ An **edge-based solution** is an integrated set of IoT assets, components, and s
 
 An edge-based solution can still forward data from your assets to the cloud for further processing such as analysis and visualization:
 
+<!-- Art Library Source# ConceptArt-0-000-025 -->
+
 :::image type="content" source="media/iot-introduction/iot-edge-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture for edge-based solutions." border="false":::
 
 You can build edge-based solutions with [Azure IoT Operations](../iot-operations/overview-iot-operations.md) or [Azure IoT Edge](../iot-edge/about-iot-edge.md). Azure IoT Operations is a new offering that follows Microsoft's [adaptive cloud approach](#solution-management) to integrate cloud and edge components.

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

@@ -19,6 +19,8 @@ This overview introduces the key concepts around developing assets and devices t
 
 The following diagram shows a high-level view of the components in a typical edge-based IoT solution. This article focuses on the assets and connectors shown in the diagram:
 
+<!-- Art Library Source# ConceptArt-0-000-025 -->
+
 :::image type="content" source="media/iot-overview-device-development/iot-edge-device-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture highlighting asset connectivity areas." border="false":::
 
 Assets typically have built-in firmware that implements standard protocols. For example, a robotic arm might be an OPC UA client and a security video camera might implement ONVIF. Azure IoT Operations includes various connectors that can use these protocols to communicate with assets and translate messages from the assets into MQTT messages. Some assets can receive messages enabling you to perform operations on them such as:
@@ -33,6 +35,8 @@ You can create your own, custom connectors to connect to assets that use protoco
 
 The following diagram shows a high-level view of the components in a typical cloud-based IoT solution. This article focuses on the devices and gateway shown in the diagram:
 
+<!-- Art Library Source# ConceptArt-0-000-025 -->
+
 :::image type="content" source="media/iot-overview-device-development/iot-cloud-device-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture highlighting device connectivity areas." border="false":::
 
 In Azure IoT, a device developer writes the code to run on the devices in the solution. This code typically: