Move IoT fundamentals articles to target service docsets

Move 5 articles from articles/iot/ to their target service directories:
- iot-mqtt-connect-to-iot-hub.md -> articles/iot-hub/
- iot-sdks.md -> articles/iot-hub/
- tutorial-use-mqtt.md -> articles/iot-hub/
- concepts-manage-device-reconnections.md -> articles/iot-hub/
- iot-mqtt-connect-to-iot-dps.md -> articles/iot-dps/

Changes include:
- Updated ms.service metadata in moved files
- Added redirects in .openpublishing.redirection.iot.json
- Updated iot/TOC.yml (removed entries)
- Updated iot-hub/TOC.yml (added local entries)
- Updated iot-dps/toc.yml (converted to local entry)
- Updated ~50 cross-references across iot-hub, iot, iot-central, iot-edge, iot-dps, and includes

Author: dominicbetts

articles/iot-central/core/concepts-architecture.md

@@ -62,7 +62,7 @@ IoT Central can also control devices by calling commands on the device. For exam
 
 The telemetry, properties, and commands that a device implements are collectively known as the device capabilities. You define these capabilities in a model that the device and the IoT Central application share. In IoT Central, this model is part of the device template that defines a specific type of device. To learn more, see [Assign a device to a device template](concepts-device-templates.md#assign-a-device-to-a-device-template).
 
-The device implementation should follow the [IoT Plug and Play conventions](/previous-versions/azure/iot/concepts-convention) to ensure that it can communicate with IoT Central. For more information, see the various language [SDKs and samples](../../iot/iot-sdks.md).
+The device implementation should follow the [IoT Plug and Play conventions](/previous-versions/azure/iot/concepts-convention) to ensure that it can communicate with IoT Central. For more information, see the various language [SDKs and samples](../../iot-hub/iot-sdks.md).
 
 Devices connect to IoT Central using one the supported protocols: [MQTT, AMQP, or HTTP](../../iot-hub/iot-hub-devguide-protocols.md).
 

articles/iot-central/core/concepts-device-implementation.md

@@ -138,7 +138,7 @@ If the device gets any of the following errors when it connects, it should use a
 
 To learn more about device error codes, see [Troubleshooting device connections](troubleshooting.md).
 
-To learn more about implementing automatic reconnections, see [Manage device reconnections to create resilient applications](../../iot/concepts-manage-device-reconnections.md).
+To learn more about implementing automatic reconnections, see [Manage device reconnections to create resilient applications](../../iot-hub/concepts-manage-device-reconnections.md).
 
 Currently, IoT Edge devices can't move between IoT hubs.
 

articles/iot-central/core/howto-use-commands.md

@@ -31,7 +31,7 @@ To learn more about the command data that a device exchanges with IoT Central, s
 
 To learn how to manage commands by using the IoT Central REST API, see [How to use the IoT Central REST API to control devices](../core/howto-control-devices-with-rest-api.md).
 
-To learn how to implement commands in a device without using the device SDKs, see [Communicate with an IoT hub using the MQTT protocol](../../iot/iot-mqtt-connect-to-iot-hub.md).
+To learn how to implement commands in a device without using the device SDKs, see [Communicate with an IoT hub using the MQTT protocol](../../iot-hub/iot-mqtt-connect-to-iot-hub.md).
 
 ## Define your commands
 

articles/iot-central/core/howto-use-properties.md

@@ -25,7 +25,7 @@ To learn more about the property data that a device exchanges with IoT Central,
 
 To learn how to manage properties by using the IoT Central REST API, see [How to use the IoT Central REST API to control devices](../core/howto-control-devices-with-rest-api.md).
 
-To learn how to implement properties in a device without using the device SDKs, see [Communicate with an IoT hub using the MQTT protocol](../../iot/iot-mqtt-connect-to-iot-hub.md).
+To learn how to implement properties in a device without using the device SDKs, see [Communicate with an IoT hub using the MQTT protocol](../../iot-hub/iot-mqtt-connect-to-iot-hub.md).
 
 ## Define your properties
 

…icles/iot/iot-mqtt-connect-to-iot-dps.md …s/iot-dps/iot-mqtt-connect-to-iot-dps.mdarticles/iot/iot-mqtt-connect-to-iot-dps.md renamed to articles/iot-dps/iot-mqtt-connect-to-iot-dps.md articles/iot/iot-mqtt-connect-to-iot-dps.md renamed to articles/iot-dps/iot-mqtt-connect-to-iot-dps.md

@@ -2,9 +2,10 @@
 title: Use MQTT to communicate with Azure IoT DPS
 titleSuffix: Azure IoT Device Provisioning Service
 description: Guidance on using the MQTT protocol to connect a device to the Azure IoT Device Provisioning Service device-facing endpoint.
-author: dominicbetts
-ms.author: dobett
-ms.service: azure-iot
+author: cwatson-cat
+ms.author: cwatson
+ms.service: azure-iot-hub
+ms.subservice: azure-iot-hub-dps
 ms.topic: how-to
 ms.date: 03/12/2025
 ms.custom:  [amqp, mqtt]
@@ -28,7 +29,7 @@ All device communication with DPS must be secured using TLS. Therefore, DPS does
 
 A device can use the MQTT protocol to connect to a DPS instance using any of the following options:
 
-* The [Azure IoT device provisioning SDKs](iot-sdks.md#dps-device-sdks).
+* The [Azure IoT device provisioning SDKs](../iot-hub/iot-sdks.md#dps-device-sdks).
 * The MQTT protocol directly.
 
 ## Use the MQTT protocol directly from a device

articles/iot-dps/toc.yml

@@ -87,7 +87,7 @@ items:
   - name: Protocols
     items: 
     - name: MQTT support
-      href: ../iot/iot-mqtt-connect-to-iot-dps.md?toc=/azure/iot-dps/toc.json&bc=/azure/iot-dps/breadcrumb/toc.json
+      href: iot-mqtt-connect-to-iot-dps.md
     - name: TLS support
       href: tls-support.md
   - name: Security practices for device manufacturers

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

@@ -130,7 +130,7 @@ Most applications use the Windows-provided TLS stack called [Schannel](/windows/
 
 ## Use certificates with Azure IoT SDKs
 
-[Azure IoT SDKs](../iot/iot-sdks.md) connect to an IoT Edge device using simple sample applications. The samples' goal is to connect the device client and send device telemetry messages to the gateway, then close the connection and exit.
+[Azure IoT SDKs](../iot-hub/iot-sdks.md) connect to an IoT Edge device using simple sample applications. The samples' goal is to connect the device client and send device telemetry messages to the gateway, then close the connection and exit.
 
 Before using the application-level samples, obtain the following items:
 

articles/iot-hub/TOC.yml

@@ -40,7 +40,7 @@
   - name: Protocol support
     items:
     - name: MQTT support
-      href: ../iot/iot-mqtt-connect-to-iot-hub.md?toc=/azure/iot-hub/toc.json&bc=/azure/iot-hub/breadcrumb/toc.json
+      href: iot-mqtt-connect-to-iot-hub.md
     - name: AMQP support
       href: iot-hub-amqp-support.md
     - name: Supporting additional protocols
@@ -242,6 +242,8 @@
     href: iot-hub-message-enrichments-overview.md
   - name: Use message enrichments
     href: tutorial-message-enrichments.md
+  - name: Tutorial - Connect a device with MQTT
+    href: tutorial-use-mqtt.md
 - name: Authentication and authorization
   items:
   - name: Built-in RBAC roles for IoT
@@ -303,6 +305,8 @@
     href: /azure/reliability/reliability-device-registry?toc=/azure/iot-hub/toc.json&bc=/azure/iot-hub/breadcrumb/toc.json
   - name: Disable disaster recovery
     href: how-to-disable-dr.md
+  - name: Manage device reconnections
+    href: concepts-manage-device-reconnections.md
   - name: Perform manual failover
     displayName: disaster recovery, failback, failover, geo-redundancy
     href: tutorial-manual-failover.md
@@ -385,7 +389,6 @@
   - name: X.509 certificates
     displayName: certificate authority (CA), subordinate CA, certificate versions, unique identifier, key identifier, binary certificate, PEM certificate, PKCS, X.509 certificates, OpenSSL, CSR, thumbprint
     href: reference-x509-certificates.md
-  - name: Feature and API retirement
   - name: Monitoring data reference
     href: monitor-iot-hub-reference.md
 - name: Resources
@@ -413,7 +416,7 @@
     - name: IoT Service SDKs
       href: ./iot-hub-devguide-sdks.md#azure-iot-hub-service-sdks
     - name: IoT Device SDKs
-      href: ../iot/iot-sdks.md
+      href: iot-sdks.md
   - name: Azure IoT samples
     items:
     - name: C# (.NET)

…/concepts-manage-device-reconnections.md …/concepts-manage-device-reconnections.mdarticles/iot/concepts-manage-device-reconnections.md renamed to articles/iot-hub/concepts-manage-device-reconnections.md articles/iot/concepts-manage-device-reconnections.md renamed to articles/iot-hub/concepts-manage-device-reconnections.md

@@ -2,13 +2,12 @@
 title: Manage device reconnections to create resilient applications
 titleSuffix: Azure IoT
 description: Manage the device connection and reconnection process to ensure resilient applications by using the Azure IoT Hub device SDKs.
-services: azure-iot
-author: dominicbetts
-ms.author: dobett
+author: cwatson-cat
+ms.author: cwatson
 ms.date: 1/10/2025
 ms.update-cycle: 1095-days
 ms.topic: concept-article
-ms.service: azure-iot
+ms.service: azure-iot-hub
 ms.custom: [amqp, mqtt, devx-track-csharp]
 ---
 

articles/iot-hub/how-to-cloud-to-device-messaging.md

@@ -86,7 +86,7 @@ For more information about the cloud-to-device message lifecycle and how IoT Hub
 
 ## Connection reconnection policy
 
-This article doesn't demonstrate a message retry policy for the device to IoT Hub connection or external application to IoT Hub connection. In production code, you should implement connection retry policies as described in [Manage device reconnections to create resilient applications](/azure/iot/concepts-manage-device-reconnections).
+This article doesn't demonstrate a message retry policy for the device to IoT Hub connection or external application to IoT Hub connection. In production code, you should implement connection retry policies as described in [Manage device reconnections to create resilient applications](concepts-manage-device-reconnections.md).
 
 ## Message retention time, retry attempts, and max delivery count