Update ONVIF connector

Author: dominicbetts

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

@@ -35,7 +35,7 @@ You need any credentials required to access the HTTP source. If the HTTP source
 
 ## Deploy the connector for REST/HTTP
 
-[!INCLUDE [deploy-preview-http-connectors](../includes/deploy-preview-media-connectors.md)]
+[!INCLUDE [deploy-preview-media-connectors-simple](../includes/deploy-preview-media-connectors-simple.md)]
 
 ## Create a device
 

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

@@ -37,7 +37,7 @@ A camera connected to your network and accessible from your Azure IoT Operations
 
 [!INCLUDE [deploy-preview-media-connectors](../includes/deploy-preview-media-connectors.md)]
 
-## Create a device
+## Create a device with a media endpoint
 
 To configure the media connector, first create a device that defines the connection to the media source. The device includes the URL of the media source and any credentials you need to access the media source:
 
@@ -70,7 +70,7 @@ Run the following commands:
 ```azurecli
 az iot ops ns device create -n media-connector-cli -g {your resource group name} --instance {your instance name} 
 
-az iot ops ns device endpoint inbound add media --device media-connector-cli -g {your resource group name} -i {your instance name}  --name media-connector-cli-0 --endpoint-address "rtsp://samplecamera:554/stream1"
+az iot ops ns device endpoint inbound add media --device media-connector-cli -g {your resource group name} -i {your instance name}  --name media-connector-cli-0 --endpoint-address rtsp://samplecamera:554/stream1
 ```
 
 To learn more, see [az iot ops ns device](/cli/azure/iot/ops/ns/device).

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

@@ -35,14 +35,13 @@ An ONVIF compliant camera that you can reach from your Azure IoT Operations clus
 
 ## Deploy the connector for ONVIF
 
-[!INCLUDE [deploy-preview-media-connectors](../includes/deploy-preview-media-connectors.md)]
-
-> [!IMPORTANT]
-> If you don't enable preview features, you see the following error message in the `aio-supervisor-...` pod logs when you try to use the media or ONVIF connectors: `No connector configuration present for AssetEndpointProfile: <AssetEndpointProfileName>`.
+[!INCLUDE [deploy-preview-media-connectors-simple](../includes/deploy-preview-media-connectors-simple.md)]
 
 ## Create a device with an ONVIF endpoint
 
-To add a device that defines an ONVIF endpoint for a compliant camera, follow these steps:
+To add a device that includes an ONVIF endpoint for a compliant camera:
+
+# [Operations experience](#tab/portal)
 
 1. In the operations experience web UI, select **Devices** from the left navigation pane:
 
@@ -62,6 +61,20 @@ To add a device that defines an ONVIF endpoint for a compliant camera, follow th
 
     :::image type="content" source="media/howto-use-onvif-connector/device-created.png" alt-text="Screenshot that shows the device created in the operations experience." lightbox="media/howto-use-onvif-connector/device-created.png":::
 
+# [Azure CLI](#tab/cli)
+
+Run the following commands:
+
+```azurecli
+az iot ops ns device create -n onvif-connector-cli -g {your resource group name} --instance {your instance name}
+
+az iot ops ns device endpoint inbound add onvif --device onvif-connector-cli -g {your resource group name} -i {your instance name}  --name onvif-connector-cli-0 --endpoint-address http://myonvifcam:2020/onvif/device_service
+```
+
+To learn more, see [az iot ops ns device](/cli/azure/iot/ops/ns/device).
+
+---
+
 ## View the discovered assets and devices
 
 After you create a device with an ONVIF endpoint, the connector for ONVIF automatically discovers the assets and devices that are available at the endpoint. To view the discovered assets and devices in the operations experience web UI, select **Discovery** from the left navigation pane:

articles/iot-operations/includes/deploy-preview-media-connectors-simple.md

