Merge pull request #313865 from dominicbetts/iot-tidy-archive

IoT: Link tidy after archive

Author: prmerger-automator[bot]

articles/digital-twins/concepts-models.md

@@ -22,7 +22,7 @@ Models for Azure Digital Twins are defined using the Digital Twins Definition La
 
 You can view the full language description for DTDL v3 in GitHub: [DTDL Version 3 Language Description](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v3/DTDL.v3.md). This page includes DTDL reference details and examples to help you get started writing your own DTDL models.
 
-DTDL is based on JSON-LD and is programming-language independent. DTDL isn't exclusive to Azure Digital Twins. It is also used to represent device data in other IoT services such as [IoT Plug and Play](../iot/overview-iot-plug-and-play.md).
+DTDL is based on JSON-LD and is programming-language independent. DTDL isn't exclusive to Azure Digital Twins. It is also used to represent device data in other IoT services such as [IoT Plug and Play](/previous-versions/azure/iot/overview-iot-plug-and-play).
 
 The rest of this article summarizes how the language is used in Azure Digital Twins.
 

articles/digital-twins/how-to-parse-models.md

@@ -41,7 +41,7 @@ The capabilities of the parser include:
 * Determine whether a model is assignable from another model.
 
 > [!NOTE]
-> [IoT Plug and Play](../iot/overview-iot-plug-and-play.md) devices use a small syntax variant to describe their functionality. This syntax variant is a semantically compatible subset of the DTDL that is used in Azure Digital Twins. When using the parser library, you don't need to know which syntax variant was used to create the DTDL for your digital twin. The parser will always, by default, return the same model for both IoT Plug and Play and Azure Digital Twins syntax.
+> [IoT Plug and Play](/previous-versions/azure/iot/overview-iot-plug-and-play) devices use a small syntax variant to describe their functionality. This syntax variant is a semantically compatible subset of the DTDL that is used in Azure Digital Twins. When using the parser library, you don't need to know which syntax variant was used to create the DTDL for your digital twin. The parser will always, by default, return the same model for both IoT Plug and Play and Azure Digital Twins syntax.
 
 ## Code with the parser library
 

articles/digital-twins/overview.md

@@ -32,7 +32,7 @@ In Azure Digital Twins, you define the digital entities that represent the peopl
 You can think of these model definitions as a specialized vocabulary to describe your business. For a building management solution, for example, you might define a model that defines a *Building* type, a *Floor* type, and an *Elevator* type. Models are defined in a JSON-like language called [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v3/DTDL.v3.md). In Azure Digital Twins, DTDL models describe types of entities according to their state properties, components, and relationships. You can design your own model sets from scratch, or get started with a pre-existing set of [DTDL industry ontologies](concepts-ontologies.md) based on common vocabulary for your industry.
 
 >[!TIP]
->Version 2 of DTDL is also used for data models throughout other Azure IoT services, including [IoT Plug and Play](../iot/overview-iot-plug-and-play.md). This compatibility helps you connect your Azure Digital Twins solution with other parts of the Azure ecosystem.
+>Version 2 of DTDL is also used for data models throughout other Azure IoT services, including [IoT Plug and Play](/previous-versions/azure/iot/overview-iot-plug-and-play). This compatibility helps you connect your Azure Digital Twins solution with other parts of the Azure ecosystem.
 
 Once you've defined your data models, use them to create [digital twins](concepts-twins-graph.md) that represent each specific entity in your environment. For example, you might use the *Building* model definition to create several *Building*-type twins (*Building 1*, *Building 2*, and so on). You can also use the relationships in the model definitions to connect twins to each other, forming a conceptual graph.
 

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](../../iot/concepts-convention.md) 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/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

@@ -27,7 +27,7 @@ An IoT Central device template includes a _model_ that specifies the behaviors a
 
 Each model has a unique _digital twin model identifier_ (DTMI), such as `dtmi:com:example:Thermostat;1`. When a device connects to IoT Central, it sends the DTMI of the model it implements. IoT Central can then assign the correct device template to the device.
 
