Merge pull request #266715 from asergaz/asergaz-aio-preview-fix

Fixing Preview mentions

Author: v-dirichards

articles/iot-operations/connect-to-cloud/howto-configure-data-lake.md

@@ -1,6 +1,5 @@
 ---
 title: Send data from Azure IoT MQ to Data Lake Storage
-titleSuffix: Azure IoT MQ
 description: Learn how to send data from Azure IoT MQ to Data Lake Storage.
 author: PatAltimore
 ms.subservice: mq
@@ -13,11 +12,11 @@ ms.date: 11/15/2023
 #CustomerIntent: As an operator, I want to understand how to configure Azure IoT MQ so that I can send data from Azure IoT MQ to Data Lake Storage.
 ---
 
-# Send data from Azure IoT MQ to Data Lake Storage
+# Send data from Azure IoT MQ Preview to Data Lake Storage
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-You can use the data lake connector to send data from Azure IoT MQ broker to a data lake, like Azure Data Lake Storage Gen2 (ADLSv2) and Microsoft Fabric OneLake. The connector subscribes to MQTT topics and ingests the messages into Delta tables in the Data Lake Storage account.
+You can use the data lake connector to send data from Azure IoT MQ Preview broker to a data lake, like Azure Data Lake Storage Gen2 (ADLSv2) and Microsoft Fabric OneLake. The connector subscribes to MQTT topics and ingests the messages into Delta tables in the Data Lake Storage account.
 
 ## What's supported
 
@@ -44,7 +43,7 @@ You can use the data lake connector to send data from Azure IoT MQ broker to a d
     - Azure Data Lake Storage Gen2 quickstart:
         - [Create a storage account to use with Azure Data Lake Storage Gen2](/azure/storage/blobs/create-data-lake-storage-account).
 
-- An IoT MQ MQTT broker. For more information on how to deploy an IoT MQ MQTT broker, see [Quickstart: Deploy Azure IoT Operations to an Arc-enabled Kubernetes cluster](../get-started/quickstart-deploy.md).
+- An IoT MQ MQTT broker. For more information on how to deploy an IoT MQ MQTT broker, see [Quickstart: Deploy Azure IoT Operations Preview to an Arc-enabled Kubernetes cluster](../get-started/quickstart-deploy.md).
 
 ## Configure the data lake connector to send data to Microsoft Fabric OneLake using managed identity
 
@@ -349,4 +348,4 @@ Like MQTT bridge, the data lake connector acts as a client to the IoT MQ MQTT br
 
 ## Related content
 
-[Publish and subscribe MQTT messages using Azure IoT MQ](../manage-mqtt-connectivity/overview-iot-mq.md)
+[Publish and subscribe MQTT messages using Azure IoT MQ Preview](../manage-mqtt-connectivity/overview-iot-mq.md)

articles/iot-operations/connect-to-cloud/howto-configure-destination-data-explorer.md

@@ -12,11 +12,11 @@ ms.date: 01/10/2024
 #CustomerIntent: As an operator, I want to send data from a pipeline to Azure Data Explorer so that I can store and analyze my data in the cloud.
 ---
 
-# Send data to Azure Data Explorer from a Data Processor pipeline
+# Send data to Azure Data Explorer from an Azure IoT Data Processor Preview pipeline
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-Use the _Azure Data Explorer_ destination to write data to a table in Azure Data Explorer from an [Azure IoT Data Processor (preview) pipeline](../process-data/overview-data-processor.md). The destination stage batches messages before it sends them to Azure Data Explorer.
+Use the _Azure Data Explorer_ destination to write data to a table in Azure Data Explorer from an [Azure IoT Data Processor Preview pipeline](../process-data/overview-data-processor.md). The destination stage batches messages before it sends them to Azure Data Explorer.
 
 ## Prerequisites
 
