Merge pull request #293008 from dominicbetts/aio-ga-pp

AIO: Clarify GA support

Author: v-ccolin

articles/iot-operations/deploy-iot-ops/concept-production-examples.md

@@ -28,6 +28,8 @@ Example hardware specifications:
 
 - AKS-EE on P3 Tiny Workstation (13th Generation Intel® Core™ i7-13700 vPro® Processor), 16 core (24 threads), 32-GB memory, 1-TB storage.
 
+[!INCLUDE [supported-environments](../includes/supported-environments.md)]
+
 The following table shows the MQTT broker configuration for the single node example:
 
 | Parameter                | Value |
@@ -70,8 +72,11 @@ When Azure IoT Operations runs on a multi-node cluster, it can process more data
 Example hardware specifications:
 
 - 5-node K3s with Azure VMs (Standard_D8d_v5 with Intel Xeon Platinum 8370C), 8 core (8 vCPU), 32-GB memory, 30 GB.
+
 - 5-node K3S with P3 Tiny Workstations (13th Generation Intel® Core™ i7-13700 vPro® Processor), 16 core (24 threads), 32-GB memory, 1-TB storage.
 
+[!INCLUDE [supported-environments](../includes/supported-environments.md)]
+
 The following table shows the MQTT broker configuration for the multi-node example:
 
 | Parameter                | Value |

articles/iot-operations/get-started-end-to-end-sample/quickstart-deploy.md

@@ -22,6 +22,8 @@ For the best new user experience, we recommend using an [Azure free account](htt
 
 We also use GitHub Codespaces as a virtual environment for this quickstart so that you can test the scenario without installing new tools on your own machines. However, if you want to deploy Azure IoT Operations to a local cluster on Ubuntu or Azure Kubernetes Service (AKS), see [Prepare your Azure Arc-enabled Kubernetes cluster](../deploy-iot-ops/howto-prepare-cluster.md).
 
+[!INCLUDE [supported-environments](../includes/supported-environments.md)]
+
 ## Prerequisites
 
 Before you begin, prepare the following prerequisites:

articles/iot-operations/includes/supported-environments.md

@@ -0,0 +1,13 @@
+---
+ title: include file
+ description: include file
+ author: dominicbetts
+ ms.topic: include
+ ms.date: 01/14/2025
+ ms.author: dobett
+ms.custom:
+  - include file
+---
+
+> [!IMPORTANT]
+> Currently, K3s on Ubuntu 24.04 is the only generally available platform for deploying Azure IoT Operations in production. To learn more, see [Supported environments](../deploy-iot-ops/overview-deploy.md#supported-environments).

articles/iot-operations/includes/validated-environments.md

@@ -34,8 +34,8 @@ sections:
          Does Azure Device Registry offer high availability across availability zones and regions?
       answer: For information on high availability across availability zones and regions for ADR, see [Reliability in Azure Device Registry](../../reliability/reliability-device-registry.md).
     - question: |
-         What Kubernetes distributions are compatible with Azure IoT Operations?
-      answer: Azure IoT Operations is only officially supported on two platforms now Ubuntu using K3s, Windows IoT using AKS Edge Essentials. For more information, see [Prepare your Azure Arc-enabled Kubernetes cluster](../deploy-iot-ops/howto-prepare-cluster.md).
+         On which platforms is Azure IoT Operations supported?
+      answer: Currently, K3s on Ubuntu 24.04 is the only generally available platform for deploying Azure IoT Operations in production. To learn more, see [Supported environments](../deploy-iot-ops/overview-deploy.md#supported-environments).
     - question: |
          Can I migrate my IoT Edge workloads to Azure IoT Operations?
       answer: Azure IoT Edge isn't an Azure Arc-enabled service like Azure IoT Operations is. Instead, IoT Edge is deeply integrated with and relies on Azure IoT Hub primitives such as device twins and direct methods for its functionality. While Azure IoT Operations can achieve outcomes similar to IoT Edge in some scenarios, the two services have fundamentally different architectures. As a result, there isn't a direct migration path for transitioning IoT Edge workload modules to Azure IoT Operations.