Merge pull request #302679 from dominicbetts/release-aio-2507-terminology

ttorble · web-flow · commit 6d469156c478 · 2025-07-15T11:57:42.000+01:00
AIO 2507: Fix terminology
diff --git a/articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md b/articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md
@@ -20,7 +20,7 @@ In this article, we discuss Azure IoT Operations *deployments* and *instances*,
   * An Azure IoT Operations instance
   * Arc extensions
   * Custom locations
-  * Resources that you can configure in your Azure IoT Operations solution, like assets and asset endpoints.
+  * Resources that you can configure in your Azure IoT Operations solution, like assets and devices.
 
 * An Azure IoT Operations *instance* is the parent resource that bundles the suite of services that are defined in [What is Azure IoT Operations?](../overview-iot-operations.md) like MQTT broker, data flows, and connector for OPC UA.
 
diff --git a/articles/iot-operations/discover-manage-assets/concept-assets-devices.md b/articles/iot-operations/discover-manage-assets/concept-assets-devices.md
@@ -50,7 +50,7 @@ You can create, edit, and delete devices and assets by using the Azure IoT Opera
 
 Before you can create an asset, you need to define a device. A device is a profile that describes southbound edge connectivity information for one or more assets.
 
-Currently, the only southbound connectors available in Azure IoT Operations are the connector for OPC UA, the media connector (preview), the connector for ONVIF (preview), and the connector for HTTP/REST (preview). You can use the Azure IoT Operations SDKs to create custom connectors. Devices are configurations for a connector that enable it to connect to an asset. For example:
+Currently, the only southbound connectors available in Azure IoT Operations are the connector for OPC UA, the media connector (preview), the connector for ONVIF (preview), and the connector for REST/HTTP (preview). You can use the Azure IoT Operations SDKs to create custom connectors. Devices are configurations for a connector that enable it to connect to an asset. For example:
 
 - A device for OPC UA stores the information you need to connect to an OPC UA server.
 - A device for the media connector stores the information you need to connect to a media source.
diff --git a/articles/iot-operations/discover-manage-assets/howto-use-http-connector.md b/articles/iot-operations/discover-manage-assets/howto-use-http-connector.md
@@ -1,5 +1,5 @@
 ---
-title: How to use the HTTP connector (preview)
+title: How to use the connector for REST/HTTP (preview)
 description: Use the operations experience web UI or the Azure CLI to configure assets and devices for connections to HTTP endpoints.
 author: dominicbetts
 ms.author: dobett
@@ -10,15 +10,15 @@ ms.date: 10/07/2024
 #CustomerIntent: As an industrial edge IT or operations user, I want configure my Azure IoT Operations environment so that I can access data from HTTP/REST endpoints.
 ---
 
-# Configure the HTTP connector (preview)
+# Configure the connector for REST/HTTP (preview)
 
-In Azure IoT Operations, the HTTP connector (preview) enables access to data from HTTP/REST endpoints such as edge-attached cameras.
+In Azure IoT Operations, the connector for REST/HTTP (preview) enables access to data from HTTP/REST endpoints such as edge-attached cameras.
 
 [!INCLUDE [iot-operations-asset-definition](../includes/iot-operations-asset-definition.md)]
 
 [!INCLUDE [iot-operations-device-definition](../includes/iot-operations-device-definition.md)]
 
-This article explains how to use the HTTP connector to perform tasks such as:
+This article explains how to use the connector for REST/HTTP to perform tasks such as:
 
 - Define the devices that connect HTTP sources to your Azure IoT Operations instance.
 - Add assets, and define their streams, data points, and events to enable data flow from the HTTP source to the MQTT broker.
@@ -31,11 +31,11 @@ To configure devices and assets, you need a running instance of Azure IoT Operat
 
 [!INCLUDE [iot-operations-entra-id-setup](../includes/iot-operations-entra-id-setup.md)]
 
-Your IT administrator must have configured the HTTP connector template for your Azure IoT Operations instance in the Azure portal.
+Your IT administrator must have configured the connector for REST/HTTP template for your Azure IoT Operations instance in the Azure portal.
 
 A camera connected to your network and accessible from your Azure IoT Operations cluster. The camera must support the Real Time Streaming Protocol for video streaming. You also need the camera's username and password to authenticate with it.
 
-## Deploy the HTTP connector
+## Deploy the connector for REST/HTTP
 
 <!--TODO: Probably not necessary now we have the connector templates? -->
 
@@ -46,9 +46,9 @@ A camera connected to your network and accessible from your Azure IoT Operations
 
 ## Create a device
 
