Merge pull request #268532 from timlt/update-akri-command

Add step to check Akri is connected to OPC UA Broker

Author: prmerger-automator[bot]

articles/iot-operations/get-started/quickstart-add-assets.md

@@ -27,7 +27,7 @@ In this quickstart, you use the Azure IoT Operations (preview) portal to create
 
 Complete [Quickstart: Deploy Azure IoT Operations Preview to an Arc-enabled Kubernetes cluster](quickstart-deploy.md) before you begin this quickstart.
 
-To sign in to the Azure IoT Operations portal you need a work or school account in the tenant where you deployed Azure IoT Operations. If you're currently using a Microsoft account (MSA), you need to create a Microsoft Entra ID with at least contributor permissions for the resource group that contains your **Kubernetes - Azure Arc** instance. To learn more, see [Known Issues > Create Entra account](../troubleshoot/known-issues.md#azure-iot-operations-preview-portal).
+To sign in to the Azure IoT Operations portal, you need a work or school account in the tenant where you deployed Azure IoT Operations. If you're currently using a Microsoft account (MSA), you need to create a Microsoft Entra ID with at least contributor permissions for the resource group that contains your **Kubernetes - Azure Arc** instance. To learn more, see [Known Issues > Create Entra account](../troubleshoot/known-issues.md#azure-iot-operations-preview-portal).
 
 ## What problem will we solve?
 
@@ -138,7 +138,7 @@ Enter the following asset information:
 
 :::image type="content" source="media/quickstart-add-assets/create-asset-details.png" alt-text="Screenshot of Azure IoT Operations asset details page.":::
 
-Scroll down on the **Asset details** page and configure any additional properties for the asset such as:
+Scroll down on the **Asset details** page and configure any other properties for the asset such as:
 
 - Manufacturer
 - Manufacturer URI
@@ -149,7 +149,7 @@ Scroll down on the **Asset details** page and configure any additional propertie
 - Serial number
 - Documentation URI
 
-You can remove the sample properties that are already defined and add your own custom properties
+You can remove the sample properties that are already defined and add your own custom properties.
 
 Select **Next** to go to the **Add tags** page.
 
@@ -162,7 +162,7 @@ Add two OPC UA tags on the **Add tags** page. To add each tag, select **Add tag
 | ns=3;s=FastUInt10  | temperature | none               |
 | ns=3;s=FastUInt100 | Tag 10      | none               |
 
-The **Observability mode** is one of: none, gauge, counter, histogram, or log.
+The **Observability mode** is one of the following values: `none`, `gauge`, `counter`, `histogram`, or `log`.
 
 You can override the default sampling interval and queue size for each tag.
 
@@ -259,9 +259,9 @@ To verify the configuration, run the following command to view the Akri instance
 kubectl get akrii -n azure-iot-operations
 ```
 
-Note that it may take a few minutes for the instance to show up.
+It might take a few minutes for the instance to show up.
 
-The output from the previous command looks like the following example. You may need to wait for a few seconds for the Akri instance to be created:
+The output from the previous command looks like the following example. 
 
 ```console
 NAMESPACE              NAME                      CONFIG             SHARED   NODES            AGE
@@ -270,13 +270,29 @@ azure-iot-operations   akri-opcua-asset-dbdef0   akri-opcua-asset   true     ["d
 
 Now you can use these resources in the local cluster namespace.
 
+To confirm that Akri connected to the OPC UA Broker, copy and paste the name of the Akri instance from the previous step into the following command: 
+
+```bash
+kubectl get akrii <AKRI_INSTANCE_NAME> -n azure-iot-operations -o json
+```
+
+The command output looks like the following example. This example output shows the Akri instance `brokerProperties` values and confirms that the OPC UA Broker is connected.
+
+```json
+"spec": {
+
+        "brokerProperties": {
+            "ApplicationUri": "Boiler #2",
+            "AssetEndpointProfile": "{\"spec\":{\"uuid\":\"opc-ua-broker-opcplc-000000-azure-iot-operation\"……   
+```
+
 ## How did we solve the problem?
 
 In this quickstart, you added an asset endpoint and then defined an asset and tags. The assets and tags model data from the OPC UA server to make the data easier to use in an MQTT broker and other downstream processes. You use the thermostat asset you defined in the next quickstart.
 
 ## Clean up resources
 
-If you're not going to continue to use this deployment, delete the Kubernetes cluster that you deployed Azure IoT Operations to and remove the Azure resource group that contains the cluster.
+If you won't use this deployment further, delete the Kubernetes cluster that you deployed Azure IoT Operations to and remove the Azure resource group that contains the cluster.
 
 ## Next step