You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -107,13 +110,25 @@ There are three steps to create an IoT Edge deployment for Azure Security Center
107
110
108
111
``` json
109
112
{
110
-
"HostConfig":{
111
-
"PortBindings":{
112
-
"8883/tcp": [{"HostPort": "8883"}],
113
-
"443/tcp": [{"HostPort": "443"}],
114
-
"5671/tcp": [{"HostPort": "5671"}]
115
-
}
116
-
}
113
+
"HostConfig":{
114
+
"PortBindings":{
115
+
"8883/tcp":[
116
+
{
117
+
"HostPort":"8883"
118
+
}
119
+
],
120
+
"443/tcp":[
121
+
{
122
+
"HostPort":"443"
123
+
}
124
+
],
125
+
"5671/tcp":[
126
+
{
127
+
"HostPort":"5671"
128
+
}
129
+
]
130
+
}
131
+
}
117
132
}
118
133
```
119
134
1. Click **Save**.
@@ -122,16 +137,15 @@ There are three steps to create an IoT Edge deployment for Azure Security Center
122
137
123
138
#### Step 2: Specify routes
124
139
125
-
1. In the **Specify Routes** tab, make sure you have a route (explicit or implicit) that will forward messages from the **azureiotsecurity** module to **$upstream**.
126
-
1. Click **Next**.
140
+
1. In the **Specify Routes** tab, make sure you have a route (explicit or implicit) that will forward messages from the **azureiotsecurity** module to **$upstream** according to the following examples, only then click **Next**.
127
141
128
-
~~~Default implicit route
129
-
"route": "FROM /messages/* INTO $upstream"
130
-
~~~
142
+
~~~Default implicit route
143
+
"route": "FROM /messages/* INTO $upstream"
144
+
~~~
131
145
132
-
~~~Explicit route
133
-
"ASCForIoTRoute": "FROM /messages/modules/azureiotsecurity/* INTO $upstream"
134
-
~~~
146
+
~~~Explicit route
147
+
"ASCForIoTRoute": "FROM /messages/modules/azureiotsecurity/* INTO $upstream"
Create a virtual network with [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork). The following example creates a virtual network named *myVnet* with *mySubnet*:
238
+
Create a virtual network with [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork). The following example creates a virtual network named *dsVnet* with *mySubnet*:
239
239
240
240
```azurepowershell-interactive
241
241
# Create dual stack subnet
@@ -360,7 +360,7 @@ The following figure shows a sample output that lists the private IPv4 and IPv6
360
360
## View IPv6 dual stack virtual network in Azure portal
361
361
You can view the IPv6 dual stack virtual network in Azure portal as follows:
362
362
1. In the portal's search bar, enter *dsVnet*.
363
-
2. When **myVirtualNetwork** appears in the search results, select it. This launches the **Overview** page of the dual stack virtual network named *dsVnet*. The dual stack virtual network shows the two NICs with both IPv4 and IPv6 configurations located in the dual stack subnet named *dsSubnet*.
363
+
2. When **dsVnet** appears in the search results, select it. This launches the **Overview** page of the dual stack virtual network named *dsVnet*. The dual stack virtual network shows the two NICs with both IPv4 and IPv6 configurations located in the dual stack subnet named *dsSubnet*.
364
364
365
365

0 commit comments