If you run industrial IoT in 2026, the center of gravity has moved to the edge. Azure IoT Operations is Microsoft's Arc-enabled, Kubernetes-native edge stack — and it is finally the answer to "how do I run real logic next to my PLCs without shipping everything to the cloud?"
Here is what it actually is and when to use it.
What IoT Operations gives you
- Arc-enabled Kubernetes as the runtime — you can use AKS Edge Essentials, K3s, or any CNCF-conformant cluster
- MQTT broker at the edge (replaces the old IoT Edge hub)
- Data flows for transformation and routing before data leaves the plant
- OPC UA connector for talking to industrial equipment
- Schema registry so you are not shipping untyped JSON around
- Built-in observability via OpenTelemetry
Where it beats classic IoT Edge
- Kubernetes-native, so your existing GitOps and Helm workflows just work
- Clean separation of broker, connectors, and data flows
- Local processing with cloud-optional operation
- Better story for high availability at the edge
Architectural patterns that work
- Plant-local MQTT + cloud fan-out. Brokers at the edge, with filtered routes to Event Hubs or Fabric.
- Protocol translation at the edge. OPC UA in, Cloud Events out.
- Rules at the edge, analytics in the cloud. Fast loops stay local, slow loops go to Fabric or ADX.
Where teams stumble
- Treating it like IoT Edge v2 instead of a Kubernetes platform
- Skipping the schema registry — you will regret it in month six
- Under-provisioning edge clusters for real workloads
Originally published on the Horizon Tech Blog.
Top comments (0)