-To configure the HTTP connector, first create a device that defines the connection to the HTTP source. The device includes the URL of the HTTP source, the type of HTTP source, and any credentials you need to access the HTTP source.
+To configure the connector for REST/HTTP, first create a device that defines the connection to the HTTP source. The device includes the URL of the HTTP source, the type of HTTP source, and any credentials you need to access the HTTP source.
 
-If your HTTP endpoint requires authentication, create a secret in your Kubernetes cluster that stores the endpoint's username and password. The HTTP connector uses this secret to authenticate with the endpoint:
+If your HTTP endpoint requires authentication, create a secret in your Kubernetes cluster that stores the endpoint's username and password. The connector for REST/HTTP uses this secret to authenticate with the endpoint:
 
 1. Create a YAML file called _contoso-http-secrets.yaml_ with the following content. Replace the placeholders with your camera's username and password encoded in base64:
 
@@ -206,7 +206,7 @@ authentication: {
 
 ## Asset configuration
 
-When you configure an asset, the `datasets.DataPoints` parameter specifies the action the HTTP connector takes on the asset. An HTTP asset supports the following task types:
+When you configure an asset, the `datasets.DataPoints` parameter specifies the action the connector for REST/HTTP takes on the asset. An HTTP asset supports the following task types:
 
 | Task type | Description |
 |-----------|-------------|
@@ -216,7 +216,7 @@ When you configure an asset, the `datasets.DataPoints` parameter specifies the a
 The following examples show how to deploy assets for each task type.
 
 > [!TIP]
-> The HTTP pods aren't created in Kubernetes until you deploy an asset that uses the HTTP connector. If you try to run the `kubectl get pods` command before deploying an asset, you see no HTTP pods.
+> The HTTP pods aren't created in Kubernetes until you deploy an asset that uses the connector for REST/HTTP. If you try to run the `kubectl get pods` command before deploying an asset, you see no HTTP pods.
 
 ## Snapshot to MQTT
 
diff --git a/articles/iot-operations/discover-manage-assets/overview-akri.md b/articles/iot-operations/discover-manage-assets/overview-akri.md
@@ -62,7 +62,7 @@ The following table shows the connectors currently available in Azure IoT Operat
 | Connector for OPC UA   |       Yes        |      Yes        |
 | Connector for ONVIF    |        No        |      Yes        |
 | Media connector        |       Yes        |       No        |
-| HTTP connector         |        No        |       No        |
+| Connector for REST/HTTP        |        No        |       No        |
 
 The media connector supports discovery of cameras and other media devices that use the ONVIF protocol.
 
diff --git a/articles/iot-operations/discover-manage-assets/overview-http-connector.md b/articles/iot-operations/discover-manage-assets/overview-http-connector.md
@@ -1,34 +1,34 @@
 ---
-title: Connect HTTP sources using the HTTP connector (preview)
-description: The HTTP connector (preview) in Azure IoT Operations makes HTTP from HTTP sources such as IP cameras available to other Azure IoT Operations components.
+title: Connect HTTP sources using the connector for REST/HTTP (preview)
+description: The connector for REST/HTTP (preview) in Azure IoT Operations makes HTTP from HTTP sources such as IP cameras available to other Azure IoT Operations components.
 author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot-operations
 ms.topic: overview
 ms.date: 11/12/2024
 
-#CustomerIntent: As an industrial edge IT or operations user, I want to understand what the HTTP connector is so that I can determine whether I can use it in my industrial IoT solution.
+#CustomerIntent: As an industrial edge IT or operations user, I want to understand what the connector for REST/HTTP is so that I can determine whether I can use it in my industrial IoT solution.
 ---
 
-# What is the Azure IoT Operations HTTP connector (preview)?
+# What is the Azure IoT Operations connector for REST/HTTP (preview)?
 
-This article introduces the HTTP connector (preview) in Azure IoT Operations. The HTTP connector calls REST endpoints to retrieve data to share with other Azure IoT Operations components. The HTTP connector is secure and performant.
+This article introduces the connector for REST/HTTP (preview) in Azure IoT Operations. The connector for REST/HTTP calls REST endpoints to retrieve data to share with other Azure IoT Operations components. The connector for REST/HTTP is secure and performant.
 
 ## HTTP source types
 
-The HTTP connector can connect to various sources.
+The connector for REST/HTTP can connect to various sources.
 
 <!-- TODO: Add details here when we have more information -->
 
 ## Example uses
 
-Example uses of the HTTP connector include calling REST APIs to retrieve data from industrial devices such as cameras, sensors, and other devices that expose data over HTTP.
+Example uses of the connector for REST/HTTP include calling REST APIs to retrieve data from industrial devices such as cameras, sensors, and other devices that expose data over HTTP.
 
 <!-- TODO: Add details here when we have more information -->
 
 ## How does it relate to Azure IoT Operations?
 
-The HTTP connector is part of Azure IoT Operations. The connector deploys to an Arc-enabled Kubernetes cluster on the edge as part of an Azure IoT Operations deployment. The connector interacts with other Azure IoT Operations components, such as:
+The connector for REST/HTTP is part of Azure IoT Operations. The connector deploys to an Arc-enabled Kubernetes cluster on the edge as part of an Azure IoT Operations deployment. The connector interacts with other Azure IoT Operations components, such as:
 
 - [Assets and devices](./concept-assets-devices.md)
 - [The MQTT broker](../connect-to-cloud/overview-dataflow.md)
@@ -37,4 +37,4 @@ The HTTP connector is part of Azure IoT Operations. The connector deploys to an
 ## Next step
 
 > [!div class="nextstepaction"]
-> [How to use the HTTP connector](howto-use-http-connector.md)
+> [How to use the connector for REST/HTTP](howto-use-http-connector.md)
diff --git a/articles/iot-operations/discover-manage-assets/overview-manage-assets.md b/articles/iot-operations/discover-manage-assets/overview-manage-assets.md
@@ -78,7 +78,7 @@ Azure IoT Operations includes several services that help you manage devices and
 - The **connector for OPC UA** is a data ingress and protocol translation service that enables Azure IoT Operations to ingress data from OPC UA servers. A key requirement in industrial environments is for a common standard or protocol for machine-to-machine and machine-to-cloud data exchange. [OPC UA](https://opcfoundation.org/about/opc-technologies/opc-ua/) is a specification for a platform independent service-oriented architecture that enables data exchange in industrial environments. The connector receives messages and events from your assets and publishes the data to topics in the MQTT broker.
 - 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.
-- The **REST/HTTP connector** is a service that lets you connect to REST/HTTP endpoints and publish data to the MQTT broker.
+- The **connector for REST/HTTP** is a service that lets you connect to REST/HTTP endpoints and publish data to the MQTT broker.
 - **Custom connectors** are services that you can create to connect to other data sources and publish data to the MQTT broker. Use the Azure IoT Operations SDKS to create custom connectors that meet your specific requirements.
 - **Akri services** are a set of services that enable the automatic discovery of physical assets and devices in your environment. Akri services can help you create and configure assets and devices in operations experience. To learn more, see [What is asset discovery (preview)?](overview-akri.md).
 
@@ -120,9 +120,9 @@ And the final screenshot shows the same thermostat asset as a Kubernetes custom
 
 ### Automatic asset discovery
 
-Akri services let you deploy and configure connectivity protocols, such as OPC UA and ONVIF, at the edge. Akri services use the asset and asset endpoint resources in Azure Device Registry to model the different device and protocol connections in your environment.
+Akri services let you deploy and configure connectivity protocols, such as OPC UA and ONVIF, at the edge. Akri services use the asset and device resources in Azure Device Registry to model the different device and protocol connections in your environment.
 
-Akri services simplify the process of creating assets by automatically onboarding assets with pre-configured datasets and asset endpoints generated by the connectors to represent capabilities and devices on the network.
+Akri services simplify the process of creating assets by automatically onboarding assets with pre-configured datasets and device endpoints generated by the connectors to represent capabilities and devices on the network.
 
 Currently:
 
diff --git a/articles/iot-operations/toc.yml b/articles/iot-operations/toc.yml
@@ -115,10 +115,10 @@ items:
           displayName: camera, PTZ, pan, tilt, zoom, DiscoveredAsset, DiscoveredAssetEndpointProfile, media, events, stream, southbound
       - name: Connect to HTTP endpoints
         items:
-        - name: Understand the HTTP connector
+        - name: Understand the connector for REST/HTTP
           href: discover-manage-assets/overview-http-connector.md
           displayName: HTTP, REST, API, southbound
-        - name: Use the HTTP connector
+        - name: Use the connector for REST/HTTP
           href: discover-manage-assets/howto-use-http-connector.md
           displayName: HTTP, REST, API, southbound
     - name: Manage MQTT broker
diff --git a/articles/iot-operations/troubleshoot/tips-tools.md b/articles/iot-operations/troubleshoot/tips-tools.md
@@ -208,7 +208,7 @@ To view custom resource types other that pods in the cluster:
     > [!TIP]
     > To search for a custom resource type by name, type **/** and then start typing the name of the type you're looking for.
 
-1. Select a custom resource and choose one of the available operations. For example, you can view the YAML definition os an asset endpoint profile by selecting it and pressing **y**. For some resources, you can edit the configuration.
+1. Select a custom resource and choose one of the available operations. For example, you can view the YAML definition of a device endpoint profile by selecting it and pressing **y**. For some resources, you can edit the configuration.
 
 The following table describes some of the custom resource types you might work with in Azure IoT Operations:
 
