Skip to content

Commit c5f1a74

Browse files
authored
Merge pull request #112130 from dominicbetts/central-developer-next-steps
Update next steps for device developers
2 parents 338764c + 5dc3d16 commit c5f1a74

14 files changed

+70
-40
lines changed

articles/iot-central/core/concepts-get-connected.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ ms.custom: [amqp, mqtt]
1414

1515
# Get connected to Azure IoT Central
1616

17+
*This article applies to operators and device developers.*
18+
1719
This article describes the options for connecting your devices to an Azure IoT Central application.
1820

1921
Typically, you must register a device in your application before it can connect. However, IoT Central does support scenarios where [devices can connect without first being registered](#connect-without-registering-devices).
@@ -262,7 +264,8 @@ All data exchanged between devices and your Azure IoT Central is encrypted. IoT
262264

263265
## Next steps
264266

265-
Now that you've learned about device connectivity in Azure IoT Central, here are the suggested next steps:
267+
If you're a device developer, some suggested next steps are to:
266268

267-
- [Prepare and connect a DevKit device](howto-connect-devkit.md)
268-
- [C SDK: Provisioning Device Client SDK](https://github.com/Azure/azure-iot-sdk-c/blob/master/provisioning_client/devdoc/using_provisioning_client.md)
269+
- Learn how to [Monitor device connectivity using Azure CLI](./howto-monitor-devices-azure-cli.md)
270+
- Learn how to [Define a new IoT device type in your Azure IoT Central application](./howto-set-up-template.md)
271+
- Read about [Azure IoT Edge devices and Azure IoT Central](./concepts-iot-edge.md)

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ services: iot-central
1111

1212
# Connect Azure IoT Edge devices to an Azure IoT Central application
1313

14+
*This article applies to solution builders and device developers.*
15+
1416
IoT Edge is made up of three components:
1517

1618
* **IoT Edge modules** are containers that run Azure services, partner services, or your own code. Modules are deployed to IoT Edge devices, and run locally on those devices.
@@ -67,4 +69,4 @@ If you selected an IoT Edge device to be a gateway device, you can add downstrea
6769

6870
## Next steps
6971

70-
Now that you know what IoT Central application templates are, get started by [creating an IoT Central Application](quick-deploy-iot-central.md).
72+
If you're a device developer, a suggested next step is to learn about [gateway device types in IoT Central](./tutorial-define-gateway-device-type.md).

articles/iot-central/core/howto-connect-devkit.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ manager: jeffya
1212

1313
# Connect an MXChip IoT DevKit device to your Azure IoT Central application
1414

15+
*This article applies to device developers.*
16+
1517
This article shows you how to connect an MXChip IoT DevKit (DevKit) device to an Azure IoT Central application. The device uses the certified IoT Plug and Play (preview) model for the DevKit device to configure its connection to IoT Central.
1618

1719
In this how-to article, you:
@@ -99,4 +101,7 @@ To review the code or modify and compile it, go to the [Code Samples](https://do
99101

100102
## Next steps
101103

102-
Now that you've learned how to connect a DevKit device to your Azure IoT Central application, the suggested next step is to learn how to [set up a custom device template](./howto-set-up-template.md) for your own IoT device.
104+
If you're a device developer, some suggested next steps are to:
105+
106+
- Read about [Device connectivity in Azure IoT Central](./concepts-get-connected.md)
107+
- Learn how to [Monitor device connectivity using Azure CLI](./howto-monitor-devices-azure-cli.md)

articles/iot-central/core/howto-connect-rigado-cascade-500.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ ms.date: 11/27/2019
1212

1313
# Connect a Rigado Cascade 500 gateway device to your Azure IoT Central application
1414

15+
*This article applies to solution builders and device developers.*
1516

1617
This article describes how, as a solution builder, you can connect a Rigado Cascade 500 gateway device to your Microsoft Azure IoT Central application.
1718

@@ -65,4 +66,7 @@ You are now ready to use your C500 device in your IoT Central application!
6566

6667
## Next steps
6768

68-
Now that you've learned how to connect a Rigado Cascade 500 to your Azure IoT Central application, the suggested next step is to learn how to [create an in-store analytics application](../retail/tutorial-in-store-analytics-create-app-pnp.md) to build an end to end solution.
69+
If you're a device developer, some suggested next steps are to:
70+
71+
- Read about [Device connectivity in Azure IoT Central](./concepts-get-connected.md)
72+
- Learn how to [Monitor device connectivity using Azure CLI](./howto-monitor-devices-azure-cli.md)

articles/iot-central/core/howto-connect-ruuvi.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ ms.date: 11/27/2019
1212

1313
# Connect a RuuviTag sensor to your Azure IoT Central application
1414

15+
*This article applies to solution builders and device developers.*
16+
1517
This article describes how, as a solution builder, you can connect a RuuviTag sensor to your Microsoft Azure IoT Central application.
1618

1719
What is a Ruuvi tag?
@@ -70,4 +72,7 @@ To create a simulated RuuviTag:
7072

7173
## Next Steps
7274

73-
Now that you've learned how to connect a RuuviTag to your Azure IoT Central application, the suggested next step is to learn how to [customize your IoT Central application](../retail/tutorial-in-store-analytics-customize-dashboard-pnp.md) to build an end to end solution.
75+
If you're a device developer, some suggested next steps are to:
76+
77+
- Read about [Device connectivity in Azure IoT Central](./concepts-get-connected.md)
78+
- Learn how to [Monitor device connectivity using Azure CLI](./howto-monitor-devices-azure-cli.md)

articles/iot-central/core/howto-monitor-devices-azure-cli.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ manager: corywink
1212

1313
# Monitor device connectivity using Azure CLI
1414

15-
*This topic applies to builders and administrators.*
15+
*This topic applies to device developers and solution builders.*
1616

1717
Use the Azure CLI IoT extension to see messages your devices are sending to IoT Central and observe changes in the device twin. You can use this tool to debug and observe device connectivity and diagnose issues of device messages not reaching the cloud or devices not responding to twin changes.
1818

@@ -76,4 +76,4 @@ az iot central device-twin show --app-id <app-id> --device-id <device-id>
7676

7777
## Next steps
7878

79-
Now that you've learned how to use the IoT Central Explorer, the suggested next step is to explore [managing devices IoT Central](howto-manage-devices.md).
79+
If you're a device developer, a suggested next step is to read about [Device connectivity in Azure IoT Central](./concepts-get-connected.md).

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

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ manager: peterpr
1212

1313
# Define a new IoT device type in your Azure IoT Central application
1414

15+
*This article applies to solution builders and device developers.*
16+
1517
A device template is a blueprint that defines the characteristics and behaviors of a type of device that connects to an Azure IoT Central application.
1618

1719
For example, a builder can create a device template for a connected fan that has the following characteristics:
@@ -248,18 +250,6 @@ To publish a device template, go to you your device template, and select **Publi
248250

249251
After you publish a device template, an operator can go to the **Devices** page, and add either real or simulated devices that use your device template. You can continue to modify and save your device template as you're making changes. When you want to push these changes out to the operator to view under the **Devices** page, you must select **Publish** each time.
250252

251-
252253
## Next steps
253254

254-
In this tutorial, you learned how to:
255-
256-
* Create a new IoT device template.
257-
* Create cloud properties.
258-
* Create customizations.
259-
* Define a visualization for the device telemetry.
260-
* Publish your device template.
261-
262-
Next, you can:
263-
264-
> [!div class="nextstepaction"]
265-
> [Connect a device](howto-connect-devkit.md)
255+
If you're a device developer, a suggested next step is to read about [device template versioning](./howto-version-device-template.md).

articles/iot-central/core/howto-version-device-template.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ manager: peterpr
1212

1313
# Create a new device template version
1414

15-
15+
*This article applies to solution builders and device developers.*
1616

1717
Azure IoT Central allows rapid development of IoT Applications. You can quickly iterate over your device template designs by adding, editing, or deleting device capabilities, views, and customizations. Once you have published your device template, the device capability model shows as **Published** with lock icons next to the model. In order to make changes to the device capability model, you will need to create a new version of the device template. Meanwhile the cloud properties, customizations, and views can all be edited at any time without needing to version the device template. Once you have saved any of these changes, you can publish the device template to make the latest changes available for the operator to view in Device Explorer.
1818

@@ -76,7 +76,4 @@ You can create multiple versions of the device template. Over time, you will hav
7676

7777
## Next steps
7878

79-
Now that you have learned how to use device template versions in your Azure IoT Central application, here is the suggested next step:
80-
81-
> [!div class="nextstepaction"]
82-
> [How to create telemetry rules](tutorial-create-telemetry-rules.md)
79+
If you're a device developer, a suggested next step is to read about [Azure IoT Edge devices and Azure IoT Central](./concepts-iot-edge.md).

articles/iot-central/core/overview-iot-central.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -192,11 +192,13 @@ Each Azure subscription has default quotas that could impact the scope of your I
192192

193193
## Next steps
194194

195-
Now that you have an overview of IoT Central, here are suggested next steps:
195+
Now that you have an overview of IoT Central, here are some suggested next steps:
196196

197197
- Understand the available [Azure technologies and services for creating IoT solutions](../../iot-fundamentals/iot-services-and-technologies.md).
198198
- Familiarize yourself with the [Azure IoT Central UI](overview-iot-central-tour.md).
199199
- Get started by [creating an Azure IoT Central application](quick-deploy-iot-central.md).
200200
- Learn more about [IoT Plug and Play (preview)](../../iot-pnp/overview-iot-plug-and-play.md).
201201
- Learn how to [Connect an Azure IoT Edge device](./tutorial-add-edge-as-leaf-device.md).
202202
- Learn more about [Azure IoT technologies and services](../../iot-fundamentals/iot-services-and-technologies.md).
203+
204+
If you're a device developer and want to dive into some code, the suggested next step is to [Create and connect a client application to your Azure IoT Central application](./tutorial-connect-device-nodejs.md).

articles/iot-central/core/quick-deploy-iot-central.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,11 @@ To create a new Azure IoT Central application from the **Custom application** te
5454

5555
## Next steps
5656

57-
In this quickstart, you created an IoT Central application. Here's the suggested next step:
57+
In this quickstart, you created an IoT Central application. Here's the suggested next step to continue learning about IoT Central:
5858

5959
> [!div class="nextstepaction"]
6060
> [Add a simulated device to your IoT Central application](./quick-create-simulated-device.md)
61+
62+
If you're a device developer and want to dive into some code, the suggested next step is to:
63+
> [!div class="nextstepaction"]
64+
> [Create and connect a client application to your Azure IoT Central application](./tutorial-connect-device-nodejs.md)

0 commit comments

Comments
 (0)