Skip to content

Commit f04be6e

Browse files
committed
Initial extensibility updates
1 parent 92f9ab9 commit f04be6e

File tree

4 files changed

+3232
-1912
lines changed

4 files changed

+3232
-1912
lines changed

articles/iot/iot-overview-solution-extensibility.md

Lines changed: 47 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: iot
66
author: dominicbetts
77
ms.author: dobett
88
ms.topic: overview
9-
ms.date: 02/28/2024
9+
ms.date: 01/22/2025
1010
ms.custom: template-overview
1111
# Customer intent: As a solution builder, I want a high-level overview of the options for extending an IoT solution so that I can easily find relevant content for my scenario.
1212
---
@@ -15,36 +15,67 @@ ms.custom: template-overview
1515

1616
This overview introduces the key concepts around the options to extend an Azure IoT solution. Each section includes links to content that provides further detail and guidance.
1717

18-
The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the areas relevant to extending an IoT solution.
19-
20-
:::image type="content" source="media/iot-overview-solution-extensibility/iot-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture highlighting solution extensibility areas." border="false":::
21-
22-
In Azure IoT, solution extensibility refers to the ways you can add to the built-in functionality of the IoT cloud services and build integrations with other services.
23-
2418
## Extensibility scenarios
2519

2620
Extensibility scenarios for IoT solutions include:
2721

2822
### Analysis and visualization
2923

30-
A typical IoT solution includes the analysis and visualization of the data from your devices to enable business insights. To learn more, see [Analyze and visualize your IoT data](iot-overview-analyze-visualize.md).
24+
A typical IoT solution includes the analysis and visualization of the data from your devices and assets to enable business insights. To learn more, see [Analyze and visualize your IoT data](iot-overview-analyze-visualize.md).
3125

3226
### Integration with other services
3327

3428
An IoT solution might include other systems such as asset management, work scheduling, and control automation systems. Such systems might:
3529

36-
- Use data from your IoT devices as input to predictive maintenance systems that generate entries in a work scheduling system.
30+
- Use data from your IoT assets or devices as input to predictive maintenance systems that generate entries in a work scheduling system.
3731
- Update the device registry to ensure it has up to date data from your asset management system.
38-
- Send messages to your devices to control their behavior based on rules in a control automation system.
39-
40-
## Azure Data Health Services
41-
42-
[Azure Health Data Services](../healthcare-apis/healthcare-apis-overview.md) is a set of managed API services based on open standards and frameworks that enable workflows to improve healthcare and offer scalable and secure healthcare solutions. An IoT solution can use these services to integrate IoT data into a healthcare solution.
32+
- Send messages to your assets or devices to control their behavior based on rules in a control automation system.
4333

4434
## Extensibility mechanisms
4535

4636
The following sections describe the key mechanisms available to extend your IoT solution.
4737

38+
# [Edge-based solution](#tab/edge)
39+
40+
The following diagram shows a high-level view of the components in a typical edge-based IoT solution. This article focuses on the extensibility points highlighted in the diagram:
41+
42+
:::image type="content" source="media/iot-overview-solution-extensibility/iot-edge-extensibility-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture for edge-based solutions." border="false":::
43+
44+
In Azure IoT, solution extensibility refers to the ways you can add to the built-in functionality of the edge and cloud services and build integrations with other services.
45+
46+
### Message broker
47+
48+
Azure IoT Operations includes an MQTT broker that routes messages from the connectors to dataflows that connect to cloud endpoints. You can deploy your own pods to the cluster to interact with the message broker to:
49+
50+
- Use custom message processing logic on the MQTT messages.
51+
- Build custom application logic to run at the edge.
52+
53+
The message broker is based on the [MQTT protocol](https://mqtt.org/) and supports APIs and SDKs such as:
54+
55+
- [DAPR](../iot-operations/create-edge-apps/howto-develop-dapr-apps.md)
56+
- [MQTTnet](../iot-operations/create-edge-apps/howto-develop-mqttnet-apps.md).
57+
58+
The message broker includes a [state store](../iot-operations/create-edge-apps/overview-state-store.md) that lets you manage distributed application state across the edge cluster.
59+
60+
### Cloud services
61+
62+
The northbound connectors in Azure IoT Operations let you route messages from your assets to different cloud endpoints. Routing messages enables you to build integrations with other services and to export data for analysis and visualization.
63+
64+
### REST APIs
65+
66+
The Azure IoT Operations REST API provides the following capabilities that are useful for extending your IoT solution:
67+
68+
- Manage the message broker.
69+
- Manage your dataflows.
70+
71+
# [Cloud-based solution](#tab/cloud)
72+
73+
The following diagram shows a high-level view of the components in a typical IoT solution. This article focuses on the extensibility points highlighted in the diagram:
74+
75+
:::image type="content" source="media/iot-overview-solution-extensibility/iot-cloud-extensibility-architecture.svg" alt-text="Diagram that shows the high-level IoT solution architecture highlighting solution extensibility areas." border="false":::
76+
77+
In Azure IoT, solution extensibility refers to the ways you can add to the built-in functionality of the IoT cloud services and build integrations with other services.
78+
4879
### Service APIs (IoT Hub)
4980

5081
IoT Hub and the Device Provisioning Service (DPS) provide a set of service APIs that you can use to manage and interact with your hub and devices. These APIs include:
@@ -82,3 +113,5 @@ In addition to device telemetry, both IoT Hub and IoT Central can send property
82113
### IoT Central application templates
83114

84115
The IoT Central application templates provide a starting point for building IoT solutions that include integrations with other services. You can use the templates to create an application that includes resources that are relevant to your solution. To learn more, see [IoT Central application templates](../iot-central/core/howto-create-iot-central-application.md#create-and-use-a-custom-application-template).
116+
117+
---

0 commit comments

Comments
 (0)