Update Akri overview

dominicbetts · dominicbetts · commit f43cf9d5d219 · 2024-05-17T12:08:10.000+01:00
diff --git a/articles/iot-operations/manage-devices-assets/media/overview-akri/akri-logo.png b/articles/iot-operations/manage-devices-assets/media/overview-akri/akri-logo.png
diff --git a/articles/iot-operations/manage-devices-assets/overview-akri.md b/articles/iot-operations/manage-devices-assets/overview-akri.md
@@ -4,107 +4,105 @@ description: Understand how Azure IoT Akri enables you to discover devices and a
 author: dominicbetts
 ms.author: dobett
 ms.subservice: akri
-ms.topic: concept-article
+ms.topic: overview
 ms.custom:
   - ignite-2023
-ms.date: 10/26/2023
+ms.date: 05/13/2024
 
 # CustomerIntent: As an industrial edge IT or operations user, I want to to understand how Azure IoT Akri
 # enables me to discover devices and assets at the edge, and expose them as resources on a Kubernetes cluster.
 ---
 
-# Detect assets with Azure IoT Akri Preview
+# What is Azure IoT Akri Preview?
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-Azure IoT Akri Preview is a hosting framework for discovery handlers that enables you to detect devices and assets at the edge, and expose them as resources on a Kubernetes cluster. By using Azure IoT Akri, you can simplify the process of projecting leaf devices (OPC UA devices, cameras, IoT sensors, and peripherals) into your cluster.  Azure Iot Akri projects leaf devices into a cluster by using the devices' own protocols. For administrators who attach devices to or remove them from the cluster, this capability reduces the level of coordination and manual configuration. The hosting framework is also extensible. You can use it as shipped, or you can add custom discovery and provisioning by adding protocol handlers, brokers and behaviors. Azure IoT Akri is a Microsoft-managed commercial version of [Akri](https://docs.akri.sh/), an open source Cloud Native Computing Foundation (CNCF) project.  
+Azure IoT Akri Preview is a host for discovery handlers that enable you to detect devices and assets at the edge, and expose them as resources on a Kubernetes cluster. Use Azure IoT Akri to simplify the process of projecting leaf devices such as OPC UA devices, cameras, IoT sensors, and peripherals into your cluster. Azure Iot Akri uses the devices' own protocols to project leaf devices into your cluster. For administrators who attach or remove devices from a cluster, this capability reduces the amount of coordination and manual configuration required.
 
-:::image type="content" source="media/overview-akri/akri-logo.png" alt-text="Logo for the Akri project." border="false":::
+Azure IoT Akri is also extensible. You can use it as shipped, or you can add custom discovery and provisioning capabilities by adding protocol handlers, brokers, and behaviors.
 