@@ -50,7 +50,7 @@ For the destination stage to connect to Azure Data Explorer, it needs access to
     az keyvault secret set --vault-name <your-key-vault-name> --name AccessADXSecret --value <client-secret>
     ```
 
-1. Add the secret reference to your Kubernetes cluster by following the steps in [Manage secrets for your Azure IoT Operations deployment](../deploy-iot-ops/howto-manage-secrets.md).
+1. Add the secret reference to your Kubernetes cluster by following the steps in [Manage secrets for your Azure IoT Operations Preview deployment](../deploy-iot-ops/howto-manage-secrets.md).
 
 # [Managed identity](#tab/managedidentity)
 

articles/iot-operations/connect-to-cloud/howto-configure-destination-fabric.md

@@ -16,7 +16,7 @@ ms.date: 10/09/2023
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-Use the _Fabric Lakehouse_ destination to write data to a lakehouse in Microsoft Fabric from an [Azure IoT Data Processor (preview) pipeline](../process-data/overview-data-processor.md). The destination stage writes parquet files to a lakehouse that lets you view the data in delta tables. The destination stage batches messages before it sends them to Microsoft Fabric.
+Use the _Fabric Lakehouse_ destination to write data to a lakehouse in Microsoft Fabric from an [Azure IoT Data Processor Preview pipeline](../process-data/overview-data-processor.md). The destination stage writes parquet files to a lakehouse that lets you view the data in delta tables. The destination stage batches messages before it sends them to Microsoft Fabric.
 
 ## Prerequisites
 
@@ -68,7 +68,7 @@ For the destination stage to connect to Microsoft Fabric, it needs access to a s
     az keyvault secret set --vault-name <your-key-vault-name> --name AccessFabricSecret --value <client-secret>
     ```
 
-1. Add the secret reference to your Kubernetes cluster by following the steps in [Manage secrets for your Azure IoT Operations deployment](../deploy-iot-ops/howto-manage-secrets.md).
+1. Add the secret reference to your Kubernetes cluster by following the steps in [Manage secrets for your Azure IoT Operations Preview deployment](../deploy-iot-ops/howto-manage-secrets.md).
 
 # [Managed identity](#tab/managedidentity)
 

articles/iot-operations/connect-to-cloud/howto-configure-kafka.md

@@ -1,6 +1,5 @@
 ---
-title: Send and receive messages between Azure IoT MQ and Azure Event Hubs or Kafka
-titleSuffix: Azure IoT MQ
+title: Send receive messages between Azure IoT MQ and Event Hubs or Kafka
 description: Learn how to send and receive messages between Azure IoT MQ and Azure Event Hubs or Kafka.
 author: PatAltimore
 ms.author: patricka
@@ -13,11 +12,11 @@ ms.date: 01/16/2024
 #CustomerIntent: As an operator, I want to understand how to configure Azure IoT MQ to send and receive messages between Azure IoT MQ and Kafka.
 ---
 
-# Send and receive messages between Azure IoT MQ and Event Hubs or Kafka
+# Send and receive messages between Azure IoT MQ Preview and Azure Event Hubs or Kafka
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-The Kafka connector pushes messages from Azure IoT MQ's MQTT broker to a Kafka endpoint, and similarly pulls messages the other way. Since [Azure Event Hubs supports Kafka API](/azure/event-hubs/event-hubs-for-kafka-ecosystem-overview), the connector works out-of-the-box with Event Hubs.
+The Kafka connector pushes messages from Azure IoT MQ Preview MQTT broker to a Kafka endpoint, and similarly pulls messages the other way. Since [Azure Event Hubs supports Kafka API](/azure/event-hubs/event-hubs-for-kafka-ecosystem-overview), the connector works out-of-the-box with Event Hubs.
 
 
 ## Configure Event Hubs connector via Kafka endpoint
@@ -493,4 +492,4 @@ This connector only uses MQTT v5.
 
 ## Related content
 
-[Publish and subscribe MQTT messages using Azure IoT MQ](../manage-mqtt-connectivity/overview-iot-mq.md)
+[Publish and subscribe MQTT messages using Azure IoT MQ Preview](../manage-mqtt-connectivity/overview-iot-mq.md)

articles/iot-operations/connect-to-cloud/howto-configure-mqtt-bridge.md

@@ -1,6 +1,5 @@
 ---
 title: Connect MQTT bridge cloud connector to other MQTT brokers
-titleSuffix: Azure IoT MQ
 description: Bridge Azure IoT MQ to another MQTT broker.
 author: PatAltimore
 ms.author: patricka
