Skip to content

Commit 110e72f

Browse files
Merge pull request #287098 from baanders/release-aio-m2
AIO Nit quickstart edits
2 parents b7524c0 + 08cc41e commit 110e72f

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,12 +58,12 @@ To create asset endpoints, assets and subscribe to OPC UA tags and events, use t
5858

5959
Browse to the [operations experience](https://iotoperations.azure.com) in your browser and sign in with your Microsoft Entra ID credentials.
6060

61-
:::image type="content" source="media/quickstart-add-assets/site-list.png" alt-text="Screenshot that shows the unassigned instances node in the operations experience.":::
62-
6361
## Select your site
6462

6563
A _site_ is a collection of Azure IoT Operations instances. Sites typically group instances by physical location and make it easier for OT users to locate and manage assets. Your IT administrator creates [sites and assigns Azure IoT Operations instances to them](/azure/azure-arc/site-manager/overview). 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 **Unassigned instances**. In the operations experience, an instance represents a cluster where you deployed Azure IoT Operations.
6664

65+
:::image type="content" source="media/quickstart-add-assets/site-list.png" alt-text="Screenshot that shows the unassigned instances node in the operations experience.":::
66+
6767
## Select your instance
6868

6969
Select the instance where you deployed Azure IoT Operations in the previous quickstart:

articles/iot-operations/get-started-end-to-end-sample/quickstart-deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ Run the following CLI commands in your Codespaces terminal.
121121
>This command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.7.0 deployed on it, you can skip this step.
122122
123123
```azurecli
124-
az iot ops init --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --sr-resource-id $(az iot ops schema registry show --name $SCHEMA_REGISTRY -o tsv --query id)
124+
az iot ops init --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --sr-resource-id $(az iot ops schema registry show --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP -o tsv --query id)
125125
```
126126

127127
1. Deploy Azure IoT Operations. This command takes several minutes to complete:

0 commit comments

Comments
 (0)