Quickstart updates for devices

Author: dominicbetts

articles/iot-operations/get-started-end-to-end-sample/media/quickstart-configure/asset-endpoint-list.png

@@ -1,12 +1,12 @@
 ---
 title: "Quickstart: Configure your cluster"
-description: "Quickstart: Configure asset endpoints, assets, and data flows in your cluster to process and route data from a simulated OPC PLC server to the cloud."
+description: "Quickstart: Configure devices, assets, and data flows in your cluster to process and route data from a simulated OPC PLC server to the cloud."
 author: dominicbetts
 ms.author: dobett
 ms.topic: quickstart
 ms.custom:
   - ignite-2023
-ms.date: 10/17/2024
+ms.date: 07/18/2025
 
 #CustomerIntent: As an OT user, I want to configure my Azure IoT Operations cluster so that I can see how to process and route data to a cloud endpoint.
 ---
@@ -15,13 +15,13 @@ ms.date: 10/17/2024
 
 In this quickstart, you configure the following resources in your Azure IoT Operations cluster:
 
-- An *asset endpoint* that defines a connection to a simulated OPC PLC server that simulates an oven in a bakery.
+- A *device* that defines a connection to a simulated OPC PLC server that simulates an oven in a bakery.
 - An *asset* that represents the oven and defines the data points that the oven exposes.
 - A *data flow* that manipulates the messages from the simulated oven.
 
-An _asset_ is a physical device or logical entity that represents a device, a machine, a system, or a process. For example, a physical asset could be a pump, a motor, a tank, or a production line. A logical asset that you define can have properties, stream messages such as sensor data, or generate events.
+In the context of Azure IoT operations, an asset is a logical representation of a physical device or system that you want to monitor or control.
 
-_OPC UA servers_ are software applications that communicate with assets. _OPC UA tags_ are data points that OPC UA servers expose. OPC UA tags can provide real-time or historical data about the status, performance, quality, or condition of assets.
+*OPC UA servers* are software applications that communicate with assets. *OPC UA data points* are values that OPC UA servers expose. OPC UA data points can provide real-time or historical data about the status, performance, quality, or condition of assets.
 
 In this quickstart, you use a Bicep file to configure your Azure IoT Operations instance.
 
