azure iot
216 TopicsFrom Connected Devices to AI-Ready Operations
For years, the promise of connected devices was visibility; collect telemetry, monitor assets and help people see what was happening. Customer conversations have moved past dashboards and alerts toward a bigger goal, which is turning operational insight into timely, coordinated action. Organizations want their teams to have contextual intelligence that reflects operational reality, and architectures that deliver data and control wherever they're needed. They're asking how to anticipate failures, automate maintenance, improve safety and manage entire fleets without adding complexity. At Ignite, we're reaching a major milestone in modernizing the Azure IoT stack, with new capabilities that help customers move from connected devices to AI-ready operations. Scaling Physical AI starts with three things: a simpler way to deploy, manage and secure connected device fleets; operational data that lands in the right destinations with its context intact; and the Agent ready integrations that bring the full cycle of perceive, reason, act and learn to life. As we evolve the platform, our goal is to meet customers wherever they are and make it easier for them to unlock the full potential of Physical AI. What You’ll See at Ignite Unified Management with Azure Device Registry: Announcing the general availability of Azure Device Registry integration with Azure IoT Hub with X509 cert management capabilities. Azure Device Registry represents IoT devices as Azure resources in Azure Resource Manager. Customers can manage and govern their fleets with familiar Azure capabilities, applying their existing cloud management, security and governance practices to even the smallest connected devices. Unified Data: Announcing the general availability of Fabric Eventstream as a native Azure IoT Hub endpoint. Customers can now route device data directly into Microsoft Fabric Real-Time Intelligence, where operational data gains physical-world context and joins enterprise data to power real-time insights, AI and agents. At Microsoft Ignite we're also previewing MQTT v5 support in Azure IoT Hub, which brings more flexible, application-aware messaging to connected devices. Unified Intelligence: Announcing the preview of Model Context Protocol (MCP) tools for Azure IoT Hub and Azure Device Registry. These agent-ready interfaces let agents orchestrate device management and connect the management and data foundations. Agents can then reason across operational and enterprise context and take governed actions on physical systems. Together, these capabilities help customers build on their existing investments while advancing toward more intelligent, adaptive, and autonomous operations. Unified Management with Azure Device Registry Azure Device Registry (ADR) extends that management model to IoT devices and assets, bringing them into a single management plane. By representing devices and assets as Azure resources, ADR provides a centralized source of truth for their metadata and a consistent foundation for management across the fleet. Customers using Azure IoT Hub can take advantage of ADR’s unified registry alongside familiar Azure management capabilities, including Azure Resource Graph queries, role-based access control (RBAC), and Azure Policy. This brings device management into established cloud governance practices rather than requiring a separate set of tools and controls. Azure Device Registry also delivers one of the most requested device security capabilities: fully managed, Microsoft-issued X.509 certificates for device operational credentials. Certificate management is built into device provisioning and connectivity, which simplifies the full certificate lifecycle. This is critical for Physical AI, before customers can safely give systems more autonomy, they need the tools to build Zero Trust solutions they can trust. The general availability of these capabilities marks a major milestone in modernizing the Azure IoT stack, bringing it deeper into Azure so customers can manage connected devices the same way they manage the rest of their cloud resources. Building on this foundation, we're also previewing new capabilities at Ignite that extend connected device management and operations. ADR software update enters preview, letting customers use ADR groups to organize devices into fleets that span IoT Hub boundaries. They can then use ADR jobs to coordinate software updates across those fleets. Azure's firmware analysis capabilities now integrate more deeply into ADR, putting fleet-wide security insights and continuous vulnerability visibility right inside device management. Customers can find risky code, keep vulnerability data current, and discover more of the firmware components running across their fleets. ADR brings inventory, governance, credentials, and software updates together under one management surface, helping customers move from managing individual connected devices to governing their fleets consistently at scale. “Connecting devices is only the beginning. By bringing Azure IoT Hub and Azure Device Registry together, Microsoft is making it easier for organizations to manage connected fleets as part of their broader Azure environment. At Mesh, we see this as an important step toward simpler, more scalable connected operations.” - Andrew Cohoat, President and CEO, Mesh Systems Unified Operations Data For agents to act on what's happening in the physical world, they need operational data that is unified, structured, and ready to use. Azure IoT Hub already brings that data into Azure. With the general availability of Fabric Eventstream as a native IoT Hub endpoint, you can now route device data straight from IoT Hub into Microsoft Fabric Real-Time Intelligence, with no custom pipelines or intermediate services to build and maintain. You configure the route in IoT Hub, choose Fabric Eventstream as the destination, and your device messages flow into Fabric in the open CloudEvents format. From there, Eventstreams' no-code and low-code tools let you transform, enrich, and route events to a unified operational data foundation. Three new previews extend what IoT Hub delivers through that connection. A standardized message format, set on the endpoint, wraps each message in a consistent, self-describing envelope, so downstream consumers see one structure whatever devices send. Device type and data schema references tell consumers what each device is and what shape its data takes, so meaning travels with the data. And Fabric Accelerator improvements guide you from streaming data to dashboards, alerts, and data agents, shortening the path from signal to action. At Microsoft Ignite, we’re previewing MQTT v5 support in Azure IoT Hub. Default Azure Device Registry (ADR) linking combines modern messaging with unified device management across IoT hubs. Custom topics let customers structure messaging around application needs, while routing based on user properties directs messages using application-defined context. A unified SDK ties these capabilities together, providing a consistent development experience. Together, these capabilities deliver a modern, extensible, and flexible cloud IoT stack secure by design and built for the future of device connectivity and fleet management at scale Physical AI is redefining the future of Industrial Autonomy, enabling connected assets to sense, learn and act intelligently. By combining TCS’ industry expertise with Azure IoT Hub and Azure Device Registry, enables us to blend digital intelligence with physical contexts to transform device data into self-healing, secure and autonomous ecosystems to unlock exponential business value.” – Mahesh Singhal, Director Alliances, Industrial Autonomy and Engineering (IAE), TCS “Industrial operations are moving from connected assets to intelligent, AI-driven decisions at the edge. The integration of Azure IoT Hub and Azure Device Registry creates a strong foundation for helping customers make that shift at scale.” - Martijn Handels, CTO, Helin Unified Intelligence Bringing these capabilities together, we are enabling a unified intelligence foundation that helps customers perceive, reason, and act on their physical environments. Secure cloud connectivity provides the foundation, while Model Context Protocol (MCP) tools for Azure IoT Hub and Azure Device Registry enable agents to orchestrate device management. Operational data flows into Microsoft Fabric’s OneLake, carrying the semantic context of physical assets so AI and agents can interpret it alongside enterprise data, reason across systems, and inform intelligent action. This connects the full cycle of Physical AI to perceive, reason, act, and learn advancing IoT from connected devices to connected operations and, ultimately, governed autonomy. “Physical AI becomes meaningful when intelligence is connected to the real operational environment. Azure IoT provides the secure connectivity foundation, while CogitX brings the reasoning, workflows, and safeguards needed to turn insight into responsible action.” - Pradeep Parappil, CEO, CogitX Customers / Partners The shift to Physical AI won't happen through technology alone. It takes an ecosystem that understands devices, operational environments and industry workflows, along with the safeguards needed to turn intelligence into responsible action. Across industries, partners are already combining these capabilities to solve real operational challenges and deliver measurable outcomes. The next chapter will be written together. We invite customers and partners to join us in bringing these possibilities to life across real-world operations. Spirax Group | Accelerating Industrial Maintenance with Azure IoT Hub and AI Spirax Group, working with Mesh Systems, uses Azure IoT Hub and AI to remotely monitor approximately 20,000 connected steam traps and automatically detect failures. The solution reduces failure notification times from months to hours, enabling faster maintenance response, reducing manual inspections, and helping minimize downtime and energy waste. WLS Lighting | Safer, Smarter, More Energy-Efficient Working with Mesh Systems, WLS Lighting leverages Azure IoT Hub to remotely manage over 250,000 commercial light poles through its netLiNK Controls platform. Intelligent monitoring, dimming, and scheduling have helped deliver over $78 million in cost savings and 951 million kWh in energy savings, while optimizing lighting for safety and efficiency. CogitX | Turning Industrial IoT Data into Intelligent Operations CogitX builds multi-agent AI solutions on Azure IoT Hub and Microsoft Fabric to transform industrial telemetry into actionable intelligence. In aluminum smelting operations, its AI agents correlate equipment signals, identify emerging risks, and recommend actions that operators can review and approve before production is affected. Watch the video Resources Getting started Azure IoT Hub Devices in ADR X509 Cert management with ADR Fabric as native Azure IoT Hub endpoint Azure IoT Hub support for MQTT5 (Preview) Partner Guide Microsoft Industrial AI Partner Guide666Views2likes0CommentsResource Guide: Making Physical AI Practical for Real‑World Industrial Operations
Microsoft's adaptive cloud approach brings together connected devices, industrial data, contextual intelligence, and governed actions across the edge and cloud. Azure IoT Hub and Azure IoT Operations connect operational assets, Azure Device Registry provides a common management foundation, Microsoft Fabric turns operational signals into contextualized intelligence, and Foundry Local enables AI inferencing at the edge. Together with Azure Arc and Azure Local, these technologies help organizations build, manage, and scale Physical AI solutions across real-world environments. Key Purpose Offering Direct-to-cloud device management + telemetry ingestion Azure IoT Hub Unified device and asset management + governance Azure Device Registry Industrial connectivity + edge data plane Azure IoT Operations Unified analytics + real-time intelligence Microsoft Fabric On-device AI inferencing runtime Foundry Local Azure-managed infrastructure for edge computing and AI workloads Azure Local Industry recognition Microsoft named a Leader in the 2026 Gartner® Magic Quadrant™ for Global Industrial AIoT Platforms Read the announcement See it all come together Before diving into each component, watch this end-to-end demo showing how Azure IoT Operations, Azure IoT Hub, Microsoft Fabric, and Foundry Local work as one stack across the edge-to-cloud lifecycle - Making industrial AI practical for real-world operations with adaptive cloud. How these components work together Azure IoT Hub and Azure IoT Operations connect devices and industrial assets, bringing operational data from the physical world into Azure. Azure Device Registry provides a unified foundation for managing devices and assets, while Microsoft Fabric combines real-time operational signals with business context for analytics and intelligence. Foundry Local enables AI inferencing at the edge, with Azure Arc and Azure Local extending Azure management and infrastructure capabilities into on-premises environments. Together, these technologies provide the foundation for building and scaling Physical AI solutions across the edge and cloud. This blog walks through where to get started with each product capability: 1. Manage Cloud-Connected Devices and Telemetry with Azure IoT Hub Azure IoT Hub is a fully managed cloud service that enables secure bidirectional communication, device-to-cloud telemetry ingestion, cloud-to-device command execution, per-device authentication, remote management and more. Azure IoT Hub also integrates directly with Microsoft Fabric Eventstreams, enabling organizations to ingest, transform, and route device telemetry for real-time analytics and downstream intelligence. Recommended Usage: Azure IoT Hub is best suited for distributed, standalone devices that connect directly to the cloud for telemetry, monitoring, and remote management. These devices typically do not require cloud-managed containerized workloads or local industrial protocol connectivity. Examples include water monitoring stations, vehicle telematics, and distributed fluid-level sensors. Resources Check out the latest announcements from Ignite 2026 in our blog post: https://aka.ms/ignite-2026-do-services Overview of generally available services: Azure IoT Hub Azure IoT Hub Device Provisioning Service Azure Device Registry Certificate management (new) Firmware analysis with Azure Device Registry (new) Azure Device Update for IoT Hub Overview of preview capabilities: IoT Hub: MQTT v5 connection profile Azure Device Registry: Groups, Jobs, and Software Update Connect IoT data to Microsoft Fabric: https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-streams/ Scalable solution guides: Best practices for large-scale IoT deployments - Azure IoT Hub Device Provisioning Service Scale Out an Azure IoT Hub-based Solution to Support Millions of Devices - Azure Architecture Center Azure IoT Hub scaling 2. Connect Industrial Assets with Azure IoT Operations Azure IoT Operations provides a unified industrial data plane running on Azure Arc-enabled Kubernetes clusters. It connects industrial equipment and operational systems, processes and contextualizes data locally, and routes it to cloud analytics and intelligence services. With the latest release, Azure IoT Operations expands connectivity to systems such as SQL Server and REST endpoints, supports direct data flow outputs to Microsoft Fabric OneLake and other analytics destinations, and introduces preview capabilities for semantic modeling and governed agent access. Recommended Usage: Azure IoT Operations is designed for environments that need local industrial connectivity, edge data processing, and cloud-managed workloads. It supports deployments ranging from small gateways and remote sites to factory infrastructure. Azure IoT Operations Essentials provides a lightweight option for single-node deployments, while Azure IoT Operations Standard supports more complex industrial environments, including OPC UA connectivity and multi-node configurations. Resources Product documentation and getting started What is Azure IoT Operations Azure IoT Operations Documentation Hub Releases · Azure/azure-iot-operations Quickstart: Explore Sample Latest release announcement: https://aka.ms/aio2610 Demos and open-source projects Making industrial AI practical for real-world operations with adaptive cloud Explore Azure IoT Operations: How we built the demo Microsoft Edge AI GitHub repository Physical AI Toolchain (Azure + NVIDIA): microsoft/physical-ai-toolchain Additional video tutorials Microsoft IoT Developers on YouTube Microsoft Developer: Azure Essentials Show, Video 1 Microsoft Developer: Azure Essentials Show, Video 2 Latest Announcements & Blogs Put Your Industrial Data to Work with New Azure Capabilities From Connected Devices to AI-Ready Operations Making Physical AI Practical: Part 1 and Part 2 Introducing small form factor infrastructure Unlock Industrial Intelligence | Microsoft Hannover Messe 2026 3. Advanced Analytics with Microsoft Fabric Microsoft Fabric brings together streaming operational data and enterprise information to deliver real-time analytics and actionable insights. Fabric Real-Time Intelligence enables organizations to ingest, analyze, and visualize live industrial signals, while Operations Agents help detect conditions and recommend actions. Fabric IQ adds business context through governed entities, relationships, and semantic models, helping agents reason over operational data in the context of business processes. Resources Get Started with Microsoft Fabric Learning Path Fabric Real-Time Intelligence documentation - Microsoft Fabric Microsoft Fabric Eventstreams documentation Fabric IQ documentation - Microsoft Fabric Introducing the new Microsoft IQ: Putting your organization's intelligence to work in every agent 4.Run AI Models at the Edge with Foundry Local and Azure Local Foundry Local enables AI models to run directly in edge environments, supporting low-latency inference and scenarios where connectivity or data residency requirements make local processing important. Together with Azure Local, organizations can deploy and manage intelligent workloads on Azure-managed infrastructure at the edge. New capabilities announced at Ignite 2026 expand support for smaller devices, including ARM64-based hardware such as NVIDIA Jetson AGX Thor, and vision-language-action models for physical AI applications. Resources Introducing small form factor infrastructure Foundry Local on Azure Local Documentation Participate in Foundry Local on Azure Local preview form Foundry Local on Azure Local: HELM deployment Demo Customer Stories Chevron: Chevron plans facilities of the future with Azure IoT Operations Husqvarna: Husqvarna Group Boosts Operational Efficiency with Azure Adaptive Cloud Ecopetrol: Ecopetrol standardizes industrial data across 100+ energy assets with Azure IoT Operations and Microsoft Fabric P&G: Procter & Gamble cuts model deployment time up to 90% with Azure IoT Operations Toyota: Toyota Industries innovates its paint shop processes with Azure industrial AI and Azure IoT Hub Partner Solutions and Industrial AI Ecosystem Microsoft partners bring industrial connectivity, domain expertise, and specialized solutions that help organizations turn operational data into actionable intelligence. Explore how partners are building on Azure IoT to address real-world industrial challenges: Physical AI Partner Resource Guide From pilots to production: How Microsoft and partners are accelerating intelligent operations How Mesh Systems Builds on Azure IoT Hub and Azure IoT Operations to Accelerate Industrial AI Unlocking the Human Telemetry Layer for Safer Industrial Operations Unlocking Smart Manufacturing: Siemens Industrial Edge Meets Azure IoT Operations Solving the Data Challenge for Manufacturers with Sight Machine & Azure IoT Operations Microsoft and Rockwell Automation: Transforming Industrial AI Together Scaling Industrial AI at the Edge with Helin and Azure IoT1.8KViews4likes0CommentsMicrosoft Physical AI Partner Guide: Choosing the Right Data Expertise for Every Stage
As organizations scale Physical AI, the challenge shifts from technology selection to deciding who should lead which part of the journey -- and when. Which partners should establish secure connectivity? Who enables production grade, AI ready industrial data? When do systems integrators step in to scale globally? This Partner Guide helps customers navigate these decisions with clarity and confidence: Identify which partners align to their current digital transformation and Physical AI scenarios leveraging Azure IoT and Azure IoT Operations Confidently combine partners over time as they evolve from connectivity to intelligence to autonomous operations This guide focuses on the data foundation for Physical AI, highlighting the partners and capabilities that connect industrial systems, contextualize operational data, and make it available to AI-powered applications. It does not attempt to catalog every Physical AI solution. Instead, it helps customers understand how specialized partners establish the trusted data and operational context needed for AI systems to move from insight toward informed, responsible action in the physical world. Common Customer Journey Steps 1. Modernize Connectivity & Edge Foundations The industrial transformation journey starts with securely accessing operational data without touching deterministic control loops. Customers connect automation systems to a scalable, standards-based data foundation that modernizes operations while preserving safety, uptime and control. Outcomes customers realize Standardized OT data access across plants and sites Faster onboarding of legacy and new assets Clear OT–IT boundaries that protect safety and uptime Partner strengths at this stage Industrial hardware and edge infrastructure providers Protocol translation and OT connectivity Automation and edge platforms aligned with Azure IoT Operations 2. Turn Operational Data into Intelligence With a consistent edge-to-cloud data foundation in place, customers can move beyond dashboards to build repeatable, production-ready intelligence into their industrial operations. Expert partners help transform operational data into contextualized signals that support analytics, intelligent applications, and increasingly sophisticated Physical AI scenarios across assets, lines, and sites. Outcomes customers realize Improved Operational efficiency and performance Adaptive facilities and production quality intelligence Energy, safety, and defect detection at scale Partner strengths at this stage Industrial data services that contextualize and standardize OT signals for AI consumption Domain-specific acceleration for common Industrial AI scenarios Data pipelines integrated with Azure IoT Operations and Microsoft Fabric 3. Prepare for Intelligent, Governed Action As organizations move from insights toward intelligent action, the focus shifts to safely connecting operational intelligence with real-world processes. Partners help align data, infrastructure, and operational interfaces while supporting the governance, monitoring, and lifecycle management needed for increasingly automated operations. Outcomes customers realize Proven reference architectures deployed across plants AI‑ready data foundations that adapt as operations scale Coordinated interaction between OT systems, AI models, and cloud intelligence Partner strengths at this stage Industrial automation leadership and control system expertise AI-ready edge infrastructure designed to support industrial intelligence and Physical AI workloads Systems integrators enabling end‑to‑end implementation and repeatability Partner Ecosystem: Building the Data Foundation for Physical AI This matrix highlights partners with specialized expertise in accessing, contextualizing, and operationalizing industrial data to support Physical AI solutions at scale. The matrix is not a catalog of end‑to‑end Physical AI applications; each partner contributes specialized capabilities that customers can combine to connect operational systems, establish trusted context, and support increasingly intelligent applications. How to use this matrix: Start with your scenario → identify primary partner types → layer complementary partners as you scale. Partner Type Adaptive Cloud Primary Solution Example Scenarios Geography Advantech Industrial Hardware, Industrial Connectivity LoRaWAN gateway integration + Azure IoT Operations Industrial edge platforms with built in connectivity, industrial compute, LoRaWAN, sensor networks Global Accenture GSI Industrial AI, Digital Transformation, Modernization OEE, predictive maintenance, real-time defect detection, optimize supply chains, intelligent automation and robotics, energy efficiency Global Avanade GSI Factory Agents and Analytics based on Manufacturing Data Solutions Yield / Quality optimization, OEE, Agentic Root Cause Analysis and process optimization; Unified ISA-95 Manufacturing Data estate on MS Fabric Global Belden Industrial Connectivity, Networking, Security Belden Horizon Data Operations (BHDO) + LioN-X with Azure IoT Operations OT-IT convergence, network orchestration and monitoring, ruggedized ethernet and switching, industrial WiFi, multi-vendor protocol connectivity, OT security, OPC UA Global Capgemini GSI The new AI imperative in manufacturing OEE, maintenance, defect detection, energy, robotics Global DXC GSI Intelligent Boost AI and IoT Analytics Platform 5G Industrial Connectivity, Defect detection, OEE, safety, energy monitoring Global Helin Industrial Data Services, Edge-to-Cloud IoT Platform RedZone Vision AI solution, Helin Platform built on Azure IoT Hub Renewable energy monitoring, maritime fleet monitoring, oil & gas vision/hazard detection, Azure IoT Central migration Global Innominds SI Intelligent Connected Edge Platform Predictive maintenance, AI on edge, asset tracking North America, EMEA Litmus Automation Industrial Connectivity, Industrial Data Ops Litmus Edge + Azure IoT Operations Edge Data, Smart manufacturing, IIoT deployments at scale Global, North America Mesh Systems GSI & ISV Azure IoT & Azure IoT Operations implementation services and solutions (including Azure IoT Operations-aligned connector patterns) Device connectivity and management, data platforms, visualization, AI agents, and security North America, EMEA Nortal GSI Data-driven Industry Solutions IT/OT Connectivity, Unified Namespace, Digital Twins, Optimization, Edge, Industrial Data, Real‑Time Analytics & AI EMEA, North America & LATAM NVIDIA Technology Partner Accelerated AI Infrastructure; Open libraries, models, frameworks, and blueprints for AI development and deployment. Cross industry digitalization and AI development and deployment: Generative AI, Agentic AI, Physical AI, Robotics Global Oracle ISV Oracle Fusion Cloud SCM + Azure IoT Operations Real-time manufacturing Intelligence, AI powered insights, and automated production workflows Global Rockwell Automation Industrial Automation FactoryTalk Optix + Azure IoT Operations Factory modernization, visualization, edge orchestration, DataOps with connectivity context at scale, AI ops and services, physical equipment, MES Global Schneider Electric Industrial Automation Industrial Edge Physical equipment, Device modernization, energy, grid Global Siemens Industrial Automation & Software Industrial Edge + Azure IoT Operations reference architecture Industrial edge infrastructure at scale, OT/IT convergence, DataOps, Industrial AI suite, virtualized automation. Global Sight Machine ISV Integrated Industrial AI Stack Industrial AI, bottling, process optimization Global Softing Industrial Industrial Connectivity edgeConnector + Azure IoT Operations OT connectivity, multi-vendor PLC- and machine data integration, OPC UA information model deployment EMEA, Global TCS GSI Sensor to cloud intelligence Operations optimization, healthcare digital twin experiences, supply chain monitoring Global This Ecosystem Model enables Physical AI solutions to scale through clear roles, respected boundaries and composable systems: Control systems continue to be driven by automation leaders Safety‑critical, deterministic control stays with industrial automation partners who manage real‑time operations and plant safety. Customers modernize analytics and AI while preserving uptime, reliability, and operational integrity. Data, AI, and analytics scale independently A consistent edge to cloud data plane supports cloud scale analytics and AI, accelerating insight delivery without entangling control systems or slowing operational change. This separation allows customers and software providers to build AI solutions on top of a stable, industrial‑grade data foundation without redefining control system responsibilities. Specialized partners align solutions across the estate Partners contribute focused expertise across connectivity, analytics, security, and operations, assembling solutions that reduce integration risk, shorten deployment cycles, and speed time to value across the operational estate. From Data to Physical Intelligence Physical AI starts with a reliable understanding of the physical world. By connecting industrial systems, contextualizing operational data, and bringing together the right partner expertise, organizations can build a foundation for intelligence that goes beyond insights to support better decisions and responsible action. Use this guide to identify the partners and capabilities that can help you take the next step on your Physical AI journey with Microsoft Azure.2.3KViews4likes0CommentsAzure IoT Operations 2610 is now available: Scaling the foundation for Physical AI
AI is moving out of dashboards and onto factory floors, oil fields, and production lines, where it can sense, reason, and act in the physical world. Most industrial organizations are only beginning to make that shift, and they need a platform that lets them start with confidence and keep going as their ambitions grow. Azure IoT Operations 2610 is built for exactly that. For the first time, Azure IoT Operations ships on two channels at once. The generally available (GA) release delivers production-ready capabilities that help organizations understand their operations across many more sites, at lower cost. A new public preview channel gives customers hands-on access to the capabilities that are coming next, including governed access to operations for AI agents and AI inference running directly inside edge data pipelines. Taken together, the two channels show where the platform is today and where it is heading. This release is part of a broader set of Physical AI announcements at Microsoft Ignite. Microsoft's Ignite Physical AI announcement (https://aka.ms/Ignite2026/PhysicalAIBlog) describes how IoT, Industrial AI, and Physical AI connect data, decisions, and action: IoT helps organizations understand their operations, Industrial AI helps them reason, and Physical AI helps them act, together forming a continuous learning loop. Within Microsoft's adaptive cloud approach, Azure IoT Operations is the on-site foundation for that loop. This post goes one level deeper into what 2610 delivers and what it makes possible. Physical AI and where Azure IoT Operations fits Physical AI is AI that works in the physical world. It perceives what is happening across an operation, reasons about what it means, and acts to improve the outcome. Getting there is a journey rather than a single leap, and customers should not feel they have to take on everything at once. Azure IoT Operations is designed to make that journey practical, so organizations can start simply, prove value, and evolve toward far more sophisticated applications of AI and agents at their own pace. The journey begins with easy integration into the physical operation customers already run. Many start with perception: connecting equipment, bringing in data from sensors and cameras, and seeing what is happening in real time. From there, they move into reasoning, with AI models and agents that diagnose issues and recommend improvements. Ultimately, they move into action, where approved decisions reach equipment through partner control systems. Each step builds on the one before it, on the same platform. Azure IoT Operations is also designed from the ground up to protect each customer's proprietary operational data. Customers decide who can access which data and how, and that applies to AI agents as much as to people and applications. They also decide what data leaves the site, if any at all. That control lets customers choose the deployment model that fits their operation: cloud-first deployments that rely on AI in the cloud, hybrid deployments that combine cloud AI with local AI models and agents, and fully local deployments where AI and agents run only on site and data never leaves it. Whichever path and deployment model a customer chooses, the role of Azure IoT Operations comes down to three core functions and two key intersections with the systems around it. Three core functions Understand the operation. Azure IoT Operations keeps trusted operational context close to the process: what each asset is, what its data means, how equipment relates, its current and historical state, observations from cameras and other sensors, and the capabilities and constraints of the process. Standards such as OPC UA and W3C Web of Things are the tools. The outcome is context that people and AI can rely on. Optimize the operation. AI models and agents run at the edge, next to the operational data and the process, where they can perceive, diagnose, recommend, optimize, and coordinate. Microsoft Foundry supplies the models and agent development capabilities. Azure IoT Operations supplies the operational environment in which those agents become useful. Govern action. When an agent proposes an action, Azure IoT Operations turns it into an authorized, bounded, and observable operation. It authenticates the actor, evaluates policy and current conditions, obtains approval where required, invokes an authoritative command path, records the decision, and verifies the result. Two key intersections Where AI meets control: Azure IoT Operations optimizes, partners actuate. Azure IoT Operations decides, predicts, and recommends, sometimes in the form of a control input such as a new setpoint, and issues that intent through governed interfaces. Partner control systems and robots run the deterministic real-time loop and own safety, for people and machines, at all times. As a simple example, Azure IoT Operations can set the thermostat, but the thermostat and the HVAC system get the room to the correct temperature. Partners are already proving this pattern. Azure IoT Operations integrates with Rockwell Automation's FactoryTalk Optix and is part of Schneider Electric's EcoStruxure Automation Expert. In Schneider's green-hydrogen pilot with H2E Power, AI agents validated control logic in simulation before deploying it to hardware; the system ran for more than 6,000 hours autonomously and cut the levelized cost of hydrogen by roughly 10%. Where edge meets cloud: local intelligence at the edge, enterprise intelligence in the cloud. Azure IoT Operations integrates local operational intelligence at each site. Microsoft Fabric integrates enterprise-wide and cross-site intelligence. The two are federated, so when customers choose to share data beyond the site, the context created at the edge flows to the cloud without being rebuilt. These three core functions follow the same path customers take into Physical AI: understanding the operation turns raw data into trusted context, optimizing it is where AI reasons over that context, and governing action is how decisions safely reach the physical world. Clear roles at each intersection are what make AI credible to the people who run plants. Customers get AI that is useful on the floor without trading away the control systems, certifications, and safety practices they already trust. What 2610 delivers Azure IoT Operations already provides the foundation many industrial customers run in production today: governed cloud-to-edge management actions, no-code data flow graphs, broad industrial connectivity, and unified health reporting. Release 2610 builds on that foundation in two directions. The GA release deepens the first core function, understanding the operation, and makes it practical at fleet scale. It also strengthens the intersection where edge meets cloud by landing edge data directly in the lakehouse. The preview release takes the first concrete steps into the second and third core functions: running AI against live operational data at the edge, and giving AI agents governed, auditable access to operations. Core function Generally available in 2610 In preview with 2610 Understand the operation Essentials SKU for large fleets, ODBC-based connector for SQL Server, smarter OPC UA collection, leaner data flow writes to the lakehouse Asset context with Web of Things and the edge registry, type-based OPC UA discovery, live data in the operations experience, Azure Marketplace connectors and the Akri Connector Builder, Microsoft Fabric integration Optimize the operation Service calls from custom WebAssembly modules, AI-assisted data flow authoring in VS Code Inference connector with Foundry Local and Azure Machine Learning, file-backed graph processing Govern action Management actions for HTTP/REST assets MCP server with policy-governed tool access, data-driven management actions, application lifecycle for agents and MCP servers Two release channels: what you can run today, and what is coming next Starting with 2610, every Azure IoT Operations release ships on two channels. GA (stable) is production-ready and fully supported. This is what you run on the factory floor. Preview includes everything in GA plus new capabilities that are ready for hands-on feedback. Use it in test or pilot environments to evaluate what is coming and help shape it before it reaches GA. You choose a channel when you deploy, through the Azure portal deployment wizard or the Azure CLI, and you upgrade within that channel. Switching an existing instance between GA and preview is not supported, so production deployments stay on a predictable, stable path. Connector and transform versions follow the same rule: GA instances see only GA versions, while preview instances see both. For technology leaders, the second channel changes how you can plan. You no longer have to wait for GA to evaluate a major capability or sign up for a one-off private preview. The preview channel is a working view of the roadmap, available every release, that your teams can put in front of real equipment and real operators while production keeps running. Generally available: understanding operations at scale Physical AI is only as good as the operational context beneath it, and that context has to exist at every site, not just at the flagship plant. The GA capabilities in 2610 turn on-site data into actionable intelligence: they make operational context cheaper to establish, broader in what it covers, and easier to hand up to enterprise analytics. Bring Physical AI to more sites: Azure IoT Operations Essentials A new Essentials SKU sits alongside the full-featured offering, now called Standard. Essentials delivers the core of Azure IoT Operations, the edge MQTT broker, Akri connectors, and data flows, on single-node clusters at a lower price point. Many organizations need a reliable edge data layer at hundreds or thousands of small sites, such as stores, substations, wind turbines, or remote equipment, that do not need the full industrial feature set. Essentials makes those fleet-wide rollouts cost-effective. Standard remains the choice for full industrial deployments that need OPC UA connectivity or multi-node clusters. You choose the SKU when you create an instance, and moving to Essentials requires a new deployment. Together with ARM64 support, generally available since release 2607, Essentials lowers both the cost and the hardware bar for line-level and pilot deployments. Data flow graphs that land data directly in your lakehouse Data flow graphs write directly to Azure Data Lake Storage Gen2 in Delta or Parquet, Microsoft Fabric OneLake tables in Delta, and Azure Data Explorer or local storage in Parquet. Teams can branch, window, filter, and run custom WebAssembly transforms at the edge, then write the result straight into analytics-ready tables with no extra messaging hop and no second pipeline to maintain. In 2610, Delta Lake writes use less memory and carry less transaction-log overhead, with checkpoints running in the background. Less, cleaner data goes to the cloud, which lowers storage and ingestion costs. This is where edge meets cloud, in practice: the edge does the local work, and Fabric receives context it can use for cross-site analysis. More of the plant, connected The new ODBC-based connector for SQL Server brings data from the databases behind MES, quality, batch, and historian systems into the same pipelines as OPC UA and MQTT telemetry. Teams configure a SQL Server connection and its assets in the operations experience and define datasets with SQL queries, with no custom extraction code. Management actions now extend to assets connected through the HTTP/REST connector as well, so teams can collect data from and act on REST-connected equipment alongside everything else. That brings governed management actions to more of the plant. Smarter OPC UA data collection OPC UA is a widely used open standard that lets industrial machines share their data, and 2610 makes the Azure IoT Operations connector for it smarter about what it collects and sends. It can now ignore values that barely change, drop readings the equipment itself flags as unreliable, and sample data at a fixed interval. Filtering out noise and bad readings at the source means less data to move and store, lower cloud costs, and cleaner input for analytics and AI. When a machine restarts or the network drops, applications can request a complete snapshot of the machine's current state, or receive one automatically when a key value changes, instead of waiting for values to trickle back in. Optional health signals confirm that the connection is alive and that data has been delivered, and an optional fast failover gets data flowing again sooner when a connection fails. Faster to build, easier to operate Several GA capabilities shorten the path from idea to running pipeline. Developers can describe a data flow in plain language to GitHub Copilot in VS Code, validate it locally, and deploy it. Custom WebAssembly modules in data flow graphs can now call request-response services over MQTT while processing a message, for enrichment, lookups, routing decisions, or asset management actions. The edge state store now supports paged key scans and multi-key reads, so applications can discover and retrieve the context available to them. Live data views in the Azure IoT Operations Data Flow extension for VS Code speed up commissioning and troubleshooting, and an updated navigation layout in the operations experience makes instances and their resources easier to find. Public preview: AI that reasons over operations, with action that stays governed The preview channel is where 2610 reaches furthest toward Physical AI. These capabilities put agentic AI to work on live plant data at the edge, within the governance controls the customer sets, and give agents a governed path into operations. Customers can evaluate them now in test and pilot environments. Connect AI agents to edge operations, with guardrails Azure IoT Operations now includes a Model Context Protocol (MCP) server that gives compatible AI agents and assistants authenticated, authorized access to live MQTT telemetry and state store data at the edge. A single endpoint aggregates supported first-party and third-party MCP tools, so teams can register their own MCP servers behind the same entry point instead of managing separate client connections. Authentication and authorization policies that you control govern access to every registered tool, so each agent gets only the tools its role allows, and publishing MQTT messages requires Admin permissions. New application lifecycle capabilities also let teams deploy and manage agents and MCP servers on the cluster, alongside connectors. This is the third core function, govern action, taking shape. Teams want AI copilots that can answer "why is line 3 down?" or "which assets are unhealthy?" without giving AI broad access to production systems. With a single governed entry point, organizations bring the agent they already use and decide exactly what that agent can see and do. Run predictive AI models in the data pipeline The new Inference connector runs registered machine learning models, using predictive models served by Foundry Local on the cluster or models hosted in Azure Machine Learning, with multiple models running concurrently. Large inputs such as high-resolution images are read from files rather than passed through the message broker, and new graph-level file stores let custom WebAssembly transforms read and write those files on persistent cluster storage. Moving a model from a notebook onto a live production line usually means custom integration code for every model. With the Inference transform, a model becomes another step in the pipeline, and its results can feed downstream transforms or trigger management actions on connected assets, closing the loop from perception through reasoning to action. This is the second core function, optimize the operation, running where the data is. Give data meaning: asset context and the edge registry Raw tag values are not enough for analytics or AI to reason about an operation. A new WoT Enrich transform uses Web of Things mappings to give asset messages a consistent structure and add context such as what a value means and its units, and a new Microsoft Fabric integration formats and batches that telemetry for Eventhouse or Lakehouse. The new edge registry stores JSON Schemas and Web of Things Thing Models and Thing Descriptions on the cluster, where local workloads can reach them, and keeps them in sync with the cloud registry. Type-based OPC UA discovery finds assets and event groups from OPC UA type information, and assets such as Modbus pumps or S7 PLCs can be onboarded through OPC UA servers that implement the OPC UA Web of Things Connectivity API. When context travels with the data from the source, both Fabric reports and AI agents understand what they are looking at, even when cloud connectivity is interrupted. See data as it flows, and connect more sources Live data in the operations experience lets authorized users inspect incoming asset messages and validate data as it moves through transforms, WebAssembly modules, and data flow graphs, which answers the first question in every rollout: is the data arriving, and does it look right? To broaden connectivity, customers on the preview channel can discover and deploy supported third-party connectors from Azure Marketplace through the Azure portal or Azure CLI. For protocols that no connector covers yet, the Akri Connector Builder, a GitHub Copilot agent plugin, turns protocol specifications into connector code, tests, and documentation, and validates the result against a generated protocol simulator and a local Azure IoT Operations environment. Azure IoT Operations in Azure Government Azure IoT Operations is now in public preview in Azure Government (US Gov Virginia), running the 2610 GA feature set. US government agencies and their partners can evaluate edge data collection and processing in a government cloud, deploying through Azure CLI and using the operations experience. The preview channel is not available in Azure Government. Physical AI in action Customers are already putting this foundation to work. Unilever, working with Microsoft, NVIDIA, and Accenture, has built an advanced digital twin that captures the behavior of a whole factory as a connected system. The solution uses Azure IoT Operations to ingest and integrate sensor data, contextualize it at the edge, and feed it to edge and cloud AI services. By identifying bottlenecks, testing interventions, and recommending actions before issues affect production, it helps unlock greater efficiency, faster changeovers, and reduced waste, while giving engineers and factory teams AI-powered insight to make faster, better-informed decisions. What comes next Each Azure IoT Operations release now shows two things: what is ready for production, and what is coming next. Over the coming releases, the platform will keep moving from perceiving and informing, to reasoning and recommending, to orchestrating action through partner control systems. As it does, the human role shifts from approving every step to overseeing the system with the ability to intervene, and the platform's two key intersections, with partner control systems and with the cloud, stay the same throughout. Get started Deploy Azure IoT Operations 2610 with the Azure portal deployment wizard, Azure CLI, or Bicep, and choose the GA or preview channel and the Essentials or Standard SKU at deployment. Upgrade existing instances with Azure CLI, following the release-specific upgrade instructions. To try preview capabilities, deploy a new instance on the preview channel in a test or pilot environment. Review the public documentation (https://aka.ms/aiodocs) and release notes (https://github.com/Azure/azure-iot-operations/releases) for full details. Read Microsoft's Ignite Physical AI announcement (https://aka.ms/Ignite2026/PhysicalAIBlog) for the full picture across Azure IoT Hub, Azure Device Registry, Azure Local, Microsoft Fabric, and our partner ecosystem. Azure IoT Operations 2610 strengthens the foundation that is in production today and shows where Physical AI is heading. Wherever your organization is starting from, we look forward to building the next era of Physical AI with you.343Views3likes0CommentsAdvancing Device Firmware Security with Fleet Insights and Continuous Vulnerability Visibility
Firmware underpins IoT, OT, and network-device security, yet remains difficult to inventory, assess, and secure continuously. Earlier this year, we expanded firmware analysis enabled by Azure Arc to connect vulnerabilities to devices through Azure Device Registry, enrich CVE prioritization, analyze complex firmware, and improve software-supply-chain collaboration. At Microsoft Ignite, we're adding capabilities to surface firmware insights in device management, identify potentially risky function calls, refresh vulnerability information, and expand component discovery. These updates turn point-in-time firmware assessments into actionable insights across the device lifecycle. Bringing firmware security insights directly into Azure Device Registry In April, we introduced an integration between firmware analysis and Azure Device Registry (ADR) that maps analyzed firmware to the devices and assets running it, revealing fleet impact rather than an isolated scan result. At Ignite, we’re bringing firmware security insights directly into the Azure Device Registry experience. From an ADR device or asset, customers can view a firmware security summary, see whether vulnerabilities appear in the CISA Known Exploited Vulnerabilities (KEV) Catalog, and open the full firmware analysis report. Firmware is associated with devices and assets by manufacturer, model, and software version. Why it matters: Security teams can move from a vulnerability to affected devices, while operations teams can move from a device to firmware risk. Connecting firmware analysis and ADR reduces manual correlation and helps teams prioritize devices exposed to vulnerabilities known to be exploited in the wild. This makes firmware security part of the device-management lifecycle rather than a separate workflow. Keep firmware vulnerability information current with Latest CVEs A firmware image doesn't become static from a security perspective simply because its bits haven't changed. A firmware image’s security posture can change even when its bits do not. New CVEs or updated vulnerability data can introduce risk after the original analysis, requiring customers to re-upload firmware and compare results manually. With Latest CVEs, now in Preview, firmware analysis provides a refreshed view of vulnerabilities affecting an existing firmware image while preserving the original results for comparison and audit. It includes original and newly identified CVEs, relevant metadata changes, and additions to the CISA Known Exploited Vulnerabilities (KEV) Catalog—the authoritative catalog of vulnerabilities with evidence of exploitation in the wild. Customers can compare Original results captured at upload with the Latest view and filter for newly identified CVEs or severity-impacting metadata changes. Why it matters: Firmware may remain deployed for years, so teams need a fresh risk picture—not only the original assessment. Latest CVEs surfaces newly introduced risk, including when a vulnerability enters CISA KEV, and helps identify affected firmware and devices for priority patching, mitigation, or investigation. Finding potentially unsafe function calls in firmware Vulnerabilities aren't limited to known CVEs. Security issues can also originate in the way firmware itself is implemented. The new Unsafe Function Calls analysis, now in preview, scans supported ELF executables for functions that can create security issues without controls such as input validation, bounds checking, and buffer-size validation. The preview identifies calls to functions including strcpy, strcat, printf, fprintf, sprintf, system, mmap, and popen. It also surfaces network-related function-call information, allowing analysts to consider prioritizing executables containing both unsafe function calls and network-related calls for further review. This helps security and firmware-engineering teams identify binaries for deeper review and investigate risky implementation patterns beyond CVE analysis. A flagged function does not necessarily indicate a vulnerability; exploitability depends on its use, input data, and surrounding protections. The preview supports ELF user-space executables on AMD64/x86-64, ARM64/AArch64, ARM32 and MIPS32. Broader SBOM discovery across firmware An accurate Software Bill of Materials is essential to firmware risk assessment: unidentified components cannot be reliably mapped to disclosed vulnerabilities. Over the past few months we have added 70 new SBOM component detectors to expand discovery of software embedded in firmware images. These detectors expand the range of software components that firmware analysis can identify, improving software inventory visibility and supporting component-level vulnerability analysis. This expansion addresses component-discovery gaps across real-world firmware through ongoing validation of customer firmware and comparison results. Why it matters: Better component discovery improves software-supply-chain visibility and helps identify affected firmware when vulnerabilities are disclosed. Extending firmware security visibility beyond the initial scan Together, these capabilities make firmware security insights broader, more current, and easier to operationalize: Azure Device Registry integration connects firmware security posture—including CISA KEV findings—to the devices and assets customers manage. Latest CVEs helps customers understand how firmware vulnerability posture changes after initial analysis and prioritize affected firmware and devices when a CVE is added to CISA KEV. Unsafe Function Calls analysis adds another layer of static security analysis beyond known vulnerabilities and software inventory. Expanded SBOM detection increases visibility into the software components that make up firmware. Firmware security should continue after the scan by connecting findings to devices, detecting risks beyond CVEs, tracking vulnerabilities over time, and maintaining visibility into fleet software. These investments in firmware analysis, enabled by Azure Arc and Azure Device Registry, make firmware security more visible, actionable, and integrated into edge management and security. As always, we welcome customer feedback as we expand firmware analysis.141Views0likes0CommentsPut Your Industrial Data to Work with New Azure Capabilities
In almost every conversation I have with industrial leaders, the same question comes up: how do we do more with fewer skilled workers, less predictable supply chains, and customers who expect products made just for them? The answer isn't more sensors. Most organizations already have plenty. The problem is that the data and knowledge they need is scattered across people, processes, and systems that were never designed to work together. Closing that gap gets easier with a continuous learning loop, where organizational processes can perceive, reason, act, and manage at scale, with governance built into every step. Perceive: Gather data to create visibility from operational assets and make contextualized industrial data available at scale so teams can see what's really happening across their operations. Reason: Contextualized intelligence helps people understand why something is happening and what should happen next. Act: Put that intelligence to work through machines, systems and people, turning insight into results in the physical world. Manage: A consistent foundation to deploy, operate, and update assets, applications, and agent models across every site, from the edge to the cloud, so what works in one plant can scale to all of them. Put simply, IoT gave us visibility to know what happened. Industrial AI tells us what should happen. Physical AI helps us make it happen. Together, these form a continuous learning loop. Every action creates new data, and each cycle makes operations smarter. Customers like Unilever and Ecopetrol are already using this loop to improve throughput, quality, and asset reliability. Today, I'm excited to share new Azure capabilities that help industrial organizations see more, reason faster, act with confidence, and scale with trust. Azure as the Foundation for Physical AI In industrial settings, intelligence is only useful if it can be trusted. That means knowing where data comes from, who can access it, how AI reaches its recommendations, and what guardrails are in place before anything acts in the physical world. When governance is designed in from the start, organizations can move faster without giving up safety, security, or control. Azure makes this easier. Microsoft helps customers turn successful pilots into coordinated, governed, repeatable operations across equipment and sites. This requires a consistent, scalable foundation spanning edge to cloud that supports continuous learning and drives business outcomes. With Azure Arc, Azure management and Microsoft data services extend into industrial environments, providing a common foundation for governance, integration, and intelligence. This edge to cloud foundation is powered by Azure IoT Operations, Azure IoT Hub, Azure Device Registry, Microsoft Fabric, Foundry Local and Azure Local. Unilever is a global consumer goods company whose products reach 3.7 billion consumers every day. Across Unilever, the company is using intelligent technology to build the next generation of manufacturing. Smarter, faster and more connected factories help Unilever deliver superior products, improve efficiency, and serve consumers better than ever before. Working with Microsoft, NVIDIA and Accenture, the company has created an advanced digital twin that captures the behavior of the whole factory as a connected system. The solution leverages Azure IoT Operations to ingest and integrate sensor data, contextualize it, and feed that data to edge and cloud-based intelligence services for insight. By identifying bottlenecks, testing interventions and recommending actions before issues affect production, the platform can help unlock greater efficiency, faster changeovers and reduced waste. Just as importantly, it gives engineers and factory teams intelligence-powered insights to make faster, better-informed decisions. Microsoft, along with its partners, are excited to help Unilever scale this blueprint across its manufacturing network with the goal of advancing intelligent operations. What You’ll See at Ignite Deploy, Manage and Secure at Scale Scaling physical AI starts with a simpler path to deploying, managing, and securing connected device fleets. Azure Device Registry (ADR) introduces a unified onboarding flow anchored by an ADR namespace, guiding customers through setting up a new IoT solution or bringing existing IoT Hubs into ADR without recreating them. By linking multiple hubs to a shared ADR namespace, organizations gain a unified management surface across their fleet, with Hub-connected devices represented as Azure resources so they can apply the same auditing, Azure Policy, and governance practices they use across the rest of Azure. This unified management experience also simplifies device security. ADR certificate management helps customers issue, renew, and revoke operational X.509 certificates for Hub-connected devices, strengthening device authentication without requiring them to build and operate their own certificate infrastructure. We are also enhancing ADR’s integration with Firmware Analysis so customers can view analysis results for their devices’ firmware directly in ADR, bringing visibility into firmware vulnerabilities alongside device inventory. Together, these capabilities help customers build on existing IoT investments while simplifying deployment and ongoing fleet operations under a consistent Azure governance model. Turn Data into Actionable Intelligence We are simplifying the ability to access and transform complex industrial data into shapes that are ready for AI consumption whether the devices and assets emitting that data sit within an industrial site or are globally distributed. Distributed connected assets/devices: Agent-ready data in a unified operational data store is essential for building intelligent connected operations. Azure IoT Hub brings large volumes of operational data from the physical world into Azure. We have now built a direct route from IoT Hub to Microsoft Fabric Eventstreams, making it easier to bring IoT data into a unified data foundation for agentic operations. As part of Fabric Real-Time Intelligence, Eventstreams ingests events from multiple sources, transforms and enriches them using no-code and low-code processing, and routes them to downstream destinations. This integration helps organizations turn real-world IoT signals into agent-ready insights and accelerate the path from ingestion to action within a managed environment. On-site connected assets/devices: Azure IoT Operations 2610 brings more plant data into one governed pipeline and lands it ready for analytics and intelligence. A new ODBC-based connector for SQL Server pulls data from the databases behind MES, quality, batch and historian systems, and the REST connector is now generally available with management actions. Data flow graphs now write directly to Microsoft Fabric OneLake, Azure Data Lake Storage, Azure Data Explorer and local storage in Delta or Parquet, so data processed at the edge lands in analytics-ready tables with no second pipeline. Developers can also describe a data flow graph in plain language in VS Code and deploy it. In preview, W3C Web of Things models attach meaning to telemetry before it leaves the site, and an on-cluster Edge Registry keeps asset definitions available at the edge. Optimize Operations with Agents Operations teams want intelligence that can answer "Why is line 3 down?" However, security teams won't give intelligence broad access to production. Azure IoT Operations and Azure IoT Hub both now preview a built-in Model Context Protocol (MCP) server and gateway that meets both needs. Every agent is authenticated, with Microsoft Entra ID for remote agents, and every tool call is authorized against policies the customer controls. Customers bring the agent they already use and decide exactly what it can do on live plant data. A new inference connector, also in preview, runs vision and anomaly detection models from Foundry Local or Azure Machine Learning as a step in the edge pipeline, so predictions feed straight into operational workflows. Agents recommend and act through governed interfaces, while partner control systems run the real-time loop and own safety. Bring Physical AI to More Devices and Environments Azure IoT Operations Essentials is a new, lower-cost SKU for organizations that need a reliable edge data layer at hundreds or thousands of small sites, such as stores, substations, wind turbines and remote equipment. Essentials delivers the core data plane (MQTT broker, Akri connectors, data flows) on single-node clusters. The full offering, now Azure IoT Operations Standard, remains the choice for OPC UA and multi-node industrial deployments. Azure IoT Operations also supports ARM64 with full parity from installation through lifecycle operations. Together, these lower both the cost and the hardware bar for line-level and smaller footprint deployments. With Azure Local, organizations can centrally provision, configure, monitor, and update infrastructure across supported hardware architectures, providing a consistent management experience across distributed environments. By bringing Azure-managed infrastructure to smaller, AI-capable devices, organizations can more easily deploy and scale physical AI applications across factories, retail locations, robotics, and other environments where space, power, and cost are important considerations. Today, we're announcing several new capabilities for Azure Local small form factor deployments, including support for Arm64-based hardware, starting with NVIDIA Jetson AGX Thor, the ability to run vision-language-action (VLA) models with Foundry Local on Azure Local, and new features to simplify GPU management, networking, security, and device operations. These advancements bring together the infrastructure and AI capabilities needed to build and operate intelligent physical systems at the edge. Innovating with the Ecosystem Physical AI requires more than technology. It takes an ecosystem that brings together industrial equipment, operational expertise, AI innovation, and the ability to deploy at scale in real-world environments. Across the Microsoft ecosystem, partners are already building on Azure tobring these capabilities to life. Helin Data is bringing edge intelligence to energy and industrial operations, combining local intelligence processing with cloud-scale device management and analytics. Industrial technology partners like Siemens, Litmus, and Rockwell Automation are connecting existing automation environments to Azure through their industrial platforms. Forescout is bringing OT security visibility through its Akri Connector. Sight Machine is collaborating with Microsoft on information models that enrich and share operational context, making industrial data more meaningful for intelligent applications. NVIDIA is advancing industrial visualization and simulation with Omniverse, alongside edge intelligence on Jetson Thor devices. Partners are also turning these capabilities into repeatable customer solutions. Mesh Systems is combining connectivity, cloud platforms, and AI-enabled applications, while transformation partners like TCS are developing industry-specific accelerators to help customers modernize operations and adopt intelligence at their own pace. Through our engineering partner program, we are working directly with partners to design, validate, and scale solutions built around real customer needs. The next step starts with your operations Physical AI is opening new possibilities for how industries operate, and the opportunity starts with the data, equipment, and expertise organizations already have. With Azure and our growing partner ecosystem, customers can begin connecting their operations, applying intelligence to real business challenges, and building toward more intelligent, adaptive operations. Explore how Azure IoT and our partner ecosystem can help you get started: Microsoft Azure Physical AI Solution Resource Guide Microsoft Azure Physical AI Partner Resource Guide357Views2likes0CommentsScaling Industrial AI at the Edge with Helin and Azure IoT
Remote industrial sites generate operational data continuously, but the ability to act on that data in near real time can be challenging. Bandwidth is often limited; connectivity is inconsistent, and the analysis needed to turn raw signals into insight typically depends on cloud connection. When worker safety is on the line, that gap matters even more, since a person entering a hazardous zone has to be detected and flagged on site independent of a cloud connection. Meeting those conditions calls for a secure, repeatable foundation, one that trains models in the cloud, runs inference locally, governs distributed edge devices, and turns the right signals into insight. Helin Data built that foundation: an edge-to-cloud platform that combines local inference, industrial data collection, and fleet observability on Azure. RedZone, Helin's vision AI application for hazardous-zone monitoring, is the first proof point of this platform. It uses the CCTV cameras already installed on a rig to detect when a person enters a defined danger zone around active equipment, triggering a local alert through an on-site interface and status lights, and logging the event for later safety and operational analysis. Because inference runs at the edge, RedZone can detect and alert without waiting on a connection to the cloud, while Azure handles centralized management, analysis, and model lifecycle activities. What sets this solution apart Designed for constrained environments – Inference runs directly on the edge box, so RedZone keeps detecting and alerting even through network outages, with no dependence on the cloud at runtime. Only priority events and metadata detected by RedZone sync to Azure, which keeps bandwidth use low on a constrained connection such as satellite connectivity used at some offshore sites. Secure, scalable fleet governance – Devices onboard automatically through Device Provisioning Service (DPS) with per-device X.509 certificates. Every device is listed in Azure Device Registry (in preview) and projected as native ARM resources, so updates and configuration changes can be targeted, governed, and audited using standard Azure tooling. Helin adds multi-level security, including public key infrastructure (PKI), data encryption, and industry-trusted authentication, protecting data as it moves from the rig to the cloud. Helin's observability layer spans device health, firmware updates, application status, and the data pipeline, so organizations can promptly identify and investigate potential issues across the edge-to-cloud pipeline. A closed edge-to-cloud AI loop – Models are trained and versioned in Azure Machine Learning, then deployed to the edge for local inference. Detections stream back into Microsoft Fabric, where the data can inform model evaluation and future model versions, closing the loop between the field and the cloud. A reusable application foundation – RedZone runs on the same platform and loop that can be adapted for additional customer scenarios. A different hazard, a different zone, or a different operational question can become its own application. Delivering a governed device fleet Azure IoT Hub and DPS provide secure device connectivity, messaging, and automated provisioning. The Azure IoT Hub integration with Azure Device Registry, currently in public preview, represents devices as Azure resources, providing a foundation for Azure-native fleet inventory and governance. Together, these services help Helin onboard, connect, and manage distributed edge deployments. Azure Device Registry (public preview with Azure IoT Hub): Provides the management plane, representing each device as an Azure Resource Manager resource so it can be governed with the same patterns used for other Azure resources including role-based access control, resource groups, tags, and resource-level management, with namespaces acting as the organizational and security boundary. Azure Device Registry integration with Azure IoT Hub and Microsoft-backed X.509 certificate management is in public preview and is not recommended for production workloads. Azure IoT Hub and DPS: Deliver secure onboarding and bidirectional messaging between the devices and the cloud. Helin Data Edge Inference and Data Collector: Runs vision AI inference at the edge and connects into the industrial control systems already on site, so each detection carries operational context. Industrial data is collected, contextualized, buffered, and filtered locally before important signals are sent to Azure. Microsoft Fabric: Ingests telemetry and turns it into an operational model for analysis and reporting, giving organizations clearer insight into their operations. Customer Impact This solution is already proven in a demanding industrial environment. When Helin Data implemented RedZone on Noble’s Maersk Discoverer rig, RedZone detected a person entering a hazardous zone and raised an alert in roughly 150 milliseconds. Processing the detection locally is particularly important offshore, where limited connectivity makes a cloud-dependent response impractical. Helin’s broader edge platform is already supporting Noble across its operations. The offshore drilling contractor, which operates a fleet of more than 40 rigs, uses Helin’s Remote CCTV Manager to provide authorized personnel with live video from more than 20 rigs. Reduced resolution streams sync to Noble’s secure Azure environment for viewing while full resolution recordings stay at the rig to reduce bandwidth use. Together, these examples demonstrate the broader platform pattern: process high-volume data locally, transmit the signals that matter, and centrally manage applications deployed across a distributed industrial fleet. Closing RedZone shows what becomes possible when Azure IoT Hub is used as more than a device-connectivity service. Combined with secure provisioning, Azure-native device governance, edge inference, model lifecycle management, and Microsoft Fabric, it becomes part of a repeatable platform for building and operating industrial AI applications at scale. For customers, the value extends beyond a single safety scenario. The same foundation can support new applications across worker safety, operational visibility, process improvement, and other industrial use cases, without rebuilding the underlying device and data infrastructure each time. Helin brings the industrial application expertise; Azure provides the scalable foundation on which those applications can be deployed, governed, and continuously improved. Take the next step Read the customer case study, Improving safety across a fleet of drilling rigs Learn more about RedZone in Seeing the Human Layer: Helin Brings Edge Vision AI to Industrial Operations on Azure. Explore Helin’s Intelligent Edge Application Platform is now available in Azure Marketplace Resources Deploy Azure IoT Hub with Device Registry integration and certificate management (preview) Azure IoT Hub Documentation Product documentation | Helin Documentation803Views0likes1CommentHow Mesh Systems Builds on Azure IoT Hub and Azure IoT Operations to Accelerate Industrial AI
Manufacturers generate vast amounts of operational data, yet its complexity and fragmentation across historians, Operational Technology (OT) systems, and cloud platforms can slow AI adoption at scale. As organizations invest in AI to enhance productivity, quality, and decision making, the ability to connect and contextualize operational data becomes critical. Azure IoT Hub, Azure IoT Operations, and Mesh address this challenge together, spanning the full path from device connectivity to actionable AI-powered insights. Mesh brings deep Azure IoT platform experience and a practical path to industrial AI, with MeshCloud built on Azure IoT Hub, an open-source .NET Akri framework for Azure IoT Operations, and MeshInsights delivering generative AI-powered operational intelligence. This expertise is backed by a long history with Azure; Mesh launched its first IoT solution on Azure in private preview in 2009 and remained an early adopter of every major Azure IoT service since. Together, Azure IoT Hub, Azure IoT Operations, and Mesh give manufacturers a streamlined way to unify operational data and apply AI where it matters most. Unlocking legacy data with Mesh's Akri Connector Industrial organizations often struggle to modernize operations because critical operational data sits isolated inside historians and legacy Operational Technology (OT) systems. Many manufacturers are also wary of integrations that create new dependencies and limit future flexibility. Azure IoT Operations addresses this through an open architecture built around Akri, connecting industrial data sources while preserving interoperability across hardware and software environments. Mesh built on this foundation with its Akri Historian Connector, bringing historian and legacy operational data into Azure IoT Operations through prebuilt connectivity rather than source-by-source integration work. The result is faster access to operational data ready for analytics, AI, and industrial automation. The key features of this connector include: Restart-safe data continuity: Manufacturers can trust that operational data keeps flowing even through outages or restarts, with no data loss and no time spent recovering or reprocessing data. Secure, flexible authentication: Modern and legacy industrial systems connect under one security model, meeting enterprise-grade authentication standards without restructuring existing infrastructure. A foundation other connectors can be built on: The underlying framework handles the heavy lifting, so teams only need to build what's unique to each new OT data source. This means faster time to value for every new data source. Built in alignment with Azure IoT Operations roadmap: The connector stays up to date automatically, as new Azure IoT Operations features become available. This means manufacturers have access to the latest capabilities as the platform evolves. Together, Mesh and Azure IoT Operations give organizations a production-ready path from the shop floor into Azure IoT Operations and onward to Microsoft Fabric. Delivering Scalable Connected Products with Azure IoT Hub and MeshCloud MeshCloud helps manufacturers move from connected product pilots to fleet scale deployments faster by providing a platform build on Azure IoT Hub and other Azure native services. Azure IoT Hub provides per-device identity, support for MQTT, AMQP, and HTTPS, and built-in capabilities like device twins, direct methods, and rules-based message routing. Azure Device Provisioning Service (DPS) extends this foundation with zero-touch, just-in-time onboarding using X.509, TPM, or symmetric key attestation. Mesh operates as one cohesive engineering practice across the full connected product lifecycle, delivering hardware, firmware, wireless, edge, and cloud integration natively for Azure IoT Hub and Azure IoT Operations. That end-to-end scope is what MeshCloud, their Azure-native connected product platform, brings together. MeshCloud embeds Azure IoT Hub and DPS into an Azure-native connected product platform, giving organizations a faster path to connected product delivery without sacrificing control, scale, or solution ownership. The platform comes together across four layers: Edge to cloud: Connected devices, from MCU controllers to tablets and phones, register and authenticate through DPS and connect securely to IoT Hub, giving organizations a direct, secure line from shop floor to enterprise systems. Messaging and command: Event Hubs and Container Apps move telemetry and commands between devices and the cloud, with asset and ontology data exposed for digital twin management and device control. IT and operations: Azure Monitor, OpenTelemetry, Microsoft Entra, and Application Gateway bring platform observability, identity management, and secure ingress together, equipping IT and operations teams with a unified way to manage and secure the environment. Analytics and visualization: Telemetry flows into Azure Data Explorer and Microsoft Fabric for processing and storage, with Grafana, Power BI, and a Device Health UI giving teams fleet-wide visibility. This architecture enables organizations to move from pilot projects to fleet-scale deployments using Azure-native services, while maintaining interoperability across devices, connectivity protocols, and analytics platforms. For manufacturers, this means less time integrating infrastructure and more time delivering operational insights, connected services, and AI-powered workflows. Advancing Industrial Intelligence with MeshInsights As organizations connect more assets and operational systems, the next challenge becomes turning information into consistent actions and decisions. Microsoft Azure provides the cloud, data, and AI foundation for intelligent operational workflows, while giving organizations control over their data and business processes. Mesh extends this foundation through MeshInsights. MeshInsights is Mesh's AI agent offering for connected-product manufacturers. Mesh works with organizations to define a specific operational decision worth automating, such as classifying an alert or determining the right service response, and builds an evaluation standard from real telemetry, service history, and expert-validated examples. AI agents are then developed and measured against that standard, acting automatically on high-confidence cases and routing the rest to the organization's own experts. This extends connected systems beyond monitoring and reporting into trusted, auditable operational decisions. By combining Azure IoT platform services with MeshInsights, Mesh helps organizations move from connected infrastructure to autonomous, AI-driven action without changing where their data lives or who owns the architecture. Why This Matters Industrial transformation increasingly depends on strong collaboration between hyperscale cloud platforms and ecosystem partners who bring operational expertise, deployment acceleration, and industry-specific engineering capabilities. Mesh Systems demonstrates how partners can build differentiated value on top of Azure IoT platform services while helping organizations accelerate deployment timelines, standardize industrial data architectures, and operationalize AI across connected environments. Organizations are already putting this value to work in everyday operations. BUNN's cloud-connected coffee machines now give technicians a head start before every service call. As Kurt Powell, Executive Vice President at BUNN, put it: "With this solution, we know exactly which component to fix before we get there." WLS Lighting Systems has turned that same visibility into measurable savings at scale. Built on MeshCloud and Azure IoT, WLS's netLiNK gives property owners remote monitoring and control over individual light fixtures. Kevin Fletcher, President National Accounts at WLS, shared that the company has saved customers a little over $50 million in electrical costs since bringing netLiNK to market. Together, Azure IoT Hub, Azure IoT Operations, and Mesh Systems help manufacturers reduce integration complexity and operationalize industrial data, creating a foundation for AI driven operations spanning plant, edge, and cloud. The result: manufacturers spend less time on integration and more time improving productivity, resiliency, and decision making across their operations. Learn More Explore Mesh Systems solutions on Azure Marketplace: https://marketplace.microsoft.com/en-us/product/saas/mesh-systems.cloud?tab=Overview Read customer success stories: https://meshsystems.com/case-study-eaton-1/ Learn more about Azure IoT Operations: https://azure.microsoft.com/products/iot-operations/776Views1like0CommentsDirect IoT Hub-to-Fabric message routing, with context preserved via CloudEvents, in Public Preview
Announcing Public Preview of Microsoft Fabric Eventstreams as a native Azure IoT Hub routing endpoint. Customers can now send device telemetry directly into Fabric without building custom integration pipelines, using the same routing rules, filters, and enrichments configurable in IoT Hub. Events are delivered using the CloudEvents envelope, which preserves critical metadata for downstream analytics.705Views1like1CommentAzure IoT Edge 1.6 LTS is now available
IoT Edge 1.6 is built on .NET 10, which is an LTS release supported through November 14, 2028. IoT Edge 1.6 is supported for that same window. So if you're planning for the long term, 1.6 is the version to move to. For context, IoT Edge 1.5 LTS is supported through November 10, 2026 (it tracks .NET 8). If you're on 1.5, you have a clear, supported path forward, and we recommend planning your move to 1.6. How to upgrade from 1.5 Moving from 1.5 to 1.6 is a minor release upgrade, so update both the security daemon and the runtime containers: Update the IoT Edge security daemon on the device. sudo apt-get update && sudo apt-get install aziot-edge Update the runtime container tags in your deployment manifest. Point edgeAgent and edgeHub at 1.6, for example "mcr.microsoft.com/azureiotedge-hub:1.6", and apply the deployment. Verify the versions match. iotedge version && iotedge check Full steps are in Update IoT Edge. (Worth noting: 1.6 drops support for Debian 11. 1.5 continues to support Debian 11 through August 2026 if you need more time.) Release notes are on the Azure IoT Edge releases page. Give it a try.589Views0likes0Comments