-## The challenge of integrating IoT leaf devices at the edge
+Azure IoT Akri is a Microsoft-managed commercial version of [Akri](https://docs.akri.sh/), an open-source Cloud Native Computing Foundation (CNCF) project.
 
-It's common to run Kubernetes directly on infrastructure. But to integrate non-Kubernetes IoT leaf devices into a Kubernetes cluster requires a unique solution. 
+## Leaf device integration challenges
 
-IoT leaf devices present the following challenges:
-- Contain hardware that's too small, too old, or too locked-down to run Kubernetes
-- Use various protocols and different topologies
-- Have intermittent downtime and availability
-- Require different methods of authentication and storing secrets
+It's common to run Kubernetes directly on infrastructure. But to integrate non-Kubernetes IoT leaf devices into a Kubernetes cluster requires a unique solution.
 
-## What Azure IoT Akri Preview does
-To address the challenge of integrating non-Kubernetes IoT leaf devices, Azure IoT Akri provides several core capabilities.
+IoT leaf devices present the following challenges, They:
+
+- Contain hardware that's too small, too old, or too locked-down to run Kubernetes.
+- Use various protocols and different topologies.
+- Have intermittent downtime and availability.
+- Require different methods of authentication and secret storage.
+
+## Core capabilities
+
+To address the challenge of integrating non-Kubernetes IoT leaf devices, Azure IoT Akri has several core capabilities:
 
 ### Device discovery
-Azure IoT Akri deployments can include fixed-network discovery handlers. Discovery handlers enable assets from known network endpoints to find leaf devices as they appear on device interfaces or local subnets. Examples of network endpoints include OPC UA servers at a fixed IP address (without network scanning), and network scanning discovery handlers.
+
+Azure IoT Akri deployments can include fixed-network discovery handlers. Discovery handlers enable assets from known network endpoints to find leaf devices as they appear on device interfaces or local subnets. Examples of network endpoints include OPC UA servers at a fixed IP address, and network scanning discovery handlers.
 
 ### Dynamic provisioning
-Another capability of Azure IoT Akri is dynamic device provisioning.  
 
-With Azure IoT Akri, you can dynamically provision devices like the following examples:
+Another capability of Azure IoT Akri is dynamic device provisioning.  
 
-- USB cameras that you want to use on your cluster
-- IP cameras that you don't want to look up IP addresses for
-- OPC UA servers simulated on your host machine to test Kubernetes workloads
+With Azure IoT Akri, you can dynamically provision devices such as:
 
+- USB cameras to use in your cluster.
+- IP cameras that you don't want to look up IP addresses for.
+- OPC UA server simulations running on your host machine that you use to test Kubernetes workloads.
 
 ### Compatibility with Kubernetes
-Azure IoT Akri employs standard Kubernetes primitives. The use of Kubernetes primitives lets users apply their expertise creating applications or managing infrastructure. Small devices connected in an Akri-configured site can appear as Kubernetes resources, just like memory or CPUs. The Azure IoT Akri controller enables the cluster operator to start brokers, jobs or other workloads for individual connected devices or groups of devices. These Azure IoT Akri device configurations and properties remain in the cluster so that if there's node failure, other nodes can pick up any lost work.
 
-## Using Azure IoT Akri Preview to discover OPC UA assets
-Azure IoT Akri is a turnkey solution that enables you to discover and create assets connected to an OPC UA server at the edge. Azure IoT Akri discovers devices at the edge and maps them to assets. The assets send telemetry to upstream connectors. By using Azure IoT Akri, you eliminate the painstaking process of manually configuring from the cloud and onboarding the assets to your cluster.  
+Azure IoT Akri uses standard Kubernetes primitives that let you apply your existing expertise and knowledge. Small devices connected to an Akri-configured cluster can appear as Kubernetes resources, just like memory or CPUs. The Azure IoT Akri controller enables the cluster operator to start brokers, jobs, or other workloads for individual connected devices or groups of devices. These Azure IoT Akri device configurations and properties remain in the cluster so that if there's node failure, other nodes can pick up any lost work.
 
-The Azure IoT Operations Preview documentation provides guidance for detecting assets at the edge, by using the Azure IoT Operations OPC UA discovery handler and broker. You can use these components to process your OPC UA data and telemetry. 
+## Discover OPC UA assets
 
-## Features
-This section highlights the key capabilities and supported features in Azure IoT Akri.
+Azure IoT Akri is a turnkey solution that lets you discover and create assets connected to an OPC UA server at the edge. Azure IoT Akri discovers devices at the edge and maps them to assets in your cluster. The assets send telemetry to upstream connectors. Azure IoT Akri lets you eliminate the painstaking process of manually configuring and onboarding the assets to your cluster.
 
-### Key capabilities
-- **Dynamic discovery**. Protocol representations of devices can come and go, without static configurations in brokers or customer containers. 
-  - **Device network scanning**.  This capability is especially useful for finding devices in smaller, remote locations. For example, a replacement camera in a store. The protocols that currently support device network scanning are ONVIF and OPC UA localhost.
-  - **Device connecting**. This capability is often used in larger industrial scenarios. For example, factory environments where the network is typically static and network scanning isn't permitted. The protocols that currently support device connecting are udev and OPC UA local discovery servers.
-  - **Device attach**: Azure IoT Akri also supports implementing custom logic for mapping or connecting devices and there are [open-source templates](https://docs.akri.sh/development/handler-development) to accelerate customization.
+## Key features
 
-- **Optimal scheduling**. Azure IoT Akri can schedule devices on specified nodes with minimal latency, because the service knows where a particular device is located on the K8s cluster. Optimal scheduling applies to directly connected devices, or in scenarios where only specific nodes can access the devices.
+The following list shows the key features of Azure IoT Akri Preview:
 
-- **Optimal configuration**. Azure IoT Akri uses the capacity of the node to drive cardinality of the brokers for the discovered devices.
+- **Dynamic discovery**. Protocol representations of devices can come and go, without static configurations in brokers or customer containers. To discover devices, Azure IoT Akri uses the following methods:
 
-- **Secure credential management**. Azure IoT Akri facilitates secure access to assets and devices by integrating with services for secure distribution of credential material to brokers.
+  - **Device network scanning**. This capability is useful for finding devices in smaller, remote locations such as a replacement camera in a store. The ONVIF and OPC UA localhost protocols currently support device network scanning discovery.
+  - **Device connecting**. This capability is typically used in larger industrial scenarios such as factory environments where the network is typically static and network scanning isn't permitted. The `udev` and OPC UA local discovery server protocols currently support device connecting discovery.
+  - **Device attach**. Azure IoT Akri also supports custom logic for mapping or connecting devices. There are [open-source templates](https://docs.akri.sh/development/handler-development) to accelerate customization.
 
-### Features supported
-The following features are supported in Azure IoT Akri Preview:
+- **Optimal scheduling**. Azure IoT Akri can schedule devices on specified nodes with minimal latency because it knows where particular devices are located on the Kubernetes cluster. Optimal scheduling applies to directly connected devices, or in scenarios where only specific nodes can access the devices.
+
+- **Optimal configuration**. Azure IoT Akri uses the capacity of the node to drive cardinality of the brokers for the discovered devices.
 
-| [CNCF Akri Features](https://docs.akri.sh/)                                                    | Meaning   | Symbol   |
-| ---------------------------------------------------------------------------------------------- | --------- | -------: |
-| Dynamic discovery of devices at the edge (supported protocols: OPC UA, ONVIF, udev)            | Supported |   ✅    |
-| Schedule devices with minimal latency using Akri's information on node affinity on the cluster | Supported |   ✅    |
-| View Akri metrics/logs locally through Prometheus and Grafana                                  | Supported |   ✅    |
-| Secrets/credentials management                                                                 | Supported |   ✅    |
-| M:N device to broker ratio through configuration-level resource support                        | Supported |   ✅    |
-| Observability on Akri deployments through Prometheus and Grafana dashboards                    | Supported |   ✅    |
+- **Secure credential management**. Azure IoT Akri facilitates secure access to assets and devices by integrating with services in the cluster that enable secure distribution of credential material to brokers.
 
+### Features supported
 
-| Azure IoT Akri features  | Meaning | Symbol | 
-|---------|---------|---------:|
-| Installation through Azure IoT Akri Arc cluster extension                                         | Supported   |   ✅     |
-| Deployment through the orchestration service                                                      | Supported   |   ✅     |
-| Onboard devices as custom resources to an edge cluster                                            | Supported   |   ✅     |
-| View Azure IoT Akri metrics and logs through Azure Monitor	                                      | Unsupported |   ❌     |
-| Azure IoT Akri configuration via Azure IoT Operations (preview) portal                            | Unsupported |   ❌     |
-| Azure IoT Akri detects and creates assets that can be ingested into the Azure Device Registry     | Unsupported |   ❌     |
-| ISVs can build and sell custom protocol handlers for Azure IoT Operations solutions               | Unsupported |   ❌     |
+Azure IoT Akri Preview supports the following features:
 
+| [CNCF Akri Features](https://docs.akri.sh/) | Supported |
+| ------------------------------------------- | :-------: |
+| Dynamic discovery of devices at the edge (supported protocols: OPC UA, ONVIF, udev)              |   ✅    |
+| Schedule devices with minimal latency using Akri's information on node affinity on the cluster  |   ✅    |
+| View Akri metrics and logs locally through Prometheus and Grafana                       |   ✅    |
+| Secrets and credentials management  |   ✅    |
+| M:N device to broker ratio through configuration-level resource support                       |   ✅    |
+| Observability on Akri deployments through Prometheus and Grafana dashboards                    |   ✅    |
 
+| Azure IoT Akri features  | Supported |
+|--------------------------|:---------:|
+| Installation through Azure IoT Akri Arc cluster extension |   ✅     |
+| Deployment through the orchestration service              |   ✅     |
+| Onboard devices as custom resources to an edge cluster    |   ✅     |
+| View Azure IoT Akri metrics and logs through Azure Monitor |   ❌     |
+| Azure IoT Akri configuration by using the Azure IoT Operations (preview) portal |   ❌     |
+| Azure IoT Akri detects and creates assets that can be ingested into the Azure Device Registry  |   ❌     |
+| ISVs can build and sell custom protocol handlers for Azure IoT Operations solutions  |   ❌     |
 
-## Open-Source Akri Resources
+## Related content
 
-To learn more about the CNCF Akri, see the following open source resources.  
+To learn more about the open-source CNCF Akri, see the following resources:
 
 - [Documentation](https://docs.akri.sh/)
 - [OPC UA Sample on AKS Edge Essentials](/azure/aks/hybrid/aks-edge-how-to-akri-opc-ua)
-- [ONVIF Sample on AKS Edge Essentials](/azure/aks/hybrid/aks-edge-how-to-akri-onvif)
-
-## Next step
-In this article, you learned how Azure IoT Akri works and how it enables you to detect devices and add assets at the edge.  Here's the suggested next step: 
-
-> [!div class="nextstepaction"]
-> [Discover assets using Azure IoT Akri](howto-autodetect-opcua-assets-using-akri.md)
+- [ONVIF Sample on AKS Microsoft Edge Essentials](/azure/aks/hybrid/aks-edge-how-to-akri-onvif)
diff --git a/articles/iot-operations/monitor/howto-configure-observability-manual.md b/articles/iot-operations/monitor/howto-configure-observability-manual.md
@@ -27,7 +27,7 @@ az provider register -n "Microsoft.AlertsManagement"
 ```
 
 ## Install Azure Monitor managed service for Prometheus
-Azure Monitor managed service for Prometheus is a component of Azure Monitor Metrics. This managed service provides flexibility in the types of metric data that you can collect and analyze with Azure Monitor. Prometheus metrics share some features with platform and custom metrics. Prometheus metrics also use some different features to better support open source tools such as PromQL and Grafana.
+Azure Monitor managed service for Prometheus is a component of Azure Monitor Metrics. This managed service provides flexibility in the types of metric data that you can collect and analyze with Azure Monitor. Prometheus metrics share some features with platform and custom metrics. Prometheus metrics also use some different features to better support open-source tools such as PromQL and Grafana.
 
 Azure Monitor managed service for Prometheus allows you to collect and analyze metrics at scale using a Prometheus-compatible monitoring solution. This fully managed service is based on the Prometheus project from the Cloud Native Computing Foundation (CNCF). The service allows you to use the Prometheus query language (PromQL) to analyze and alert on the performance of monitored infrastructure and workloads, without having to operate the underlying infrastructure.
 
diff --git a/articles/iot-operations/process-data/concept-jq.md b/articles/iot-operations/process-data/concept-jq.md
@@ -16,7 +16,7 @@ ms.date: 09/07/2023
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-[jq](https://jqlang.github.io/jq/) is an open source JSON processor that you can use restructure and format structured payloads in Azure IoT Data Processor Preview) pipelines:
+[jq](https://jqlang.github.io/jq/) is an open-source JSON processor that you can use restructure and format structured payloads in Azure IoT Data Processor Preview) pipelines:
 
 - The [filter](howto-configure-filter-stage.md) pipeline stage uses jq to enable flexible filter queries.
 - The [transform](howto-configure-transform-stage.md) pipeline stage uses jq to enable data transformation.
diff --git a/articles/iot-operations/view-analyze-data/tutorial-anomaly-detection.md b/articles/iot-operations/view-analyze-data/tutorial-anomaly-detection.md
@@ -261,9 +261,9 @@ To create the ERP reference data pipeline that ingests the data from the HTTP en
 
 You now have a pipeline that queries an HTTP endpoint every 30 minutes for ERP reference data to store in a reference dataset.
 
-### OPCUA anomaly detection pipeline
+### OPC UA anomaly detection pipeline
 
-Now you can build the OPCUA anomaly detection pipeline that:
+Now you can build the OPC UA anomaly detection pipeline that:
 
 - Ingests the sensor measurements from the production line assets.
 - Detects any anomalies in the measurement data.
diff --git a/articles/iot/iot-overview-device-connectivity.md b/articles/iot/iot-overview-device-connectivity.md
@@ -1,6 +1,6 @@
 ---
 title: Device infrastructure and connectivity
-description: An overview of device infrastructure and connectivity in an Azure IoT solution, including gateways and protocols such as MQTT and OPC-UA.
+description: An overview of device infrastructure and connectivity in an Azure IoT solution, including gateways and protocols such as MQTT and OPC UA.
 ms.service: iot
 services: iot
 author: dominicbetts
diff --git a/articles/iot/tutorial-iot-industrial-solution-architecture.md b/articles/iot/tutorial-iot-industrial-solution-architecture.md
@@ -45,7 +45,7 @@ Here are the components involved in this solution:
 
 | Component | Description |
 | --- | --- |
-| Industrial Assets | A set of simulated OPC-UA enabled production lines hosted in Docker containers |
+| Industrial Assets | A set of simulated OPC UA enabled production lines hosted in Docker containers |
 | [Azure IoT Operations](/azure/iot-operations/get-started/overview-iot-operations) | Azure IoT Operations is a unified data plane for the edge. It includes a set of modular, scalable, and highly available data services that run on Azure Arc-enabled edge Kubernetes clusters. |
 | [Data Gateway](/azure/logic-apps/logic-apps-gateway-install#how-the-gateway-works) | This gateway connects your on-premises data sources (like SAP) to Azure Logic Apps in the cloud. |
 | [Azure Kubernetes Services Edge Essentials](/azure/aks/hybrid/aks-edge-overview) | This Kubernetes implementation runs at the Edge. It provides single- and multi-node Kubernetes clusters for a fault-tolerant Edge configuration. Both K3S and K8S are supported. It runs on embedded or PC-class hardware, like an industrial gateway. |
