industry
25 TopicsAnnouncing the Firmware Analysis Public Preview
Consider an organization with thousands of smart sensors, IoT/OT and network equipment deployed on factory floors. Most of these devices are running full operating systems, but unlike traditional IT endpoints which often run security agents, IoT/OT and network devices frequently function as “black boxes”: you have little visibility into what software they’re running, which patches are applied, or what vulnerabilities might exist within them. This is the challenge many organizations face with IoT/OT and networking equipment - when a critical vulnerability is disclosed, how do you know which devices are at risk? To help address this challenge, we are excited to announce the public preview of firmware analysis, a new capability available through Azure Arc. This extends the firmware analysis feature we introduced in Microsoft Defender for IoT, making it available to a broader range of customers and scenarios through Azure. Our goal is to provide deeper visibility into IoT/OT and network devices by analyzing the foundational software (firmware) they run. Firmware analysis will also help companies that build firmware for devices better meet emerging cybersecurity regulations on their products. In this post, we’ll explain how the service works, its key features, and how it helps secure the sensors and edge devices that feed data into AI-driven industrial transformation. Securing Edge Devices to Power AI-Driven Industrial Transformation In modern industrial environments, data is king. Organizations are embracing Industry 4.0 and AI-driven solutions to optimize operations, leveraging advanced analytics and machine learning. The path to AI-driven industrial transformation is fueled by data – and much of that data comes from sensors and smart devices at the edge of the network. These edge devices measure temperature, pressure, vibration, and dozens of other parameters on the factory floor or in remote sites, feeding streams of information to cloud platforms where AI models turn data into insights. In fact, sensors are the frontline data collectors in systems like predictive maintenance, continuously monitoring equipment and generating the raw data that powers AI predictions. However, if those edge devices, sensors, and networking equipment are not secure and become compromised, the quality and reliability of the data (and thus the AI insights) cannot be guaranteed. Vulnerable devices can also be used by attackers to establish a foothold in the network, allowing them to move laterally to compromise other critical systems. In an industrial setting this could mean safety hazards, unplanned downtime, or costly inefficiencies. This is why securing the smart devices and networking equipment at the foundation of your industrial IoT data pipeline is so critical to digital transformation initiatives. By using firmware analysis on the devices’ firmware before deployment (and regularly as firmware updates roll out), the manufacturer and plant operators gain visibility into the security posture of their environment. For example, they might discover that a particular device model’s firmware contains an outdated open-source library with a known critical vulnerability. With that insight, they can work with the vendor to get a patched firmware update before any exploit occurs in the field. Or the analysis might reveal a hard-coded passwords for maintenance account in the device; the ops team can then ensure those credentials are changed or the device is isolated in a network segment with additional monitoring. In short, firmware analysis provides actionable intelligence to fortify each link in the chain of devices that your industrial systems depend on. The result is a more secure, resilient data foundation for your AI-driven transformation efforts – leading to reliable insights and safer, smarter operations on the plant floor. Firmware analysis is also a key tool used by device builders – by analyzing device firmware images before they are delivered to customers, builders can make sure that new releases and firmware updates meet their and their customers’ security standards. Firmware analysis is a key component to address emerging cybersecurity regulations such as the EU Cyber Resilience Act and the U.S. Cyber Trust Mark. How Firmware Analysis Works and Key Features Firmware analysis takes a binary firmware image (the low-level software running on an IoT/OT and network device) and conducts an automated security analysis. You can upload an unencrypted, embedded Linux-based firmware image to the firmware analysis portal. The service unpacks the image, inspects its file system, and identifies potential hidden threat vectors – all without needing any agent on the device. Here are the main capabilities of the firmware analysis service: Identifying software components and vulnerabilities: The first thing the analysis does is produce an inventory of software components found inside the firmware, generating a Software Bill of Materials (SBOM). This inventory focuses especially on open-source packages used in the firmware. Using this SBOM, the service then scans for known vulnerabilities by checking the identified components against public Common Vulnerabilities and Exposures (CVEs) databases. This surfaces any known security flaws in the device’s software stack, allowing device manufacturers and operators to prioritize patches for those issues. Analyzing binaries for security hardening: Beyond known vulnerabilities, our firmware analysis examines how the firmware’s binaries were built and whether they follow security best practices. For example, it checks for protections like stack canaries, ASLR (Address Space Layout Randomization), and other compile-time defenses. This “binary hardening” assessment indicates how resistant the device’s software might be to exploitation. If the firmware lacks certain protections, it suggests the device could be easier to exploit and highlights a need for improved secure development practices by the manufacturer. In short, this feature acts as a gauge of the device’s overall security hygiene in its compiled code. Finding weak credentials and embedded secrets: Another critical aspect of the analysis is identifying hard-coded user accounts or credentials in the firmware. Hard-coded or default passwords are a well-known weakness in IoT devices – for instance, the Mirai botnet famously leveraged a list of over 60 factory-default usernames and passwords to hijack IoT devices for DDoS attacks. Firmware analysis will flag any built-in user accounts and the password hash algorithms used, so manufacturers can remove or strengthen them, and enterprise security teams can avoid deploying devices with known default credentials. Additionally, the firmware analysis looks for cryptographic materials embedded in the image. It will detect things like expired or self-signed TLS/SSL certificates, which could jeopardize secure communications from a device. It also searches for any public or private cryptographic keys left inside the firmware – secrets that, if found by adversaries, could grant unauthorized access to the device or associated cloud services. By uncovering these hidden secrets, the service helps eliminate serious risks that might otherwise go unnoticed in the device’s software. All these insights – from software inventory and CVEs to hardening checks and secret material detection – are provided in a detailed report for each firmware image you analyze. Firmware analysis provides deep insights, clear visibility, and actionable intelligence into your devices' security posture, enabling you to confidently operate your industrial environments in the era of AI-driven industrial transformation. Getting Started and What’s Next If you have IoT/OT and network devices in your environment, use firmware analysis to test just how secure your devices are. Getting started is easy: access firmware analysis public preview by searching on “firmware analysis” in the Azure portal, or access using this link. In the future, firmware analysis will be more tightly integrated into the Azure portal. Onboard your subscription to the preview and then upload firmware images for analysis - here is a step-by-step tutorial. The service currently supports embedded Linux-based images up to 1GB in size. In this preview phase, there is no cost to analyze your firmware – our goal is to gather feedback. We are excited to share this capability with you, as it provides a powerful new tool for securing IoT/OT and network devices at scale. By shedding light on the hidden risks in device firmware, firmware analysis helps you protect the very devices that enable your AI and digital transformation initiatives. Firmware is no longer just low-level code—it’s a high-stakes surface for attack, and one that demands visibility and control. Firmware analysis equips security teams, engineers, and plant operators with the intelligence needed to act decisively—before vulnerabilities become headlines, and before attackers get a foothold. Please give the firmware analysis preview a try and let us know what you think.4.3KViews5likes9CommentsResource 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.3KViews4likes0CommentsFirmware Analysis now Generally Available
Back in June, we announced the public preview of firmware analysis, a new capability available through Azure Arc to help organizations gain visibility into the security of their Internet of Things (IoT), Operational Technology (OT), and network devices. Today, we are excited to announce that firmware analysis is generally available (GA) for all Azure customers. In modern industrial environments, firmware security is a foundational requirement. IoT sensors and smart devices collect the data fueling AI-driven insights; if those devices aren’t secure, your data and operational continuity are at risk. During the preview, we heard from many customers who used firmware analysis to shine a light into their device software and address hidden vulnerabilities before attackers or downtime could strike. With general availability, firmware analysis is ready to help organizations fortify the “blind spots” in their infrastructure – from factory-floor sensors to branch office routers – by analyzing the software that runs on those devices. What Firmware Analysis Does for You Firmware analysis examines the low-level software (firmware) that powers IoT, OT and network devices, with no agent required on the device. You can upload a firmware image (for example, an extracted embedded Linux image), and the cloud service performs an automated security inspection. Key features include: Software inventory & vulnerability scanning: The service builds a Software Bill of Materials (SBOM) of components within the firmware and checks each component against known CVEs (Common Vulnerabilities and Exposures). This quickly surfaces any known vulnerabilities in your device’s software stack so you can prioritize patching those issues. Security configuration and hardening check: Firmware analysis evaluates how the firmware binaries are built, looking for security hardening measures (e.g. stack protections, ASLR) or dangerous configurations. If certain best practices are missing, the firmware might be easier to exploit – the tool flags this to inform the device manufacturer or your security team. Credential and secrets discovery: The analysis finds any hard-coded credentials (user accounts/password hashes) present in the firmware, as well as embedded cryptographic material like SSL/TLS certificates or keys. These could pose serious risks – for instance, default passwords that attackers could exploit (recall the Mirai botnet using factory-default creds) are identified so you can mitigate them. Any discovered certificates or keys can indicate potentially insecure design if left in production firmware. Comprehensive report: All security findings – from the Software Bill of Materials (SBOM), list of vulnerabilities to hardening recommendations and exposed secrets – are provided in a detailed report for each firmware image analyzed. This gives device makers and operators actionable intelligence to improve their device security posture. In short, firmware analysis provides deep insights into the contents and security quality of device firmware. It turns opaque firmware into transparent data, helping you answer, “What’s really inside my device software?” so you can address weaknesses proactively. What’s New and Licensing We’ve been hard at work making firmware analysis even better as we move to GA. Based on preview feedback, we’ve addressed bugs, implemented usability suggestions and improved the firmware analysis SDKs, CLI and PowerShell extensions. A new Azure resource called “firmware workspace” now stores analyzed firmware images. Firmware analysis workspaces are currently available as a Free Firmware Analysis Workspace SKU with capacity limits. Getting Started If you have IoT, OT and network devices in your environment, use firmware analysis to test just how secure your devices are. Getting started is easy: access firmware analysis by searching “firmware analysis” in the Azure portal, or access using this link. Onboard your subscription and then upload firmware images for analysis. For a step-by-step tutorial, visit our official documentation. The service currently supports embedded Linux-based images up to 1GB in size. We want to thank all the preview participants who tested firmware analysis and provided feedback. You helped us refine the service for GA and we’re thrilled to make this powerful tool broadly available to help secure IoT, OT and network devices around the world. We can’t wait to see how you put it to work. As always, we value your feedback, so please let us know what you think.10KViews4likes0CommentsPartners accelerating industrial transformation with Azure IoT Operations
In the digital age, the essence of innovation lies not only in groundbreaking technology but also in the power of collaboration. At Microsoft, we have always recognized that our success is intertwined with the success of our partners. Our platform products, including the newly released Azure IoT Operations, are designed to be the foundation upon which our partners can build transformative solutions. These collaborations are more than just business arrangements; they are the bedrock of a thriving ecosystem that drives innovation, addresses customer needs, and propels industry standards forward. Partnerships enable us to extend our reach and impact far beyond what we could achieve alone. By combining our technological prowess with the domain expertise and creativity of our partners, we create a dynamic synergy that fosters groundbreaking advancements. This collaborative spirit is vital as we navigate the complexities of the Internet of Things (IoT) landscape, where diverse applications and specialized knowledge are paramount. Our partners bring unique perspectives and capabilities to the table, ensuring that Azure IoT Operations can cater to a broad spectrum of industries and use cases.3.7KViews4likes0CommentsTransforming Manufacturing with the Help of Ontologies
For over three years, Microsoft has been contributing to the Digital Twin Consortium’s open-source initiative. The most successful open-source project the DTC runs is the Manufacturing Ontologies project available at: https://github.com/digitaltwinconsortium/ManufacturingOntologies We examine our most recent contributions.4.9KViews4likes0CommentsAzure 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.304Views3likes0CommentsAzure IoT Operations 2603 is now available: Powering the next era of Physical AI
Industrial AI is entering a new phase. For years, AI innovation has largely lived in dashboards, analytics, and digital decision support. Today, that intelligence is moving into the real world, onto factory floors, oil fields, and production lines, where AI systems don’t just analyze data, but sense, reason, and act in physical environments. This shift is increasingly described as Physical AI: intelligence that operates reliably where safety, latency, and real‑world constraints matter most. With the Azure IoT Operations 2603 (v1.3.38) release, Microsoft is delivering one of its most significant updates to date, strengthening the platform foundation required to build, deploy, and operate Physical AI systems at industrial scale. Why Physical AI needs a new kind of platform Physical AI systems are fundamentally different from digital‑only AI. They require: Real‑time, low‑latency decision‑making at the edge Tight integration across devices, assets, and OT systems End‑to‑end observability, health, and lifecycle management Secure cloud‑to‑edge control planes with governance built in Industry leaders and researchers increasingly agree that success in Physical AI depends less on isolated models, and more on software platforms that orchestrate data, assets, actions, and AI workloads across the physical world. Azure IoT Operations was built for exactly this challenge. What’s new in Azure IoT Operations 2603 The 2603 release delivers major advancements across data pipelines, connectivity, reliability, and operational control, enabling customers to move faster from experimentation to production‑grade Physical AI. Cloud‑to‑edge management actions Cloud‑to‑edge management actions enable teams to securely execute control and configuration operations on on‑premises assets, such as invoking methods, writing values, or adjusting settings, using Azure Resource Manager and Event Grid–based MQTT messaging. This capability extends the Azure control plane beyond the cloud, allowing intent, policy, and actions to be delivered reliably to physical systems while remaining decoupled from protocol and device specifics. For Physical AI, this closes the loop between perception and action: insights and decisions derived from models can be translated into governed, auditable changes in the physical world, even when assets operate in distributed or intermittently connected environments. Built‑in RBAC, managed identity, and activity logs ensure every action is authorized, traceable, and compliant, preserving safety, accountability, and human oversight as intelligence increasingly moves from observation to autonomous execution at the edge. No‑code dataflow graphs Azure IoT Operations makes it easier to build real‑time data pipelines at the edge without writing custom code. No‑code data flow graphs let teams design visual processing pipelines using built‑in transforms, with improved reliability, validation, and observability. Visual Editor – Build multi-stage data processing systems in the Operations Experience canvas. Drag and connect sources, transforms, and destinations visually. Configure map rules, filter conditions, and window durations inline. Deploy directly from the browser or define in Bicep/YAML for GitOps. Composable Transforms, Any Order – Chain map, filter, branch, concatenate, and window transforms in any sequence. Branch splits messages down parallel paths based on conditions. Concatenate merges them back. Route messages to different MQTT topics based on content. No fixed pipeline shape. Expressions, Enrichment, and Aggregation – Unit conversions, math, string operations, regex, conditionals, and last-known-value lookups, all built into the expression language. Enrich messages with external data from a state store. Aggregate high-frequency sensor data over tumbling time windows to compute averages, min/max, and counts. Open and Extensible – Connect to MQTT, Kafka, and OpenTelemetry (OTel) endpoints with built-in security through Azure Key Vault and managed identities. Need logic beyond what no-code covers? Drop a custom Wasm module (even embed and run ONNX AI ML models) into the middle of any graph alongside built-in transforms. You're never locked into declarative configuration. Together, these capabilities allow teams to move from raw telemetry to actionable signals directly at the edge without custom code or fragile glue logic. Expanded, production‑ready connectivity The MQTT connector enables customers to onboard MQTT devices as assets and route data to downstream workloads using familiar MQTT topics, with the flexibility to support unified namespace (UNS) patterns when desired. By leveraging MQTT’s lightweight publish/subscribe model, teams can simplify connectivity and share data across consumers without tight coupling between producers and applications. This is especially important for Physical AI, where intelligent systems must continuously sense state changes in the physical world and react quickly based on a consistent, authoritative operational context rather than fragmented data pipelines. Alongside MQTT, Azure IoT Operations continues to deliver broad, industrial‑grade connectivity across OPC UA, ONVIF, Media, REST/HTTP, and other connectors, with improved asset discovery, payload transformation, and lifecycle stability, providing the dependable connectivity layer Physical AI systems rely on to understand and respond to real‑world conditions. Unified health and observability Physical AI systems must be trustworthy. Azure IoT Operations 2603 introduces unified health status reporting across brokers, dataflows, assets, connectors, and endpoints, using consistent states and surfaced through both Kubernetes and Azure Resource Manager. This enables operators to see—not guess—when systems are ready to act in the physical world. Optional OPC UA connector deployment Azure IoT Operations 2603 introduces optional OPC UA connector deployment, reinforcing a design goal to keep deployments as streamlined as possible for scenarios that don’t require OPC UA from day one. The OPC UA connector is a discrete, native component of Azure IoT Operations that can be included during initial instance creation or added later as needs evolve, allowing teams to avoid unnecessary footprint and complexity in MQTT‑only or non‑OPC deployments. This reflects the broader architectural principle behind Azure IoT Operations: a platform built for composability and decomposability, where capabilities are assembled based on scenario requirements rather than assumed defaults, supporting faster onboarding, lower resource consumption, and cleaner production rollouts without limiting future expansion. Broker reliability and platform hardening The 2603 release significantly improves broker reliability through graceful upgrades, idempotent replication, persistence correctness, and backpressure isolation—capabilities essential for always‑on Physical AI systems operating in production environments. Physical AI in action: What customers are achieving today Azure IoT Operations is already powering real‑world Physical AI across industries, helping customers move beyond pilots to repeatable, scalable execution. Procter & Gamble Consumer goods leader P&G continually looks for ways to drive manufacturing efficiency and improve overall equipment effectiveness—a KPI encompassing availability, performance, and quality that’s tracked in P&G facilities around the world. P&G deployed Azure IoT Operations, enabled by Azure Arc, to capture real-time data from equipment at the edge, analyze it in the cloud, and deploy predictive models that enhance manufacturing efficiency and reduce unplanned downtime. Using Azure IoT Operations and Azure Arc, P&G is extrapolating insights and correlating them across plants to improve efficiency, reduce loss, and continue to drive global manufacturing technology forward. More info. Husqvarna Husqvarna Group faced increasing pressure to modernize its fragmented global infrastructure, gain real-time operational insights, and improve efficiency across its supply chain to stay competitive in a rapidly evolving digital and manufacturing landscape. Husqvarna Group implemented a suite of Microsoft Azure solutions—including Azure Arc, Azure IoT Operations, and Azure OpenAI—to unify cloud and on-premises systems, enable real-time data insights, and drive innovation across global manufacturing operations. With Azure, Husqvarna Group achieved 98% faster data deployment and 50% lower infrastructure imaging costs, while improving productivity, reducing downtime, and enabling real-time insights across a growing network of smart, connected factories. More info. Chevron With its Facilities and Operations of the Future initiative, Chevron is reimagining the monitoring of its physical operations to support remote and autonomous operations through enhanced capabilities and real-time access to data. Chevron adopted Microsoft Azure IoT Operations, enabled by Azure Arc, to manage and analyze data locally at remote facilities at the edge, while still maintaining a centralized, cloud-based management plane. Real-time insights enhance worker safety while lowering operational costs, empowering staff to focus on complex, higher-value tasks rather than routine inspections. More info. A platform purpose‑built for Physical AI Across manufacturing, energy, and infrastructure, the message is clear: the next wave of AI value will be created where digital intelligence meets the physical world. Azure IoT Operations 2603 strengthens Microsoft’s commitment to that future—providing the secure, observable, cloud‑connected edge platform required to build Physical AI systems that are not only intelligent, but dependable. Get started To explore the full Azure IoT Operations 2603 release, review the public documentation and release notes, and start building Physical AI solutions that operate and scale confidently in the real world.1.1KViews3likes0CommentsSiemens and Microsoft: Beyond Connectivity to Autonomous, Sustainable Manufacturing
Explore how Siemens Industrial Edge and Microsoft Azure IoT Operations enable secure edge-to-cloud integration, contextualized data, and AI-driven insights—transforming factories into adaptive, future-ready operations.1.7KViews2likes0CommentsFrom Space to Subsurface: Using Azure AI to Predict Gold Rich Zones
In traditional mineral exploration, identifying gold bearing zones can take months of fieldwork and high cost drilling often with limited success. In our latest project, we flipped the process on its head by using Azure AI and Satellite data to guide geologists before they break ground. Using Azure AI and Azure Machine Learning, we built an intelligent, automated pipeline that identified high potential zones from geospatial data saving time, cost, and uncertainty. Here’s a behind the scenes look at how we did it.👇 📡 Step 1: Translating Satellite Imagery into Features We began with Sentinel-2 imagery covering our Area of Interest (AOI) and derived alteration indices commonly used in mineral exploration, including: 🟤 Clay Index – proxies for hydrothermal alteration 🟥 Fe (Iron Oxide) Index 🌫️ Silica Ratio 💧 NDMI (Normalized Difference Moisture Index) Using Azure Notebooks and Python, we processed and cleaned the imagery, transforming raw reflectance bands into meaningful geochemical features. 🔍 Step 2: Discovering Patterns with Unsupervised Learning (KMeans) With feature rich geospatial data prepared, we used unsupervised clustering (KMeans) in Azure Machine Learning Studio to identify natural groupings across the region. This gave us a first look at the terrain’s underlying geochemical structure one cluster in particular stood out as a strong candidate for gold rich zones. No geology degree needed: AI finds patterns humans can't see :) 🧠 Step 3: Scaling with Azure AutoML We then trained a classification model using Azure AutoML to predict these clusters over a dense prediction grid: ✅ 7,200+ data points generated ✅ ~50m resolution grid ✅ 14 km² area of interest This was executed as a short, early stopping run to minimize cost and optimize training time. Models were trained, validated, and registered using: Azure Machine Learning Compute Instance + Compute Cluster Azure Storage for dataset access 🔬 Step 4: Validation with Field Samples To ground our predictions, we validated against lab assayed (gold concentration) from field sampling points. The results? 🔥 The geospatial cluster labeled 'Class 0' by the model showed strong correlation with lab validated gold concentrations, supporting the model's predictive validity. This gave geologists AI augmented evidence to prioritize areas for further sampling and drilling. ⚖️ Traditional vs AI-based Workflow 🚀 Why Azure? ✅ Azure Machine Learning Studio for AutoML and experiment tracking ✅ Azure Storage for seamless access to geospatial data ✅ Azure OpenAI Service for advanced language understanding, report generation, and enhanced human AI interaction ✅ Azure Notebooks for scripting, preprocessing, and validation ✅ Azure Compute Cluster for scalable, cost effective model training ✅ Model Registry for versioning and deployment 🌍 Key Takeaways AI turns mineral exploration from reactive guesswork into proactive intelligence. In our workflow, AI plays a critical role by: ✅ Extracting key geochemical features from satellite imagery 🧠 Identifying patterns using unsupervised learning 🎯 Predicting high potential zones through automated classification 🌍 Delivering full spatial coverage at scale With Azure AIand Azure ML tools, we’ve built a complete pipeline that supports: End to end automation; from data prep to model deployment Faster, more accurate exploration with lower costs A reusable, scalable solution for global teams This isn’t just a proof of concept, it’s a production ready framework that empowers geologists with AI driven insights before the first drill hits the ground. 🔗 If you're working in Mining industry, geoscience, AI for Earth, or exploration tech, let’s connect! We’re on a mission to bring AI deeper into every industry through strategic partnerships and collaborative innovation.327Views2likes0Comments