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...

AI was supposed to clear the backlog, accelerate decisions, and give every team a smarter way to work. Instead, many organizations now have Microsoft Copilot, Power BI, Microsoft Fabric, AI agents, and more data than ever before—while important decisions still crawl through meetings because nobody fully trusts the numbers or knows who can act on them. The technology spend keeps rising. The action does not. The problem is often not a lack of AI. It is the absence of an operating model connecting ...

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...

What happens when AI agents start making sense of financial and business data — not just displaying it?In this episode of M365.FM, Mirko Peters talks with Rishi Sapra Microsoft MVP about the architecture required to move beyond traditional dashboards and toward AI-powered, context-aware analytics with Microsoft Fabric, Power BI, Copilot Studio, semantic models, ontologies, and data agents.Organizations already have enormous amounts of information spread across ERP systems, Excel workbooks, Power...

Microsoft Fabric brings data engineering, analytics, business intelligence, governance and increasingly AI together in one platform. But what does an end-to-end Fabric architecture actually look like when you move beyond individual features and start connecting everything?In this episode of the M365 FM Podcast, Mirko Peters is joined by Amit Chandak [Microsoft Data Platform MVP] for a practical journey through Microsoft Fabric — starting with raw organizational data and ending with trusted infor...

What happens when a regulator requests company records, HR launches an investigation, or legal teams need to preserve critical evidence? Searching through Outlook mailboxes, Teams chats, SharePoint sites, and OneDrive folders manually is slow, error-prone, and often impossible at enterprise scale. In this episode of Microsoft Knowledge Nuggets on M365.fm, Mirko Peters explains Microsoft Purview eDiscovery in plain English. You'll learn how organizations can securely discover, preserve, review, a...

In this episode, we challenge a common misconception in Microsoft 365 governance: having policies in place does not mean your environment is truly governed. Many organizations rely on documented rules, guidelines, and compliance frameworks, assuming they will control user behavior and protect data. In reality, these policies often exist only on paper and fail to enforce consistent actions across dynamic, fast-changing environments. We explore the gap between intention and enforcement, highlighting why governance becomes fragile when it depends on manual processes, user compliance, or periodic reviews. As organizations scale, this approach leads to policy drift, inconsistent configurations, and increased risk exposure—especially in areas like data protection, identity management, and collaboration tools. The episode introduces a more resilient approach: treating governance as a system, not a document. By combining automated enforcement, identity-driven access controls, monitoring…