Manage your IoT solution
This overview introduces the key concepts around the options to manage an Azure IoT solution. Each section includes links to content that provides further detail and guidance.
The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the areas relevant to managing an IoT solution.
There are many options for managing your IoT solution including the Azure portal, PowerShell, and ARM templates. This article summarizes the main options.
To learn about securing your IoT solution, see Secure your IoT solution.
Monitoring
While there are tools specifically for monitoring devices in your IoT solution, you also need to be able to monitor the health of your IoT services:
| Service | Monitoring options |
|---|---|
| IoT Hub | Use Azure Monitor to monitor your IoT hub Check IoT Hub service and resource health |
| Device Provisioning Service (DPS) | Use Azure Monitor to monitor your DPS instance |
| IoT Edge | Use Azure Monitor to monitor your IoT Edge fleet Monitor IoT Edge deployments |
| IoT Central | Use audit logs to track activity in your IoT Central application Use Azure Monitor to monitor your IoT Central application |
| Azure Digital Twins | Use Azure Monitor to monitor Azure Digital Twins resources |
To learn more about the Azure Monitor service, see Azure Monitor overview.
Azure portal
The Azure portal offers a consistent GUI environment for managing your Azure IoT services. For example, you can use the portal to:
| Action | Links |
|---|---|
| Deploy service instances in your Azure subscription | Manage your IoT hubs Set up DPS Manage IoT Central applications Set up an Azure Digital Twins instance |
| Configure services | Create and delete routes and endpoints (IoT Hub) Deploy IoT Edge modules Configure file uploads (IoT Hub) Manage device enrollments (DPS) Manage allocation policies (DPS) |
ARM templates and Bicep
To implement infrastructure as code for your Azure IoT solutions, use Azure Resource Manager templates (ARM templates). The template is a JavaScript Object Notation (JSON) file that defines the infrastructure and configuration for your project. Bicep is a new language that offers the same capabilities as ARM templates but with a syntax that's easier to use.
For example, you can use ARM templates or Bicep to:
| Action | Links |
|---|---|
| Deploy service instances in your Azure subscription | Create an IoT hub Set up DPS |
| Manage services | Create and delete routes and endpoints (IoT Hub) Azure Resource Manager SDK samples (IoT Central) |
For ARM templates and Bicep reference documentation, see:
PowerShell
Use PowerShell to automate the management of your IoT solution. For example, you can use PowerShell to:
| Action | Links |
|---|---|
| Deploy service instances in your Azure subscription | Create an IoT hub using the New-AzIotHub cmdlet Create an IoT Central application |
| Manage services | Create and delete routes and endpoints (IoT Hub) Manage an IoT Central application |
For PowerShell reference documentation, see:
Azure CLI
Use the Azure CLI to automate the management of your IoT solution. For example, you can use the Azure CLI to:
| Action | Links |
|---|---|
| Deploy service instances in your Azure subscription | Create an IoT hub using the Azure CLI Create an IoT Central application Set up an Azure Digital Twins instance Set up DPS |
| Manage services | Create and delete routes and endpoints (IoT Hub) Deploy and monitor IoT Edge modules at scale Manage an IoT Central application Create an Azure Digital Twins graph |
For Azure CLI reference documentation, see:
az iot hubaz iot device(IoT Hub)az iot edgeaz iot dpsaz iot centralaz iot du(Azure Device Update)az dt(Azure Digital Twins)
Azure DevOps tools
Use Azure DevOps tools to automate the management of your IoT solution. For example, you can use Azure DevOps tools to enable:
- Continuous integration and continuous deployment to Azure IoT Edge devices
- Integration of IoT Central with Azure Pipelines for CI/CD
Next steps
Now that you've seen an overview of the extensibility options available to your IoT solution, some suggested next steps include: