Provisioning ten devices on a shop floor is simple, as a technician can easily punch in a connection string and confirm telemetry. However, trying that same manual approach with one hundred thousand devices spread across global factories and customer networks causes every shortcut to turn into an architectural failure. Moving beyond basic setups requires a robust understanding of device identity, trust boundaries, hub routing, and long-term fleet management. MANUFACTURING VERSUS OPERATIONAL IDE...

Welcome to a brand-new episode where we cut straight through vendor hype and tackle the real problems of digital twins on Azure. Everyone wants a digital twin, but almost nobody starts with the actual problem their plant needs to solve. Data already lives across your ERP, MES, historians, and IoT layers, yet operators still rely on manual phone calls, spreadsheets, and scattered alarms to figure out what a fault actually affects. START WITH THE DECISION, NOT THE ASSETBefore building elaborate a...

An urgent customer request sounds simple: sales promises a fast delivery date, marks the order as priority, and asks production to fit it in. But the new order does not enter an empty factory. It enters a schedule already filled with machine reservations, material allocations, setup plans, qualified people, inspection capacity, maintenance windows, and promises made to other customers. The real question is therefore not simply whether the urgent order can be produced, but which existing commitme...

A machine stops in the middle of production. ERP knows the customer orders and due dates, MES knows which operation stopped, maintenance knows the repair status, and the machine layer knows the fault code and exact timestamp. Then someone asks the obvious question: what should we do now? AI can summarize the alarm, find patterns in historical downtime, and explain what probably happened. But unless it also understands which product was running, which orders depend on that operation, which machi...

A production schedule can look correct while the factory has already moved on. A machine runs slower than expected, a setup takes longer, material is still waiting for release, or an urgent order enters the plan. ERP still shows the original dates, MES shows current execution, and the supervisor has already started adjusting the sequence on the floor. The real challenge is keeping the schedule connected to what production can actually do now. FROM PRODUCTION PLAN TO EXECUTABLE SCHEDULE A produc...

A factory can collect enormous amounts of data and still struggle to answer a basic operational question: what does this event actually affect? ERP knows customer orders, materials, planned dates, and inventory. MES knows what is executing on the shop floor. PLCs and SCADA know machine states, alarms, and process values. Maintenance knows asset condition and service history. Quality knows inspection and release status. Engineering knows the product definition. The problem is not usually a lack ...

Getting machine alarms, sensor values, production counters, and fault events into the cloud is easier than ever. OPC UA exposes the machine signal, an edge layer collects it, MQTT can distribute it locally, and Microsoft Fabric can ingest and analyze the resulting stream. The difficult part starts after the data arrives: how do you turn raw telemetry into enough production context to support an actual decision? This episode follows one machine signal from the factory floor through the Microsoft...

A connected factory can move machine signals in milliseconds and still fail to answer the operational questions that actually matter. A packaging machine stops, the PLC reports the fault, OPC UA exposes the event, MQTT distributes it, and the dashboard updates immediately. Maintenance receives an alert and everything appears connected. Then the planner asks which customer shipment is now at risk, and suddenly the answer requires MES data, ERP records, maintenance history, quality status, product...

Continuous improvement is supposed to create learning that compounds over time. In many factories, however, improvement work still depends heavily on workshops, spreadsheets, isolated reports, and what people remember from the previous shift. A Kaizen event can create visible progress, but a few weeks later the same loss often appears again under slightly different production conditions. The issue is not always the quality of the improvement idea. The bigger problem is that teams often cannot pr...

A temperature reading, a vibration sample, a machine cycle, and a device disconnect may all be described as events, but they do not represent the same architectural problem. In industrial IoT and manufacturing environments, confusing continuous telemetry with discrete events can create noisy workflows, incomplete production histories, unnecessary processing, and systems that react without enough context. In this episode, we break down the architectural difference between Azure IoT Hub Message R...

Cloud storage may look cheap. Sending factory data to the cloud may look cheap. But the real cloud bill often starts when that data begins moving. In this episode, we break down the hidden costs behind modern Industrial IoT, manufacturing cloud, edge computing, and factory data architectures — from data egress and cross-region replication to NAT gateways, backups, dashboards, and high-frequency sensor data. A single MQTT stream from a factory can quickly become multiple data flows once telemetry...

In this episode of the M365 Show, Mirko Peters speaks with Fergus Kidd, Microsoft MVP, Co-Founder and CTO of FieldPal AI, about moving enterprise AI beyond the desk. While much of the conversation around Microsoft Copilot, generative AI and productivity focuses on knowledge workers, Fergus makes the case for the people maintaining infrastructure, repairing equipment, carrying out inspections and keeping essential services running. These frontline teams often work with limited connectivity, limit...