Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into portalParam

Author: roygara

.openpublishing.redirection.iot-develop.json

@@ -440,6 +440,26 @@
       "redirect_url": "/azure/iot-develop/about-iot-develop",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/iot-develop/quickstart-devkit-mxchip-az3166-iot-hub.md",
+      "redirect_url": "/azure/iot/tutorial-devkit-mxchip-az3166-iot-hub",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/quickstart-devkit-stm-b-l475e-iot-hub.md",
+      "redirect_url": "/azure/iot/tutorial-devkit-stm-b-l475e-iot-hub",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/concepts-azure-rtos-security-practices.md",
+      "redirect_url": "/azure/iot/concepts-eclipse-threadx-security-practices",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/troubleshoot-embedded-device-quickstarts.md",
+      "redirect_url": "/azure/iot/troubleshoot-embedded-device-tutorials",
+      "redirect_document_id": false
+    }, 
     {
       "source_path_from_root": "/articles/iot-develop/how-to-use-reliability-features-in-sdks.md",
       "redirect_url": "/azure/iot-develop/concepts-manage-device-reconnections",

articles/communication-services/how-tos/router-sdk/manage-queue.md

@@ -156,7 +156,7 @@ administration_client.upsert_queue(queue.id, queue)
 ```java
 queue.setName("XBOX Updated Queue");
 queue.setLabels(Map.of("Additional-Queue-Label", new RouterValue("ChatQueue")));
-administrationClient.updateQueue(queue.getId(), BinaryData.fromObject(queue));
+administrationClient.updateQueue(queue.getId(), BinaryData.fromObject(queue), null);
 ```
 
 ::: zone-end

articles/dev-box/concept-dev-box-concepts.md

@@ -15,9 +15,9 @@ ms.custom: template-concept
 
 This article describes the key concepts and components of Microsoft Dev Box to help you set up the service successfully.
 
-Microsoft Dev Box gives developers self-service access to preconfigured and ready-to-code cloud-based workstations. You can configure the service to meet your development team and project structure, and manage security and network settings to access resources securely. Different components play a part in the configuration of Microsoft Dev Box.
+Microsoft Dev Box gives developers self-service access to preconfigured and ready-to-code cloud-based workstations. You can configure the service to meet your development team and project structure, manage security, and network settings to access resources securely. Different components play a part in the configuration of Microsoft Dev Box.
 
-Microsoft Dev Box builds on the same foundations as [Azure Deployment Environments](/azure/deployment-environments/overview-what-is-azure-deployment-environments). Deployment Environments provides developers with preconfigured cloud-based environments for developing applications. Both services are complementary and share certain architectural components, such as a [dev center](#dev-center) or [project](#project).
+Microsoft Dev Box builds on the same foundations as [Azure Deployment Environments](/azure/deployment-environments/overview-what-is-azure-deployment-environments). Deployment Environments provides developers with preconfigured cloud-based environments for developing applications. The services are complementary and share certain architectural components, such as a [dev center](#dev-center) or [project](#project).
 
 This diagram shows the key components of Dev Box and how they relate to each other. You can learn more about each component in the following sections.
 
@@ -36,7 +36,7 @@ A dev center is a collection of [Projects](#project) that require similar settin
 
 ## Catalogs
 
-The Dev Box quick start catalog contains tasks and scripts that you can use to configure your dev box during the final stage of the creation process.Microsoft provides a [*quick start* catalog](https://github.com/microsoft/devcenter-catalog) that contains a set of sample tasks. You can attach the quick start catalog to a dev center to make these tasks available to all the projects associated with the dev center. You can modify the sample tasks to suit your needs, and you can create your own catalog of tasks. 
+The Dev Box quick start catalog contains tasks and scripts that you can use to configure your dev box during the final stage of the creation process. Microsoft provides a *[quick start](https://github.com/microsoft/devcenter-catalog)*[ catalog](https://github.com/microsoft/devcenter-catalog) that contains a set of sample tasks. You can attach the quick start catalog to a dev center to make these tasks available to all the projects associated with the dev center. You can modify the sample tasks to suit your needs, and you can create your own catalog of tasks. 
 
 To learn how to create reusable customization tasks, see [Create reusable dev box customizations](./how-to-customize-dev-box-setup-tasks.md).
 

articles/iot-develop/TOC.yml

@@ -18,19 +18,11 @@
     - name: Renesas RX65N Cloud Kit
       href: quickstart-devkit-renesas-rx65n-cloud-kit-iot-hub.md
     - name: STMicroelectronics L475E-IOT01A
-      href: quickstart-devkit-stm-b-l475e-iot-hub.md
-    - name: STMicroelectronics L4S5I-IOT01A
       href: quickstart-devkit-stm-b-l4s5i-iot-hub.md
     - name: STMicroelectronics U585I-IOT02A
       href: quickstart-devkit-stm-b-u585i-iot-hub.md
     - name: NXP MIMXRT1060-EVK
       href: quickstart-devkit-nxp-mimxrt1060-evk-iot-hub.md
-    - name: MXCHIP AZ3166
-      href: quickstart-devkit-mxchip-az3166-iot-hub.md
-- name: Concepts
-  items:
-  - name: Guidelines for secured embedded development
-    href: concepts-azure-rtos-security-practices.md 
 - name: How to
   items:
   - name: Install and use IoT explorer
@@ -59,10 +51,6 @@
         href: quickstart-devkit-espressif-esp32-freertos.md
       - name: STMicroelectronics L475E
         href: quickstart-devkit-stm-b-l475e-freertos.md
-  - name: Troubleshoot
-    items:
-      - name: Troubleshoot embedded quickstarts
-        href: troubleshoot-embedded-device-quickstarts.md
 - name: Reference
   items:
     - name: Azure CLI

articles/iot-develop/about-getting-started-device-development.md

@@ -36,9 +36,9 @@ Each quickstart shows how to set up a code sample and tools, flash the device, a
 |-|-|-|
 |[Quickstart: Connect a Microchip ATSAME54-XPro Evaluation kit to IoT Hub](quickstart-devkit-microchip-atsame54-xpro-iot-hub.md)|Microchip ATSAME54-XPro|Azure RTOS middleware|
 |[Quickstart: Connect an ESPRESSIF ESP32-Azure IoT Kit to IoT Hub](../iot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md)|ESPRESSIF ESP32|FreeRTOS middleware|
-|[Quickstart: Connect an STMicroelectronics B-L475E-IOT01A Discovery kit to IoT Hub](quickstart-devkit-stm-b-l475e-iot-hub.md)|STMicroelectronics L475E-IOT01A|Azure RTOS middleware|
+|[Quickstart: Connect an STMicroelectronics B-U585I-IOT02A kit to IoT Hub](quickstart-devkit-stm-b-u585i-iot-hub.md)|STMicroelectronics L475E-IOT01A|Azure RTOS middleware|
 |[Quickstart: Connect an NXP MIMXRT1060-EVK Evaluation kit to IoT Hub](quickstart-devkit-nxp-mimxrt1060-evk-iot-hub.md)|NXP MIMXRT1060-EVK|Azure RTOS middleware|
-|[Connect an MXCHIP AZ3166 devkit to IoT Hub](quickstart-devkit-mxchip-az3166-iot-hub.md)|MXCHIP AZ3166|Azure RTOS middleware|
+
 
 ## Next steps
 To learn more about working with the IoT device SDKs and developing for general devices, see the following tutorial.

articles/iot-develop/index.yml

@@ -27,8 +27,8 @@ landingContent:
     linkLists:
     - linkListType: quickstart
       links:
-        - text: Connect an STMicroelectronics B-L475E-IOT01A to IoT Hub
-          url: quickstart-devkit-stm-b-l475e-iot-hub.md
+        - text: Connect an STMicroelectronics B-U585I-IOT02A to IoT Hub
+          url: quickstart-devkit-stm-b-u585i-iot-hub.md
         - text: Connect a Microchip ATSAME54-XPro to IoT Hub
           url: quickstart-devkit-microchip-atsame54-xpro-iot-hub.md
         - text: Connect a Renesas RX65N Cloud Kit to IoT Hub

articles/iot-develop/quickstart-devkit-microchip-atsame54-xpro-iot-hub.md

@@ -178,7 +178,7 @@ You can use the **Termite** app to monitor communication and confirm that your d
 1. Start **Termite**.
 
     > [!TIP]
-    > If you have issues getting your device to initialize or connect after flashing, see [Troubleshooting](troubleshoot-embedded-device-quickstarts.md).
+    > If you have issues getting your device to initialize or connect after flashing, see [Troubleshooting](../iot/troubleshoot-embedded-device-tutorials.md).
 
 1. Select **Settings**.
 
@@ -362,7 +362,7 @@ To use Azure CLI to call a method:
 
 ## Troubleshoot and debug
 
-If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](troubleshoot-embedded-device-quickstarts.md).
+If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](../iot/troubleshoot-embedded-device-tutorials.md).
 
 For debugging the application, see [Debugging with Visual Studio Code](https://github.com/azure-rtos/getting-started/blob/master/docs/debugging.md).
 

articles/iot-develop/quickstart-devkit-microchip-atsame54-xpro.md

@@ -185,7 +185,7 @@ You can use the **Termite** app to monitor communication and confirm that your d
 1. Start **Termite**.
 
     > [!TIP]
-    > If you have issues getting your device to initialize or connect after flashing, seeTroubleshooting](troubleshoot-embedded-device-quickstarts.md) for additional steps.
+    > If you have issues getting your device to initialize or connect after flashing, seeTroubleshooting](../iot/troubleshoot-embedded-device-tutorials.md) for additional steps.
 
 1. Select **Settings**.
 
@@ -591,7 +591,7 @@ Select **About** tab from the device page.
 
 ## Troubleshoot and debug
 
-If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](troubleshoot-embedded-device-quickstarts.md).
+If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](../iot/troubleshoot-embedded-device-tutorials.md).
 
 :::zone pivot="iot-toolset-cmake"
 For debugging the application, see [Debugging with Visual Studio Code](https://github.com/azure-rtos/getting-started/blob/master/docs/debugging.md).

articles/iot-develop/quickstart-devkit-mxchip-az3166.md

@@ -134,7 +134,7 @@ You can use the **Termite** app to monitor communication and confirm that your d
 
 1. Start **Termite**.
     > [!TIP]
-    > If you are unable to connect Termite to your devkit, install the [ST-LINK driver](https://www.st.com/en/development-tools/stsw-link009.html) and try again. See  [Troubleshooting](troubleshoot-embedded-device-quickstarts.md) for additional steps.
+    > If you are unable to connect Termite to your devkit, install the [ST-LINK driver](https://www.st.com/en/development-tools/stsw-link009.html) and try again. See  [Troubleshooting](../iot/troubleshoot-embedded-device-tutorials.md) for additional steps.
 1. Select **Settings**.
 1. In the **Serial port settings** dialog, check the following settings and update if needed:
     * **Baud rate**: 115,200
@@ -236,7 +236,7 @@ Select **About** tab from the device page.
 
 ## Troubleshoot and debug
 
-If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](troubleshoot-embedded-device-quickstarts.md).
+If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](../iot/troubleshoot-embedded-device-tutorials.md).
 
 For debugging the application, see [Debugging with Visual Studio Code](https://github.com/azure-rtos/getting-started/blob/master/docs/debugging.md).
 
@@ -252,10 +252,8 @@ To remove the entire Azure IoT Central sample application and all its devices an
 
 In this quickstart, you built a custom image that contains Azure RTOS sample code, and then flashed the image to the MXCHIP DevKit device. You also used the IoT Central portal to create Azure resources, connect the MXCHIP DevKit securely to Azure, view telemetry, and send messages.
 
-As a next step, explore the following articles to learn more about using the IoT device SDKs to connect devices to Azure IoT. 
+As a next step, explore the following article to learn more about using the IoT device SDKs to connect devices to Azure IoT. 
 
-> [!div class="nextstepaction"]
-> [Connect an MXCHIP AZ3166 devkit to IoT Hub](quickstart-devkit-mxchip-az3166-iot-hub.md)
 > [!div class="nextstepaction"]
 > [Connect a simulated device to IoT Hub](../iot/tutorial-send-telemetry-iot-hub.md)
 

articles/iot-develop/quickstart-devkit-nxp-mimxrt1060-evk-iot-hub.md

@@ -133,7 +133,7 @@ You can use the **Termite** app to monitor communication and confirm that your d
 
 1. Start **Termite**.
     > [!TIP]
-    > If you have issues getting your device to initialize or connect after flashing, see [Troubleshooting](troubleshoot-embedded-device-quickstarts.md).
+    > If you have issues getting your device to initialize or connect after flashing, see [Troubleshooting](../iot/troubleshoot-embedded-device-tutorials.md).
 1. Select **Settings**.
 1. In the **Serial port settings** dialog, check the following settings and update if needed:
     * **Baud rate**: 115,200
@@ -318,7 +318,7 @@ To use Azure CLI to call a method:
 
 ## Troubleshoot and debug
 
-If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](troubleshoot-embedded-device-quickstarts.md).
+If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](../iot/troubleshoot-embedded-device-tutorials.md).
 
 For debugging the application, see [Debugging with Visual Studio Code](https://github.com/azure-rtos/getting-started/blob/master/docs/debugging.md).