Azure 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.Azure IoT guidance for DigiCert Global Root G1 trust-store updates in sovereign clouds
At a glance The technology industry is retiring trust in an older root certificate - the DigiCert Global Root G1. As operating systems, firmware images, and CA certificate bundles update over time, some clients may stop trusting this older root. This can affect both your Azure IoT devices and the applications that connect to Azure IoT service APIs. If those devices or application hosts run on Linux or rely on a system trust store that receives periodic updates, this post explains what you might see and the simple steps to stay connected. This guidance is relevant only for a subset of Azure IoT customers using Azure Government (Fairfax) or Azure China (Mooncake) environments, and only if devices or applications adopt operating system, firmware, or trust-store updates that remove trust for the DigiCert Global Root G1 certificate. Azure public cloud customers are not affected because Azure IoT public cloud endpoints already use newer certificate chains. This is a client-side trust-store change, not a security incident, service outage, or certificate expiration event. Scope: Azure public cloud customers are not affected. This guidance applies only to specific Azure Government (Fairfax) and Azure China (Mooncake) scenarios where updated client trust stores no longer trust DigiCert Global Root G1. Could this affect my deployment? For most Azure IoT customers, the answer is no. If you use Azure IoT in the Azure public (commercial) cloud, you are not affected by this change. Azure IoT public cloud endpoints already use newer certificate chains and do not rely on the DigiCert Global Root G1 certificate. This guidance is relevant only for a subset of customers using Azure Government (Fairfax) or Azure China (Mooncake) environments, and only if: Your devices or applications rely on operating system trust stores. You recently applied Linux operating system, firmware, container image, OpenSSL, NSS, or CA certificate bundle updates. You began seeing TLS connectivity or provisioning errors after those updates were installed. If your devices continue to connect normally and you have not observed any TLS-related issues following recent updates, no action is required at this time What should I do? If your devices and applications are connecting normally, no action is required. If you manage Linux-based devices or applications that rely on operating system trust stores, we recommend validating OS, firmware, and CA bundle updates in a test environment before production rollout. If connectivity issues appear following a trust-store update, contact Microsoft Support for assistance. What you may observe After an operating system, firmware, or CA-certificate-bundle update, an affected device or application may show the symptoms below. These typically appear first in test or QA environments, because fleets and application environments usually stage updates before production. Failure to connect to Azure IoT during the TLS handshake. A certificate trust, “untrusted root,” or “unknown CA” error. Telemetry, provisioning, or service-API calls stop, while clients still running the previous trust store keep working normally. Why it could happen Your device or application validates the Azure IoT server certificate against the list of trusted root certificates in its local trust store. As updates remove the older DigiCert Global Root G1 from that store, a client that still expects it may reject the connection - even though the server certificate is valid. The change is on the client side, in the trust store, not in the Azure service. What you should check If you see connectivity or provisioning failures, confirm the following: Was there a recent OS, firmware, or CA-bundle update on the affected devices or application hosts? Do clients still running the previous trust store continue to connect? If so, the cause is a trust-store change. Is the error a certificate or trust error rather than an authentication error? What we recommend A few simple steps keep your devices and applications connected through this change: Validate firmware and OS updates in a test ring before production rollout, the single most effective way to catch trust-store changes early. If clients begin failing after such an update, pause the rollout and, where feasible, roll back the update on the affected device or application host to restore connectivity. Contact Microsoft Support if you see connectivity or provisioning failures following an OS, firmware, or CA-bundle update. Support can confirm the cause and guide you through the appropriate next steps for your configuration. Questions If you have questions, contact Microsoft Support or your Microsoft account team.Unlocking the Human Telemetry Layer for Safer Industrial Operations
What if we could track human health & safety conditions as precisely as we do with machines, and take immediate actions to protect our greatest asset, our people? Many industrial organizations still lack visibility into real-time human conditions, even as worker safety and operational risk remain major investment priorities. One of the most important operational signals has largely remained outside the industrial data estate: the human telemetry. VOORMI and Microsoft have joined forces to fill this gap in understanding real human conditions. Through the Mij™ platform, VOORMI brings human telemetry into Azure IoT, enabling enterprises to integrate worker conditions such as heat stress and fatigue into the same operational architecture already used for machines and industrial systems. VOORMI, SWNR’s performance apparel brand, is among the first to bring this technology into garments designed for real industrial field conditions. This integration brings their proprietary wearable technology directly into high-impact worker safety and field operations scenarios. The partnership helps establish a new telemetry layer for industrial operations, allowing human, machine, and environmental signals to converge and drive safer operations, real-time awareness, and adaptive AI workflows. Bringing the Human Signal into Industrial AI with Azure Industrial organizations increasingly recognize that many safety, productivity, and operational challenges occur at the intersection of people and machines. Workers operate in high-heat environments, hazardous conditions, remote sites, and physically demanding field scenarios where situational awareness matters in real time. Historically, worker telemetry has remained fragmented across proprietary wearable platforms and disconnected safety systems, creating governance and operational challenges for enterprise IT and OT teams. Mij™ is designed differently, integrating directly into customer-controlled Azure environments through Azure IoT Operations running at the edge or Azure IoT Hub in the cloud rather than introducing another isolated platform. Running intelligence at the edge enables virtual safety agents and operational workflows to execute closer to the worker, supporting low-latency responses, local interaction with OT systems, and operational resilience even in disconnected or bandwidth-constrained environments. This gives enterprises flexibility to support real-time worker safety responses at the edge while also enabling long-term analytics, reporting, and operational intelligence through Microsoft Fabric. Telemetry from garment-integrated sensors flows through edge gateways into Azure services including Azure IoT Operations, Azure Data Explorer, Azure Managed Grafana, and Microsoft Fabric. The result is a unified operational environment where worker telemetry can live beside machine, site, and environmental data under the customer’s existing identity, security, governance, and analytics model. The vision is simple and transformative: make human telemetry a trusted, first-class industrial data source. Azure Digital Operations as the Intelligence Layer The reference architecture demonstrates how Azure IoT Operations can serve as a scalable operational intelligence layer for worker safety and connected operations scenarios across manufacturing, energy, and field environments. Mij™-enabled garments broadcast Bluetooth Low Energy (BLE) telemetry that can be processed locally through edge gateways and routed into Azure IoT Operations using MQTT and dataflows. Data is then operationalized through Azure Data Explorer and visualized using Azure Managed Grafana dashboards for field operations, worker safety, fleet health, gateway monitoring, and operational readiness scenarios. Telemetry can also be made available to Foundry Local-hosted GenAI agents to support real-time, context aware safety guidance, such as prompting workers operating in high-heat conditions to hydrate or seek cooler environments. While Mij™-enabled garments are the initial implementation, the edge device-to-cloud architecture creates a broader onboarding point for additional wearable, sensor, and field telemetry scenarios over time. This allows enterprises to bring more human and operational signals into a unified Azure-native operational environment. The architecture also supports flexible ingestion patterns for environments where dedicated edge gateways are not practical. Using Microsoft Entra External ID, Azure Container Apps, and Azure IoT Hub, telemetry can securely flow into Azure services without exposing operational infrastructure credentials to client devices. This pattern aligns with the broader Azure adaptive cloud approach: enabling customers to run distributed edge-native services on Arc-enabled Kubernetes infrastructure while maintaining centralized security, governance, and analytics capabilities across the enterprise. Depending on customer architecture preferences, telemetry can be processed through Azure IoT Operations at the edge or ingested directly through Azure IoT Hub for cloud-first analytics and downstream processing in services such as Microsoft Fabric. Edge processing also enables real-time sensor fusion across worker telemetry, ambient environmental conditions, machine parameters, and site-level operational signals, supporting faster safety interventions and more context-aware operational decisions. This gives enterprises flexibility in how they balance edge processing, operational responsiveness, governance and privacy requirements. Enabling the Next Generation of Industrial Workflows The long-term opportunity extends well beyond visualization dashboards. As worker telemetry becomes part of the operational fabric, enterprises can begin building more adaptive and intelligent workflows across worker safety, field readiness, incident response, compliance, environmental monitoring, and industrial AI systems. Human telemetry can provide critical real-time context that complements machine and environmental signals enabling more responsive operations and eventually more autonomous decision-support experiences. By bringing human telemetry into enterprise AI and analytics workflows, organizations can build more adaptive operational systems that improve worker safety, situational awareness, and real-time decision making at scale. This partnership reflects a broader industry shift: industrial transformation is no longer only about connected machines. It is about connected operations where people, equipment, environments, and AI systems participate in a shared operational intelligence layer. With SWNR’s Mij™platform and Azure IoT Operations, Microsoft and VOORMI are helping unlock that future. Learn more: Mij™ product page: https://swnrtechnologies.com/pages/mij Learn more about Azure IoT Operations: Documentation & Getting Started See what’s new with Azure IoT Hub: Preview Documentation To get started with a pilot, contact: pilots@swnrtechnologies.com
Smaller updates, faster downloads with delta updates in Azure Device Update for IoT Hub
Keeping IoT fleets secure and up to date shouldn't mean shipping the full software image to every device, every time. With delta updates in Azure Device Update for IoT Hub, fleet operators can send only what has changed between versions, reducing download size, bandwidth use, and download time on most networks. In our demo below, an incremental change produced a delta ~97% smaller than the full image — a glimpse of what's possible for small, incremental changes. The timing matters. Security patch cadence keeps rising as Common Vulnerabilities and Exposures (CVEs) accumulate, more fleets (like smart meters and remote agricultural sensors) are running over metered networks such as cellular and satellite, and deployments are crossing scales where every megabyte per device adds up. At that point, full-image rollouts stop being a minor inefficiency and become a real cost and reliability problem. As part of a broader Azure IoT investment in more efficient edge-to-cloud data delivery, the new Device Update reference implementation agent 1.3.0 provides delta updates as a starting point that customers can build, validate, and integrate into their own environments. In this post, we'll walk through what delta updates are, how they work, and what else is new in 1.3.0 — including expanded Linux platform support to build on Debian 13 and Ubuntu 24.04, and new device-side visibility for tighter update control and coordination with device operations. Improving over-the-air (OTA) efficiency with delta updates When deploying OTA updates across a fleet, update size directly affects how quickly and efficiently updates move through the system. Traditional full image updates require every device to download the entire software image, even when only a small portion has changed. As deployments scale, this increases bandwidth usage and delivery overhead. Delta updates take a more efficient approach. Rather than transferring a full image each time, devices download a smaller delta artifact and reconstruct the target version locally, reducing the amount of data transferred across the fleet. By sending only what's changed between versions, delta updates improve efficiency in three ways: Less data on the network. Smaller payloads consume less bandwidth per device, and the savings multiply across large fleets. Faster downloads. Smaller artifacts reduce the time each device spends downloading the update, especially on variable or constrained networks. Lower delivery overhead at scale. With less data per rollout, teams can deliver updates more flexibly across large fleets, reducing the need to stagger deployments for bandwidth caps or capacity windows. This approach works particularly well for frequent, incremental changes such as bug fixes or small feature updates. For larger updates where most of the image has changed, or on devices with limited processing capacity, using a full image update may be more practical. How delta updates work Delta updates fit into the same Device Update deployment model you already use for full image updates. What changes is how update content is delivered and applied on the device. When you import an update into Device Update, you include both the full target update and one or more delta artifacts as part of the same update. When that update is deployed, the Device Update agent on each device picks the right path: If a compatible delta is available, the device downloads the delta, reconstructs the full target update locally, and installs it through the standard update workflow. If no compatible delta is available, the device falls back to downloading and installing the full target update. For details on integrating delta updates into your update workflow, see Deploy delta updates to devices. It guides you through generating delta artifacts on your build machine using the DiffGen reference tool, or as part of your image build process, and setting up the right components on the device to apply them. See the impact: Delta updates in action The following demo shows what a typical incremental change looks like with delta updates: a single-file change between image versions produces a 7 MB delta against a 240 MB full image — roughly a 97% reduction in data transferred for that scenario. Across 10,000 devices, that’s about ~2.3 TB less data crossing your network in a single rollout. Savings may vary depending on how much the versions have changed and how quickly the device can rebuild the full image locally, but they compound quickly at fleet scale. For example, a utility company patching firmware across hundreds of thousands of cellular-connected smart meters, or an agricultural operator updating remote field sensors over satellite links, sees carrier data costs drop significantly during each rollout. To bring this to life, the demo below shows what’s possible with delta updates — generating, deploying, and applying them on a Raspberry Pi device using Device Update for IoT Hub. Beyond delta updates: What’s new in the 1.3.0 reference implementation The 1.3.0 reference implementation also includes improvements that strengthen device-side coordination and expand Linux platform support. Coordinate updates with device workloads On many devices, updates run while the device is doing other work, such as handling sensor data, running a local UI, or managing background tasks. Without visibility into update status, device software can trigger conflicting operations or let battery-powered devices enter sleep mid-update. The 1.3.0 reference implementation helps your device software work alongside the update process rather than against it — coordinating with active updates, keeping devices awake through long downloads, and surfacing update status to local applications. A new device-local agent status API makes this possible: applications on the device can see what the Device Update agent is doing at any time, for example, whether an update is in progress. With that visibility you can: Avoid triggering operations that would conflict with an active update Keep battery-powered or low-power devices awake while an update is downloading or installing Surface update status in local applications or user interfaces Diagnose update behavior using local signals. Because the API runs locally, it works even when network connectivity is limited or intermittent. The payoff is fewer disrupted rollouts, more reliable updates across your fleet, and easier troubleshooting when something needs attention. Expanded Linux platform support The 1.3.0 reference implementation now adds Debian 13 and Ubuntu 24.04 to the Linux distributions you can already build on, including Debian 12 and Ubuntu 22.04. That gives you flexibility to work on newer OS versions without changing your existing update workflow. Call to action Ready to see the benefits? Extending and adapting the 1.3.0 reference implementation is a device-side change — existing service-side deployments and configurations stay as they are, so you can move at your own pace. Build from the Device Update for IoT Hub GitHub repository, integrate delta artifact generation into your build pipeline, and run your first delta in your next rollout to measure the bandwidth and download savings across your fleet. Learn more: Device Update for IoT Hub documentation | Microsoft Learn Deploy delta updates with Azure Device Update for IoT Hub | Microsoft Learn We’d love your feedback. Help shape the future of Azure Device Update for IoT Hub at aka.ms/dufeedback.Resource Guide: Making Physical AI Practical for Real‑World Industrial Operations
Microsoft’s adaptive cloud approach enables organizations to turn operational technology (OT) data into intelligent actions, autonomously, without requiring everything to live in the cloud by unifying cloud-to-edge management plane, data plane, and intelligence platform. At the center of this approach are key foundational technologies: Key Purpose Offering Direct-to-cloud device management + telemetry ingestion Azure IoT Hub Industrial connectivity + edge data plane Azure IoT Operations Unified analytics + real-time intelligence Microsoft Fabric On-device AI inferencing runtime Foundry Local Microsoft Azure IoT Gartner winner: Microsoft named a Leader in the 2025 Gartner® Magic Quadrant™ for Global Industrial IoT Platforms 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 Operations and Azure IoT Hub collect real-time data from operational assets and send semantically-ready, modeled data to Microsoft Fabric, where it's contextualized with enterprise data for downstream analytics. Microsoft Foundry extends to the edge through Foundry Local, so the same tooling used to deploy and manage AI models in the cloud applies to edge use cases. All of it integrates into Azure Resource Manager, bringing OT devices, assets, and edge AI models into the same management and security paradigm as every other Azure-managed resource. 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. Telemetry from IoT Hub can also be routed downstream into analytics platforms like Microsoft Fabric for visualization or AI modeling. Recommended Usage: Devices that utilize IoT Hub are distributed, stand-alone devices with fixed-functions. These devices typically do not require cloud-managed containerized workloads or cloud-managed proximal industrial protocol connectivity. Examples of appropriate device-to-cloud IoT Hub endpoint devices include water monitoring stations, vehicle telematics, distributed fluid level sensors, etc. Resources Current in-market services overview: IoT Hub: What is Azure IoT Hub? - Azure IoT Hub DPS: Overview of Azure IoT Hub Device Provisioning Service - Azure IoT Hub Device Provisioning Service ADU: Introduction to Device Update for Azure IoT Hub Building scalable solutions with Azure IoT platform: 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 Try out our preview of new IoT Hub capabilities (integration with Azure Device Registry and Certificate Management) Learn more about these capabilities on our blog post: Azure IoT Hub + Azure Device Registry (Preview Refresh): Device Trust and Management at Fleet Scale… Integration with Azure Device Registry (preview): Integration with Azure Device Registry (preview) - Azure IoT Hub Microsoft-backed X.509 certificate management (preview): What is Microsoft-backed X.509 Certificate Management (Preview)? - Azure IoT Hub How to start with the preview: Deploy IoT Hub with ADR integration and certificate management (Preview) - Azure IoT Hub 2. Connect Industrial Assets with Azure IoT Operations Azure IoT Operations provides a unified data plane for the edge that runs on Azure Arc–enabled Kubernetes clusters and supports open industrial standards. It allows organizations to connect and capture equipment telemetry, normalize OT data locally, route hot-path signals to real-time analytics, securely manage layered industrial networks, and more. Edge‑processed data can then be sent upstream to Microsoft Fabric for AI‑driven analysis. Recommended Usage: Azure IoT Operations is intended to be the data plane for an adaptive cloud deployment extending the management, data, and AI capabilities of the Microsoft cloud to an on-prem device. This device binds to these cloud planes providing a platform for local data processing and intermittent connectivity. The target for these devices range from a small-gateway-style PC to a full data center. Azure IoT Operations endpoints enable cloud-managed containerized workloads and cloud-managed proximal industrial protocol connectivity. Examples of appropriate adaptive cloud and Azure IoT Operations endpoints include, on-robot computers, industrial machine controllers, retail store sensor/vision processing, and top-of-factory site infrastructure for line of business applications. Resources Azure IoT Operations Overview Azure IoT Operations Documentation Hub Quickstart: explore-iot-operations/quickstart at main · Azure-Samples/explore-iot-operations Open-source framework for scaling robotics from simulation to production on Azure + NVIDIA: microsoft/physical-ai-toolchain Demo video showcasing this in action: Making industrial AI practical for real-world operations with adaptive cloud How we built the demo: explore-iot-operations/quickstart at main · Azure-Samples/explore-iot-operations Edge-AI: microsoft/edge-ai: Production-ready Infrastructure as Code, applications, pluggable components, and… Latest Announcements & Blogs Making Physical AI Practical for Real-World Industrial Operations: Part 1 | Microsoft Community Hub Making Physical AI Practical for Real-World Industrial Operations: Part 2 | Microsoft Community Hub Unlock Industrial Intelligence | Microsoft Hannover Messe 2026 From pilots to production: How Microsoft and partners are accelerating intelligent operations 3. Advanced Analytics with Microsoft Fabric Microsoft Fabric delivers a unified, end‑to‑end analytics platform that transforms streaming OT telemetry into real‑time insights and live dashboards. Fabric Operations Agents monitor industrial signals to recommend targeted actions, while Fabric IQ provides a shared semantic foundation that enables AI agents to reason over enterprise data with business context. Together, Fabric turns live industrial data into AI‑powered operational intelligence. Resources Get Started with Microsoft Fabric Learning Path Fabric Real-Time Intelligence documentation - Microsoft Fabric | Microsoft Learn Create and Configure Operations Agents - Microsoft Fabric | Microsoft Learn Fabric IQ documentation - Microsoft Fabric | Microsoft Learn 4.Run AI Models On‑Device with Foundry Local Foundry Local extends on‑device AI to Arc‑enabled Kubernetes edge clusters, providing a Microsoft‑validated inferencing layer for running AI models in industrial, disconnected or sovereign environments. Resources 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: Azure IoT Operations and Azure IoT for energy help Ecopetrol optimize energy distribution while lowering operational costs 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 HubMaking Physical AI Practical for Real-World Industrial Operations: Part 1
We’ve all read the headlines, but are companies really implementing AI with success, and at scale in manufacturing? The answer is yes - by replicating proven operational practices through simple, but highly practical AI implementations that help improve operational efficiency. For many years I helped industrial customers complete manual data analysis of root causes, lean black-belt style, using pareto charts and continuous improvement cycles to get results. Doing so required practical expertise, manual scrubbing to get good quality data (garbage in, garbage out), and a bit of charting to get to a simple set of recommendations for areas of focus. With modern advances, it’s not hard to see how easily that task can be accomplished with more range, more accuracy, and more speed using agentic AI running over AI-curated data sets. What once required weeks of expert-led analysis can now be surfaced continuously, turning root cause analysis from a retrospective exercise into a real-time operational capability. AI innovation is accelerating rapidly, and industrial organizations are eager to translate that momentum into real business outcomes. As the companies we partner with advance their AI initiatives, they are increasingly focused on designing and deploying scalable, responsible AI systems that can access and contextualize diverse data sources to proactively identify issues, assess business impact, and coordinate appropriate responses. Microsoft has been working closely with these organizations to build the right architecture to support their modernization goals while maintaining the control and stability required in industrial environments. At Hannover Messe 2026, we’re excited to share our vision for running AI‑powered factories, highlight the partners helping bring this vision to life, and announce our latest innovations in this space. Operationalizing Continuous Improvement with Agentic AI Industrial organizations are at varying stages of AI maturity, but many are exploring how AI can enhance established methodologies such as Lean and Six Sigma that utilize continuous improvement loops like identify–observe–analyze–decide–act. By enabling the ongoing collection and analysis of operational data, AI agents can fundamentally change the speed and accuracy of these data driven processes. In the early stages, organizations often start by using AI to generate chat-style insights and recommendations based on observed patterns; but as model performance improves and trust increases, they’re often motivated to include agents as part of a mixed human/AI team for supervised decision‑making and closed loop actions. Even simple agents can be used deliver ongoing analytics including cross‑deployment comparisons, failure clustering, and variance analysis across plants, regions, or device fleets on the fly by continuously monitoring telemetry, reading free-text fields on incident reports & support summaries, and by adding context from deployment metadata. This enables earlier intervention, helping reduce waste, improve sustainability, enhance quality, and increase operational efficiency. To support the effective use of AI agents across industrial operations, organizations need an architecture that captures real‑time operational data from machines and processes, transforms it into cloud‑ready formats, and contextualizes it with enterprise systems such as ERP and CRM to understand both operational and fiscal impact. AI and analytics must be developed and deployed across both edge and cloud environments - using cloud capabilities for scalable analytics, enterprise integration, and complex workloads, while leveraging edge execution for low‑latency insights, resilience to connectivity loss, and support for sovereign on‑site data. Leveraging cloud and edge-based data, agents can help enable coordinated, proactive responses across systems and teams. In addition, organizations need the ability to scale and govern these capabilities consistently across sites, while maintaining the control, security, and reliability required in industrial environments. You can learn more about Microsoft’s Industrial AI stack in Part 2 of this blog, which provides the foundation for scalable industrial AI deployments. However, I would first like to shine a light on the role of our ecosystem, who play a critical role in enabling physical AI in complex operational environments. How our partners help accelerate and scale Physical AI deployments We recently had a partner, Sight Machine, accelerate a customer outcome by reducing their deployment timeline by about 90% using a validated, repeatable solution built on adaptive cloud architectural patterns. This is not an uncommon outcome. Our partners work to extend Azure IoT's capabilities with end-to-end solutions that give manufacturers the confidence to standardize once and deploy everywhere with security, governance, and repeatability built in. Advantech At HMI, Advantech is showcasing its LoRaWAN industrial sensing portfolio, including sensors connected through the WISE‑6610 LoRaWAN gateway. The gateway aggregates telemetry from distributed sensors and publishes it via MQTT, enabling seamless integration with Azure IoT Operations and downstream Azure cloud services. Learn more here and drop by our booth to see it in action as part of the hero demo. Celebal Tech At HMI, Celebal Tech is showcasing how its UniPlant platform integrates with Azure IoT Hub and Azure IoT Operations to harmonize fragmented OT data from machines, SCADA, PLCs, and MES systems into ISA 95 aligned, enterprise ready models. By transforming real time industrial telemetry into contextualized KPIs and operational insights, the joint solution enables unified plant visibility, predictive maintenance workflows, and AI ready data foundations across production environments. Stop by the Microsoft booth or CT’s booth A02 in Hall 16 to see how Celebal Tech and Microsoft are helping manufacturers scale intelligent operations with trusted, decision grade industrial data powered by Azure IoT. Helin Helin has built its edge‑to‑cloud industrial operations platform on Azure IoT Hub, orchestrating secure device connectivity and streaming large‑scale industrial telemetry into Microsoft Fabric and Azure Databricks to power real‑time operational intelligence for energy and maritime customers. As an early validation partner for Azure Device Registry (ADR) and Microsoft-backed certificate management, Helin is helping shape the future of unified asset identity and fleet‑scale device lifecycle management across distributed industrial environments. Meet Helin at Hannover Messe to learn how they're advancing unified asset identity across industrial fleets, learn more here. Litmus Automation At Hannover Messe, Litmus is announcing Litmus Edge Bridge for Azure IoT Operations, enabling automated, real-time discovery, cataloging, and onboarding of industrial assets. When Litmus Edge detects a new PLC, sensor, or controller, it becomes visible in Azure IoT Operations and can be onboarded with a single click – no manual mapping, scripting, or custom pipelines required. Built on the open-source Akri framework, this integration provides Azure-native representation of devices and their data models, enabling OT and IT teams to bring industrial data into Azure in a consistent, governed way. Learn more here and stop by the Litmus booth (Hall 16, booth A09) to see a live demo. Mesh Systems Mesh Systems is showcasing its Akri‑based industrial connectivity architecture at Hannover Messe 2026, designed to enable flexible integration across new and existing OT assets. Built to align with Azure IoT Operations and Kubernetes‑based edge architectures, Mesh’s framework provides a scalable way to onboard industrial protocols at the customer site and route operational data across edge‑to‑cloud environments, accelerating time to value for downstream AI‑driven workflows. As a trusted Azure IoT partner, Mesh delivers end‑to‑end implementation to help customers move from connectivity to production‑ready, data‑driven operations. Read their announcement press release here. NVIDIA Microsoft and NVIDIA are partnering to accelerate customers’ adoption of Physical AI through two new collaborative efforts unveiled at GTC. A public Azure Physical AI Toolchain GitHub repository - integrated with the NVIDIA Physical AI Data Factory and core Azure services - enables developers to build, train, and operate robotics and physical AI workflows that connect physical assets, simulation environments, and cloud‑based training into repeatable, enterprise‑grade pipelines. In addition, a deeper integration between Microsoft Fabric and NVIDIA Omniverse libraries connects live operational data with physically accurate digital twins and simulation, allowing organizations to monitor physical systems in real time and use AI‑driven insights to inform next‑best actions. These capabilities will be brought to life at HMI in Microsoft’s Factory of the Future demo. Rockwell Automation Rockwell Automation and Microsoft are advancing an established adaptive cloud pattern for scalable industrial AI. FactoryTalk Optix captures and contextualizes OT data at the edge, while Azure IoT Operations provides consistent governance and lifecycle management across site deployments through Azure’s control plane. Together, Rockwell and Microsoft are co-innovating to do information model discovery and synchronization at the edge to bring agent-ready data to cloud. Stop by the Microsoft booth at HMI to learn how the joint architecture enables scalable industrial AI deployments from factory floor to cloud analytics. Sight Machine In 2025, Sight Machine integrated its industrial AI platform with Azure IoT Operations and Microsoft Fabric to turn fragmented plant data into contextualized, production-ready insights. Its unified marketplace offering for industrial data ingestion, streaming, and AI analysis helps manufacturers standardize OT data at scale and move from pilot to production in weeks. This is proven in the field: a major global bottler moved from setup to full rollout in under two months using the joint solution, and many manufacturers across industries are seeing similar gains while realizing their industrial AI goals. Toyota Industries Corporation (TICO) reports improved paint shop quality with AI-powered defect detection with Sight Machine and Azure IoT Hub. Join Sight Machine’s MSFT booth theatre session at HMI (Mon, April 20, 2:30 PM) to learn more - or explore their solution here. Siemens Siemens Industrial Edge and Azure IoT help manufacturers move from fragmented OT environments to unified, insight‑driven operations across sites. By standardizing how industrial data is captured and governed from edge to cloud through Siemens’ Industrial Edge Management (IEM) and Azure IoT Operations, customers can reuse operational data across analytics, AI models, and digital twins without re‑architecting underlying systems. The joint solution accelerates time to value, reduces integration effort, and enables real‑time optimization, predictive maintenance, and closed‑loop quality across production environments. Join the theatre session on April 22 at 9:45am in Microsoft’s booth to learn how Siemens and Microsoft are enabling scalable industrial AI in production environments. Conclusion As manufacturers scale AI from pilots to production, success depends on a foundation that connects operational data, applies AI where it’s needed, and governs everything consistently from edge to cloud. At Hannover Messe 2026, we’re proud to share how Microsoft and our partners are helping customers run AI powered factories with an adaptive cloud approach - so teams can move faster with confidence, improve uptime, and turn real-time insights into action. To learn more: Visit us at Hannover Messe 2026 in Hall 17, Booth G06 to explore the latest partner innovations across Azure IoT Operations, Azure IoT Hub, Foundry Local, and Azure Local. Not attending in person this year? Reach out to your Microsoft account team to find the right solution for your environment. Read the next blog in this series that details the latest product innovations we will be sharing at Hannover Messe 2026: Making Physical AI Practical for Real-World Industrial Operations: Part 2 See full list of our industrial ecosystem partners here: Microsoft Industrial AI Partner Guide: Choosing the Right Data Expertise for Every StageMaking Physical AI Practical for Real-World Industrial Operations: Part 2
In my previous blog, I talked about how we collaborate with great partners such as Sight Machine, Litmus, Mesh Systems, Siemens, Rockwell, Schneider Electric, and others to deliver end to end value for the practical application of AI in manufacturing environments. These partners, along with forward-thinking customers like Chevron, Husqvarna and Ecopetrol continue to drive our innovation roadmap and push the boundaries of how to use Agentic AI for operational efficiency improvements, visual inspection, and safety enhancements. How Ecopetrol is modernizing its data platform to take advantage of AI As an integrated energy conglomerate, Ecopetrol operates across the entire hydrocarbon chain encompassing exploration, production, transportation, refining, and commercialization, as well as linear infrastructure, including energy transmission and road concessions. The company is dedicated to leading the energy sector into a more sustainable future by adopting technology that enables intelligent operations. Ecopetrol has partnered with Microsoft to build a flexible and secure edge to cloud platform, based on Azure IoT Operations and Fabric Real-Time Intelligence, that can standardize data across diverse sources to enable data contextualization and eventually, AI integration. This improved ability to harness data can help Ecopetrol meet key objectives such as improved operational performance, cost savings, lowered energy consumption, and reduced carbon emissions. New innovations introduced at Hannover Messe 2026: Microsoft’s Industrial AI platform has been purpose-built to support edge and physical AI scenarios. It offers a comprehensive foundation to build, scale, and govern Industrial AI initiatives with a unified intelligence layer powering AI (Fabric IQ, Foundry IQ, Work IQ) and a consistent framework to managing apps, data and infrastructure with the adaptive cloud approach. Looking more closely at how these components come together to enable business outcomes: Azure IoT Operations and Azure IoT Hub collect real-time data from operational assets and devices and send semantically-ready modelled data to Fabric IQ so that it can be contextualized with other enterprise data sources for downstream analytics. Microsoft Foundry has been extended to the edge with Foundry Local so that organizations can use the same tooling that they use to deploy and manage AI models in the cloud for edge use cases as well. Azure IoT Operations, Azure IoT Hub, and Foundry Local integrate into Azure Resource Manager, which brings OT devices, assets, and edge AI models into the same management and security paradigm as all other Azure managed resources. For organizations with sovereignty requirements, Microsoft enables Sovereign Private Cloud with Azure Local, which can run in connected or disconnected mode, depending on customer requirements. At HMI 2026, we are announcing our next set of innovations in this space to help manufacturers and partners initiate and scale industrial AI initiatives on a trusted foundation. Unlocking value from operational data Azure IoT Operations, enabled by Azure Arc, is a set of scalable edge services, built on industry standards to easily capture device and equipment data, process and normalize it at the edge, seamlessly send and receive operational insights to and from the cloud, and contextualize that data so it can be used directly by Physical AI workloads running at the edge. Through Arc and Kubernetes, Azure IoT Operations empowers our customers with a unified technology architecture and data plane that supports repeatable solution deployment, automated updates to apps, cost-effective high availability, and redundancy at the edge. At HMI 2026, we are announcing the next major release of Azure IoT Operations, 2603. This release enables manufacturers to build, manage, and operate industrial data flows across the full edge-cloud lifecycle without custom code. Key new capabilities include edge-to-cloud industrial data management with no-code visual data pipelines, cloud-to-edge device and asset command and control, unified health status and observability, as well as new connector integrations for third-party MQTT brokers and Litmus Edge industrial gateways. Furthering our commitment to open standards, we also recently announced support for WC3 Web of Things (WoT) in Azure IoT Operations, which simplifies the process of integrating industrial assets into intelligent applications. Agentic operations at the edge Foundry Local enabled by Azure Arc extends cloud grade AI inference to on-premises and edge environments. It allows organizations to deploy, run, and manage generative and predictive AI models directly on customer-controlled infrastructure, such as factory floors, remote industrial sites, and disconnected environments, where low latency, data locality, and operational autonomy are critical. The solution builds on Azure Arc-enabled Kubernetes as a unified control plane, enabling AI workloads to be deployed and operated locally using the same paradigms as in the cloud. Today, we are excited to announce Foundry model catalog in Azure Local, which supports both curated open-source models from a managed catalog and customer proprietary bring-your-own-model (BYOM) deployments. Models can run concurrently across available on-premises hardware, on CPU-only systems or with GPU acceleration, so customers can match performance and cost requirements across diverse edge environments. AI models are delivered as containerized services, exposing standard REST endpoints, including OpenAI compatible APIs for generative models and dedicated APIs for predictive workloads. This allows applications to consume local AI inference in the same way they consume cloud AI services, with minimal changes. New capabilities for secure policy and identity management While properly contextualized data and AI hold the key to optimizing business outcomes, organizations cannot risk rolling out these initiatives without the proper management and security foundation in place. Taking an adaptive cloud approach for these capabilities is also crucial, to ensure organizations have the right level of visibility, control, and protection across their entire digital and physical domain. Azure IoT Hub is Microsoft’s key offering to connect and manage IoT devices and assets with direct connections to the cloud. In November, we announced the public preview of Azure IoT Hub integration with Azure Device Registry which brought IoT devices under the purview of the Azure management plane (ARM, Azure resource manager) and allowed them to be secured with best-in-class Microsoft-backed X.509 certificate management capabilities. Today, we are expanding upon that preview with strengthened device identity, security, and fleet‑scale management. This refresh delivers a more complete, end‑to‑end certificate management experience, covering certificate issuance, renewal, and revocation, with support for hybrid trust models, including customer‑managed root CAs from non‑Microsoft PKIs. It also introduces a more cohesive Azure Portal experience for service configuration and device operations, allowing operators to manage devices consistently as ADR resources using standard Azure tooling and workflows. Firmware analysis capabilities Another critical security consideration for customers is the security profile of the device itself. With firmware analysis, enabled by Azure Arc, our goal is to provide deeper visibility into IoT/OT and network devices by analyzing the foundational software (firmware) they run. At HMI, we are releasing a preview of integration of firmware analysis with Azure Device Registry, delivering fleet-level visibility into where firmware vulnerabilities exist across deployed IoT and OT environments. This new integration correlates analyzed firmware images with devices and assets registered in Azure Device Registry, allowing customers with both Azure IoT Operations and IoT Hub to quickly see how many devices are running a given firmware image and which specific assets may be exposed to known security risks, bridging the gap between firmware insights and real-world operational impact. This release also offers new capabilities to help customers prioritize vulnerabilities, work with larger firmware images, and share security analysis results with supply chain partners. Sovereign options for mission-critical workloads While security continues to be a strategic priority for most large, global organizations, digital sovereignty is an increasingly critical requirement for many manufacturers as well. For these scenarios, Microsoft offers capabilities that support customers across connected, intermittently connected and fully disconnected modes. With Azure Local disconnected, organizations can now run mission-critical infrastructure with Azure governance and policy control, with no cloud connectivity, optimizing continuity for sovereign, classified, or isolated environments. With Azure Local disconnected operations, management, policy, and workload execution stay within the customer-operated environments, so services continue running securely even when environments must be isolated or connectivity is not available. Using familiar Azure experiences and consistent policies, organizations can deploy and govern workloads locally without depending on continuous connection to public cloud services. Azure Local is designed to scale with mission-critical needs from smaller deployments to larger footprints that support data-intensive and AI-driven workloads. Conclusion As a leading forum for industrial innovation, Hannover Messe provides manufacturers with an opportunity to explore the latest technologies transforming modern operations. This year’s theme, “Think Tech Forward,” aligns with the industry’s growing emphasis on applying proactive, AI‑driven intelligence across business processes and ecosystems. Join Microsoft in Hall 17, Booth G06 to discover practical approaches for implementing AI to improve operational outcomes. Learn more about Microsoft’s overall presence at the show here. For a deeper dive into how Microsoft is driving industrial outcomes with partners, please refer to the first blog in this series: Making Physical AI Practical for Real-World Industrial Operations: Part 1 holderAzure IoT Hub + Azure Device Registry (Preview Refresh): Device Trust and Management at Fleet Scale
What’s New in this Preview In November 2025, we announced the preview integration of Azure IoT Hub with Azure Device Registry, marking a huge step towards integrating IoT devices into the broader Azure ecosystem. We’re grateful to the customers and partners who participated in the preview and shared valuable feedback along the way. Today, we’re expanding the preview with new capabilities to strengthen security, improve fleet management, and simplify development for connected devices. With this refresh, preview customers can: Automate device certificate renewals with zero-touch, at-runtime operations to minimize downtime and maintain a strong security posture. Integrate existing security infrastructure like private certificate authorities with your Azure Device Registry namespace. Leverage certificate revocation controls to isolate device or fleet-level risks and maintain operational continuity Utilize an improved Azure Portal experience for streamlined configuration and lifecycle management of your devices. Accelerate solution development with expanded IoT Hub and DPS Device SDK compatibility for smoother integration and faster time to value. Together, these enhancements help organizations to secure, govern, and manage their IoT deployments using familiar Azure-native tools and workflows. Why this matters: From Connected Devices to Connected Operations Operational excellence begins by bridging the gap between physical assets and digital intelligence. Consider a global logistics fleet where every vehicle is more than just a machine; it is a trusted, connected, and manageable digital entity in the cloud. As these assets move, they emit a continuous stream of telemetry - from engine vibrations to fuel consumption – directly to a unified data ecosystem, where AI agents can reason over it with greater context. Instead of waiting for a breakdown, these agents detect wear patterns, cross-reference with digital twins, and provide recommendations to reroute a vehicle for service before a failure occurs. This completes a shift from reactive troubleshooting to proactive physical operations. Yet, for many organizations, this transformation is often stalled by fragmented systems where security policies, device registries, and data streams exist in silos. Overcoming this requires a sophisticated stack designed to establish trust, manage device lifecycles, and orchestrate data flows at a global scale: The Digital Operations stack for cloud-connected devices This journey starts with having a secure foundation for fleet management. In an era where perimeter security is no longer enough, organizations need an identity foundation that is both hardware-rooted and deeply integrated with device provisioning. Utilizing robust X.509 certificate management, where keys and credentials are anchored in tamper-resistant hardware, provides high-assurance system integrity across millions of endpoints. Once trust is established, Azure Device Registry creates a unified management plane, where devices are represented as first-class Azure resources, enabling ARM-based fleet management, role-based access control for lifecycle operations, and Azure Policy for enforcement. Simultaneously, IoT Hub provides secure, bidirectional messaging for at-scale fleets. This high-fidelity data provides the essential fuel for Physical AI. By streaming trusted telemetry into Microsoft Fabric, organizations can break down data silos and allow AI agents to reason over real-world events in a centralized analytics environment. The Azure IoT stack provides the essential bridge for cloud-connected devices, enabling customers to transform their industrial environments into highly secure and intelligent ecosystems. For more information on Azure's approach to industrial AI, check out: Making Physical AI Practical for Real-World Industrial Operations. Azure IoT Hub + ADR (Preview): Expanding Fleet and Certificate Lifecycle Management The April 2026 Preview for Azure IoT Hub and Azure Device Registry (ADR) deliver key features to further standardize device identity and enable policy‑driven management for certificates at scale. You can think of device identity in Azure Device Registry like the birth record of a person. When someone is born, certain information becomes permanently associated with them - such as their date and place of birth. In the same way, a device’s identity represents its immutable existence within your solution - things like its serial number, model, or ownership context. However, as that person moves through life, they obtain different credentials that allow them to prove who they are in different situations - such as a driver’s license or passport. These credentials may expire, be renewed, or even replaced entirely over time without changing the person’s underlying identity. In IoT, devices use X.509 certificates as their credential to prove identity to services like IoT Hub. In your Azure Device Registry namespace, you can define the public key infrastructure (PKI) that manage your X.509 certificates and certificate authorities (CAs). In this preview, we are making it easier to integrate with existing security infrastructure and manage certificates at fleet scale. Certificate Management for Cloud-connected Devices in Azure Bring Your Own Certificate Authority (BYO CA) in Azure Device Registry Organizations that already operate sophisticated certificate authorities, with well‑established compliance controls, audit processes, and key custody requirements, want to integrate their trusted CA with the Azure Device Registry operating model. With BYO CA, customers can use their own private certificate authority while still benefiting from Azure’s fully managed device provisioning, and lifecycle management. Azure handles the heavy lifting of issuing, rotating, and revoking issuing certificate authorities (ICAs) and device certificates - while you stay in control of the top-most CA. Full Ownership of Trust and Keys: By bringing their own CA, organizations maintain absolute control over their private keys and security boundaries. Azure never takes custody of the external CA, ensuring existing governance, auditability, and compliance controls remain fully intact. Automated Lifecycle Management: While the CA remains customer-owned, Azure Device Registry automates the issuance, rotation, and revocation of device certificates. This eliminates the need for custom tooling or manual, per-device workflows that typically slow down deployments. Bring your own Certificate Authority in Azure Device Registry Fleet‑Wide Protection with Certificate Revocations Revocation is a mechanism for selective isolation, used to contain a single or group of devices by decommissioning a single device's certificates or the entire anchor of trust. When a single device is compromised, lost, or retired, device certificate revocation enables a precise, targeted response. This allows organizations to isolate individual devices instantly, reduce blast radius, and maintain uninterrupted operations for healthy devices - without rebuilding device identities. ADR propagates the revocation state to IoT Hub, blocking revoked devices until they’re re-provisioned. When a subset of devices requires isolation, policy revocation allows operators to decommission an entire trust anchor rather than managing individual devices. By mapping a specific Issuing CA to a single ADR policy, organizations gain a high-precision containment mechanism. In a single action, an operator can invalidate a compromised CA and then plan for a staged credential rollover across the entire segment. ADR automatically enforces this updated trust chain within IoT Hub, ensuring that only devices with newly issued certificates can connect. This makes large‑scale certificate rotation predictable, controlled, and operationally simple. Revoking the certificate for a single ADR Device on Azure Portal Flexible Options to renew Device Certificates Managing X.509 certificates at scale doesn’t stop once a device is onboarded. Operational certificates are short-lived by design, ensuring devices do not rely on long-lived credentials for authentication. In real-world IoT fleets, devices are often intermittently connected, deployed in hard-to-reach locations, and expected to run continuously - making certificate renewal one of the most operationally challenging parts of device security. Azure IoT Hub now enables device certificate renewal directly through IoT Hub, complementing the role of Device Provisioning Service (DPS). While DPS remains the solution for first-time device onboarding and certificate issuance, IoT Hub renewal is designed for the steady state - keeping already-connected devices securely authenticated over time without introducing downtime. IoT Hub certificate renewal follows similar patterns as other device-initiated operations such as twin updates and direct methods. With this capability, devices can request a new certificate as part of normal operation, using the same secure MQTT connection they already rely on. Support for IoT Hub and Device Provisioning Service (DPS) Device SDKs Managing credential issuance and renewals at scale is only possible if devices can handle their own credential lifecycles. We’ve added Certificate Signing Request (CSR) support to our C, C# (.NET), Java, Python, and Embedded device SDKs for IoT Hub and Device Provisioning Service (DPS). Beyond developer convenience, this provides multiple device-initiated paths for certificate renewal and trust-chain agility. Devices can generate CSRs and request newly signed X.509 certificates through IoT Hub or DPS as part of normal operation. This allows security teams to rotate and update certificates in the field without touching the hardware, keeping fleets secure as certificate authorities and policies evolve over time. Customer Feedback from Preview We’re grateful to the customers and partners who participated in the preview and shared valuable feedback along the way. Hear some of what our customers had to say: "The availability of a built-in certificate manager is a great upgrade in keeping the IoT space more secure."— Martijn Handels, CTO, Helin Data “Secure data is the starting line for industrial AI. With Azure certificate management, at CogitX we can ingest manufacturing signals safely and confidently - then use domain‑aware models to deliver real‑time insights and agentic workflows that improve throughput, quality, and responsiveness.” – Pradeep Parappil, CEO, CogitX Get Started Explore the new capabilities in preview today and start building the next generation of connected operations with Azure IoT Hub and Azure Device Registry: Get Started with Certificate Management in Preview.Advancing Firmware Security: Fleet Visibility and New Capabilities in Firmware Analysis
When we announced general availability of firmware analysis enabled by Azure Arc last October, our goal was clear: help organizations gain deep visibility into the security of the firmware that powers their IoT, OT, and network devices. Since then, adoption has continued to grow as customers use firmware analysis to uncover vulnerabilities, inventory software components, and secure their software supply chain. Leading into the Hannover Messe (HMI) 2026 conference, we’re excited to share the next wave of firmware analysis capabilities, delivering enhancements that help customers connect firmware risk to real-world fleet impact, prioritize vulnerabilities more effectively, scale to larger and more complex firmware images, and expand security analysis for UEFI-based platforms. These updates are driven directly by customer feedback and by the rapidly evolving threat landscape facing embedded and edge devices. Connecting Firmware Risk to Your Deployed Fleet with Azure Device Registry (Preview) Securing connected devices doesn’t stop at identifying vulnerabilities in firmware—it requires understanding where those vulnerabilities exist in your deployed fleet and which devices are affected. We’re excited to announce a new preview integration between firmware analysis enabled by Azure Arc and Azure Device Registry, bringing fleet-level visibility of IoT and OT devices directly into the firmware analysis experience. This helps customers quickly understand how many devices and assets are running a given firmware image, and which ones may be exposed to known security issues. From firmware insights to fleet impact Firmware analysis helps customers uncover security risks hidden deep inside the firmware running IoT, OT, and network devices—risks such as known CVEs, outdated open-source components, weak cryptography, and insecure configurations. Until now, these insights were primarily scoped to the firmware image itself. With this new preview integration, firmware analysis now connects directly to Azure Device Registry, allowing customers to: See how many devices from IoT Hub integration with ADR (preview) and assets from Azure IoT Operations are associated with a specific analyzed firmware image Understand the real-world blast radius of vulnerabilities discovered in firmware Quickly identify which devices may require patching, mitigation, or isolation This preview bridges an important gap between security analysis and operational decision-making. What’s included in this preview With this release, we’re introducing new fleet-level context directly into the firmware analysis experience: A new Devices + Assets count column in the firmware analysis workspace showing how many Azure Device Registry devices and assets are running each analyzed firmware image A click-through experience that lets users view the list of affected devices and assets in Azure Device Registry Visibility spanning both: Devices connected via IoT Hub Assets managed through Azure IoT Operations This information is derived by correlating firmware metadata with device and asset inventory in Azure Device Registry, giving customers immediate insight into deployment exposure. Key use cases Identify vulnerable devices at scale: When critical CVEs are discovered in a firmware image, customers can immediately see how many deployed devices are impacted—without manually correlating spreadsheets, tools, or inventories. Prioritize remediation actions: With fleet visibility, teams can decide whether to patch devices, temporarily isolate affected devices from the network, or disable devices that pose unacceptable risk. Bridge security and operations teams: Security teams gain clear insight into where vulnerabilities exist, while operations teams can quickly act on specific devices and assets—all within the Azure portal. This integration is especially valuable in environments where downtime, safety, or regulatory compliance matter—such as manufacturing, energy, telecommunications, and critical infrastructure. Prioritizing Vulnerabilities with Enhanced CVE Metadata (Preview) The number of publicly disclosed vulnerabilities continues to rise year over year, making it increasingly difficult for security teams to determine which CVEs truly require urgent action. Simply knowing that a vulnerability exists is no longer enough—teams need context to prioritize remediation efforts. With this release, firmware analysis now provides richer metadata for each discovered CVE, helping customers focus on vulnerabilities that pose the greatest real-world risk. New CVE metadata includes: CISA Known Exploited Vulnerabilities (KEV) status – Indicates whether a CVE is listed in the CISA KEV catalog, signaling that the vulnerability is actively exploited in the wild. EPSS score (Exploit Prediction Scoring System) – A data-driven probability score that estimates the likelihood of a vulnerability being exploited in the next 30 days, complementing traditional severity metrics by focusing on exploitation likelihood rather than impact alone. Additional vulnerability context, including CVSS vectors and base scores, CWE classifications, and expanded metadata to support filtering and analysis. Together, these enhancements make it easier to triage findings, align remediation with risk, and communicate priorities across security, engineering, and product teams. Faster Performance for Large and Complex Firmware Images As firmware analysis adoption has grown, we’ve seen customers analyze increasingly large and complex firmware images—particularly in domains like networking equipment, where a single image can generate thousands of findings. To support these scenarios, we’ve made architectural enhancements to the service that significantly improve performance when working with large result sets. Key improvements include: Up to 90% reduction in load times of analysis results, especially for firmware images producing 10,000+ findings More responsive filtering and exploration of results These changes ensure that firmware analysis remains fast and usable at scale, even for complex network and infrastructure firmware images. Expanding UEFI Firmware Analysis (Preview) Modern devices increasingly rely on UEFI firmware as a foundational security boundary. In this release, we’re expanding our UEFI analysis capabilities to provide deeper visibility into UEFI executables and components. New UEFI-focused capabilities include: Detection of OpenSSL libraries and related CVEs within UEFI firmware Binary hardening analysis for UEFI executables, including detection of proper configuration of Data Execution Prevention (DEP) memory protection Continued support for discovering cryptographic material in UEFI images, including embedded certificates and keys This preview allows customers to evaluate the new capabilities, provide feedback, and help shape future enhancements in this area. Note: UEFI SBOM and binary analysis features are currently in preview and intended for evaluation and feedback. Bulk Export of Analysis Results for Supply Chain Collaboration We also recently released a highly requested feature that makes it easier to share firmware analysis results with partners and suppliers. Customers can now: Bulk download analysis results across one or more firmware images Export results as CSV files packaged into a ZIP archive This capability simplifies workflows such as sharing findings with device manufacturers or firmware suppliers, integrating results into downstream analysis or reporting pipelines, and supporting software supply chain security and compliance processes. Looking Ahead We’re excited about the progress we’ve made with this release and what it means for customers securing IoT, OT, and network devices. From connecting firmware risk to fleet-level impact with Azure Device Registry, to richer vulnerability prioritization, improved scalability, and deeper UEFI analysis—these enhancements reinforce firmware analysis as a critical tool for addressing some of the most challenging blind spots in modern infrastructure security. Firmware security is foundational to trustworthy systems—especially as edge devices continue to play a central role in industrial operations, networking, and data collection. If you’re already using firmware analysis and Azure Device Registry, the ADR integration preview will appear directly within the firmware analysis experience as it rolls out. We look forward to your feedback as we continue building secure, observable, and manageable digital operations with Azure. As always, we value your feedback, so please let us know what you think.W3C Web of Things (WoT) support in Azure IoT Operations
Integration challenges often pose a barrier to the ability to scale industrial solutions. When new or updated assets show up having a new protocol, a slightly different telemetry shape, or an undocumented interface, teams end up rewriting glue code and retesting end-to-end pipelines. Azure IoT Operations reduces that friction by providing a unified data plane at the edge: modular services running on Azure Arc-enabled Kubernetes, with an edge-native MQTT broker as the backbone for reliable, event-driven architectures. Key concepts Azure IoT Operations is Microsoft’s edge platform for running IoT services on Kubernetes via Azure Arc. MQTT is the pub/sub messaging protocol Azure IoT Operations uses for event-driven data movement. OPC UA is a common industrial connectivity standard that can expose rich information models, but many assets don’t implement it directly. W3C Web of Things (WoT) standardizes machine-readable descriptions of an asset’s interface via a “Thing Model.” We’re announcing a key step toward open, model-driven interoperability in Azure IoT Operations: W3C Web of Things (WoT) is now a first-class modeling input for developer workflows, backed by the Azure IoT Operations SDKs and the code generation (codegen) v2 toolchain. Why WoT in Azure IoT Operations? Azure IoT Operations already emphasizes open standards such as MQTT and OPC UA to foster interoperability across OT and IT systems while staying Kubernetes-native and scalable. In practice, though, many assets cannot natively present an OPC UA information model and integration documentation still often arrives as a static PDF. To scale deployments, teams need a machine-readable asset description they can use for automated onboarding and repeatable pipelines. WoT enables that path for non-OPC UA assets: instead of relying on a PDF, vendors (or integrators) can provide a WoT Thing Model that describes the asset’s telemetry, commands, and properties so onboarding and integration can be automated. What’s included The Azure IoT Operations SDKs are a set of tools and libraries (across multiple languages) for building and extending solutions. Within that toolbox, the Protocol Compiler is the centerpiece: it takes an interface model as input and generates client and server code so you can focus on business logic instead of message plumbing. With WoT support, you can use a WoT Thing Model as that input to generate code stubs for telemetry and for mRPC (message-based remote procedure calls used for service-to-service interactions in Azure IoT Operations). If you’re coming from the DTDL (Digital Twins Definition Language) world, the workflow will feel familiar: the Protocol Compiler takes a model as input and outputs generated client/server libraries in your target language. When an asset interface and data model are expressed as a WoT Thing Model, you can treat that model as the contract. Generated code then enforces the expected payload shapes for telemetry and mRPC interactions, reducing bespoke glue code and lowering the risk of mismatched or undocumented data. Eclipse ediTDor as a practical editor for WoT Thing Models A model-first workflow only works if authoring is approachable. Eclipse ediTDor is an open-source, web-based editor that helps you create and validate W3C WoT Thing Models, including export to JSON-LD (a standard JSON format for linked data). It is hosted by the Eclipse Foundation, and you can try it here: Eclipse ediTDor. WoT as the asset description that unlocks automation Putting it all together, a typical workflow looks like this: Start with a WoT Thing Model for the asset (from the vendor, a partner, or authored in-house). Open the model in Eclipse ediTDor to review, validate, and refine it. Use the Protocol Compiler (codegen v2) to generate client/server code stubs for telemetry and mRPC interactions. Deploy your application into an Azure IoT Operations environment running on Azure Arc-enabled Kubernetes and integrate with data services via the built-in MQTT broker. Getting Started If you want to explore this further, here are the key starting points: Azure IoT Operations SDKs overview and quick start: [Azure IoT Operations Developer Guide] Codegen V2 in the SDK repo: Azure IoT Operations SDK Eclipse ediTDor for WoT authoring: Edi{td}or Azure IoT Operations product overview: [What Is Azure IoT Operations] Conclusion With WoT support in Azure IoT Operations, we continue our commitment of building an open, standardized ecosystem where machine-readable asset descriptions are a first-class input to onboarding and development. Combined with the Protocol Compiler and practical authoring options like Eclipse ediTDor, it becomes feasible to go from an asset description to running code with significantly less integration friction.
