diff --git a/MXChip/AZ3166/app/azure_config.h b/MXChip/AZ3166/app/azure_config.h index 6818c27d..03a569d2 100644 --- a/MXChip/AZ3166/app/azure_config.h +++ b/MXChip/AZ3166/app/azure_config.h @@ -20,38 +20,38 @@ typedef enum #define WIFI_MODE WPA2_PSK_AES // ---------------------------------------------------------------------------- -// Azure IoT Hub Connection Transport -// Define to use the legacy MQTT connection, else Azure RTOS SDK for Azure IoT +// Azure IoT Dynamic Provisioning Service +// Define this to use the DPS service, otherwise direct IoT Hub // ---------------------------------------------------------------------------- -//#define ENABLE_LEGACY_MQTT +#define ENABLE_DPS // ---------------------------------------------------------------------------- -// Azure IoT Dynamic Provisioning Service -// Define this to use the DPS service, otherwise direct IoT Hub +// Azure IoT DPS connection config +// IOT_DPS_ID_SCOPE: The DPS ID Scope +// IOT_DPS_REGISTRATION_ID: The DPS device Registration Id +// ---------------------------------------------------------------------------- +#define IOT_DPS_ID_SCOPE "" +#define IOT_DPS_REGISTRATION_ID "" + +// ---------------------------------------------------------------------------- +// Azure IoT Hub Connection Transport +// Define to use the legacy MQTT connection, else Azure RTOS SDK for Azure IoT // ---------------------------------------------------------------------------- -//#define ENABLE_DPS +//#define ENABLE_LEGACY_MQTT // ---------------------------------------------------------------------------- // Azure IoT DPS Self-Signed X509Certificate // Define this to connect to DPS or Iot Hub using a X509 certificate // ---------------------------------------------------------------------------- -// #define ENABLE_X509 +//#define ENABLE_X509 // ---------------------------------------------------------------------------- // Azure IoT Hub connection config // IOT_HUB_HOSTNAME: The Azure IoT Hub hostname // IOT_HUB_DEVICE_ID: The Azure IoT Hub device id // ---------------------------------------------------------------------------- -#define IOT_HUB_HOSTNAME "" -#define IOT_HUB_DEVICE_ID "" - -// ---------------------------------------------------------------------------- -// Azure IoT DPS connection config -// IOT_DPS_ID_SCOPE: The DPS ID Scope -// IOT_DPS_REGISTRATION_ID: The DPS device Registration Id -// ---------------------------------------------------------------------------- -#define IOT_DPS_ID_SCOPE "" -#define IOT_DPS_REGISTRATION_ID "" +//#define IOT_HUB_HOSTNAME "" +//#define IOT_HUB_DEVICE_ID "" // ---------------------------------------------------------------------------- // Azure IoT device SAS key diff --git a/MXChip/AZ3166/media/azure-iot-central-device-about.png b/MXChip/AZ3166/media/azure-iot-central-device-about.png new file mode 100644 index 00000000..bc90dffa Binary files /dev/null and b/MXChip/AZ3166/media/azure-iot-central-device-about.png differ diff --git a/MXChip/AZ3166/media/azure-iot-central-device-telemetry.png b/MXChip/AZ3166/media/azure-iot-central-device-telemetry.png new file mode 100644 index 00000000..7d204ef9 Binary files /dev/null and b/MXChip/AZ3166/media/azure-iot-central-device-telemetry.png differ diff --git a/MXChip/AZ3166/media/azure-iot-central-device-template-migrate.png b/MXChip/AZ3166/media/azure-iot-central-device-template-migrate.png new file mode 100644 index 00000000..55cdab72 Binary files /dev/null and b/MXChip/AZ3166/media/azure-iot-central-device-template-migrate.png differ diff --git a/MXChip/AZ3166/media/azure-iot-central-device-view-status.png b/MXChip/AZ3166/media/azure-iot-central-device-view-status.png new file mode 100644 index 00000000..4025afab Binary files /dev/null and b/MXChip/AZ3166/media/azure-iot-central-device-view-status.png differ diff --git a/MXChip/AZ3166/media/azure-iot-central-invoke-method.png b/MXChip/AZ3166/media/azure-iot-central-invoke-method.png new file mode 100644 index 00000000..edb99fe2 Binary files /dev/null and b/MXChip/AZ3166/media/azure-iot-central-invoke-method.png differ diff --git a/MXChip/AZ3166/media/azure-iot-explorer-create-connection.png b/MXChip/AZ3166/media/azure-iot-explorer-create-connection.png deleted file mode 100644 index fe7b8fd7..00000000 Binary files a/MXChip/AZ3166/media/azure-iot-explorer-create-connection.png and /dev/null differ diff --git a/MXChip/AZ3166/media/azure-iot-explorer-device-identity.png b/MXChip/AZ3166/media/azure-iot-explorer-device-identity.png deleted file mode 100644 index b60f600e..00000000 Binary files a/MXChip/AZ3166/media/azure-iot-explorer-device-identity.png and /dev/null differ diff --git a/MXChip/AZ3166/media/azure-iot-explorer-device-telemetry.png b/MXChip/AZ3166/media/azure-iot-explorer-device-telemetry.png deleted file mode 100644 index 93ed7f08..00000000 Binary files a/MXChip/AZ3166/media/azure-iot-explorer-device-telemetry.png and /dev/null differ diff --git a/MXChip/AZ3166/media/azure-iot-explorer-invoke-method.png b/MXChip/AZ3166/media/azure-iot-explorer-invoke-method.png deleted file mode 100644 index abca4039..00000000 Binary files a/MXChip/AZ3166/media/azure-iot-explorer-invoke-method.png and /dev/null differ diff --git a/MXChip/AZ3166/media/com_port.png b/MXChip/AZ3166/media/com_port.png deleted file mode 100644 index cea7c408..00000000 Binary files a/MXChip/AZ3166/media/com_port.png and /dev/null differ diff --git a/MXChip/AZ3166/media/iotcentralcreate-custom.png b/MXChip/AZ3166/media/iotcentralcreate-custom.png new file mode 100644 index 00000000..9617ab8b Binary files /dev/null and b/MXChip/AZ3166/media/iotcentralcreate-custom.png differ diff --git a/MXChip/AZ3166/media/iotcentralcreate-device.png b/MXChip/AZ3166/media/iotcentralcreate-device.png new file mode 100644 index 00000000..a05d2764 Binary files /dev/null and b/MXChip/AZ3166/media/iotcentralcreate-device.png differ diff --git a/MXChip/AZ3166/media/iotcentraldevice-connection-info.png b/MXChip/AZ3166/media/iotcentraldevice-connection-info.png new file mode 100644 index 00000000..80e88b2c Binary files /dev/null and b/MXChip/AZ3166/media/iotcentraldevice-connection-info.png differ diff --git a/MXChip/AZ3166/readme.md b/MXChip/AZ3166/readme.md index 544abd02..045f3d40 100644 --- a/MXChip/AZ3166/readme.md +++ b/MXChip/AZ3166/readme.md @@ -21,13 +21,11 @@ You will complete the following tasks: * Install a set of embedded development tools for programming the MXChip DevKit in C * Build an image and flash it onto the MXCHIP DevKit -* Use Azure CLI to create and manage an Azure IoT hub that the MXCHIP DevKit will securely connect to -* Use Azure IoT Explorer to view properties, view device telemetry, and call direct commands +* Use Azure IoT Central to create cloud components, view properties, view device telemetry, and call direct commands ## Prerequisites * A PC running Microsoft Windows 10 -* If you don't have an Azure subscription, [create one for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin. * [Git](https://git-scm.com/downloads) for cloning the repository * Hardware @@ -54,11 +52,9 @@ git clone --recursive https://github.com/azure-rtos/getting-started.git The cloned repo contains a setup script that installs and configures the required tools. If you installed these tools in another tutorial in the getting started guide, you don't need to do it again. > Note: The setup script installs the following tools: -> * [GCC](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm): Compile > * [CMake](https://cmake.org): Build +> * [ARM GCC](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm): Compile > * [Termite](https://www.compuphase.com/software_termite.htm): Monitor serial port output for connected devices -> * [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/): Manage Azure resources -> * [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases): Cross-platform utility to monitor and manage Azure IoT resources To install the tools: @@ -66,8 +62,6 @@ To install the tools: > *getting-started\tools\get-toolchain.bat* - After the installation completes, the Azure IoT Explorer opens automatically. Keep the IoT Explorer open, you'll use it in later steps. - 1. After the installation, open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows. 1. Run the following code to confirm that CMake version 3.14 or later is installed. @@ -75,59 +69,53 @@ To install the tools: cmake --version ``` -### Create an IoT hub - -You can use Azure CLI to create an IoT hub that handles events and messaging for your device. +## Create the cloud components -To create an IoT hub: +### Create the IoT Central Application -1. From your console window, run the [az group create](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az-group-create) command to create a resource group. The following command creates a resource group named *MyResourceGroup* in the *centralus* region. +There are several ways to connect devices to Azure IoT. In this section, you learn how to connect a device by using Azure IoT Central. IoT Central is an IoT application platform that reduces the cost and complexity of creating and managing IoT solutions. - > Note: You can optionally set an alternate `location`. To see available locations, run [az account list-locations](https://docs.microsoft.com/cli/azure/account?view=azure-cli-latest#az-account-list-locations). For this tutorial we recommend using `centralus` as in the example CLI command. The IoT Plug and Play feature that you use later in the tutorial, is currently only available in three regions, including `centralus`. - - ```shell - az group create --name MyResourceGroup --location centralus - ``` +To create a new application: +1. From [Azure IoT Central portal](https://apps.azureiotcentral.com/), select **My apps** on the side navigation menu. +1. Select **+ New application**. +1. Select **Custom apps**. +1. Add Application Name and a URL. +1. Choose the **Free** Pricing plan to activate a 7-day trial. -1. Run the [az iot hub create](https://docs.microsoft.com/cli/azure/iot/hub?view=azure-cli-latest#az-iot-hub-create) command to create an IoT hub. It might take a few minutes to create an IoT hub. + ![IoT Central create an application](media/iotcentralcreate-custom.png) - *YourIotHubName*. Replace this placeholder below with the name you chose for your IoT hub. An IoT hub name must be globally unique in Azure. This placeholder is used in the rest of this tutorial to represent your unique IoT hub name. +1. Select **Create**. +1. After IoT Central provisions the application, it redirects you automatically to the new application dashboard. - ```shell - az iot hub create --resource-group MyResourceGroup --name {YourIoTHubName} - ``` + > Note: If you have an existing IoT Central application, you can use it to complete the steps in this article rather than create a new application. -1. After the IoT hub is created, view the JSON output in the console, and copy the `hostName` value to use in a later step. The `hostName` value looks like the following example: +### Create a new device - `{Your IoT hub name}.azure-devices.net` +In this section, you use the IoT Central application dashboard to create a new device. You will use the connection information for the newly created device to securely connect your physical device in a later section. -### Register a device +To create a device: +1. From the application dashboard, select **Devices** on the side navigation menu. +1. Select **+ New** to bring up the **Create a new device** window. +1. Leave Device template as **Unassigned**. +1. Fill in the desired Device name and Device ID. -In this section, you create a new device instance and register it with the IoT hub you created. You will use the connection information for the newly registered device to securely connect your physical device in a later section. + ![IoT Central create a device](media/iotcentralcreate-device.png) -To register a device: +1. Select the **Create** button. +1. The newly created device will appear in the **All devices** list. Select on the device name to show details. +1. Select **Connect** in the top right menu bar to display the connection information used to configure the device in the next section. -1. In your console, run the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-device-identity-create) command. This creates the simulated device identity. + ![IoT Central create a device](media/iotcentraldevice-connection-info.png) - *YourIotHubName*. Replace this placeholder below with the name you chose for your IoT hub. +1. Note the connection values for the following connection string parameters displayed in **Connect** dialog. You'll add these values to a configuration file in the next step: - *MyMXCHIPDevice*. You can use this name directly for the device in CLI commands in this tutorial. Optionally, use a different name. - - ```shell - az iot hub device-identity create --device-id MyMXCHIPDevice --hub-name {YourIoTHubName} - ``` - -1. After the device is created, view the JSON output in the console, and copy the `deviceId` and `primaryKey` values to use in a later step. +> * `ID scope` +> * `Device ID` +> * `Primary key` ## Prepare the device -Confirm that you have the copied the following values from the JSON output from the previous sections: - -> * `hostName` -> * `deviceId` -> * `primaryKey` - -To connect the MXCHIP DevKit to Azure, you'll modify a configuration file for Wi-Fi and Azure IoT settings, rebuild the image, and flash the image to the device. +To connect the STM DevKit to Azure, you'll modify a configuration file for Wi-Fi and Azure IoT settings, rebuild the image, and flash the image to the device. ### Add configuration @@ -136,20 +124,19 @@ To connect the MXCHIP DevKit to Azure, you'll modify a configuration file for Wi > *getting-started\MXChip\AZ3166\app\azure_config.h* 1. Set the Wi-Fi constants to the following values from your local environment. - |Constant name|Value| |-------------|-----| |`WIFI_SSID` |{*Your Wi-Fi ssid*}| |`WIFI_PASSWORD` |{*Your Wi-Fi password*}| - |`WIFI_MODE` |{*One of the enumerated Wi-Fi mode values in the file.*}| + |`WIFI_MODE` |{*One of the enumerated Wi-Fi mode values in the file*}| 1. Set the Azure IoT device information constants to the values that you saved after you created Azure resources. |Constant name|Value| |-------------|-----| - |`IOT_HUB_HOSTNAME` |{*Your Iot hub hostName value*}| - |`IOT_HUB_DEVICE_ID` |{*Your deviceID value*}| - |`IOT_DEVICE_SAS_KEY` |{*Your primaryKey value*}| + |`IOT_DPS_ID_SCOPE` |{*Your ID scope value*}| + |`IOT_DPS_REGISTRATION_ID` |{*Your Device ID value*}| + |`IOT_DEVICE_SAS_KEY` |{*Your Primary key value*}| 1. Save and close the file. @@ -161,7 +148,7 @@ In your console or in File Explorer, run the script *rebuild.bat* at the followi After the build completes, confirm that the binary files were created in the following path: -> *getting-started\MXChip/AZ3166\build\app\mxchip_azure_iot.bin* +> *getting-started\MXChip\AZ3166\build\app\mxchip_azure_iot.bin* ### Flash the image @@ -178,26 +165,20 @@ After the build completes, confirm that the binary files were created in the fol 1. Paste the binary file into the root folder of the MXCHIP Devkit. Flashing starts automatically and completes in a few seconds. - > Note: During the flashing process, a green LED toggles on MXCHIP DevKit. The process completes in a few seconds without further notification. + > Note: During the flashing process, a green LED toggles on MXCHIP DevKit. ### Confirm device connection details You can use the **Termite** utility to monitor communication and confirm that your device is set up correctly. > Note: If you have issues getting your device to initialize or connect after flashing, see [Troubleshooting](../../docs/troubleshooting.md). -1. Open Device Manager and find the COM port for the MXCHIP IoT DevKit. - - ![COM Port](./media/com_port.png) - 1. Start **Termite**. 1. Select **Settings**. 1. In the **Serial port settings** dialog, check the following settings and update if needed: - * **Baud rate**: 115,200 - * **Port**: The port that your MXCHIP Devkit is connected to. + * **Port**: The port that your STM DevKit is connected to. If there are multiple port options in the dropdown, you can find the correct port to use. Open Windows **Device Manager**, and view **Ports** to identify which port to use. ![Termite](media/termite-settings.png) - 1. Select OK. 1. Press the **Reset** button on the device. The button is labeled on the device and located near the micro USB connector. 1. In the **Termite** console, check the following checkpoint values to confirm that the device is initialized and connected to Azure IoT. @@ -243,129 +224,51 @@ You can use the **Termite** utility to monitor communication and confirm that yo Keep Termite open to monitor device output in the following steps. -## View device properties - -> **Note**: From this point in the tutorial, you can continue these steps, or you can optionally follow the same steps using the IoT Plug and Play preview. IoT Plug and Play provides a standard device model that lets a compatible device advertise its capabilities to an application. This approach simplifies the process of adding, configuring, and interacting with devices. To try IoT Plug and Play with your device, see [Using IoT Plug and Play with Azure RTOS](../../docs/plugandplay.md). - -You can use the Azure IoT Explorer to view and manage the properties of your devices. In the following steps, you'll add a connection to your IoT hub in IoT Explorer. With the connection, you can view properties for devices associated with the IoT hub. Optionally, you can perform the same task using Azure CLI. - -To add a connection to your IoT hub: - -1. In your console window, run the [az iot hub show-connection-string](https://docs.microsoft.com/en-us/cli/azure/iot/hub?view=azure-cli-latest#az-iot-hub-show-connection-string) command to get the connection string for your IoT hub. - - ```shell - az iot hub show-connection-string --name {YourIoTHubName} - ``` - -1. Copy the connection string without the surrounding quotation characters. -1. In Azure IoT Explorer, select **IoT hubs > Add connection**. -1. Paste the connection string into the **Connection string** box. -1. Select **Save**. - - ![Azure IoT Explorer connection string](media/azure-iot-explorer-create-connection.png) - -If the connection succeeds, the Azure IoT Explorer switches to a **Devices** view and lists your device. - -To view device properties using Azure IoT Explorer: - -1. Select the link for your device identity. IoT Explorer displays details for the device. +## Verify the device status - ![Azure IoT Explorer device identity](media/azure-iot-explorer-device-identity.png) +To view the device status in IoT Central portal: +1. From the application dashboard, select **Devices** on the side navigation menu. +1. Check the **Device status** of the device is updated to **Provisioned**. +1. Check the **Device template** of the device has updated to **Getting Stared Guide**. -1. Inspect the properties for your device in the **Device identity** panel. -1. Optionally, select the **Device twin** panel and inspect additional device properties. + ![IoT Central device status](media/azure-iot-central-device-view-status.png) -To use Azure CLI to view device properties: +> Note: If the **Device template** of the device remains as **Unassigned**, select the device and select **Migrate** to the "Getting Started Guide" template in order to see the graphic visual data representation. -1. Run the [az iot hub device-identity show](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext-azure-iot-az-iot-hub-device-identity-show) command. - - ```shell - az iot hub device-identity show --device-id MyMXCHIPDevice --hub-name {YourIoTHubName} - ``` - -1. Inspect the properties for your device in the console output. +![IoT Central device template migrate](media/azure-iot-central-device-template-migrate.png) ## View telemetry -With Azure IoT Explorer, you can view the flow of telemetry from your device to the cloud. Optionally, you can perform the same task using Azure CLI. +With IoT Central, you can view the flow of telemetry from your device to the cloud. -To view telemetry in Azure IoT Explorer: +To view telemetry in IoT Central portal: -1. In IoT Explorer select **Telemetry**. Confirm that **Use built-in event hub** is set to *Yes*. -1. Select **Start**. -1. View the telemetry as the device sends messages to the cloud. +1. From the application dashboard, select **Devices** on the side navigation menu. +1. Select the device from the device list. +1. View the telemetry as the device sends messages to the cloud in the **Overview** tab. - ![Azure IoT Explorer device telemetry](media/azure-iot-explorer-device-telemetry.png) + ![IoT Central device telemetry](media/azure-iot-central-device-telemetry.png) - Note: You can also monitor telemetry from the device by using the Termite terminal. - -1. Select **Stop** to end receiving events. - -To use Azure CLI to view device telemetry: - -1. In your CLI console, run the [az iot hub monitor-events](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-monitor-events) command. Use the names that you created previously in Azure IoT for your device and IoT hub. - - ```shell - az iot hub monitor-events --device-id MyMXCHIPDevice --hub-name {YourIoTHubName} - ``` - -1. View the JSON output in the console. - - ```json - { - "event": { - "origin": "MyMXCHIPDevice", - "payload": "{\"temperature\": 25}" - } - } - ``` - -1. Select CTRL+C to end monitoring. +> Note: You can also monitor telemetry from the device by using the Termite terminal. ## Call a direct method on the device -You can also use Azure IoT Explorer to call a direct method that you have implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that enables you to turn an LED on or off. Optionally, you can perform the same task using Azure CLI. - -To call a method in Azure IoT Explorer: +You can also use IoT Central to call a direct method that you have implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that enables you to turn an LED on or off. -1. Select **Direct method**. -1. In the **Direct method** panel add the following values for the method name and payload. The payload value *true* indicates to turn the LED on. - * **Method name**: `setLedState` - * **Payload**: `true` -1. Select **Invoke method**. The yellow User LED light should turn on. +To call a method in IoT Central portal: - ![Azure IoT Explorer invoke method](media/azure-iot-explorer-invoke-method.png) -1. Change **Payload** to *false*, and again select **Invoke method**. The yellow User LED should turn off. -1. Optionally, you can view the output in Termite to monitor the status of the methods. +1. Select **Command** tab from the device page. +1. Select **State** and select **Run**. The LED light should turn on. -To use Azure CLI to call a method: + ![IoT Central invoke method](media/azure-iot-central-invoke-method.png) +1. Unselect **State** and select **Run**. The LED light should turn off. -1. Run the [az iot hub invoke-device-method](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-invoke-device-method) command, and specify the method name and payload. For this method, setting `method-payload` to `true` turns the LED on, and setting it to `false` turns it off. +## View device information - - - az iot hub invoke-device-method --device-id MyMXCHIPDevice --method-name setLedState --method-payload true --hub-name {YourIoTHubName} - +You can view the device information from IoT Central. - The CLI console shows the status of your method call on the device, where `200` indicates success. - - ```json - { - "payload": {}, - "status": 200 - } - ``` - -1. Check your device to confirm the LED state. - -1. View the Termite terminal to confirm the output messages: - - ```output - Received direct method call: setLedState - Payload: true - LED is turned ON - Device twin property sent: {"ledState":true} - ``` +Select **About** tab from the device page. +![IoT Central device info](media/azure-iot-central-device-about.png) ## Debugging @@ -373,28 +276,20 @@ For debugging the application, see [Debugging with Visual Studio Code](../../doc ## Clean up resources -If you no longer need the Azure resources created in this tutorial, you can use the Azure CLI to delete the resource group and all the resources you created for this tutorial. Optionally, you can use Azure IoT Explorer to delete individual resources including devices and IoT hubs. - -If you continue to another tutorial in this Getting Started guide, you can keep the resources you've already created and reuse them. +If you no longer need the Azure resources created in this tutorial, you can delete them from the IoT Central portal. Optionally, if you continue to another tutorial in this Getting Started guide, you can keep the resources you've already created and reuse them. -> **Important**: Deleting a resource group is irreversible. The resource group and all the resources contained in it are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources. +To keep the Azure IoT Central sample application but remove only specific devices: +1. Select the **Devices** tab for your application. +1. Select the device from the device list. +1. Select **Delete**. -To delete a resource group by name: -1. Run the [az group delete](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az-group-delete) command. This removes the resource group, the IoT Hub, and the device registration you created. - - ```shell - az group delete --name MyResourceGroup - ``` - -1. Run the [az group list](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az-group-list) command to confirm the resource group is deleted. - - ```shell - az group list - ``` +To remove the entire Azure IoT Central sample application and all its devices and resources: +1. Select **Administration** > **Your application**. +1. Select **Delete**. ## Next Steps -In this tutorial 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 Azure CLI to create Azure resources, connect the MXCHIP DevKit securely to Azure, view telemetry, and send messages. +In this tutorial 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. * For device developers, the suggested next step is to see the other tutorials in the series [Getting started with Azure RTOS](https://go.microsoft.com/fwlink/p/?linkid=2129824). * If you have issues getting your device to initialize or connect after following the steps in this guide, see [Troubleshooting](../../docs/troubleshooting.md). diff --git a/NXP/MIMXRT1050-EVKB/readme.md b/NXP/MIMXRT1050-EVKB/readme.md index 44b1a1ed..12c08bb0 100644 --- a/NXP/MIMXRT1050-EVKB/readme.md +++ b/NXP/MIMXRT1050-EVKB/readme.md @@ -59,7 +59,7 @@ The cloned repo contains a setup script that installs and configures the require > * [GCC](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm): Compile > * [CMake](https://cmake.org): Build > * [Termite](https://www.compuphase.com/software_termite.htm): Monitor serial port output for connected devices -> * [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/): Manage Azure resources +> * [Azure CLI](https://docs.microsoft.com/cli/azure/): Manage Azure resources > * [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases): Cross-platform utility to monitor and manage Azure IoT resources To install the tools: @@ -109,7 +109,7 @@ In this section, you create a new device instance and register it with the IoT h To register a device: -1. In your console, run the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-device-identity-create) command. This creates the simulated device identity. +1. In your console, run the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext_azure_iot_az_iot_hub_device_identity_create) command. This creates the simulated device identity. *YourIotHubName*. Replace this placeholder below with the name you chose for your IoT hub. @@ -233,7 +233,7 @@ You can use the Azure IoT Explorer to view and manage the properties of your dev To add a connection to your IoT hub: -1. In your console window, run the [az iot hub show-connection-string](https://docs.microsoft.com/en-us/cli/azure/iot/hub?view=azure-cli-latest#az-iot-hub-show-connection-string) command to get the connection string for your IoT hub. +1. In your console window, run the [az iot hub show-connection-string](https://docs.microsoft.com/cli/azure/iot/hub?view=azure-cli-latest#az_iot_hub_show_connection_string) command to get the connection string for your IoT hub. ```shell az iot hub show-connection-string --name {YourIoTHubName} @@ -259,7 +259,7 @@ To view device properties using Azure IoT Explorer: To use Azure CLI to view device properties: -1. Run the [az iot hub device-identity show](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext-azure-iot-az-iot-hub-device-identity-show) command. +1. Run the [az iot hub device-identity show](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext_azure_iot_az_iot_hub_device_identity_show) command. ```shell az iot hub device-identity show --device-id MyNXPDevice --hub-name {YourIoTHubName} @@ -285,7 +285,7 @@ To view telemetry in Azure IoT Explorer: To use Azure CLI to view device telemetry: -1. In your CLI console, run the [az iot hub monitor-events](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-monitor-events) command. Use the names that you created previously in Azure IoT for your device and IoT hub. +1. In your CLI console, run the [az iot hub monitor-events](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext_azure_iot_az_iot_hub_monitor_events) command. Use the names that you created previously in Azure IoT for your device and IoT hub. ```shell az iot hub monitor-events --device-id MyNXPDevice --hub-name {YourIoTHubName} @@ -322,7 +322,7 @@ To call a method in Azure IoT Explorer: To use Azure CLI to call a method: -1. Run the [az iot hub invoke-device-method](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-invoke-device-method) command, and specify the method name and payload. For this method, setting `method-payload` to `true` turns the LED on, and setting it to `false` turns it off. +1. Run the [az iot hub invoke-device-method](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext_azure_iot_az_iot_hub_invoke_device_method) command, and specify the method name and payload. For this method, setting `method-payload` to `true` turns the LED on, and setting it to `false` turns it off. diff --git a/NXP/MIMXRT1060-EVK/readme.md b/NXP/MIMXRT1060-EVK/readme.md index 3fdea011..04d55bb9 100644 --- a/NXP/MIMXRT1060-EVK/readme.md +++ b/NXP/MIMXRT1060-EVK/readme.md @@ -59,7 +59,7 @@ The cloned repo contains a setup script that installs and configures the require > * [GCC](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm): Compile > * [CMake](https://cmake.org): Build > * [Termite](https://www.compuphase.com/software_termite.htm): Monitor serial port output for connected devices -> * [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/): Manage Azure resources +> * [Azure CLI](https://docs.microsoft.com/cli/azure/): Manage Azure resources > * [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases): Cross-platform utility to monitor and manage Azure IoT resources To install the tools: @@ -109,7 +109,7 @@ In this section, you create a new device instance and register it with the IoT h To register a device: -1. In your console, run the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-device-identity-create) command. This creates the simulated device identity. +1. In your console, run the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext_azure_iot_az_iot_hub_device_identity_create) command. This creates the simulated device identity. *YourIotHubName*. Replace this placeholder below with the name you chose for your IoT hub. @@ -233,7 +233,7 @@ You can use the Azure IoT Explorer to view and manage the properties of your dev To add a connection to your IoT hub: -1. In your console window, run the [az iot hub show-connection-string](https://docs.microsoft.com/en-us/cli/azure/iot/hub?view=azure-cli-latest#az-iot-hub-show-connection-string) command to get the connection string for your IoT hub. +1. In your console window, run the [az iot hub show-connection-string](https://docs.microsoft.com/cli/azure/iot/hub?view=azure-cli-latest#az_iot_hub_show_connection_string) command to get the connection string for your IoT hub. ```shell az iot hub show-connection-string --name {YourIoTHubName} @@ -259,7 +259,7 @@ To view device properties using Azure IoT Explorer: To use Azure CLI to view device properties: -1. Run the [az iot hub device-identity show](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext-azure-iot-az-iot-hub-device-identity-show) command. +1. Run the [az iot hub device-identity show](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext_azure_iot_az_iot_hub_device_identity_show) command. ```shell az iot hub device-identity show --device-id MyNXPDevice --hub-name {YourIoTHubName} @@ -285,7 +285,7 @@ To view telemetry in Azure IoT Explorer: To use Azure CLI to view device telemetry: -1. In your CLI console, run the [az iot hub monitor-events](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-monitor-events) command. Use the names that you created previously in Azure IoT for your device and IoT hub. +1. In your CLI console, run the [az iot hub monitor-events](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext_azure_iot_az_iot_hub_monitor_events) command. Use the names that you created previously in Azure IoT for your device and IoT hub. ```shell az iot hub monitor-events --device-id MyNXPDevice --hub-name {YourIoTHubName} @@ -322,7 +322,7 @@ To call a method in Azure IoT Explorer: To use Azure CLI to call a method: -1. Run the [az iot hub invoke-device-method](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-invoke-device-method) command, and specify the method name and payload. For this method, setting `method-payload` to `true` turns the LED on, and setting it to `false` turns it off. +1. Run the [az iot hub invoke-device-method](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext_azure_iot_az_iot_hub_invoke_device_method) command, and specify the method name and payload. For this method, setting `method-payload` to `true` turns the LED on, and setting it to `false` turns it off. diff --git a/README.md b/README.md index 44384734..af28c378 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ This Getting Started guides shows device developers how to start working with Azure RTOS. Each guide will step through from installation of the required toolchain, to connecting the device to Azure IoT Hub using IoT Plug and Play. * Refer to [Getting Started with Azure RTOS](https://go.microsoft.com/fwlink/p/?linkid=2129824) for additional information on the guides and Azure RTOS. -* Refer to [IoT Plug and Play](https://docs.microsoft.com/en-us/azure/iot-pnp) for information on the Iot Plug and Play Preview Refresh. +* Refer to [IoT Plug and Play](https://docs.microsoft.com/azure/iot-pnp) for information on the Iot Plug and Play Preview Refresh. * Ask questions on the [Azure RTOS Q&A](https://aka.ms/QnA/azure-rtos) site. ## Getting Started Guides diff --git a/Renesas/RSK_RX65N_2MB/readme.md b/Renesas/RSK_RX65N_2MB/readme.md index 5a8a8f1b..60a3bca7 100644 --- a/Renesas/RSK_RX65N_2MB/readme.md +++ b/Renesas/RSK_RX65N_2MB/readme.md @@ -61,7 +61,7 @@ The cloned repo contains a setup script that installs and configures the require > * [GCC](http://gcc-renesas.com/downloads/get.php?f=rx/8.3.0.202004-gnurx/gcc-8.3.0.202004-GNURX-ELF.exe): Compile > * [CMake](https://cmake.org): Build > * [Termite](https://www.compuphase.com/software_termite.htm): Monitor serial port output for connected devices -> * [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/): Manage Azure resources +> * [Azure CLI](https://docs.microsoft.com/cli/azure/): Manage Azure resources > * [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases): Cross-platform utility to monitor and manage Azure IoT resources To install the tools: @@ -121,7 +121,7 @@ In this section, you create a new device instance and register it with the IoT h To register a device: -1. In your console, run the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-device-identity-create) command. This creates the simulated device identity. +1. In your console, run the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext_azure_iot_az_iot_hub_device_identity_create) command. This creates the simulated device identity. *YourIotHubName*. Replace this placeholder below with the name you chose for your IoT hub. @@ -274,7 +274,7 @@ You can use the Azure IoT Explorer to view and manage the properties of your dev To add a connection to your IoT hub: -1. In your console window, run the [az iot hub show-connection-string](https://docs.microsoft.com/en-us/cli/azure/iot/hub?view=azure-cli-latest#az-iot-hub-show-connection-string) command to get the connection string for your IoT hub. +1. In your console window, run the [az iot hub show-connection-string](https://docs.microsoft.com/cli/azure/iot/hub?view=azure-cli-latest#az_iot_hub_show_connection_string) command to get the connection string for your IoT hub. ```shell az iot hub show-connection-string --name {YourIoTHubName} @@ -300,7 +300,7 @@ To view device properties using Azure IoT Explorer: To use Azure CLI to view device properties: -1. Run the [az iot hub device-identity show](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext-azure-iot-az-iot-hub-device-identity-show) command. +1. Run the [az iot hub device-identity show](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub/device-identity?view=azure-cli-latest#ext_azure_iot_az_iot_hub_device_identity_show) command. ```shell az iot hub device-identity show --device-id MyRenesasDevice --hub-name {YourIoTHubName} @@ -326,7 +326,7 @@ To view telemetry in Azure IoT Explorer: To use Azure CLI to view device telemetry: -1. In your CLI console, run the [az iot hub monitor-events](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-monitor-events) command. Use the names that you created previously in Azure IoT for your device and IoT hub. +1. In your CLI console, run the [az iot hub monitor-events](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext_azure_iot_az_iot_hub_monitor_events) command. Use the names that you created previously in Azure IoT for your device and IoT hub. ```shell az iot hub monitor-events --device-id MyRenesasDevice --hub-name {YourIoTHubName} @@ -363,7 +363,7 @@ To call a method in Azure IoT Explorer: To use Azure CLI to call a method: -1. Run the [az iot hub invoke-device-method](https://docs.microsoft.com/en-us/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext-azure-iot-az-iot-hub-invoke-device-method) command, and specify the method name and payload. For this method, setting `method-payload` to `true` turns the LEDs on, and setting it to `false` turns them off. +1. Run the [az iot hub invoke-device-method](https://docs.microsoft.com/cli/azure/ext/azure-iot/iot/hub?view=azure-cli-latest#ext_azure_iot_az_iot_hub_invoke_device_method) command, and specify the method name and payload. For this method, setting `method-payload` to `true` turns the LEDs on, and setting it to `false` turns them off. diff --git a/SECURITY.md b/SECURITY.md index 323bf81c..2b1735b7 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -2,7 +2,7 @@ Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). -If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below. +If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below. ## Reporting Security Issues @@ -10,7 +10,7 @@ If you believe you have found a security vulnerability in any Microsoft-owned re Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report). -If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc). +If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/msrc/pgp-key-msrc). You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc). @@ -32,4 +32,4 @@ We prefer all communications to be in English. ## Policy -Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd). \ No newline at end of file +Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/msrc/cvd). \ No newline at end of file diff --git a/STMicroelectronics/STM32L4_L4+/readme.md b/STMicroelectronics/STM32L4_L4+/readme.md index d6335166..5d0b87e9 100644 --- a/STMicroelectronics/STM32L4_L4+/readme.md +++ b/STMicroelectronics/STM32L4_L4+/readme.md @@ -19,9 +19,9 @@ In this tutorial you use Azure RTOS to connect either the STMicroelectronics [B- You will complete the following tasks: -* Install a set of embedded development tools for programming the STM DevKit in C. -* Build an image and flash it onto the STM DevKit. -* Use Azure IoT Central to create cloud components, view properties, view device telemetry, and call direct commands. +* Install a set of embedded development tools for programming the STM DevKit in C +* Build an image and flash it onto the STM DevKit +* Use Azure IoT Central to create cloud components, view properties, view device telemetry, and call direct commands ## Prerequisites diff --git a/core/src/azure_iot_mqtt/azure_iot_dps_mqtt.c b/core/src/azure_iot_mqtt/azure_iot_dps_mqtt.c index 5bb489c8..231fd156 100644 --- a/core/src/azure_iot_mqtt/azure_iot_dps_mqtt.c +++ b/core/src/azure_iot_mqtt/azure_iot_dps_mqtt.c @@ -1,7 +1,7 @@ /* Copyright (c) Microsoft Corporation. Licensed under the MIT License. */ -// https://docs.microsoft.com/en-us/azure/iot-dps/iot-dps-mqtt-support +// https://docs.microsoft.com/azure/iot-dps/iot-dps-mqtt-support #include diff --git a/core/src/azure_iot_mqtt/sas_token.c b/core/src/azure_iot_mqtt/sas_token.c index e301e497..a3018708 100644 --- a/core/src/azure_iot_mqtt/sas_token.c +++ b/core/src/azure_iot_mqtt/sas_token.c @@ -1,7 +1,7 @@ /* Copyright (c) Microsoft Corporation. Licensed under the MIT License. */ -// https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support +// https://docs.microsoft.com/azure/iot-hub/iot-hub-mqtt-support #include "sas_token.h" diff --git a/docs/plugandplay.md b/docs/plugandplay.md index f109f00c..5fb82706 100644 --- a/docs/plugandplay.md +++ b/docs/plugandplay.md @@ -2,7 +2,7 @@ ## Introduction -The [Azure RTOS Getting Started guide](../README.md) code sample includes a feature called IoT Plug and Play. The current tutorials in the guide don't show you how to use this feature. Instead, they demonstrate a more manual process of interacting with the device, using Azure IoT Explorer or Azure CLI. In contrast, IoT Plug and Play provides an open device model that lets applications programmatically query a device's capabilities and interact with it. A device uses this model to broadcast its capabilities to an IoT Plug and Play-enabled application. By using this model, you can streamline and enhance the tasks of adding, configuring, and managing devices. For more information see the [IoT Plug and Play documentation](https://docs.microsoft.com/en-us/azure/iot-pnp/). +The [Azure RTOS Getting Started guide](../README.md) code sample includes a feature called IoT Plug and Play. The current tutorials in the guide don't show you how to use this feature. Instead, they demonstrate a more manual process of interacting with the device, using Azure IoT Explorer or Azure CLI. In contrast, IoT Plug and Play provides an open device model that lets applications programmatically query a device's capabilities and interact with it. A device uses this model to broadcast its capabilities to an IoT Plug and Play-enabled application. By using this model, you can streamline and enhance the tasks of adding, configuring, and managing devices. For more information see the [IoT Plug and Play documentation](https://docs.microsoft.com/azure/iot-pnp/). To use IoT Plug and Play with your device, follow the steps in this article. The device model lets IoT Explorer automatically generate a UI based on the device's properties. You'll use IoT Explorer to view the device's properties and telemetry, call a direct method, and modify a writeable property. @@ -119,4 +119,4 @@ To call a direct method on the connected device: In this tutorial you used Azure IoT Explorer to work with an IoT Plug and Play enabled device. You used IoT Explorer to add an IoT Plug and Play device model. Then you used the UI generated by IoT Explorer to interact with device properties, view telemetry, and invoke a direct method to toggle the LED. * To continue learning about Azure RTOS, return to the tutorial you started with in the [Azure RTOS Getting Started guide](../README.md). You can optionally learn how to perform the same tasks you completed in this tutorial, but without using IoT Plug and Play. The tutorials also provide directions to clean up IoT resources that you created for the sample application. -* To learn more about IoT Plug and Play, see the [IoT Plug and Play documentation](https://docs.microsoft.com/en-us/azure/iot-pnp/). +* To learn more about IoT Plug and Play, see the [IoT Plug and Play documentation](https://docs.microsoft.com/azure/iot-pnp/). diff --git a/docs/using-azure-rtos.md b/docs/using-azure-rtos.md index d5bc15a9..0c048c62 100644 --- a/docs/using-azure-rtos.md +++ b/docs/using-azure-rtos.md @@ -1,6 +1,6 @@ # Using Azure RTOS in the Getting started guide -The getting started guide in this repository uses Microsoft Azure RTOS for general operations and for connecting to [Azure IoT Hub](https://azure.microsoft.com/en-us/services/iot-hub). This article explains how the sample code implements Azure RTOS components for devices. +The getting started guide in this repository uses Microsoft Azure RTOS for general operations and for connecting to [Azure IoT Hub](https://azure.microsoft.com/services/iot-hub). This article explains how the sample code implements Azure RTOS components for devices. The sample code in the getting started guide uses the following Azure RTOS components: diff --git a/docs/using-self-signed-x509-certificates.md b/docs/using-self-signed-x509-certificates.md index 80c010f4..fd579679 100644 --- a/docs/using-self-signed-x509-certificates.md +++ b/docs/using-self-signed-x509-certificates.md @@ -40,7 +40,7 @@ Run the setup script to install the required tools. > * [GCC](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm) > * [CMake](https://cmake.org/) > * [Termite](https://www.compuphase.com/software/termite-3.4.exe) -> * [Azure IoT Explorer](https://docs.microsoft.com/en-us/azure/iot-pnp/howto-use-iot-explorer) +> * [Azure IoT Explorer](https://docs.microsoft.com/azure/iot-pnp/howto-use-iot-explorer) Install required tools using the provided batch script: ```bash @@ -55,7 +55,7 @@ cmake --version ``` ## Create Azure Resources -Follow [this](https://docs.microsoft.com/en-us/azure/iot-dps/quick-setup-auto-provision) guide to set up your DPS and IoT Hub enpoints. +Follow [this](https://docs.microsoft.com/azure/iot-dps/quick-setup-auto-provision) guide to set up your DPS and IoT Hub enpoints. ## Create a Self-Signed X.509 Certificate ```bash @@ -70,7 +70,7 @@ xxd -i private_key_formatted.der >> cert.c ``` ## Create a device enrollment entry in DPS -If you haven't already, please set up your [DPS and IoT Hub instances](https://docs.microsoft.com/en-us/azure/iot-dps/quick-setup-auto-provision). +If you haven't already, please set up your [DPS and IoT Hub instances](https://docs.microsoft.com/azure/iot-dps/quick-setup-auto-provision). 1. Sign in to the Azure portal, select the **All resources** button on the left-hand menu and open your Device Provisioning service. 1. Select the **Manage enrollments** tab @@ -106,9 +106,9 @@ If you haven't already, please set up your [DPS and IoT Hub instances](https://d ## Use Azure IoT Explorer to See Your Device in Action -1. Follow [this](https://docs.microsoft.com/en-us/azure/iot-pnp/howto-use-iot-explorer) guide to install and set up your Azure IoT Explorer. +1. Follow [this](https://docs.microsoft.com/azure/iot-pnp/howto-use-iot-explorer) guide to install and set up your Azure IoT Explorer. -2. [Link the explorer to the IoT Hub](https://docs.microsoft.com/en-us/azure/iot-pnp/howto-use-iot-explorer#connect-to-your-hub) you created in this tutorial. +2. [Link the explorer to the IoT Hub](https://docs.microsoft.com/azure/iot-pnp/howto-use-iot-explorer#connect-to-your-hub) you created in this tutorial. 3. You can now click on the IoT Hub link in the explorer and see your device listed. * Click into your device dashboard