Update rest/http how-to

Author: dominicbetts

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

@@ -66,18 +66,15 @@ An Azure IoT Operations deployment can include an optional built-in OPC PLC simu
 
 # [Azure CLI](#tab/cli)
 
-Run the following command:
+Run the following commands:
 
 ```azurecli
 az iot ops ns device create -n opc-ua-connector-cli -g {your resource group name} --instance {your instance name} 
 
 az iot ops ns device endpoint inbound add opcua --device opc-ua-connector-cli -g {your resource group name} -i {your instance name} --name opc-ua-connector-0 --endpoint-address "opc.tcp://opcplc-000000:50000"
 ```
 
-> [!TIP]
-> Use `az connectedk8s list` to list the clusters you have access to.
-
-To learn more, see [az iot ops device](/cli/azure/iot/ops/asset/endpoint).
+To learn more, see [az iot ops ns device](/cli/azure/iot/ops/ns/device).
 
 ---
 

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

@@ -21,7 +21,7 @@ In Azure IoT Operations, the connector for REST/HTTP (preview) enables access to
 This article explains how to use the connector for REST/HTTP to perform tasks such as:
 
 - Define the devices that connect HTTP sources to your Azure IoT Operations instance.
-- Add assets, and define the data points to enable the data flow from the HTTP source to the MQTT broker.
+- Add assets, and define the data points to enable the data flow from the HTTP source to the MQTT broker or [broker state store](../develop-edge-apps/overview-state-store.md).
 
 ## Prerequisites
 
@@ -37,12 +37,11 @@ You need any credentials required to access the HTTP source. If the HTTP source
 
 [!INCLUDE [deploy-preview-http-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 HTTP, media, or ONVIF connectors: `No connector configuration present for AssetEndpointProfile: <AssetEndpointProfileName>`.
-
 ## Create a device
 
-To configure the connector for REST/HTTP, first create a device that defines the connection to the HTTP source. The device includes the URL of the HTTP source and any credentials you need to access the HTTP source.
+To configure the connector for REST/HTTP, first create a device that defines the connection to the HTTP source. The device includes the URL of the HTTP source and any credentials you need to access the HTTP source:
+
+# [Operations experience](#tab/portal)
 
 1. In the operations experience web UI, select **Devices** in the left navigation pane. Then select **Create new**.
 
@@ -64,10 +63,26 @@ To configure the connector for REST/HTTP, first create a device that defines the
 
     :::image type="content" source="media/howto-use-http-connector/http-connector-device-created.png" alt-text="Screenshot that shows the list of devices." lightbox="media/howto-use-http-connector/http-connector-device-created.png":::
 
+# [Azure CLI](#tab/cli)
+
+Run the following commands:
+
+```azurecli
+az iot ops ns device create -n rest-http-connector-cli -g {your resource group name} --instance {your instance name} 
+
+az iot ops ns device endpoint inbound add rest --device rest-http-connector-cli -g {your resource group name} -i {your instance name}  --name rest-http-connector-0 --endpoint-address "https://rest-http-connector-0"
+```
+
+To learn more, see [az iot ops ns device](/cli/azure/iot/ops/ns/device).
+
+---
+
 ## Create a namespace asset
 
 To define a namespace asset that publishes data points from the HTTP endpoint, follow these steps:
 
+# [Operations experience](#tab/portal)
+
 1. In the operations experience web UI, select **Assets** in the left navigation pane. Then select **Create namespace asset**.
 
 1. Select the inbound endpoint for the connector for REST/HTTP that you created in the previous section.
@@ -80,8 +95,26 @@ To define a namespace asset that publishes data points from the HTTP endpoint, f
 
     :::image type="content" source="media/howto-use-http-connector/add-data-point.png" alt-text="Screenshot that shows how to add a data point for HTTP source." lightbox="media/howto-use-http-connector/add-data-point.png":::
 
-    Add details for each data point to publish to the MQTT broker. Then select **Next** to continue.
+    Add details for each data point to publish to the MQTT broker.
+
+1. To configure the destination for the data, select **Manage default dataset**. Choose either **MQTT broker** or **Broker state store** as the destination. If you choose **MQTT broker**, you can enter the name of the topic to publish to. If you choose **Broker state store**, you can enter the key of the entry in the state store to use.
+
+    :::image type="content" source="media/howto-use-http-connector/configure-dataset.png" alt-text="Screenshot that shows how to configure the dataset for HTTP source." lightbox="media/howto-use-http-connector/configure-dataset.png":::
+
+    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:
 
     :::image type="content" source="media/howto-use-http-connector/http-asset-created.png" alt-text="Screenshot that shows the list of assets." lightbox="media/howto-use-http-connector/http-asset-created.png":::
+
+# [Azure CLI](#tab/cli)
+
+Run the following command:
+
+```azurecli
+az iot ops ns asset rest create --name myrestasset --instance {your instance name} -g {your resource group name} --device rest-http-connector-cli --endpoint rest-http-connector-0 --dataset-dest topic="azure-iot-operations/data/erp" retain=Never qos=Qos1 ttl=3600
+```
+
+To learn more, see [az iot ops ns asset rest](/cli/azure/iot/ops/ns/asset/rest).
+
+---

articles/iot-operations/discover-manage-assets/media/howto-use-http-connector/configure-dataset.png

@@ -7,50 +7,13 @@ ms.date: 07/25/2025
 ms.author: dobett
 ---
 
-Before you can use the preview connectors (ONVIF, media, and REST/HTTP) in the operations experience web UI, an administrator must:
+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:
 
-1. Enable them in your Azure IoT Operations instance.
-1. Add connector template instances to your Azure IoT Operations instance.
+:::image type="content" source="media/deploy-preview-media-connectors/portal-enable-preview-connectors.png" alt-text="Screenshot of Azure portal that shows that preview features are enabled." lightbox="media/deploy-preview-media-connectors/portal-enable-preview-connectors.png":::
 
-To enable the preview connectors, you can either enable them when you deploy your Azure IoT Operations instance or enable them after you deploy your instance.
+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.
 
-To enable the preview connectors when you deploy your Azure IoT Operations instance:
-
-# [Azure portal](#tab/portal)
-
-Select **ONVIF Connector and Media Connector (Preview)** in the **Connectors** section of the **Install Azure IoT Operations > Basics** page:
-
-:::image type="content" source="media/deploy-preview-media-connectors/portal-deploy-preview-connectors.png" alt-text="Screenshot of Azure portal that shows how to select the preview connectors." lightbox="media/deploy-preview-media-connectors/portal-deploy-preview-connectors.png":::
-
-# [Azure CLI](#tab/cli)
-
-Include the `--feature connectors.settings.preview=Enabled` parameter when you run the `az iot ops create` command.
-
----
-
-To enable the preview connectors after you deploy your Azure IoT Operations instance:
-
-# [Azure portal](#tab/portal)
-
-1. Go to your Azure IoT Operations instance in the Azure portal.
-
-1. Enable the preview connectors:
-
-  :::image type="content" source="media/deploy-preview-media-connectors/portal-enable-preview-connectors.png" alt-text="Screenshot of Azure portal that shows how to enable the preview connectors." lightbox="media/deploy-preview-media-connectors/portal-enable-preview-connectors.png":::
-
-# [Azure CLI](#tab/cli)
-
-Run the following command to enable the preview connectors:
-
-```azcli
-az iot ops update -n <your-instance> -g <your-resource-group> --feature connectors.settings.preview=Enabled
-```
-
----
-
-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 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 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).
 
 To add a connector template instance to your Azure IoT Operations instance: