Merge pull request #303252 from dominicbetts/release-aio-2507-connectors

AIO 2507: Add ADR screenshots

Author: JillGrant615

articles/iot-operations/deploy-iot-ops/howto-manage-update-uninstall.md

@@ -109,21 +109,39 @@ You can run `az iot ops check` on your cluster to assess health and configuratio
 
 ### View Azure Device Registry
 
-<!-- TODO - 2507 Expand this section with more details about the Azure Device Registry. -->
-
-In the Azure portal, you can view the Azure Device Registry, which is a collection of all devices and assets that are connected to your Azure IoT Operations instance.
+In the Azure portal, you can view the Azure Device Registry, which is a collection of all the devices and assets that are connected to your Azure IoT Operations instance.
 
 The Azure Device Registry uses _namespaces (preview)_ to organize assets and devices. Each Azure IoT Operations instance uses a single namespace for its assets and devices. Multiple instances can share a single namespace.
 
-<!-- TODO - 2507 Expand this section with more details about the connector template configuration. -->
+To view items in the Azure Device Registry in the Azure portal:
+
+1. In the [Azure portal](https://portal.azure.com), search for and select **Azure Device Registry**. The **Overview** page summarizes the number of assets, schema registries and namespaces in your subscription:
+
+    :::image type="content" source="media/howto-manage-update-uninstall/azure-device-registry-overview.png" alt-text="Screenshot of Azure Device Registry overview page in the Azure portal." lightbox="media/howto-manage-update-uninstall/azure-device-registry-overview.png":::
+
+1. Use the **Assets** page to view the assets in Azure Device Registry. By default, the **Assets** page shows the assets in all namespaces in your subscription. Use the filters to view a subset of the assets, such as the assets in a specific namespace or resource group:
+
+    :::image type="content" source="media/howto-manage-update-uninstall/azure-device-registry-assets.png" alt-text="Screenshot of Azure Device Registry assets page in the Azure portal." lightbox="media/howto-manage-update-uninstall/azure-device-registry-assets.png":::
+
+1. Use the **Schema registries** page to view the schema registries in Azure Device Registry. By default, the **Schema registries** page shows the schema registries in all namespaces in your subscription. Use the filters to view a subset of the schema registries, such as the schema registries in a specific namespace or resource group:
+
+    :::image type="content" source="media/howto-manage-update-uninstall/azure-device-registry-schema-registries.png" alt-text="Screenshot of Azure Device Registry schema registries page in the Azure portal." lightbox="media/howto-manage-update-uninstall/azure-device-registry-schema-registries.png":::
+
+1. Use the **Namespaces** page to view the namespaces in Azure Device Registry. By default, the **Namespaces** page shows the namespaces in your subscription. Use the filters to view a subset of the namespaces, such as the namespaces in a specific resource group. From this page, you can create new namespaces, or view the details of existing namespaces:
+
+    :::image type="content" source="media/howto-manage-update-uninstall/azure-device-registry-namespaces.png" alt-text="Screenshot of Azure Device Registry namespaces page in the Azure portal." lightbox="media/howto-manage-update-uninstall/azure-device-registry-namespaces.png":::
+
+You can also view the details of an existing namespace in the resource group that includes your Azure IoT Operations instance. For example, the following screenshot shows the **adr-namespace** resource associated with the **aio-131235032** Azure IoT Operations instance:
+
+:::image type="content" source="media/howto-manage-update-uninstall/portal-resources.png" alt-text="Screenshot of Azure portal showing resources in the resource group." lightbox="media/howto-manage-update-uninstall/portal-resources.png":::
+
+The previous screenshot also shows the other resources in Azure Device Registry such as the **IoT Schema Registry**, **IoT Namespace Assets**, and **Devices** in the context of the resource group that contains your Azure IoT Operations instance.
 
 ### Configure connector templates
 
 In the Azure portal, you can configure *connector templates* for your Azure IoT Operations instance. Connector templates define the configuration of connectors, such as the connector for OPC UA, that are deployed to your cluster. When you create a connector template, it enables an OT user to create a device that uses the connector type in the operations experience web UI.
 
-### Configure discovery handlers
-
-In the Azure portal, you can configure *discovery handlers* for your Azure IoT Operations instance. Discovery handlers define the configuration of the handlers that can automatically discover assets and devices in your environment. When you create a discovery handler, it enables an OT user to configure the discovery of assets and devices of the type defined in the handler in the operations experience web UI.
+<!-- TODO - 2507 Expand this section with more details about the connector template configuration. -->
 
 ### Clone instance (preview)
 

articles/iot-operations/deploy-iot-ops/media/howto-manage-update-uninstall/azure-device-registry-assets.png

@@ -105,8 +105,6 @@ An *event* is a notification of a state changes to your asset. For example, a ph
 
 ### Streams
 
-<!-- TODO: Add more information about streams. -->
-
 A *stream* is streaming data from a physical device. For example, a camera connected to the media connector can stream video data. Streams include the following properties:
 
 | Property | Description |

articles/iot-operations/deploy-iot-ops/media/howto-manage-update-uninstall/azure-device-registry-namespaces.png

@@ -14,17 +14,25 @@ ms.date: 11/12/2024
 
 This article introduces the connector for REST/HTTP (preview) in Azure IoT Operations. The connector for REST/HTTP calls REST endpoints to retrieve data to share with other Azure IoT Operations components. The connector for REST/HTTP is secure and performant.
 
-## HTTP source types
+The connector for REST/HTTP enables integration with RESTful endpoints by periodically performing GET requests to devices, sensors, or systems that expose REST APIs. The connector can register the data's schema with the Azure Device Registry service, and forward the data to destinations such as MQTT broker or the state store for further processing and observability.
 
-The connector for REST/HTTP can connect to various sources.
+The connector for REST/HTTP supports the following features:
 
-<!-- TODO: Add details here when we have more information -->
+- Automatic retries when sampling failures occur. Reports a failed status for errors that can't be retried.
+- Integration with OpenTelemetry.
+- Use of _device endpoints_ and _namespace assets_.
+- Device endpoint and asset definition validation for REST compatibility.
+- Multiple authentication methods:
+  - Username/password basic HTTP authentication
+  - x509 client certificates
+  - Anonymous access for testing purposes
+  - Certificate trust bundle to specify additional certificate authorities
 
-## Example uses
+For each configured dataset, the connector for REST/HTTP:
 
-Example uses of the connector for REST/HTTP include calling REST APIs to retrieve data from industrial devices such as cameras, sensors, and other devices that expose data over HTTP.
-
-<!-- TODO: Add details here when we have more information -->
+- Performs a GET request to the address specified in the device endpoint and appends the dataset's data source from the namespace asset.
+- Generates a message schema for each dataset based on the data it receives, and registers it with Schema Registry and Azure Device Registry.
+- Forwards the data to the specified destination.
 
 ## How does it relate to Azure IoT Operations?