Skip to content

Commit 2bdea16

Browse files
committed
Cont
1 parent 7e0e5e4 commit 2bdea16

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/iot/iot-overview-device-connectivity.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,8 @@ Assets use the following industry standards to exchange data with Azure services
4545

4646
- **MQTT messaging**. MQTT allows a single broker to serve tens of thousands of clients simultaneously, with lightweight publish-subscribe topic creation and management. Many IoT devices support MQTT natively out of the box. The MQTT broker underpins the messaging layer in Azure IoT Operations and supports both MQTT v3.1.1 and MQTT v5.
4747

48+
Once asset data is received, Azure IoT Operations uses *data flows* to process and route data to cloud endpoints or other edge components.
49+
4850
# [Cloud-based solution](#tab/cloud)
4951

5052
Azure IoT devices use the following primitives to exchange data with cloud services:
@@ -101,7 +103,9 @@ To learn more about implementing automatic reconnections to endpoints, see [Mana
101103

102104
Assets and asset endpoints in Azure IoT Operations are represented as custom resources in the Kubernetes cluster and as resources in Azure. You can use Azure role-based access control (Azure RBAC) to secure access to these resources. To learn more, see [Secure access to assets and asset endpoints](../iot-operations/discover-manage-assets/howto-secure-assets.md).
103105

104-
Asset endpoint profiles include user authentication information for accessing those endpoints. This authentication can be anonymous or username/password authentication where the values are stored as secrets in Azure Key Vault.
106+
Asset endpoint profiles include user authentication information for accessing those endpoints. This authentication can be anonymous or username/password authentication where the values are stored as secrets in Azure Key Vault. Access to the Azure key vault is configured with a user-assigned managed identity.
107+
108+
Any Azure IoT Operations components that require cloud connections, like data flow enpoints that send data to cloud resources, use a user-assigned managed identity. For more information, see [Enable secure settings in Azure IoT Operations](../iot-operations/deploy-iot-ops/howto-enable-secure-settings.md).
105109

106110
# [Cloud-based solution](#tab/cloud)
107111

@@ -132,7 +136,7 @@ To learn more about security in your IoT solution, see [Security architecture fo
132136

133137
# [Edge-based solution](#tab/edge)
134138

135-
Industrial IoT scenarios often use the [open platform communications unified architecture (OPC UA)](https://opcfoundation.org/about/opc-technologies/opc-ua/) industry standard open interface. To enable connectivity to the Azure cloud, use Azure IoT Operations. To learn more, see [What is Azure IoT Operations?](../iot-operations/get-started/overview-iot-operations.md).
139+
The MQTT broker underpins the messaging layer in IoT Operations and supports both MQTT v3.1.1 and MQTT v5.
136140

137141
# [Cloud-based solution](#tab/cloud)
138142

0 commit comments

Comments
 (0)