Skip to content

Commit b7836b3

Browse files
committed
update
1 parent 970ff5d commit b7836b3

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/iot-edge/how-to-install-iot-edge-ubuntuvm-bicep.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,42 +34,42 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
3434

3535
1. Ensure that you have installed the Azure CLI iot extension with:
3636

37-
```azurecli-interactive
37+
```azurecli
3838
az extension add --name azure-iot
3939
```
4040

4141
1. Next, if you're using Azure CLI on your desktop, start by logging in:
4242

43-
```azurecli-interactive
43+
```azurecli
4444
az login
4545
```
4646

4747
1. If you have multiple subscriptions, select the subscription you'd like to use:
4848
1. List your subscriptions:
4949

50-
```azurecli-interactive
50+
```azurecli
5151
az account list --output table
5252
```
5353
5454
1. Copy the SubscriptionID field for the subscription you'd like to use.
5555
5656
1. Set your working subscription with the ID that you copied:
5757
58-
```azurecli-interactive
58+
```azurecli
5959
az account set -s <SubscriptionId>
6060
```
6161
6262
1. Create a new resource group (or specify an existing one in the next steps):
6363
64-
```azurecli-interactive
64+
```azurecli
6565
az group create --name IoTEdgeResources --location westus2
6666
```
6767

6868
1. Create a new virtual machine:
6969
:::moniker range="iotedge-2018-06"
7070
To use an **authenticationType** of `password`, see the example below:
7171

72-
```azurecli-interactive
72+
```azurecli
7373
az deployment group create \
7474
--resource-group IoTEdgeResources \
7575
--template-file "main.bicep" \
@@ -82,7 +82,7 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
8282

8383
To authenticate with an SSH key, you may do so by specifying an **authenticationType** of `sshPublicKey`, then provide the value of the SSH key in the **adminPasswordOrKey** parameter. An example is shown below.
8484

85-
```azurecli-interactive
85+
```azurecli
8686
#Generate the SSH Key
8787
ssh-keygen -m PEM -t rsa -b 4096 -q -f ~/.ssh/iotedge-vm-key -N ""
8888
@@ -101,7 +101,7 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
101101
:::moniker range=">=iotedge-2020-11"
102102
To use an **authenticationType** of `password`, see the example below:
103103

104-
```azurecli-interactive
104+
```azurecli
105105
az deployment group create \
106106
--resource-group IoTEdgeResources \
107107
--template-file "main.bicep" \
@@ -114,7 +114,7 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
114114

115115
To authenticate with an SSH key, you may do so by specifying an **authenticationType** of `sshPublicKey`, then provide the value of the SSH key in the **adminPasswordOrKey** parameter. An example is shown below.
116116

117-
```azurecli-interactive
117+
```azurecli
118118
#Generate the SSH Key
119119
ssh-keygen -m PEM -t rsa -b 4096 -q -f ~/.ssh/iotedge-vm-key -N ""
120120

0 commit comments

Comments
 (0)