This article provides a list of frequently asked questions (FAQ) for Azure IoT Operations and their answers.
How do I share feedback with the Azure IoT Operations product team?
Share your feedback on the Azure IoT Operations public feedback forum.
Does Azure IoT Operations offer high availability across multi-node setup?
Yes, Azure IoT Operations workloads on K3s and HCI/AKS-Arc multi-node clusters support distribution of workloads across multi-nodes setups. The MQTT Broker does automatically replicates states across multiple nodes governed by the Broker's 'cardinality' setting. Replicas are distributed across different nodes in a multi-node cluster and data isn't lost if there's one set of replicas running and healthy.
How can we ensure zero or minimal data loss in an Azure IoT Operations setup?
To achieve zero message loss, a minimum 3-node cluster is required. This configuration allows for one node to reboot or go offline without data loss. However, if the entire cluster goes down or enough nodes are lost to disrupt quorum, message loss might occur.
Is MQTT with QoS 2 supported in Azure IoT Operations?
Currently, MQTT with QoS-2 isn't supported. QoS 2 provides strict message guarantees (Exactly Once) and requires complex state management and synchronization which can impact performance and scalability. QoS-0 (At most once) and QoS-1 (At least once) provide sufficient message delivery guarantees for Azure IoT Operations applications, where a balance between availability, throughput, latency, and reliable message delivery is desired.
Is message persistence supported in Azure IoT Operations?
Full message persistence is on the roadmap, however, Azure IoT Operations supports in-memory message persistence with optional spillover to disk. This setup allows messages to remain available in memory, with overflow messages stored temporarily on disk to prevent data loss during high message volumes. However, if a pod restarts, any messages that were written to disk can't be restored.
Does Azure Device Registry offer high availability across availability zones and regions?
For information on high availability across availability zones and regions for ADR, see Reliability in Azure Device Registry.
What Kubernetes distributions are compatible with Azure IoT Operations?
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.
Can I migrate my IoT Edge workloads to Azure IoT Operations?
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.
For IoT Operations, which device communication protocols supported.
Currently, Azure IoT Operations supports OPC-UA and MQTT for device communication.
Which Azure regions is Azure IoT Operations currently available in?
Azure IoT Operations is available in East US2, West US 3, West Europe, East US, West US, West US 2, North Europe regions.
Does Azure IoT Operations support connecting via proxy servers?
Azure IoT Operations supports connecting via passthrough proxies that don't require proxy authentication. Proxies that require authentication or can inspect encrypted traffic are currently not supported.
Does Azure IoT Operations support Azure Private Link and private endpoints?
Azure IoT Operations currently does not support Azure Private Link and private endpoints.
Related content
To learn more, see IoT Operations overview and documentation.