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
Copy file name to clipboardExpand all lines: articles/iot-edge/about-iot-edge.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ The Azure IoT Edge runtime runs on a large set of IoT devices that enables using
61
61
62
62
It's difficult to manage the software life cycle for millions of IoT devices that are often different makes and models or geographically scattered. Workloads are created and configured for a particular type of device, deployed to all of your devices, and monitored to catch any misbehaving devices. These activities can't be done on a per device basis and must be done at scale.
63
63
64
-
Azure IoT Edge integrates seamlessly with [Azure IoT Central](/azure/iot-central/) to provide one control plane for your solution's needs. Cloud services allow you to:
64
+
Azure IoT Edge integrates seamlessly with [Azure IoT Central](../iot-central/index.yml) to provide one control plane for your solution's needs. Cloud services allow you to:
65
65
66
66
* Create and configure a workload to be run on a specific type of device.
Copy file name to clipboardExpand all lines: articles/iot-edge/quickstart.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,7 +155,7 @@ Run the following PowerShell commands on the target device where you want to dep
155
155
156
156
1. Enter 'O' or 'R' to toggle **Optional diagnostic data** on or off, depending on your preference. A successful deployment is pictured below.
157
157
158
-
:::image type="content" source="./media/quickstart/successful-powershell-deployment.png" alt-text="Screenshot that show that a successful deployment will say Deployment successful at the end of the messages in the console.":::
158
+
:::image type="content" source="./media/quickstart/successful-powershell-deployment.png" alt-text="Screenshot that show that a successful deployment will say Deployment successful at the end of the messages in the console." lightbox="./media/quickstart/successful-powershell-deployment.png":::
159
159
160
160
1. Provision your device using the device connection string that you retrieved in the previous section. Replace the placeholder text with your own value.
161
161
@@ -215,7 +215,7 @@ Follow these steps to deploy your first module from Azure Marketplace.
215
215
216
216
You should see three modules: **$edgeAgent**, **$edgeHub**, and **SimulatedTemperatureSensor**. If one or more of the modules has **Yes** under **Specified in Deployment** but not under **Reported by Device**, your IoT Edge device is still starting them. Wait a few minutes, and then refresh the page.
217
217
218
-
:::image type="content" source="./media/quickstart-linux/view-deployed-modules.png" alt-text="Screenshot that shows the Simulated Temperature Sensor in the list of deployed modules..":::
218
+
:::image type="content" source="./media/quickstart-linux/view-deployed-modules.png" alt-text="Screenshot that shows the Simulated Temperature Sensor in the list of deployed modules." lightbox="./media/quickstart-linux/view-deployed-modules.png":::
219
219
220
220
## View the generated data
221
221
@@ -238,7 +238,7 @@ The module that you pushed generates sample environment data that you can use fo
238
238
sudo iotedge list
239
239
```
240
240
241
-
:::image type="content" source="./media/quickstart/iotedge-list-screen.png" alt-text="Screenshot that shows where to verify that your temperature sensor, agent, and hub modules are running.":::
241
+
:::image type="content" source="./media/quickstart/iotedge-list-screen.png" alt-text="Screenshot that shows where to verify that your temperature sensor, agent, and hub modules are running." lightbox="./media/quickstart/iotedge-list-screen.png":::
242
242
243
243
1. View the messages being sent from the temperature sensor module to the cloud using the following Linux command:
244
244
@@ -249,7 +249,7 @@ The module that you pushed generates sample environment data that you can use fo
249
249
>[!IMPORTANT]
250
250
>IoT Edge commands are case-sensitive when they refer to module names.
251
251
252
-
:::image type="content" source="./media/quickstart/temperature-sensor-screen.png" alt-text="Screenshot that shows the output logs of the Simulated Temperature Sensor module when it's running.":::
252
+
:::image type="content" source="./media/quickstart/temperature-sensor-screen.png" alt-text="Screenshot that shows the output logs of the Simulated Temperature Sensor module when it's running." lightbox="./media/quickstart/temperature-sensor-screen.png":::
253
253
254
254
You can also use the [Azure IoT Hub extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-toolkit) to watch messages arrive at your IoT hub.
0 commit comments