Updated links to Coiote DM User Guide

Pantofel102 · Pantofel102 · commit dcf94959c182 · 2025-08-20T14:41:22.000+02:00
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Central/Set_an_Observation.md b/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Central/Set_an_Observation.md
@@ -2,7 +2,7 @@
 
 This section describes how to set an Observation in your Azure IoT Central application.
 
-Setting an Observation lets your devices know what value changes and for what particular resources they need to notify you about. An Observation can be set for any or all the components of the [data model](../Concepts/LwM2M_mappings_Central.md ): objects, objects instances, and resources. Whenever there is a change in values, a device will send a Notify message to {{ coiote_short_name }}, which in turn will transfer it to Azure IoT Central.
+Setting an Observation lets your devices know what value changes and for what particular resources they need to notify you about. An Observation can be set for any or all the components of the [data model](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/): objects, objects instances, and resources. Whenever there is a change in values, a device will send a Notify message to {{ coiote_short_name }}, which in turn will transfer it to Azure IoT Central.
 
 In this section, you learn how to:
 
@@ -16,13 +16,13 @@ In this section, you learn how to:
 1. An active Azure IoT Central with hub owner access permissions.
 2. A {{ coiote_short_name }} user account with permissions to use the Azure IoT Central integration.
 3. A device group created in {{ coiote_short_name }}.
-4. [A configured integration between {{ coiote_short_name }} and Azure Iot Central]( Configure_Azure_IoT_Central_integration.md).
-5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](../Configure_integration_templates/Azure_integration_templates.md).
-5. A connected device in {{ coiote_short_name }} that has been [exported to](./Configure_Azure_IoT_Central_integration.md) or [imported from](./Configure_Azure_IoT_Central_integration.md) Azure IoT Central.
+4. [A configured integration between {{ coiote_short_name }} and Azure Iot Central](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-central/integrate-with-azure-iot-central/).
+5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/configure-integration-templates/).
+5. A connected device in {{ coiote_short_name }} that has been [exported to or imported from](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-central/synchronize-devices-with-azure-iot-central/) Azure IoT Central.
 
 ## Assign a device template
 
-To enable correct communication between {{ coiote_short_name }} and Azure IoT Central, you need two templates. The first template configures the {{ coiote_short_name }} integration with Azure. ([Follow the instruction](../Configure_integration_templates/Azure_integration_templates.md) to learn how to configure it.) The second template builds on the first one and allows to provide information that is used only in Azure IoT Central. For example: a given resource is temperature and is measured in Celsius.
+To enable correct communication between {{ coiote_short_name }} and Azure IoT Central, you need two templates. The first template configures the {{ coiote_short_name }} integration with Azure. ([Follow the instruction](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/configure-integration-templates/) in the Coiote DM User Documentation to learn how to configure it.) The second template builds on the first one and allows to provide information that is used only in Azure IoT Central. For example: a given resource is temperature and is measured in Celsius.
 
 ### Download LwM2M template in {{ coiote_short_name }}
 
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Perform_Execute.md b/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Perform_Execute.md
@@ -13,16 +13,16 @@ In this section, you learn how to:
 1. An active Azure IoT Hub with hub owner access permissions.
 2. A {{ coiote_short_name }} user account with permissions to use the integration extension.
 3. A device group created in {{ coiote_short_name }}.
-4. [A configured extension between {{ coiote_short_name }} and Azure Iot Hub](../Azure_IoT_Hub/Configure_Azure_IoT_Hub_integration.md).
-5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](../Configure_integration_templates/Azure_integration_templates.md).
-5. [A connected device](../../../Coiote_IoT_DM/Onboarding/connect.md).
+4. [A configured extension between {{ coiote_short_name }} and Azure Iot Hub](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-hub/integrate-with-azure-iot-hub/).
+5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/configure-integration-templates/).
+5. [A connected device](https://{{coiote_server}}/doc/user/getting-started/onboard-your-first-device/).
 
 ## Perform EXECUTE
 
 Let’s perform an EXECUTE operation on the **Factory Reset** resource with ID **3/0/5**.
 
 !!! note
-    From the Azure IoT integration standpoint, **Factory Reset** is interpreted as a *Command*. Read more about how LwM2M data model is mapped to Azure IoT Hub mechanisms in [Concepts](../Concepts/LwM2M_mappings_Hub.md).
+    From the Azure IoT integration standpoint, **Factory Reset** is interpreted as a *Command*. Read more about how LwM2M data model is mapped to Azure IoT Hub mechanisms in [LwM2M mappings - Azure IoT Hub](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/) in the Coiote DM User Documentation.
 
 1. In your Azure IoT Hub account, go to **Devices** from the left pane.
 
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Perform_Read_Write.md b/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Perform_Read_Write.md
@@ -2,7 +2,7 @@
 
 This section describes how to perform a LwM2M WRITE and READ operations in your Azure IoT Hub and {{ coiote_short_name }}.
 
-A WRITE operation lets you change the current value on the given [data model](../Concepts/LwM2M_mappings_Hub.md) component: object, object instance, and resource. The READ enables you to see the updated value of an object, object instance, or resource.
+A WRITE operation lets you change the current value on the given data model component: object, object instance, and resource. The READ enables you to see the updated value of an object, object instance, or resource.
 
 In this section, you learn how to:
 
@@ -15,15 +15,15 @@ In this section, you learn how to:
 1. An active Azure IoT Hub with hub owner access permissions.
 2. A {{ coiote_short_name }} user account with permissions to use the integration extension.
 3. A device group created in {{ coiote_short_name }}.
-4. [A configured extension between {{ coiote_short_name }} and Azure Iot Hub](../Azure_IoT_Hub/Configure_Azure_IoT_Hub_integration.md).
-5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](../Configure_integration_templates/Azure_integration_templates.md).
-5. [A connected device](../../../Coiote_IoT_DM/Onboarding/connect.md).
+4. [A configured extension between {{ coiote_short_name }} and Azure Iot Hub](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-hub/integrate-with-azure-iot-hub/).
+5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/configure-integration-templates/).
+5. [A connected device](https://{{coiote_server}}/doc/user/getting-started/onboard-your-first-device/).
 
 ## Perform WRITE
 
 Let’s perform a WRITE operation on the **Lifetime** resource with ID **1/1/1**. From the Azure IoT integration standpoint, **Lifetime** it is interpreted as a *Property*.
 
-In Azure IoT Hub, value changes for both *Telemetry* and *Property* are stored in the [Device twin](https://https://iotdevzone.avsystem.com/docs/Azure_IoT_Integration_Guide/Concepts/LwM2M_mappings_Hub/#lwm2m-readable-and-writable-resources). To perform a WRITE operation, do the following:
+In Azure IoT Hub, value changes for both *Telemetry* and *Property* are stored in the [Device twin](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/#lwm2m-readable-and-writable-resources). To perform a WRITE operation, do the following:
 
 1. In your Azure IoT Hub account, go to **Devices** from the left pane.
 
@@ -88,9 +88,9 @@ You have successfully performed a LwM2M WRITE on a resource.
 
 ## Perform READ
 
-Let’s perform a READ operation on the **Temperature** object's **Sensor Value** resource with ID **3303/0/5700** defined as a *Property* in the [integration template in {{ coiote_short_name }}](../Configure_integration_templates/Azure_integration_templates.md).
+Let’s perform a READ operation on the **Temperature** object's **Sensor Value** resource with ID **3303/0/5700** defined as a *Property* in the [integration template in {{ coiote_short_name }}](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/configure-integration-templates/).
 
-To learn more about reading value changes for both *Telemetry* and *Property*, refer to [LwM2M mappings for Azure IoT Hub](../Concepts/LwM2M_mappings_Hub.md). To perform a READ operation, do the following:
+To learn more about reading value changes for both *Telemetry* and *Property*, refer to [LwM2M mappings for Azure IoT Hub](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/). To perform a READ operation, do the following:
 
 1. In {{ coiote_short_name }}, go to your device and select the **Data model** tab.
 2. Expand the **Temperature** object, and find the **Sensor Value (3303/0/5700)** resource in the list.
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Set_an_Observation.md b/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Set_an_Observation.md
@@ -2,7 +2,7 @@
 
 This section describes how to set an Observation in your Azure IoT Hub.
 
-Setting an Observation lets your devices know what value changes and for what particular resources they need to notify you about. An Observation can be set for any or all the components of the [data model](../Concepts/LwM2M_mappings_Hub.md): objects, objects instances, and resources. Whenever there is a change in values, a device will send a Notify message to {{ coiote_short_name }}, which in turn will transfer it to Azure IoT Hub.
+Setting an Observation lets your devices know what value changes and for what particular resources they need to notify you about. An Observation can be set for any or all the components of the [data model](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/): objects, objects instances, and resources. Whenever there is a change in values, a device will send a Notify message to {{ coiote_short_name }}, which in turn will transfer it to Azure IoT Hub.
 
 In this section, you learn how to:
 
@@ -15,15 +15,15 @@ In this section, you learn how to:
 1. An active Azure IoT Hub with hub owner access permissions.
 2. A {{ coiote_short_name }} user account with permissions to use the integration extension.
 3. A device group created in {{ coiote_short_name }}.
-4. [A configured extension between {{ coiote_short_name }} and Azure Iot Hub](../Azure_IoT_Hub/Configure_Azure_IoT_Hub_integration.md).
-5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](../Configure_integration_templates/Azure_integration_templates.md).
-5. [A connected device](../../../Coiote_IoT_DM/Onboarding/connect.md).
+4. [A configured extension between {{ coiote_short_name }} and Azure Iot Hub](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-hub/integrate-with-azure-iot-hub/).
+5. [A configured integration template in {{ coiote_short_name }}, assigned to the device group](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/configure-integration-templates/).
+5. [A connected device](https://{{coiote_server}}/doc/user/getting-started/onboard-your-first-device/).
 
 ## Set an Observation and define its attributes
 
 Let’s set two Observations: one on the whole object with ID **1/1 (1 LwM2M Server, 1 Lifetime)** and on the resource with ID **3/0/13** (3 Device, 13 Current time). Both of them are Properties.
 
-In Azure IoT Hub, value changes for both Telemetry and Property are stored in [Device twin](../Concepts/LwM2M_mappings_Hub.md), because Observation is a Property in itself and it does not keep track of historical changes in values. To set an Observation, do the following:
+In Azure IoT Hub, value changes for both Telemetry and Property are stored in [Device twin](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/#lwm2m-readable-and-writable-resources), because Observation is a Property in itself and it does not keep track of historical changes in values. To set an Observation, do the following:
 
 1. In your Azure IoT Hub account, go to **Devices** from the left pane.
 
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Upgrading_firmware.md b/docs/Coiote_IoT_DM/Cloud_integrations/Azure_IoT_Hub/Upgrading_firmware.md
@@ -4,7 +4,7 @@ If you would like to upgrade the firmware of devices using the Azure IoT Hub, fo
 
 ## Prerequisites
 
- - At least one [synchronized](../Synchronize_devices_with_Azure_IoT_Hub) {{ coiote_short_name }} - Azure IoT Hub device.
+ - At least one [synchronized](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-hub/synchronize-devices-with-azure-iot-hub/) {{ coiote_short_name }} - Azure IoT Hub device.
  - A firmware file hosted on an HTTP server that is reachable by the {{ coiote_short_name }} server.
 
 !!! note
@@ -148,4 +148,4 @@ To cancel the firmware upgrade procedure, follow these steps:
 
 ## See also
 
-See the relevant section of [LwM2M mappings](https://iotdevzone.avsystem.com/docs/Cloud_integrations/Azure_IoT/Concepts/LwM2M_mappings_Hub/) to learn the details of how Azure IoT Hub Direct Methods are mapped in {{ coiote_short_name }}.
+See [LwM2M mappings - Azure IoT Hub](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/) in the Coiote DM User Documentation to learn the details of how Azure IoT Hub Direct Methods are mapped in {{ coiote_short_name }}.
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Device_Integration_Center/datacake.md b/docs/Coiote_IoT_DM/Cloud_integrations/Device_Integration_Center/datacake.md
@@ -93,7 +93,7 @@ This decoder does several things required to ingest device data into the Datacak
 
 ## Monitor events in Datacake
 
-After activating the event handler, go to your Datacake account and open the Dashboard of your device. If you have already [set an observation on the Temperature object](../../../Coiote_IoT_DM/Device_Center.md), you should see that the **Last update** field of your device in Datacake changed to the time when Datacake received last information from {{ coiote_short_name }}.
+After activating the event handler, go to your Datacake account and open the Dashboard of your device. If you have already set an observation on the Temperature object, you should see that the **Last update** field of your device in Datacake changed to the time when Datacake received last information from {{ coiote_short_name }}.
 
 ![Last update time of the device in Datacake](../images/datacake-last-update.webp "Last update time of the device in Datacake")
 
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Device_Integration_Center/graphql.md b/docs/Coiote_IoT_DM/Cloud_integrations/Device_Integration_Center/graphql.md
@@ -31,7 +31,7 @@ This tutorial explains how to use **Data Integration Center** to send e.g. a mut
 
 !!! Info
 
-    For detailed instructions on how to create webhooks, see the [Webhook](../webhooks.md) and [Overview](../overview.md) chapters.
+    For detailed instructions on how to create webhooks, see [Create a webhook event handler](https://{{coiote_server}}/doc/user/integrations/how-to-guides/data-integration-center/create-webhook-event-handler/) in the Coiote DM User Documentation.
 
 ![graphql-configuration](../images/graphql-configuration.webp)
 
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/Device_Integration_Center/slack.md b/docs/Coiote_IoT_DM/Cloud_integrations/Device_Integration_Center/slack.md
@@ -32,7 +32,7 @@ To send messages to Slack:
 
 !!! Info
 
-    For detailed instructions on how to create webhooks, see the [Webhook](../webhooks.md) and [Overview](../overview.md) chapters.
+    For detailed instructions on how to create webhooks, see [Create a webhook event handler](https://{{coiote_server}}/doc/user/integrations/how-to-guides/data-integration-center/create-webhook-event-handler/) in the Coiote DM User Documentation.
 
 ![Slack Configuration](../images/slack-configuration.webp)
 
diff --git a/docs/Coiote_IoT_DM/Cloud_integrations/cloud-integrations.md b/docs/Coiote_IoT_DM/Cloud_integrations/cloud-integrations.md
@@ -0,0 +1,22 @@
+# IoT Cloud Integrations
+
+With the {{ coiote_long_name }}, you can integrate your LwM2M devices with Microsoft Azure, AWS and nRF Cloud.
+
+These guides will take you on a step-by-step journey to seamlessly activate the integrations.
+
+## Microsoft Azure integrations
+
+See guides in Coiote DM User Documentation to learn how you can get started with the {{ coiote_short_name }} – Azure IoT integration:
+
+[Azure IoT Hub](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-hub/integrate-with-azure-iot-hub/){: .md-button .md-button--big :style="float: left;margin-right: 30px;"} [Azure IoT Central](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-central/integrate-with-azure-iot-central/){: .md-button .md-button--big :style="float: left;margin-right: 30px;"} [Azure DPS](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/integrate-with-azure-dps/){: .md-button .md-button--big }
+
+## AWS integration
+
+Integrate {{ coiote_short_name }} with the Amazon Web Services and gain new opportunities to leverage your IoT data.
+
+[Integrate with AWS](https://{{coiote_server}}/doc/user/integrations/how-to-guides/configure-aws-iot-core-integration/){: .md-button .md-button--big }
+
+## nRF Cloud Location services
+Integrate {{ coiote_short_name }} with the nRF Cloud Location Services to track your devices' location and save battery life.
+
+[Integrate with nRF Cloud](https://{{coiote_server}}/doc/user/integrations/how-to-guides/configure-nrf-cloud-integration/){: .md-button .md-button--big }
diff --git a/docs/Demo_Projects/Air_quality_monitoring_tutorial.md b/docs/Demo_Projects/Air_quality_monitoring_tutorial.md
@@ -56,7 +56,7 @@ While your new IoT hub is deploying, you can add a new storage account:
 ## Configuring the Azure IoT Hub integration extension
 
 Once the deployments are complete, go to {{ coiote_short_name }} to set up the Azure IoT Hub extension.
-If you haven't done this yet, please follow the [instruction for the Azure IoT Hub integration configuration](../Cloud_integrations/Azure_IoT/Azure_IoT_Hub/Configure_Azure_IoT_Hub_integration.md).
+If you haven't done this yet, please follow the [instruction for the Azure IoT Hub integration configuration](https://{{coiote_server}}/doc/user/integrations/how-to-guides/hyperscaler-integrations/azure-iot-hub/integrate-with-azure-iot-hub/) in the Coiote DM User Documentation.
 
 ## Adding and connecting LwM2M air quality meter simulators to {{ coiote_short_name }} and Azure IoT Hub
 1. Go to your Azure IoT Hub and add new devices:
@@ -76,7 +76,7 @@ If you haven't done this yet, please follow the [instruction for the Azure IoT H
 3. Go to your command line and register the device simulators:
     - Paste and run the following command to create a container group:
         ```
-         az container create -g coiote-dm-experiments --name air-quality-meter-example-0 --image avsystemcom/air-quality-meter-example --environment-variables DEVICEID=air-quality-meter-example-0 SERVER_ADDRESS={{ coiote_server }} OPEN_WEATHER_API_TOKEN=exampletoken
+         az container create -g coiote-dm-experiments --name air-quality-meter-example-0 --image avsystemcom/air-quality-meter-example --environment-variables DEVICEID=air-quality-meter-example-0 SERVER_ADDRESS={{coiote_server}} OPEN_WEATHER_API_TOKEN=exampletoken
 
         ```
 
@@ -108,7 +108,7 @@ If you haven't done this yet, please follow the [instruction for the Azure IoT H
 ### From Azure IoT Hub to {{ coiote_short_name }}
 
 !!! note
-    To read more about how the Device Twins work in the {{ coiote_short_name }} - Azure IoT Hub integration, please refer to [the LwM2M Mappings section](../Cloud_integrations/Azure_IoT/Concepts/LwM2M_mappings_Hub.md).
+    To read more about how the Device Twins work in the {{ coiote_short_name }} - Azure IoT Hub integration, please refer to [the LwM2M Mappings document](https://{{coiote_server}}/doc/user/integrations/topic-guides/lwm2m-mappings-azure-iot-hub/) in the Coiote DM User Documentation.
 
 1. In your Azure IoT hub, select **IoT devices**, click one of your added devices and select the **Device Twin** panel.
 2. To change the ``Lifetime`` resource in {{ coiote_short_name }}, you need to modify the relevant Device Twin desired property.
diff --git a/docs/Demo_Projects/Edge_Impulse_demo.md b/docs/Demo_Projects/Edge_Impulse_demo.md
diff --git a/docs/Demo_Projects/Tracking_tutorial.md b/docs/Demo_Projects/Tracking_tutorial.md
diff --git a/docs/academy/index.md b/docs/academy/index.md
diff --git a/docs/cloud-integrations.md b/docs/cloud-integrations.md
diff --git a/mkdocs.yml b/mkdocs.yml
