Skip to content

Commit def5090

Browse files
authored
Merge pull request #303104 from dominicbetts/release-aio-2507-opcua
AIO 2507: OPC UA howto updates
2 parents f477548 + d639edf commit def5090

17 files changed

+81
-115
lines changed

articles/iot-operations/discover-manage-assets/howto-configure-opc-ua.md

Lines changed: 69 additions & 103 deletions
Large diffs are not rendered by default.

articles/iot-operations/discover-manage-assets/howto-use-media-connector.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ To create a device configuration:
100100

101101
1. Select **devices** and then **Create device**:
102102

103-
:::image type="content" source="media/howto-configure-opc-ua/asset-endpoints.png" alt-text="Screenshot that shows the devices page in the operations experience." lightbox="media/howto-configure-opc-ua/asset-endpoints.png":::
103+
:::image type="content" source="media/howto-configure-opc-ua/devices.png" alt-text="Screenshot that shows the devices page in the operations experience." lightbox="media/howto-configure-opc-ua/devices.png":::
104104

105105
> [!TIP]
106106
> You can use the filter box to search for devices.
@@ -176,7 +176,7 @@ authentication: {
176176
}
177177
```
178178

179-
# [Bicep (PowersShell)](#tab/bicep-powershell)
179+
# [Bicep (PowerShell)](#tab/bicep-powershell)
180180

181181
1. Set the following environment variables:
182182

@@ -297,7 +297,7 @@ The following snippet shows the bicep file that you used to create the asset:
297297

298298
:::code language="bicep" source="~/azure-iot-operations-samples/samples/media-connector-bicep/asset-snapshot-to-mqtt.bicep":::
299299

300-
# [Bicep (PowersShell)](#tab/bicep-powershell)
300+
# [Bicep (PowerShell)](#tab/bicep-powershell)
301301

302302
1. Set the following environment variables:
303303

@@ -408,7 +408,7 @@ The following snippet shows the bicep file that you used to create the asset:
408408

409409
:::code language="bicep" source="~/azure-iot-operations-samples/samples/media-connector-bicep/asset-snapshot-to-fs.bicep":::
410410

411-
# [Bicep (PowersShell)](#tab/bicep-powershell)
411+
# [Bicep (PowerShell)](#tab/bicep-powershell)
412412

413413
1. Set the following environment variables:
414414

@@ -500,7 +500,7 @@ The following snippet shows the bicep file that you used to create the asset:
500500

501501
:::code language="bicep" source="~/azure-iot-operations-samples/samples/media-connector-bicep/asset-clip-to-fs.bicep":::
502502

503-
# [Bicep (PowersShell)](#tab/bicep-powershell)
503+
# [Bicep (PowerShell)](#tab/bicep-powershell)
504504

505505
1. Set the following environment variables:
506506

@@ -595,7 +595,7 @@ The following snippet shows the bicep file that you used to create the asset:
595595

596596
:::code language="bicep" source="~/azure-iot-operations-samples/samples/media-connector-bicep/asset-stream-to-rtsp.bicep":::
597597

598-
# [Bicep (PowersShell)](#tab/bicep-powershell)
598+
# [Bicep (PowerShell)](#tab/bicep-powershell)
599599

600600
1. Set the following environment variables:
601601

articles/iot-operations/discover-manage-assets/howto-use-onvif-connector.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ To create a device configuration:
8080

8181
1. Select **devices** and then **Create device**:
8282

83-
:::image type="content" source="media/howto-configure-opc-ua/asset-endpoints.png" alt-text="Screenshot that shows the devices page in the operations experience." lightbox="media/howto-configure-opc-ua/asset-endpoints.png":::
83+
:::image type="content" source="media/howto-configure-opc-ua/devices.png" alt-text="Screenshot that shows the devices page in the operations experience." lightbox="media/howto-configure-opc-ua/devices.png":::
8484

8585
> [!TIP]
8686
> You can use the filter box to search for devices.
@@ -156,7 +156,7 @@ authentication: {
156156
}
157157
```
158158

159-
# [Bicep (PowersShell)](#tab/bicep-powershell)
159+
# [Bicep (PowerShell)](#tab/bicep-powershell)
160160

161161
1. Set the following environment variables:
162162

@@ -280,7 +280,7 @@ The following snippet shows the bicep file that you used to create the asset. Th
280280

281281
:::code language="bicep" source="~/azure-iot-operations-samples/samples/onvif-connector-bicep/asset-ptz.bicep":::
282282

283-
# [Bicep (PowersShell)](#tab/bicep-powershell)
283+
# [Bicep (PowerShell)](#tab/bicep-powershell)
284284

285285
1. Set the following environment variables:
286286

@@ -354,7 +354,7 @@ The following snippet shows the bicep file that you used to create the asset. Th
354354

355355
:::code language="bicep" source="~/azure-iot-operations-samples/samples/onvif-connector-bicep/asset-onvif-media.bicep":::
356356

357-
# [Bicep (PowersShell)](#tab/bicep-powershell)
357+
# [Bicep (PowerShell)](#tab/bicep-powershell)
358358

359359
1. Set the following environment variables:
360360

@@ -483,7 +483,7 @@ The connector for ONVIF now receives notifications of motion detected events fro
483483
}
484484
```
485485

486-
# [Bicep (PowersShell)](#tab/bicep-powershell)
486+
# [Bicep (PowerShell)](#tab/bicep-powershell)
487487

488488
1. Set the following environment variables:
489489

@@ -542,7 +542,7 @@ The sample application uses the Azure IoT Operations MQTT broker to send command
542542

543543
### Access the camera's video streams
544544

545-
To manually create an device and asset that enable access to the video streams of the ONVIF-compliant camera:
545+
To manually create a device and asset that enable access to the video streams of the ONVIF-compliant camera:
546546

547547
1. During public preview, first use a tool to discover the RTSP stream URLs of the camera.
548548

-1.18 KB
Loading
-8.61 KB
Loading
-1.98 KB
Loading
-9.25 KB
Loading
-22 Bytes
Loading
-8.37 KB
Loading

0 commit comments

Comments
 (0)