Skip to content

Commit a0fe50a

Browse files
Merge pull request #312450 from jlian/fix/broken-scp-links-batch
Fix broken SCP documentation links across IoT Edge gateway docs
2 parents c4db1f4 + b720cd7 commit a0fe50a

5 files changed

Lines changed: 10 additions & 10 deletions

articles/iot-edge/how-to-authenticate-downstream-device.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Authenticate downstream devices - Azure IoT Edge
33
description: How to authenticate downstream devices to IoT Hub, and route their connection through Azure IoT Edge gateway devices.
44
author: sethmanheim
55
ms.author: sethm
6-
ms.date: 05/27/2025
6+
ms.date: 02/27/2026
77
ms.topic: concept-article
88
ms.service: azure-iot-edge
99
services: iot-edge
@@ -122,7 +122,7 @@ For X.509 self-signed authentication, sometimes referred to as thumbprint authen
122122
123123
4. Copy both the primary and secondary device certificates and their keys to any location on the downstream device. Also move a copy of the shared root CA certificate that generated both the gateway device certificate and the downstream device certificates.
124124
125-
You'll reference these certificate files in any applications on the downstream device that connect to IoT Hub. You can use a service like [Azure Key Vault](/azure/key-vault/) or a function like [Secure copy protocol](https://www.ssh.com/ssh/scp/) to move the certificate files.
125+
You'll reference these certificate files in any applications on the downstream device that connect to IoT Hub. You can use a service like [Azure Key Vault](/azure/key-vault/) or a function like [Secure copy protocol](https://www.ssh.com/academy/ssh/scp) to move the certificate files.
126126
127127
5. Depending on your preferred language, review samples of how X.509 certificates can be referenced in IoT applications:
128128

articles/iot-edge/how-to-connect-downstream-device.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Connect a downstream device to an Azure IoT Edge gateway
33
description: How to configure downstream devices to connect to Azure IoT Edge gateway devices.
44
author: sethmanheim
55
ms.author: sethm
6-
ms.date: 06/06/2025
6+
ms.date: 02/27/2026
77
ms.topic: concept-article
88
ms.service: azure-iot-edge
99
services: iot-edge
@@ -82,7 +82,7 @@ To verify the gateway device's certificates, the downstream device needs its own
8282

8383
If you haven't already, move this certificate file to any directory on your downstream device. Move the file by installing the CA certificate in the operating system's certificate store, or by referencing the certificate within applications that use the Azure IoT SDKs.
8484

85-
Use a service like [Azure Key Vault](/azure/key-vault/) or a tool like [Secure copy protocol](https://www.ssh.com/ssh/scp/) to move the certificate file.
85+
Use a service like [Azure Key Vault](/azure/key-vault/) or a tool like [Secure copy protocol](https://www.ssh.com/academy/ssh/scp) to move the certificate file.
8686

8787
## Install certificates in the OS
8888

articles/iot-edge/how-to-create-transparent-gateway.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create transparent gateway device using Azure IoT Edge
33
description: Use an Azure IoT Edge device as a transparent gateway that can process information from downstream devices
44
author: sethmanheim
55
ms.author: sethm
6-
ms.date: 06/05/2025
6+
ms.date: 02/27/2026
77
ms.topic: concept-article
88
ms.service: azure-iot-edge
99
services: iot-edge
@@ -87,7 +87,7 @@ If you don't have your own certificate authority and want to use demo certificat
8787
# [IoT Edge](#tab/iotedge)
8888

8989
1. Check the certificate meets [format requirements](how-to-manage-device-certificates.md#format-requirements).
90-
1. If you created the certificates on a different machine, copy them to your IoT Edge device. Use a USB drive, a service like [Azure Key Vault](/azure/key-vault/general/overview), or a command like [Secure file copy](https://www.ssh.com/ssh/scp/).
90+
1. If you created the certificates on a different machine, copy them to your IoT Edge device. Use a USB drive, a service like [Azure Key Vault](/azure/key-vault/general/overview), or a command like [Secure file copy](https://www.ssh.com/academy/ssh/scp).
9191
1. Create the certificates and keys directories and set permissions. Store your certificates and keys in the preferred `/var/aziot` directory: `/var/aziot/certs` for certificates and `/var/aziot/secrets` for keys.
9292

9393
```bash

articles/iot-edge/tutorial-nested-iot-edge-for-linux-on-windows.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Tutorial - Create a hierarchy of IoT Edge devices - Azure IoT Edge for Li
33
description: This tutorial shows you how to create a hierarchical structure of IoT Edge for Linux on Windows devices.
44
author: sethmanheim
55
ms.author: sethm
6-
ms.date: 07/22/2025
6+
ms.date: 02/27/2026
77
ms.topic: tutorial
88
ms.service: azure-iot-edge
99
ms.custom: devx-track-azurecli, linux-related-content
@@ -162,7 +162,7 @@ In addition to the provisioning of your devices, the configuration steps establi
162162

163163
To configure the IoT Edge runtime, you need to apply the configuration bundles to your devices. The configurations differ between the *top layer device* and a *lower layer device*, so be mindful of the device configuration file you're applying to each device.
164164

165-
Each device needs its corresponding configuration bundle. You can use a USB drive or [secure file copy](https://www.ssh.com/ssh/scp/) to move the configuration bundles to each device. You need to copy the configuration bundle to the Windows host OS of each EFLOW device and then copy it to the EFLOW VM.
165+
Each device needs its corresponding configuration bundle. You can use a USB drive or [secure file copy](https://www.ssh.com/academy/ssh/scp) to move the configuration bundles to each device. You need to copy the configuration bundle to the Windows host OS of each EFLOW device and then copy it to the EFLOW VM.
166166

167167
> [!WARNING]
168168
> Be sure to send the correct configuration bundle to each device.

articles/iot-edge/tutorial-nested-iot-edge.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create a hierarchy of Azure IoT Edge devices
33
description: This tutorial shows you how to create a hierarchical structure of IoT Edge devices with secure communication. The configuration is also known as nested edge.
44
author: sethmanheim
55
ms.author: sethm
6-
ms.date: 07/11/2025
6+
ms.date: 02/27/2026
77
ms.topic: tutorial
88
ms.service: azure-iot-edge
99
services: iot-edge
@@ -165,7 +165,7 @@ In addition to the provisioning of your devices, the configuration steps establi
165165

166166
To configure the IoT Edge runtime, apply the configuration bundles to your devices. The configurations are different for the *top layer device* and a *lower layer device*, so make sure you use the right configuration file for each device.
167167

168-
1. Copy each configuration bundle archive file to its corresponding device. You can use a USB drive, a service like [Azure Key Vault](/azure/key-vault/general/overview), or with a function like [Secure file copy](https://www.ssh.com/ssh/scp/). Choose one of these methods that best matches your scenario.
168+
1. Copy each configuration bundle archive file to its corresponding device. You can use a USB drive, a service like [Azure Key Vault](/azure/key-vault/general/overview), or with a function like [Secure file copy](https://www.ssh.com/academy/ssh/scp). Choose one of these methods that best matches your scenario.
169169

170170
For example, to send the *parent-1* configuration bundle to the home directory on the *parent-1* VM, you could use a command like the following example:
171171

0 commit comments

Comments
 (0)