@@ -13,11 +12,11 @@ ms.date: 11/15/2023
 #CustomerIntent: As an operator, I want to bridge Azure IoT MQ to another MQTT broker so that I can integrate Azure IoT MQ with other messaging systems.
 ---
 
-# Connect MQTT bridge cloud connector to other MQTT brokers
+# Connect Azure IoT MQ Preview MQTT bridge cloud connector to other MQTT brokers
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
-You can use the Azure IoT MQ MQTT bridge to connect to Azure Event Grid or other MQTT brokers. MQTT bridging is the process of connecting two MQTT brokers together so that they can exchange messages.
+You can use the Azure IoT MQ Preview MQTT bridge to connect to Azure Event Grid or other MQTT brokers. MQTT bridging is the process of connecting two MQTT brokers together so that they can exchange messages.
 
 - When two brokers are bridged, messages published on one broker are automatically forwarded to the other and vice versa.
 - MQTT bridging helps to create a network of MQTT brokers that communicate with each other, and expand MQTT infrastructure by adding additional brokers as needed.
@@ -377,7 +376,7 @@ This helps you balance the message traffic for the bridge between multiple clien
 
 To minimize credential management, using the system-assigned managed identity and Azure RBAC is the recommended way to bridge Azure IoT MQ with [Azure Event Grid's MQTT broker feature](../../event-grid/mqtt-overview.md).
 
-For an end-to-end tutorial, see [Tutorial: Configure MQTT bridge between IoT MQ and Azure Event Grid](tutorial-connect-event-grid.md).
+For an end-to-end tutorial, see [Tutorial: Configure MQTT bridge between Azure IoT MQ Preview and Azure Event Grid](tutorial-connect-event-grid.md).
 
 ### Connect to Event Grid MQTT broker with managed identity
 
@@ -406,10 +405,10 @@ If `bridgeInstances` is set higher than `1`, configure the Event Grid MQTT broke
 
 If using managed identity isn't possible, keep the per-connection limits for Event Grid MQTT broker in mind when designing your setup. At the time of publishing, the limit is 100 messages/second each direction for a connection. To increase the MQTT bridge throughput, use shared subscriptions to increase the number of clients serving each route.
 
-## Bridge from another broker to Azure IoT MQ
+## Bridge from another broker to Azure IoT MQ Preview
 
 Azure IoT MQ is a compliant MQTT broker and other brokers can bridge to it with the appropriate authentication and authorization credentials. For example, see MQTT bridge documentation for [HiveMQ](https://www.hivemq.com/docs/bridge/4.8/enterprise-bridge-extension/bridge-extension.html), [VerneMQ](https://docs.vernemq.com/configuring-vernemq/bridge), [EMQX](https://www.emqx.io/docs/en/v5/data-integration/data-bridge-mqtt.html), and [Mosquitto](https://mosquitto.org/man/mosquitto-conf-5.html).
 
 ## Related content
 
-- [Publish and subscribe MQTT messages using Azure IoT MQ](../manage-mqtt-connectivity/overview-iot-mq.md)
+- [Publish and subscribe MQTT messages using Azure IoT MQ Preview](../manage-mqtt-connectivity/overview-iot-mq.md)

articles/iot-operations/connect-to-cloud/tutorial-connect-event-grid.md

@@ -1,7 +1,6 @@
 ---
 title: Configure MQTT bridge between IoT MQ and Azure Event Grid
-titleSuffix: Azure IoT MQ
-description: Learn how to configure IoT MQ for bi-directional MQTT bridge with Azure Event Grid MQTT broker PaaS.
+description: Learn how to configure Azure IoT MQ for bi-directional MQTT bridge with Azure Event Grid MQTT broker PaaS.
 author: PatAltimore
 ms.subservice: mq
 ms.custom: devx-track-azurecli
@@ -12,15 +11,15 @@ ms.date: 02/28/2024
 #CustomerIntent: As an operator, I want to configure IoT MQ to bridge to Azure Event Grid MQTT broker PaaS so that I can process my IoT data at the edge and in the cloud.
 ---
 
-# Tutorial: Configure MQTT bridge between IoT MQ and Azure Event Grid
+# Tutorial: Configure MQTT bridge between Azure IoT MQ Preview and Azure Event Grid
 
 [!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
 
 In this tutorial, you learn how to configure IoT MQ for bi-directional MQTT bridge with Azure Event Grid MQTT broker PaaS. You can use this feature to process your IoT data at the edge and in the cloud. For example, you can use IoT MQ to process telemetry data at the edge, and then bridge the data to Azure Event Grid for further processing in the cloud.
 
 ## Prerequisites
 
-* [Deploy Azure IoT Operations](../get-started/quickstart-deploy.md)
+* [Deploy Azure IoT Operations Preview](../get-started/quickstart-deploy.md)
 
 ## Set environment variables
 
@@ -86,7 +85,7 @@ az eventgrid namespace topic-space create \
 
 By using the `#` wildcard in the topic template, you can publish to any topic under the `telemetry` topic space. For example, `telemetry/temperature` or `telemetry/humidity`.
 
-## Give IoT MQ access to the Event Grid topic space
+## Give Azure IoT MQ Preview access to the Event Grid topic space
 
 Using `az k8s-extension show`, find the principal ID for the Azure IoT MQ Arc extension. The command stores the principal ID in a variable for later use.
 

articles/iot-operations/deploy-custom/concept-manifests.md

@@ -1,9 +1,9 @@
 ---
-title: Manifests - Azure IoT Orchestrator
+title: How Azure IoT Orchestrator uses manifests
 description: Understand how Azure IoT Orchestrator uses manifests to define resources and deployments for Azure IoT Operations
 author: kgremban
 ms.author: kgremban
-# ms.subservice: orchestrator
+ms.subservice: orchestrator
 ms.topic: concept-article
 ms.custom:
   - ignite-2023
@@ -12,13 +12,15 @@ ms.date: 10/25/2023
 #CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
 ---
 
-# Orchestrator manifests
+# Azure IoT Orchestrator Preview - manifests
 
-The Azure IoT Orchestrator service extends the resource management capabilities of Azure beyond the cloud. Through the orchestration service, customers are able to define and manage their edge infrastructure using the same Arm manifest files they use to manage cloud resources today. There are two main types of resources use for orchestration: targets and solutions. Together these resources define the desired state of an edge environment.
+[!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
+
+The Azure IoT Orchestrator Preview service extends the resource management capabilities of Azure beyond the cloud. Through the orchestration service, customers are able to define and manage their edge infrastructure using the same Arm manifest files they use to manage cloud resources today. There are two main types of resources use for orchestration: targets and solutions. Together these resources define the desired state of an edge environment.
 
 ## Target
 
-A *target* is a specific deployment environment, such as a Kubernetes cluster or an edge device. It describes infrastructural components, which are components installed once on a device, like PowerShell or Azure IoT Data Processor (preview). Each target has its own configuration settings, which can be customized to meet the specific needs of the deployment environment. It also specifies provider bindings that define what types of resources are to be managed on the target (for example, Helm, PowerShell scripts, K8s, CRs, or Bash scripts).
+A *target* is a specific deployment environment, such as a Kubernetes cluster or an edge device. It describes infrastructural components, which are components installed once on a device, like PowerShell or Azure IoT Data Processor Preview. Each target has its own configuration settings, which can be customized to meet the specific needs of the deployment environment. It also specifies provider bindings that define what types of resources are to be managed on the target (for example, Helm, PowerShell scripts, K8s, CRs, or Bash scripts).
 
 To create a target resource for an Arc-enabled K8s cluster, add the resource definition JSON to an Azure Resource Manager template. The following example creates a target resource that defines multiple components and bindings.
 

articles/iot-operations/deploy-custom/concept-providers.md

@@ -1,9 +1,9 @@
 ---
-title: Providers - Azure IoT Orchestrator
+title: How Azure IoT Orchestrator uses providers and components
 description: Understand how Azure IoT Orchestrator uses providers and components to define resources to deploy to your edge solution
 author: kgremban
 ms.author: kgremban
-# ms.subservice: orchestrator
+ms.subservice: orchestrator
 ms.topic: concept-article
 ms.custom:
   - ignite-2023
@@ -12,9 +12,11 @@ ms.date: 11/02/2023
 #CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
 ---
 
-# Providers and components
+# Azure IoT Orchestrator Preview - providers and components
 
-Providers are an extensibility model in the Azure IoT Orchestrator service that allows it to support deployments and configuration across a wide range of OS platforms and deployment mechanisms. Providers are responsible for executing the actions required to achieve the desired state of a resource.
+[!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
+
+Providers are an extensibility model in the Azure IoT Orchestrator Preview service that allows it to support deployments and configuration across a wide range of OS platforms and deployment mechanisms. Providers are responsible for executing the actions required to achieve the desired state of a resource.
 
 A provider encapsulates platform specific knowledge and implements a specific capability. In other words, the provider forms an API layer on top of the individual target resources like helm charts, ARC extensions etc., bundles them into a single entity and performs operations like installations, deletions and updates on them. A separate provider to handle each of these target resources.
 

articles/iot-operations/deploy-custom/howto-helm.md

@@ -1,9 +1,9 @@
 ---
-title: Deploy Helm chart workloads - Azure IoT Orchestrator
+title: Deploy Helm chart workloads with IoT Orchestrator
 description: Use Helm charts to deploy custom workloads to Azure IoT Operations clusters with the Azure IoT Orchestrator
 author: kgremban
 ms.author: kgremban
-# ms.subservice: orchestrator
+ms.subservice: orchestrator
 ms.topic: how-to
 ms.custom:
   - ignite-2023
@@ -12,13 +12,15 @@ ms.date: 11/01/2023
 #CustomerIntent: As an OT professional, I want to deploy custom workloads to a Kubernetes cluster.
 ---
 
-# Deploy a Helm chart to a Kubernetes cluster
+# Deploy a Helm chart to a Kubernetes cluster with Azure IoT Orchestrator Preview
 
-Once you have Azure IoT Operations deployed to a connected cluster, you can use Azure IoT Orchestrator to deploy custom workloads including Helm charts.
+[!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
+
+Once you have Azure IoT Operations Preview deployed to a connected cluster, you can use Azure IoT Orchestrator Preview to deploy custom workloads including Helm charts.
 
 ## Prerequisites
 
-* An Arc-enabled Kubernetes cluster with Azure IoT Orchestrator deployed to it. For more information, see [Deploy Azure IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md).
+* An Arc-enabled Kubernetes cluster with Azure IoT Orchestrator deployed to it. For more information, see [Deploy Azure IoT Operations Preview extensions to a Kubernetes cluster](../deploy-iot-ops/howto-deploy-iot-operations.md).
 
 ## Deploy a helm chart with override values
 

articles/iot-operations/deploy-custom/howto-k8s.md

@@ -1,9 +1,9 @@
 ---
-title: Deploy K8s workloads - Azure IoT Orchestrator
+title: Deploy K8s workloads with IoT Orchestrator 
 description: Use K8s to deploy custom workloads to Azure IoT Operations clusters with the Azure IoT Orchestrator
 author: kgremban
 ms.author: kgremban
-# ms.subservice: orchestrator
+ms.subservice: orchestrator
 ms.topic: how-to
 ms.custom:
   - ignite-2023
@@ -12,13 +12,15 @@ ms.date: 11/01/2023
 #CustomerIntent: As an OT professional, I want to deploy custom workloads to a Kubernetes cluster.
 ---
 
-# Deploy a K8s resource to a Kubernetes cluster
+# Deploy a K8s resource to a Kubernetes cluster with Azure IoT Orchestrator Preview
 
-Once you have Azure IoT Operations deployed to a connected cluster, you can use Azure IoT Orchestrator to deploy custom workloads including K8s custom resources.
+[!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
+
+Once you have Azure IoT Operations Preview deployed to a connected cluster, you can use Azure IoT Orchestrator Preview to deploy custom workloads including K8s custom resources.
 
 ## Prerequisites
 
-* An Arc-enabled Kubernetes cluster with Azure IoT Orchestrator deployed to it. For more information, see [Deploy Azure IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md).
+* An Arc-enabled Kubernetes cluster with Azure IoT Orchestrator deployed to it. For more information, see [Deploy Azure IoT Operations Preview extensions to a Kubernetes cluster](../deploy-iot-ops/howto-deploy-iot-operations.md).
 
 ## Deploy a K8s resource