@@ -0,0 +1,40 @@
+---
+title: Include file
+description: Include file
+author: dominicbetts
+ms.topic: include
+ms.date: 07/25/2025
+ms.author: dobett
+---
+
+When you deploy the preview version of Azure IoT Operations, the deployment includes the three preview connectors. You can verify that you have a preview instance of Azure IoT Operations by checking in the Azure portal that preview features are enabled for your instance:
+
+:::image type="content" source="media/deploy-preview-media-connectors-simple/portal-enable-preview-connectors.png" alt-text="Screenshot of Azure portal that shows that preview features are enabled." lightbox="media/deploy-preview-media-connectors-simple/portal-enable-preview-connectors.png":::
+
+Before you can use the preview connectors (ONVIF, media, and REST/HTTP) in the operations experience web UI, an administrator must add connector template instances to your Azure IoT Operations instance.
+
+All three preview connectors can publish captured data to the MQTT broker.
+
+To add a connector template instance to your Azure IoT Operations instance:
+
+1. In the Azure portal, go to your Azure IoT Operations instance, select **Connector templates**, and then select **Add connector template instances**:
+
+    :::image type="content" source="media/deploy-preview-media-connectors-simple/portal-add-connector-template.png" alt-text="Screenshot of Azure portal that shows how to add a connector template instance." lightbox="media/deploy-preview-media-connectors-simple/portal-add-connector-template.png":::
+
+1. On the first page of the **Add an Akri connector template** wizard, select the type of connector template you want to add, such as **ONVIF**, **Media**, or **HTTP REST**. Then select **Metadata**.
+
+    :::image type="content" source="media/deploy-preview-media-connectors-simple/select-connector-template-type.png" alt-text="Screenshot of Azure portal that shows how to select the connector template instance type." lightbox="media/deploy-preview-media-connectors-simple/select-connector-template-type.png":::
+
+1. On the **Metadata** page, accept the defaults, and then select **Device inbound endpoint type**.
+
+1. On the **Device inbound endpoint type** page, accept the defaults, and then select **Diagnostics configurations**.
+
+1. On the **Diagnostics configurations** page, accept the defaults, and then select **Runtime configuration**.
+
+1. On the **Runtime configuration** page,  accept the defaults, and then select **Review**:
+
+1. On the **Review** page, review the details of the connector template instance, and then select **Create** to create the connector template instance.
+
+An OT user can now use the operations experience web UI to create a device with a preview connector endpoint.
+
+---

articles/iot-operations/includes/deploy-preview-media-connectors.md

@@ -13,7 +13,7 @@ When you deploy the preview version of Azure IoT Operations, the deployment incl
 
 Before you can use the preview connectors (ONVIF, media, and REST/HTTP) in the operations experience web UI, an administrator must add connector template instances to your Azure IoT Operations instance.
 
-All three preview connectors can publish captured data to the MQTT broker and save captured data to storage. Azure IoT Operations uses [Azure Container Storage enabled by Azure Arc](/azure/azure-arc/container-storage/overview) to transfer the captured data to cloud storage destinations such as Azure Blob Storage. When you configure a connector template instance, you specify a _persistent volume claim_ and _mount path_ for the connector to use to save captured data. To learn how to create a suitable persistent volume claim, see [Cloud Ingest Edge Volumes configuration](/azure/azure-arc/container-storage/cloud-ingest-edge-volume-configuration).
+All three preview connectors can publish captured data to the MQTT broker. The media connector can also save captured data to storage. Azure IoT Operations uses [Azure Container Storage enabled by Azure Arc](/azure/azure-arc/container-storage/overview) to transfer the captured data to cloud storage destinations such as Azure Blob Storage. When you configure a connector template instance, you specify a _persistent volume claim_ and _mount path_ for the connector to use to save captured data. To learn how to create a suitable persistent volume claim, see [Cloud Ingest Edge Volumes configuration](/azure/azure-arc/container-storage/cloud-ingest-edge-volume-configuration).
 
 To add a connector template instance to your Azure IoT Operations instance: