Azure IoT Operations
Azure IoT Operations is a set of modular services enabled by Azure Arc.
34 questions
Hello @Aydin Homay ,
welcome to this moderated Azure community forum.
This is good question regarding the evolution of Azure IoT, especially the edge solutions.
Microsoft Azure has a very popular and much used IoT ecosystem based on the IoT Hub.
The foundation is coming from around 2016 and the biggest players are the IoT Hub, the Device Provisioning Service, Azure IoT Central and Azure IoT Edge.
These services are still actively supported by Microsoft and used by many customers.
Still Microsoft has marked these services are feature-complete.
This means customers still get full support and SLA's are honoured.
We only will not see new features being deploy.
Meanwhile, we see the IoT ecosystem being expanded with new tools.
We have a new cloud gateway with vanilla MQTT support, the EventGrid Namespace MQTT Broker support.
We have a new Real-Time visualization using Fabric Real-Time Intelligence (based on Azure Data Explorer with Real-Time dashboards).
And finally, Azure IoT Operations is introduced: the new edge solution.
As you probably have seen, Azure IoT Operations is based on new standards like MQTT, Kubernetes, Azure Arc, etc. and it needs much more powerful edge devices to run on.
Azure IoT Operations is not a replacement for Azure IoT Edge.
From what Microsoft has shared, it is developed on these new standards and a tighter integration with Azure to support features like high-availability, fail over, vanilla MQTT on the edge, separation of the control plane from the data plane.
This makes Azure IoT Operations ideal for more Industrial IoT situations where multiple Kubernetes nodes (multiple edge devices sharing the load) offer a great extension of the cloud IoT solutions.
It's not the silver bullet, if you have constrained devices or need very long offline support, Azure IoT Edge is probably still a more interesting solution.
Personally, I work with both platforms because I now have a choice to meet more requirements. Meanwhile, I'm taking into account some from Azure IoT Operations features in Azure IoT Edge (like the local MQTT broker) so I keep my options open for the future.
Just check out Azure IoT Operations, for example via this series of blog posts and see if this works out for you.
If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.