Glossary for Azure IoT Operations Preview - enabled by Azure Arc
Important
Azure IoT Operations Preview – enabled by Azure Arc is currently in PREVIEW. You shouldn't use this preview software in production environments.
See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
This article lists and defines some of the key terms associated with Azure IoT Operations. The article includes usage guidance to help you use the terms correctly if you're talking or writing about Azure IoT Operations.
Service and component names
This section lists the names of the services and components that make up Azure IoT Operations.
Azure IoT Operations Preview - enabled by Azure Arc
A unified data plane for the edge. It's a collection of modular, scalable, and highly available data services that run on Azure Arc-enabled edge Kubernetes clusters. It enables data capture from various different systems and integrates with data modeling applications such as Microsoft Fabric to help organizations deploy the industrial metaverse.
On first mention in an article, use Azure IoT Operations Preview - enabled by Azure Arc. On subsequent mentions, you can use Azure IoT Operations. Never use an acronym.
Azure IoT Akri Preview
This component helps you discover and connect to devices and assets.
On first mention in an article, use Azure IoT Akri Preview. On subsequent mentions, you can use Azure IoT Akri. Never use an acronym.
Azure IoT Data Processor Preview
This component lets you aggregate, enrich, normalize, and filter the data from your devices and assets. Data Processor is a pipeline-based data processing engine that lets you process data at the edge before you send it to the other services either at the edge or in the cloud
On first mention in an article, use Azure IoT Data Processor Preview. On subsequent mentions, you can use Data Processor. Never use an acronym.
Azure IoT Layered Network Management Preview
This component lets you secure communication between devices and the cloud through isolated network environments based on the ISA-95/Purdue Network architecture.
On first mention in an article, use Azure IoT Layered Network Management Preview. On subsequent mentions, you can use Layered Network Management. Never use an acronym.
Azure IoT MQ Preview
An MQTT broker that runs on the edge. The component lets you publish and subscribe to MQTT topics. You can use MQ to build event-driven architectures that connect your devices and assets to the cloud.
On first mention in an article, use Azure IoT MQ Preview. On subsequent mentions, you can use MQ.
Azure IoT OPC UA Broker Preview
This component manages the connection to OPC UA servers and other leaf devices. The OPC UA Broker component publishes data from the OPC UA servers and the devices discovered by Azure IoT Akri to Azure IoT MQ topics.
On first mention in an article, use Azure IoT OPC UA Broker Preview. On subsequent mentions, you can use OPC UA Broker. Never use an acronym.
Azure IoT Orchestrator Preview
This component manages the deployment, configuration, and update of the Azure IoT Operations components that run on your Arc-enabled Kubernetes cluster.
On first mention in an article, use Azure IoT Orchestrator Preview. On subsequent mentions, you can use Orchestrator. Never use an acronym.
Azure IoT Operations (preview) portal
This web UI provides a unified experience for operational technologists to manage assets and Data Processor pipelines in an Azure IoT Operations deployment.
On first mention in an article, use Azure IoT Operations (preview) portal. On subsequent mentions, you can use Operations portal. Never use an acronym.
Azure Device Registry Preview
This component provides a single centralized registry for devices and assets that are projected as Azure resources.
On first mention in an article, use Azure Device Registry Preview. On subsequent mentions, you can use Device Registry. Never use an acronym.
Related content
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for