Merge pull request #300238 from dominicbetts/aio-telemetry-terminology

JillGrant615 · web-flow · commit 7b8c107bad42 · 2025-05-22T09:20:02.000-06:00
AIO: Terminology update to remove "telemetry"
diff --git a/articles/iot-operations/discover-manage-assets/concept-opcua-message-format.md b/articles/iot-operations/discover-manage-assets/concept-opcua-message-format.md
@@ -13,11 +13,11 @@ ms.service: azure-iot-operations
 
 # Connector for OPC UA message format
 
-The connector for OPC UA publishes messages from OPC UA servers to the MQTT broker in JSON format. Each message has a payload and a collection of properties that are a part of the MQTT user properties section. The payload contains the telemetry data from the OPC UA server, and the properties provide metadata about the message.
+The connector for OPC UA publishes messages from OPC UA servers to the MQTT broker in JSON format. Each message has a payload and a collection of properties that are a part of the MQTT user properties section. The payload contains the messages from the OPC UA server, and the properties provide metadata about the message.
 
 ## Payload
 
-The payload of an OPC UA message is a JSON object that contains the telemetry data from the OPC UA server. The following example shows the payload of a message from the sample thermostat asset used in the quickstarts. Use the following command to subscribe to messages in the `azure-iot-operations/data` topic:
+The payload of an OPC UA message is a JSON object that contains the messages from the OPC UA server. The following example shows the payload of a message from the sample thermostat asset used in the quickstarts. Use the following command to subscribe to messages in the `azure-iot-operations/data` topic:
 
 ```console
 mosquitto_sub --host aio-broker --port 18883 --topic "azure-iot-operations/data/#" -v --debug --cafile /var/run/certs/ca.crt -D CONNECT authentication-method 'K8S-SAT' -D CONNECT authentication-data $(cat /var/run/secrets/tokens/broker-sat)
diff --git a/articles/iot-operations/discover-manage-assets/howto-manage-assets-remotely.md b/articles/iot-operations/discover-manage-assets/howto-manage-assets-remotely.md
@@ -18,7 +18,7 @@ An _asset_ in Azure IoT Operations is a logical entity that you create to repres
 
 _OPC UA servers_ are software applications that communicate with assets. OPC UA servers expose _OPC UA tags_ that represent data points. OPC UA tags provide real-time or historical data about the status, performance, quality, or condition of assets.
 
-An _asset endpoint_ is a custom resource in your Kubernetes cluster that connects OPC UA servers to connector for OPC UA modules. This connection enables a connector for OPC UA to access an asset's data points. Without an asset endpoint, data can't flow from an OPC UA server to the connector for OPC UA and MQTT broker. After you configure the custom resources in your cluster, a connection is established to the downstream OPC UA server and the server forwards telemetry to the connector for OPC UA.
+An _asset endpoint_ is a custom resource in your Kubernetes cluster that connects OPC UA servers to connector for OPC UA modules. This connection enables a connector for OPC UA to access an asset's data points. Without an asset endpoint, data can't flow from an OPC UA server to the connector for OPC UA and MQTT broker. After you configure the custom resources in your cluster, a connection is established to the downstream OPC UA server and the server forwards messages such as sensor data to the connector for OPC UA.
 
 A _site_ is a collection of Azure IoT Operations instances. Sites typically group instances by physical location and make it easier for OT users to locate and manage assets. Your IT administrator creates sites and assigns Azure IoT Operations instances to them. To learn more, see [What is Azure Arc site manager (preview)?](/azure/azure-arc/site-manager/overview).
 
@@ -221,7 +221,7 @@ Now you can define the tags associated with the asset. To add OPC UA tags:
     | ns=3;s=FastUInt10 | Temperature | None |
     | ns=3;s=FastUInt100 | Humidity | None |
 
-1. Select **Manage default settings** to configure default telemetry settings for the asset. These settings apply to all the OPC UA tags that belong to the asset. You can override these settings for each tag that you add. Default telemetry settings include:
+1. Select **Manage default settings** to configure default settings for messages from the asset. These settings apply to all the OPC UA tags that belong to the asset. You can override these settings for each tag that you add. Default settings include:
 
     - **Sampling interval (milliseconds)**: The sampling interval indicates the fastest rate at which the OPC UA server should sample its underlying source for data changes.
     - **Publishing interval (milliseconds)**: The rate at which OPC UA server should publish data.
diff --git a/articles/iot-operations/discover-manage-assets/overview-akri.md b/articles/iot-operations/discover-manage-assets/overview-akri.md
@@ -55,7 +55,7 @@ The Akri services use standard Kubernetes primitives that let you apply your exi
 
 ## Discover OPC UA assets
 
-The Akri services and OPC UA connector are a turnkey solution that lets you discover assets connected to an OPC UA server and add the asset configurations into Azure Device Registry. The OPC UA connector discovers assets at the edge and Akri services maps them to assets in Azure Device Registry. The assets send telemetry to upstream brokers and components. The Akri services let you eliminate the time-consuming and error-prone process of manually configuring and onboarding the assets to your cluster and Azure Device Registry.
+The Akri services and OPC UA connector are a turnkey solution that lets you discover assets connected to an OPC UA server and add the asset configurations into Azure Device Registry. The OPC UA connector discovers assets at the edge and Akri services maps them to assets in Azure Device Registry. The assets send messages, such as sensor data, to upstream brokers and components. The Akri services let you eliminate the time-consuming and error-prone process of manually configuring and onboarding the assets to your cluster and Azure Device Registry.
 
 ### Features supported
 
diff --git a/articles/iot-operations/discover-manage-assets/overview-manage-assets.md b/articles/iot-operations/discover-manage-assets/overview-manage-assets.md
@@ -20,7 +20,7 @@ In Azure IoT Operations, a key task is to manage the assets that are part of you
 
 ## Understand assets
 
-Assets are a core element of an Azure IoT Operations solution. In Azure IoT Operations, an *asset* is a logical entity that you create to represent a real asset. An Azure IoT Operations asset can emit telemetry and events. You use these logical asset instances to reference the real assets in your industrial edge environment.
+Assets are a core element of an Azure IoT Operations solution. In Azure IoT Operations, an *asset* is a logical entity that you create to represent a real asset. An Azure IoT Operations asset can send messages such as sensor data and events. You use these logical asset instances to reference the real assets in your industrial edge environment.
 
 Assets connect to Azure IoT Operations instances through *asset endpoints*, which are the OPC UA servers that have southbound connections to one or more assets.
 
@@ -37,7 +37,7 @@ The following diagram shows the high-level architecture of Azure IoT Operations.
 - The **operations experience** is a web UI that lets you create and configure assets in your solution. The web UI simplifies the task of managing assets and is the recommended service to manage assets.
 - **Azure Device Registry** is a backend service that enables the cloud and edge management of assets. Device Registry projects assets defined in your edge environment as Azure resources in the cloud. It provides a single unified registry so that all apps and services that interact with your assets can connect to a single source. Device Registry also manages the synchronization between assets in the cloud and assets as custom resources in Kubernetes on the edge.
 - The schema registry is a service that lets you define and manage the schema for your assets. Data flows use schemas to deserialize and serialize messages.
-- The **connector for OPC UA** is a data ingress and protocol translation service that enables Azure IoT Operations to ingress data from your assets. The broker receives telemetry and events from your assets and publishes the data to topics in the MQTT broker. The broker is based on the widely used OPC UA standard.
+- The **connector for OPC UA** is a data ingress and protocol translation service that enables Azure IoT Operations to ingress data from your assets. The connector receives messages and events from your assets and publishes the data to topics in the MQTT broker. The connector is based on the widely used OPC UA standard.
 - The **media connector (preview)** is a service that makes media from media sources such as edge-attached cameras available to other Azure IoT Operations components.
 - The **connector for ONVIF (preview)** is a service that discovers and registers ONVIF assets such as cameras. The connector enables you to manage and control ONVIF assets such as cameras connected to your cluster.
 
diff --git a/articles/iot-operations/discover-manage-assets/overview-opcua-broker-certificates-management.md b/articles/iot-operations/discover-manage-assets/overview-opcua-broker-certificates-management.md
@@ -26,7 +26,7 @@ To learn more about OPC UA application security, see [Application Authentication
 
 ## Connector for OPC UA application instance certificate
 
-The connector for OPC UA is an OPC UA client application. The connector for OPC UA makes use of a single OPC UA application instance certificate for all the sessions it establishes to collect telemetry data from OPC UA servers. A default deployment of the connector for OPC UA uses [cert-manager](https://cert-manager.io/) to manage its application instance certificate:
+The connector for OPC UA is an OPC UA client application. The connector for OPC UA makes use of a single OPC UA application instance certificate for all the sessions it establishes to collect messages and data from OPC UA servers. A default deployment of the connector for OPC UA uses [cert-manager](https://cert-manager.io/) to manage its application instance certificate:
 
 - Cert-manager generates a self-signed OPC UA compatible certificate and stores it as Kubernetes native secret. The default name for this certificate is *aio-opc-opcuabroker-default-application-cert*.
 - The connector for OPC UA maps and uses this certificate for all the pods it uses to connect to OPC UA servers.
diff --git a/articles/iot-operations/discover-manage-assets/overview-opcua-broker.md b/articles/iot-operations/discover-manage-assets/overview-opcua-broker.md
@@ -1,6 +1,6 @@
 ---
 title: Connect industrial assets using the connector for OPC UA
-description: Use the connector for OPC UA to connect to OPC UA servers and exchange telemetry with a Kubernetes cluster.
+description: Use the connector for OPC UA to connect to OPC UA servers and exchange messages and data with the MQTT broker in a Kubernetes cluster.
 author: dominicbetts
 ms.author: dobett
 ms.subservice: azure-opcua-connector
@@ -24,7 +24,7 @@ The connector for OPC UA is a client application that runs as a middleware servi
 As part of Azure IoT Operations, the connector for OPC UA is a native Kubernetes application that:
 
 - Connects existing OPC UA servers and assets to a native Kubernetes cluster at the edge.
-- Publishes JSON-encoded telemetry data from OPC UA servers in OPC UA PubSub format, using a JSON payload. By using this standard format for data exchange, you can reduce the risk of future compatibility issues.
+- Publishes JSON-encoded messages from OPC UA servers in OPC UA PubSub format, using a JSON payload. By using this standard format for data exchange, you can reduce the risk of future compatibility issues.
 - Connects to Azure Arc-enabled services in the cloud.
 
 ### Other features
diff --git a/articles/iot-operations/get-started-end-to-end-sample/quickstart-configure.md b/articles/iot-operations/get-started-end-to-end-sample/quickstart-configure.md
@@ -19,7 +19,7 @@ In this quickstart, you configure the following resources in your Azure IoT Oper
 - An *asset* that represents the oven and defines the data points that the oven exposes.
 - A *data flow* that manipulates the messages from the simulated oven.
 
-An _asset_ is a physical device or logical entity that represents a device, a machine, a system, or a process. For example, a physical asset could be a pump, a motor, a tank, or a production line. A logical asset that you define can have properties, stream telemetry, or generate events.
+An _asset_ is a physical device or logical entity that represents a device, a machine, a system, or a process. For example, a physical asset could be a pump, a motor, a tank, or a production line. A logical asset that you define can have properties, stream messages such as sensor data, or generate events.
 
 _OPC UA servers_ are software applications that communicate with assets. _OPC UA tags_ are data points that OPC UA servers expose. OPC UA tags can provide real-time or historical data about the status, performance, quality, or condition of assets.
 
diff --git a/articles/iot-operations/overview-iot-operations.md b/articles/iot-operations/overview-iot-operations.md
@@ -110,9 +110,9 @@ Azure IoT Operations support max offline time for 72 hours. Degradation may occu
 
 [Data flows](connect-to-cloud/overview-dataflow.md) provide enhanced data transformation and data contextualization capabilities within Azure IoT Operations. Data flows can use schemas stored in the schema registry to deserialize and serialize messages.
 
-## Visualize and analyze telemetry
+## Visualize and analyze sensor data
 
-To visualize and analyze telemetry from your devices and assets, you can use cloud services such as:
+To visualize and analyze sensor data and messages from your devices and assets, you can use cloud services such as:
 
 * [Microsoft Fabric](/fabric/get-started/fabric-trial)
 * [Power BI](https://powerbi.microsoft.com/)
diff --git a/articles/iot-operations/toc.yml b/articles/iot-operations/toc.yml
@@ -259,8 +259,8 @@ items:
         - name: Add OPC UA assets to your cluster
           href: end-to-end-tutorials/tutorial-add-assets.md
           displayName: tutorial, e2e, end-to-end, asset, asset endpoint, OPC UA, connector, MQTT
-        - name: Upload data to the cloud
-          href: end-to-end-tutorials/tutorial-upload-telemetry-to-cloud.md
+        - name: Upload sensor data to the cloud
+          href: end-to-end-tutorials/tutorial-upload-messages-to-cloud.md
           displayName: tutorial, e2e, end-to-end, asset, asset endpoint, OPC UA, connector, MQTT
         - name: Get insights from your data
           href: end-to-end-tutorials/tutorial-get-insights.md
