Skip to content

Commit d88e2ab

Browse files
Merge pull request #213118 from msjasteppe/iot-hub-url-updates
Fixing broken URLs.
2 parents 00f2ffd + 4815c57 commit d88e2ab

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/healthcare-apis/iot/device-data-through-iot-hub.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ For more information on Azure role-based access control, see [Azure role-based a
3939

4040
## Connect IoT Hub with the MedTech service
4141

42-
Azure IoT Hub supports a feature called [message routing](/azure/iot-hub/iot-hub-devguide-messages-d2c.md). Message routing provides the capability to send device data to various Azure services (for example: event hub, Storage Accounts, and Service Buses). MedTech service uses this feature to allow an IoT Hub to connect and send device messages to the MedTech service device message event hub endpoint.
42+
Azure IoT Hub supports a feature called [message routing](../../iot-hub/iot-hub-devguide-messages-d2c.md). Message routing provides the capability to send device data to various Azure services (for example: event hub, Storage Accounts, and Service Buses). MedTech service uses this feature to allow an IoT Hub to connect and send device messages to the MedTech service device message event hub endpoint.
4343

44-
Follow these directions to grant access to the IoT Hub system-assigned managed identity to your MedTech service device message event hub and set up message routing: [Configure message routing with managed identities](/azure-pipelines.yml/iot-hub/iot-hub-managed-identitymd#egress-connectivity-from-iot-hub-to-other-azure-resources)
44+
Follow these directions to grant access to the IoT Hub system-assigned managed identity to your MedTech service device message event hub and set up message routing: [Configure message routing with managed identities](../../iot-hub/iot-hub-managed-identity.md#egress-connectivity-from-iot-hub-to-other-azure-resources).
4545

4646
## Send device message to IoT Hub
4747

@@ -90,4 +90,4 @@ To learn about the different stages of data flow within MedTech service, see
9090
>[!div class="nextstepaction"]
9191
>[MedTech service data flow](iot-data-flow.md)
9292
93-
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
93+
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

0 commit comments

Comments
 (0)