-[IoT Plug and Play](../../iot/overview-iot-plug-and-play.md) defines a set of [conventions](../../iot/concepts-convention.md) that a device should follow when it implements a Digital Twin Definition Language (DTDL) model.
+[IoT Plug and Play](/previous-versions/azure/iot/overview-iot-plug-and-play) defines a set of [conventions](/previous-versions/azure/iot/concepts-convention) that a device should follow when it implements a Digital Twin Definition Language (DTDL) model.
 
 The [Azure IoT device SDKs](#device-sdks) include support for the IoT Plug and Play conventions.
 
@@ -51,7 +51,7 @@ A DTDL model can be a _no-component_ or a _multi-component_ model:
 > [!TIP]
 > You can [import and export a complete device model or individual interface](howto-set-up-template.md#interfaces-and-components) from an IoT Central device template as a DTDL v2 file.
 
-To learn more about device models, see the [IoT Plug and Play modeling guide](../../iot/concepts-modeling-guide.md)
+To learn more about device models, see the [IoT Plug and Play modeling guide](/previous-versions/azure/iot/concepts-modeling-guide)
 
 ### Conventions
 
@@ -65,9 +65,9 @@ A device should follow the IoT Plug and Play conventions when it exchanges data
 > [!NOTE]
 > Currently, IoT Central does not fully support the DTDL **Array** and **Geospatial** data types.
 
-To learn more about the IoT Plug and Play conventions, see [IoT Plug and Play conventions](../../iot/concepts-convention.md).
+To learn more about the IoT Plug and Play conventions, see [IoT Plug and Play conventions](/previous-versions/azure/iot/concepts-convention).
 
-To learn more about the format of the JSON messages that a device exchanges with IoT Central, see [Telemetry, property, and command payloads](../../iot/concepts-message-payloads.md).
+To learn more about the format of the JSON messages that a device exchanges with IoT Central, see [Telemetry, property, and command payloads](/previous-versions/azure/iot/concepts-message-payloads).
 
 ### Device SDKs
 

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

@@ -15,7 +15,7 @@ ms.custom: device-developer
 
 A device template in Azure IoT Central is a blueprint that defines the characteristics and behaviors of a type of device that connects to your application. For example, the device template defines the telemetry that a device sends so that IoT Central can create visualizations that use the correct units and data types. Telemetry that matches the device template definition is referred to as *modeled* data. Telemetry that doesn't match the device template definition is referred to as *unmodeled* data.
 
-A solution builder adds device templates to an IoT Central application. A device developer writes the device code that implements the behaviors defined in the device template. To learn more about how to create a device template or have one automatically generated, see [Create a device template in your Azure IoT Central application](howto-set-up-template.md). To learn more about the data that a device exchanges with IoT Central, see [Telemetry, property, and command payloads](../../iot/concepts-message-payloads.md).
+A solution builder adds device templates to an IoT Central application. A device developer writes the device code that implements the behaviors defined in the device template. To learn more about how to create a device template or have one automatically generated, see [Create a device template in your Azure IoT Central application](howto-set-up-template.md). To learn more about the data that a device exchanges with IoT Central, see [Telemetry, property, and command payloads](/previous-versions/azure/iot/concepts-message-payloads).
 
 A device template includes the following sections:
 
@@ -88,7 +88,7 @@ The JSON file that defines the device model uses the [Digital Twin Definition La
 ]
 ```
 
-To learn more about DTDL models, see the [IoT Plug and Play modeling guide](../../iot/concepts-modeling-guide.md).
+To learn more about DTDL models, see the [IoT Plug and Play modeling guide](/previous-versions/azure/iot/concepts-modeling-guide).
 
 > [!NOTE]
 > IoT Central defines some extensions to the DTDL v2 language. To learn more, see [IoT Central extension](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/DTDL.iotcentral.v2.md).
@@ -251,4 +251,4 @@ A solution developer creates views that let operators monitor and manage connect
 
 ## Next step
 
-Now that you've learned about device templates, a suggested next step is to read [Telemetry, property, and command payloads](../../iot/concepts-message-payloads.md) to learn more about the data a device exchanges with IoT Central.
+Now that you've learned about device templates, a suggested next step is to read [Telemetry, property, and command payloads](/previous-versions/azure/iot/concepts-message-payloads) to learn more about the data a device exchanges with IoT Central.

articles/iot-central/core/howto-control-devices-with-rest-api.md

@@ -34,7 +34,7 @@ To learn how to control devices by using the IoT Central UI, see
 
 ## Components and modules
 
-Components let you group and reuse device capabilities. To learn more about components and device models, see the [IoT Plug and Play modeling guide](../../iot/concepts-modeling-guide.md).
+Components let you group and reuse device capabilities. To learn more about components and device models, see the [IoT Plug and Play modeling guide](/previous-versions/azure/iot/concepts-modeling-guide).
 
 Not all device templates use components. The following screenshot shows the device template for a simple [thermostat](https://github.com/Azure/iot-plugandplay-models/blob/main/dtmi/com/example/thermostat-2.json) where all the capabilities are defined in a single interface called the **Root component**:
 

articles/iot-central/core/howto-set-up-template.md

@@ -102,7 +102,7 @@ To create a device model, you can:
 
 1. To view the component ID, select **Edit Identity** on any of the component interfaces in the model.
 
-To learn more, see the [IoT Plug and Play modeling guide](../../iot-pnp/concepts-modeling-guide.md).
+To learn more, see the [IoT Plug and Play modeling guide](/previous-versions/azure/iot/concepts-modeling-guide).
 
 ### Interfaces and components
 
@@ -112,7 +112,7 @@ To view and manage the interfaces in your device model:
 
     :::image type="content" source="media/howto-set-up-template/device-template.png" alt-text="Screenshot that shows root interface for a model":::
 
-1. Select the ellipsis to add an inherited interface or component to the root interface. To learn more about interfaces and component see [multiple components](../../iot/concepts-modeling-guide.md) in the modeling guide.
+1. Select the ellipsis to add an inherited interface or component to the root interface. To learn more about interfaces and component see [multiple components](/previous-versions/azure/iot/concepts-modeling-guide) in the modeling guide.
 
     :::image type="content" source="media/howto-set-up-template/add-interface.png" alt-text="Screenshot that shows how to add interface or component." lightbox="media/howto-set-up-template/add-interface.png":::
 
@@ -195,7 +195,7 @@ The following table shows the configuration settings for a command capability:
 | Response | If enabled, a definition of the command response, including: name, display name, schema, unit, and display unit. |
 |Initial value | The default parameter value. This parameter is an IoT Central extension to DTDL. |
 
-To learn more about how devices implement commands, see [Telemetry, property, and command payloads > Commands and long running commands](../../iot/concepts-message-payloads.md#commands).
+To learn more about how devices implement commands, see [Telemetry, property, and command payloads > Commands and long running commands](/previous-versions/azure/iot/concepts-message-payloads#commands).
 
 #### Offline commands
 

articles/iot-central/core/howto-transform-data.md

@@ -34,7 +34,7 @@ The following table shows three example transformation types:
 
 | Transformation | Description | Example  | Notes |
 |------------------------|-------------|----------|-------|
-| Message Format         | Convert to or manipulate JSON messages. | CSV to JSON  | At ingress. IoT Central only accepts value JSON messages. To learn more, see [Telemetry, property, and command payloads](../../iot/concepts-message-payloads.md). |
+| Message Format         | Convert to or manipulate JSON messages. | CSV to JSON  | At ingress. IoT Central only accepts value JSON messages. To learn more, see [Telemetry, property, and command payloads](/previous-versions/azure/iot/concepts-message-payloads). |
 | Computations           | Math functions that [Azure Functions](../../azure-functions/index.yml) can execute. | Unit conversion from Fahrenheit to Celsius.  | Transform using the egress pattern to take advantage of scalable device ingress through direct connection to IoT Central. Transforming the data lets you use IoT Central features such as visualizations and jobs. |
 | Message Enrichment     | Enrichments from external data sources not found in device properties or telemetry. To learn more about internal enrichments, see  [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md). | Add weather information to messages using [location data](howto-use-location-data.md) from devices. | Transform using the egress pattern to take advantage of scalable device ingress through direct connection to IoT Central. |
 

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

@@ -25,9 +25,9 @@ A device can:
 
 By default, commands expect a device to be connected and fail if the device can't be reached. If you select the **Queue if offline** option in the device template UI a command can be queued until a device comes online. These *offline commands* are described in a separate section later in this article.
 
-To learn about the IoT Pug and Play command conventions, see [IoT Plug and Play conventions](../../iot/concepts-convention.md).
+To learn about the IoT Pug and Play command conventions, see [IoT Plug and Play conventions](/previous-versions/azure/iot/concepts-convention).
 
-To learn more about the command data that a device exchanges with IoT Central, see [Telemetry, property, and command payloads](../../iot/concepts-message-payloads.md).
+To learn more about the command data that a device exchanges with IoT Central, see [Telemetry, property, and command payloads](/previous-versions/azure/iot/concepts-message-payloads).
 
 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).
 
@@ -54,7 +54,7 @@ The following table shows the configuration settings for a command capability:
 | Request     | The payload for the device command.|
 | Response     | The payload of the device command response.|
 
-To learn about the Digital Twin Definition Language (DTDL) that Azure IoT Central uses to define commands in a device template, see [IoT Plug and Play conventions > Commands](../../iot/concepts-convention.md#commands).
+To learn about the Digital Twin Definition Language (DTDL) that Azure IoT Central uses to define commands in a device template, see [IoT Plug and Play conventions > Commands](/previous-versions/azure/iot/concepts-convention#commands).
 
 Optional fields, such as display name and description, let you add more details to the interface and capabilities.
 
@@ -177,4 +177,4 @@ You can call commands on a device that isn't assigned to a device template. To c
 
 ## Next steps
 
-Now that you know how to use commands in your Azure IoT Central application, see [Telemetry, property, and command payloads](../../iot/concepts-message-payloads.md) to learn more about command parameters and [Create and connect a client application to your Azure IoT Central application](tutorial-connect-device.md) to see complete code samples in different languages.
+Now that you know how to use commands in your Azure IoT Central application, see [Telemetry, property, and command payloads](/previous-versions/azure/iot/concepts-message-payloads) to learn more about command parameters and [Create and connect a client application to your Azure IoT Central application](tutorial-connect-device.md) to see complete code samples in different languages.