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

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

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

Azure architecture looks easy when everything works.The real test starts when dependencies fail, regions become unavailable, traffic spikes, assumptions turn out to be wrong, requirements change, and someone eventually asks the uncomfortable question: why did we design it this way in the first place?In this episode of M365.FM, Mirko Peters talks with Mike Martin [MVP] about what Azure architecture looks like when it has to survive real production conditions rather than just look good on a diagra...

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

Microsoft Power Platform is often described as a low-code platform. But what happens when the applications you build become business-critical, highly integrated, and too complex for a simple maker-first approach?In this episode of M365 FM, Mirko Peters talks with Power Platform Solution Architect Ian Tweedie about what happens when Power Platform moves beyond simple low-code applications and becomes part of a serious enterprise architecture. LOW-CODE DOESN’T MEAN LOW ARCHITECTURE Power Platform...

What happens when your cloud strategy cannot live entirely in the public cloud? Organizations are modernizing infrastructure with Azure, platform services, Infrastructure as Code, automated deployment pipelines, and Azure Landing Zones. At the same time, some workloads still need to remain close to factories, offices, regulated environments, existing infrastructure, or latency-sensitive systems. In this episode of M365 FM, Mirko Peters talks with Microsoft MVP Christoffer Klarskov Jakobsen about...

Modern Microsoft 365 development is about far more than writing code. Organizations expect solutions that integrate seamlessly across SharePoint, Microsoft Teams, Microsoft Graph, Azure, and Microsoft 365 while remaining scalable, secure, maintainable, and ready for future innovation. In this episode of M365.FM, Microsoft MVP Julie Turner shares decades of real-world experience designing enterprise-grade Microsoft 365 solutions. From SharePoint Framework (SPFx) and Microsoft Graph to PnPjs, open...

For decades, enterprise software followed a predictable financial model. Organizations purchased licenses, assigned them to users, and budgeted annual IT spending with confidence. AI changes that completely. Modern AI platforms are no longer sold purely as software—they're becoming consumption-based services where autonomous agents perform work on your behalf. Every action, every reasoning cycle, every orchestration task, and every AI workflow consumes credits instead of simply using a fixed lic...

In this episode of the M365.fm podcast, Mirko Peters sits down with Microsoft MVP Isha Kapoor to explore what it really takes to scale Microsoft Copilot Studio in large enterprise environments. The conversation moves beyond simple chatbot scenarios and focuses on the architectural, governance, and operational challenges organizations face when deploying AI-powered agents at scale. Isha shares practical insights into designing enterprise-grade Copilot Studio solutions that remain secure, maintainable, and aligned with business goals. The discussion highlights why successful AI adoption requires more than technology alone. Governance, data quality, security controls, lifecycle management, and clear ownership models are critical factors that determine whether AI initiatives succeed or fail. The episode examines how enterprises can balance innovation with control while empowering business teams to build and use AI agents responsibly. Topics include agent orchestration, integration w…

In this episode of the M365.fm podcast, Mirko Peters speaks with Microsoft MVP and MCT Anitha Eswaran about the realities of integrating Dynamics 365 Finance & Operations (D365FO) into modern enterprise environments. The discussion focuses on why integrations often become fragile, difficult to scale, and hard to govern when organizations rely on outdated architectural thinking or tightly coupled systems. The episode explores how Azure-native integration patterns can improve reliability, scalability, and long-term maintainability. Anitha explains the importance of event-driven architecture, asynchronous communication, APIs, and message-based systems when connecting D365FO with Microsoft 365, Power Platform, external SaaS platforms, and legacy enterprise applications. Rather than building direct point-to-point integrations, the conversation emphasizes designing loosely coupled systems that can evolve without constantly breaking dependencies. Another key topic is governance and ope…