@@ -101,7 +101,7 @@ AIO_EXTENSION_NAME=$(az k8s-extension list -g $RESOURCE_GROUP --cluster-name $CL
 AIO_INSTANCE_NAME=$(az iot ops list -g $RESOURCE_GROUP --query "[0].name" -o tsv)
 CUSTOM_LOCATION_NAME=$(az iot ops list -g $RESOURCE_GROUP --query "[0].extendedLocation.name" -o tsv | awk -F'/' '{print $NF}')
 
-az deployment group create --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --template-file quickstart.bicep --parameters clusterName=$CLUSTER_NAME customLocationName=$CUSTOM_LOCATION_NAME aioExtensionName=$AIO_EXTENSION_NAME aioInstanceName=$AIO_INSTANCE_NAME
+az deployment group create --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --template-file quickstart.bicep --parameters clusterName=$CLUSTER_NAME customLocationName=$CUSTOM_LOCATION_NAME aioExtensionName=$AIO_EXTENSION_NAME aioInstanceName=$AIO_INSTANCE_NAME aioNamespaceName=myqsnamespace
 ```
 
 # [PowerShell](#tab/powershell)
@@ -113,7 +113,7 @@ $AIO_EXTENSION_NAME = (az k8s-extension list -g $RESOURCE_GROUP --cluster-name $
 $AIO_INSTANCE_NAME = $(az iot ops list -g $RESOURCE_GROUP --query "[0].name" -o tsv)
 $CUSTOM_LOCATION_NAME = (az iot ops list -g $RESOURCE_GROUP --query "[0].extendedLocation.name" -o tsv) -split '/' | Select-Object -Last 1
 
-az deployment group create --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --template-file quickstart.bicep --parameters clusterName=$CLUSTER_NAME customLocationName=$CUSTOM_LOCATION_NAME aioExtensionName=$AIO_EXTENSION_NAME aioInstanceName=$AIO_INSTANCE_NAME
+az deployment group create --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --template-file quickstart.bicep --parameters clusterName=$CLUSTER_NAME customLocationName=$CUSTOM_LOCATION_NAME aioExtensionName=$AIO_EXTENSION_NAME aioInstanceName=$AIO_INSTANCE_NAME aioNamespaceName=myqsnamespace
 ```
 
 ---
@@ -122,18 +122,18 @@ az deployment group create --subscription $SUBSCRIPTION_ID --resource-group $RES
 
 The Bicep file configured the following resources:
 
-- An asset endpoint that connects to the OPC PLC simulator.
+- A device that connects to the OPC PLC simulator.
 - An asset that represents the oven and defines the data points that the oven exposes.
 - Two data flows that process the messages from the simulated oven.
 - An Azure Event Hubs namespace that contains a destination hub for the data flows.
 
-To view the asset endpoint, asset, and data flows, navigate to the [operations experience](https://iotoperations.azure.com) UI in your browser and sign in with your Microsoft Entra ID credentials. Because you're working with a new deployment, there are no sites yet. You can find the cluster you created in the previous quickstart by selecting **View unassigned instances**. In the operations experience, an instance represents a cluster where you deployed Azure IoT Operations.
+To view the device, asset, and data flows, navigate to the [operations experience](https://iotoperations.azure.com) UI in your browser and sign in with your Microsoft Entra ID credentials. Because you're working with a new deployment, there are no sites yet. You can find the cluster you created in the previous quickstart by selecting **View unassigned instances**. In the operations experience, an instance represents a cluster where you deployed Azure IoT Operations.
 
 :::image type="content" source="media/quickstart-configure/instance-list.png" alt-text="Screenshot in the operations experience showing unassigned instances.":::
 
-The asset endpoint defines the connection to the OPC PLC simulator:
+The opc-ua-connector device defines the connection to the OPC PLC simulator:
 
-:::image type="content" source="media/quickstart-configure/asset-endpoint-list.png" alt-text="Screenshot in the operations experience that shows a list of asset endpoints.":::
+:::image type="content" source="media/quickstart-configure/device-list.png" alt-text="Screenshot in the operations experience that shows a list of devices.":::
 
 The oven asset defines the data points that the oven exposes:
 
@@ -166,7 +166,7 @@ If messages are flowing, you can use the **Data Explorer** to view the messages:
 
 ## How did we solve the problem?
 
-In this quickstart, you used a bicep file to configure your Azure IoT Operations instance with an asset endpoint, asset, and data flow. The configuration processes and routes data from a simulated oven. The data flow in the configuration routes the messages to an Azure Event Hubs instance.
+In this quickstart, you used a bicep file to configure your Azure IoT Operations instance with a device, asset, and data flow. The configuration processes and routes data from a simulated oven. The data flow in the configuration routes the messages to an Azure Event Hubs instance.
 
 ## Clean up resources
 

articles/iot-operations/get-started-end-to-end-sample/media/quickstart-configure/asset-list.png

@@ -187,6 +187,16 @@ Run the following CLI commands in your Codespaces terminal.
    az iot ops schema registry create --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP --registry-namespace $SCHEMA_REGISTRY_NAMESPACE --sa-resource-id $(az storage account show --name $STORAGE_ACCOUNT -o tsv --query id)
    ```
 
+## Create an Azure Device Registry namespace
+
+Azure IoT Operations and Azure Device Registry use _namespaces_ to organize assets and devices. Each Azure IoT Operations instance uses a single namespace for its assets and devices.
+
+Run the following CLI command to create an Azure Device Registry namespace.
+
+```azurecli
+az iot ops ns create -n myqsnamespace -g $RESOURCE_GROUP
+```
+
 ## Deploy Azure IoT Operations
 
 In this section, you configure your cluster with the dependencies for your Azure IoT Operations components, then deploy Azure IoT Operations.
@@ -207,7 +217,7 @@ Run the following CLI commands in your Codespaces terminal.
 1. Deploy Azure IoT Operations.
 
    ```azurecli
-   az iot ops create --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name ${CLUSTER_NAME}-instance  --sr-resource-id $(az iot ops schema registry show --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP -o tsv --query id) --broker-frontend-replicas 1 --broker-frontend-workers 1  --broker-backend-part 1  --broker-backend-workers 1 --broker-backend-rf 2 --broker-mem-profile Low
+   az iot ops create --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name ${CLUSTER_NAME}-instance --sr-resource-id $(az iot ops schema registry show --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP -o tsv --query id) --ns-resource-id $(az iot ops ns show --name myqsnamespace --resource-group $RESOURCE_GROUP -o tsv --query id) --broker-frontend-replicas 1 --broker-frontend-workers 1  --broker-backend-part 1  --broker-backend-workers 1 --broker-backend-rf 2 --broker-mem-profile Low
    ```
 
    This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.