Azure IoT is Microsoft’s portfolio of connectivity and edge services for building IoT solutions on Azure. TagoIO is a full-stack IoT platform where the application layer, dashboards, rules, custom code, and end-user portals, comes built in. The comparison depends on which Azure IoT product you mean, so it helps to lay out the portfolio first.
Azure IoT Hub is the core service: a managed device gateway supporting MQTT, AMQP, and HTTPS, with device twins for state, jobs for fleet operations, and the Device Provisioning Service for zero-touch onboarding. Like AWS IoT Core, it stops at connectivity and message routing; storage, analytics, dashboards, and applications come from other Azure services or your own code.
Azure IoT Central is Microsoft’s hosted application platform on top of IoT Hub, with device templates, built-in dashboards, a rules engine, and per-device pricing. In February 2024, a message in the Azure portal announced IoT Central’s retirement for 2027; Microsoft retracted it within a day and stated the service is not currently slated to retire. The service remains available, and buyers evaluating it can weigh Microsoft’s public statements alongside where its investment is visibly going.
Azure IoT Operations, generally available since late 2024, is that investment: a Kubernetes-based, Azure Arc-managed edge data plane aimed at industrial scenarios, built around an edge MQTT broker and OPC UA connectivity.
TagoIO is a single platform covering device connectivity (MQTT, HTTPS, and 500+ device connectors), time-series storage, dashboards, serverless Analysis scripts in Node.js, Deno, or Python, Actions for rules and alerts, and TagoRUN white-label portals for end users. Dedicated deployments are available through TagoDeploy in 12+ regions.
Device connectivity and provisioning
IoT Hub is strong infrastructure: device twins are a mature pattern for state synchronization, DPS handles provisioning at fleet scale, and Device Update manages OTA. LoRaWAN is not a native Azure service, so LoRaWAN projects bring a partner network server and integrate it themselves.
TagoIO connects devices through MQTT and HTTPS and through its connector library, which includes LoRaWAN network servers (The Things Network, The Things Industries, Actility, Loriot, ChirpStack, Helium, and others), Sigfox, and satellite providers such as Myriota and Kinéis. Payload parsers and a Live Inspector for debugging device traffic are part of the platform. Network usage is free; plans meter data input and output.
Where the application gets built
With IoT Hub, the application is yours to assemble: Stream Analytics or Fabric for processing, Power BI or Grafana for visualization, and custom development for anything customers touch. Organizations standardized on Microsoft tooling often want exactly this, because the IoT data lands in the same Fabric and Power BI stack the rest of the business uses.
IoT Central includes operator dashboards and rules, and its REST API supports building beyond them, though customer-facing applications remain custom work.
In TagoIO, dashboards, rules, and user-facing portals are platform features. Blueprint dashboards apply one layout across a whole fleet of devices. TagoRUN adds branded portals with user management, access policies, custom domains, and an optional mobile app under your own brand, which is the part Azure does not offer as a product at any layer.
Custom logic
Azure routes IoT Hub messages into Event Hubs, Functions, and the broader data platform. The pattern is capable and unbounded, and it means owning deployment and operations for each function and pipeline.
TagoIO’s Analysis engine runs custom scripts inside the platform without separate infrastructure, triggered by data conditions, schedules, or dashboard interactions. Platform analytics also cover forecasts and predictions on sensor data, not only dashboards. Teams that outgrow built-in limits can run External Analysis on their own compute while keeping the same platform APIs.
Edge
Azure has the deeper industrial edge story: IoT Edge modules and, more recently, IoT Operations on Arc-enabled Kubernetes with OPC UA support, aimed at factories with OT infrastructure and Kubernetes skills.
TagoIO’s edge component is TagoCore, a free, open-source IoT engine that runs on hardware from a Raspberry Pi to a cloud VM, distributed as a Docker image with a plugin architecture. It suits local collection and processing that syncs with the TagoIO cloud rather than Kubernetes-scale industrial deployments.
Pricing model
IoT Hub prices by capacity units and tiers with a free tier; IoT Central prices per device; IoT Operations is licensed through Arc. Storage, processing, and visualization services bill separately, so solution cost is the sum of several meters.
TagoIO uses plan tiers plus service usage: free for 5 devices and 5 dashboards, Starter at $49/month, Scale at $199/month, and TagoDeploy dedicated instances from $850/month. Usage is measured in data transactions, storage, Analysis minutes, notifications, and end users, in one bill.
The bottom line
Azure IoT suits organizations committed to the Microsoft stack, teams that want IoT data inside Fabric and Power BI, and industrial deployments that can invest in IoT Operations at the edge.
TagoIO fits when the deliverable is a finished IoT application, especially one your customers log into under your brand, and you would rather configure a platform than integrate a set of services. Both approaches run production fleets; the difference is how much of the solution you want to own as code.