Power Platform Episodes

This episode explains that constantly searching for files is a sign of a poorly designed system rather than a normal part of work. Many organizations struggle with scattered documents, duplicate versions, and unclear structures, which leads to wasted time and inefficiency—what the host describes as a “search tax.” Instead of relying on better search tools, the episode suggests a different approach: rethinking how information is organized and accessed. It introduces the idea of a “Cowork Engine,” where AI like Copilot is not just a reactive assistant that answers prompts, but an active system that anticipates needs and delivers the right information automatically. The main message is that organizations should move away from file-based work and toward context-driven systems. By doing this, employees spend less time looking for information and more time making decisions and getting work done.

This episode explains that many managers misunderstand what the “Copilot coworker” actually is. They treat it like a simple productivity tool, expecting quick gains, but in reality AI changes how work, decisions, and responsibilities are structured. Because of this, teams using Copilot often don’t see real results. The problem isn’t the technology—it’s that organizations keep old management models, unclear ownership, and weak accountability. Managers focus on tasks and activity instead of outcomes, and they fail to redesign roles, decision-making, and workflows around AI. The “architect move” means shifting from managing people and tasks to designing systems: clear ownership, strong governance, and defined execution. Without this structural change, Copilot just exposes existing organizational problems instead of improving productivity. In short, AI success requires rethinking management itself—not just adding new tools.

Frictionless automation feels efficient, but it can quietly create chaos. When systems remove effort and decisions become automatic, organizations lose visibility into how things actually work. Instead of improving control, automation can hide complexity and shift decision-making into the system itself. Over time, this leads to unintended behaviors, misalignment, and risk—because no one is actively shaping outcomes anymore. The organization you think you designed (based on structure or intent) diverges from the one that actually operates through automated processes. The key insight: automation doesn’t eliminate complexity—it redistributes it into hidden layers. If you don’t intentionally design governance, decision logic, and system behavior, the system will make decisions for you. In short, friction isn’t always bad. It can act as a control mechanism. Removing it without replacing it with deliberate governance leads to invisible chaos rather than true efficiency.

Stop wiring every business rule into fragile workflows. In this episode, we break down why complex logic does not belong in Power Automate flows and how an orchestration-first architecture changes everything. You will learn how to move decisions into a durable control plane, keep workflows lightweight, and build automation that actually survives real-world change.

This episode explains that most Microsoft 365 setups unintentionally destroy focus because they are designed to maximize activity and responsiveness rather than deep work. The real issue isn’t users mismanaging notifications, but a system that constantly pushes interruptions from tools like Teams and Outlook without clear governance. As a result, people are stuck in reactive mode, switching context instead of doing meaningful work. The fix isn’t simply turning off notifications—it requires rethinking how communication, alerts, and collaboration are structured across the entire environment.

In this episode of the M365.fm podcast, “The Multi-Tenant Copilot Trap: Mastering Global AI Governance,” the discussion centers on a critical but often overlooked challenge in enterprise AI adoption: the misconception that deploying Microsoft 365 Copilot across multiple tenants is simply a scaling exercise, when in reality it introduces complex governance, security, and data boundary risks that can quickly spiral out of control. The hosts unpack how Copilot fundamentally amplifies whatever data foundation already exists—meaning poor governance, oversharing, and permission sprawl are no longer hidden issues but instantly exposed through AI-driven access and insights . They emphasize that organizations operating in multi-tenant environments must rethink traditional governance models, moving beyond tenant-level controls to a unified, global strategy that enforces consistent policies, identity management, and data protection across all environments. The episode highlights the danger of fr…

Build your first Power App step-by-step—from initial idea to a fully working solution. This episode of the M365.fm podcast explains how to turn a simple business need into a functional app using Microsoft Power Apps, even with little or no coding experience. It walks through the core process: defining the problem, connecting to data sources like SharePoint or Excel, designing screens, and building key features such as forms and navigation. You’ll learn practical best practices for beginners, including why starting small is critical, how to structure your app logically, and how to avoid common mistakes when building your first solution. The episode focuses on real-world use cases and shows how low-code tools enable fast development and iteration. Perfect for IT pros, business users, and makers who want to quickly move from idea to a working Power Apps solution and start building impactful apps in the Microsoft 365 ecosystem.

Dataverse is the core data foundation behind Power Platform apps, not just a database. This episode explains how it provides structured, secure, and scalable data storage with built-in relationships, logic, and governance. The key message is that your data model is what truly determines whether your apps succeed or fail—more than the UI or automation. When designed properly, Dataverse enables consistent data, reliable integrations, and scalable business applications across Power Apps, Power Automate, and Dynamics 365.

This episode explains that most Power Platform solutions fail not because of the technology, but because teams start with the wrong mindset—jumping straight to “let’s build an app” instead of first understanding the actual business problem and system behind it. It emphasizes that the Power Platform is not a single tool but a set of distinct layers—Power Apps for interaction, Power Automate for execution, Power BI for visibility, Power Pages for external access, and Copilot as an assistant—and that treating them as interchangeable leads to solutions that look good in demos but break in real operations. The core message is a shift from solution-first thinking to system thinking: real problems are usually rooted in disconnected processes, unclear ownership, and missing structure, and only by separating these layers and understanding their roles can organizations build scalable, effective solutions instead of fragile apps.

High performers aren’t breaking because of workload alone—they’re breaking because of a system that isolates them. The episode explains that as people become more successful, they also become more alone: they’re expected to have answers, stay strong, and not show uncertainty. That removes real, honest conversations and replaces them with performance. Over time, they stop being seen as people and start being treated as roles. It highlights that modern work systems (especially in tech and leadership) reward output, control, and constant availability—but ignore emotional support and human connection. This creates a hidden feedback loop: the better you perform, the less safe it feels to admit struggle. The core idea is that loneliness at the top isn’t accidental—it’s designed into how organizations operate. And unless systems change to allow vulnerability, shared responsibility, and real connection, high performers will continue to burn out quietly while still appearing successfu…

Most organizations believe they understand how their business operates. They point to org charts, policies, and compliance frameworks as proof. They are wrong. In this episode, Mirko Peters reframes Microsoft Purview from a compliance tool into...

This episode argues that the biggest governance mistake in Microsoft 365 isn’t misconfiguration—it’s timing. Most organizations treat governance as something to “add later,” but by doing that, they unintentionally design failure into the system from day one. The core idea is that governance isn’t a layer you apply after deployment. It’s the underlying decision system that determines how identities, permissions, and data behave. When it’s missing at the start, the environment defaults to maximum permissiveness, and that becomes very hard to reverse later. The episode explains that many organizations optimize for fast adoption—rolling out Teams, SharePoint, and Copilot quickly—while postponing structure. The result is predictable: after months, tenants are full of orphaned teams, unclear ownership, overshared files, and uncontrolled external access. This isn’t seen as a failure, but as the natural outcome of the initial design choices. A key point is that tools like Copilot don…

You didn’t fail as an admin. The system failed because it needed you. After years of manual governance—access reviews, approvals, lifecycle policies—this episode exposes the uncomfortable truth: human-driven administration was never scalable in a...

This episode argues that most Microsoft 365 problems are not technical, but organizational. Technical experts often design tenants that are logically perfect but fail in real-world use. They focus too much on configuration and not enough on how people actually work. As a result, systems become difficult to manage and quickly lose structure. The speaker highlights that Microsoft 365 should be treated as an operating system for the business, not just a collection of tools. Many issues like oversharing and sprawl come from missing governance, not bad technology. Technical teams often fall into the trap of building complex, elegant solutions without clear ownership. Over time, these systems break down because no one is responsible for maintaining them. Governance is often treated as a one-time project instead of an ongoing process. This leads to long-term risks, especially around security and scalability. The episode emphasizes the importance of intent-based governance rather than just te…

After 500 episodes, Mirko Peters shares an uncomfortable truth: consistency alone does not create results. What started as a daily podcast to get hired failed in its original goal—but revealed something far more valuable. This episode breaks down the difference between output and leverage, why visibility doesn’t convert, and what actually drives business outcomes: distribution, positioning, execution, and relationships. 🚀 Key Topics Covered 1. The Original Plan (That Failed) Podcast started ...

This episode explains why traditional Microsoft 365 consulting is rapidly losing value and introduces five modern business models that generate high-margin, recurring revenue by focusing on governance, identity, automation, and system-level outcomes instead of implementation work. It argues that Microsoft 365 should be understood as a distributed decision engine rather than a set of tools, and the real opportunity lies in controlling how that system behaves. As complexity in the Microsoft ecosystem increases, organizations struggle with governance, creating demand for specialists who can design and operate control systems rather than deliver one-time projects. The episode highlights a shift from hourly billing to outcome-based pricing, where value is tied to measurable business impact such as risk reduction, automation, and efficiency gains.

This episode challenges one of the most common (and costly) assumptions in Microsoft Copilot deployments: that governance must be “fixed” before rollout. It argues that treating governance as a gate—something that blocks progress until perfection—is an architectural mistake. Real-world environments are inherently messy, with orphaned sites, inconsistent data classification, and fragmented ownership. Waiting for perfection doesn’t reduce risk—it creates governance debt and delays value. Instead, organizations should treat governance as a continuous track that evolves alongside deployment, using automation, prioritization, and real-time controls to manage risk while productivity gains are already being realized.

This episode challenges one of the most common assumptions in the Microsoft ecosystem: 👉 “If it’s Microsoft, it must already be secure.” The reality is the opposite. Power Platform is enterprise-grade secure by design—but becomes risky the moment governance is missing. The episode explains that most organizations don’t fail because of vulnerabilities or attackers. They fail because of perfectly allowed behavior in an ungoverned system—driven by low-code speed, citizen development, and lack of ownership. The key insight: 👉 Power Platform doesn’t create chaos—it exposes missing governance decisions.

This episode breaks down a major transformation happening in the Microsoft partner ecosystem: 👉 The shift from technical implementation → economic stewardship The key message is blunt: If your business still competes on technical delivery, you’re competing in a market that no longer exists. Technical expertise—once a differentiator—is now expected. Meanwhile, structural changes in Microsoft’s partner model, automation, and AI are eroding traditional revenue streams and compressing margins. The episode explains why many partner businesses are under pressure and introduces a new model where partners win by owning financial outcomes, not technical execution.

How to Build a Microsoft 365 Service So Valuable Clients Beg to Work With You This episode explains why most Microsoft 365 consulting services become commoditized—and how to escape that trap by designing services around outcomes instead of tasks. The core argument: 👉 Technical expertise is no longer a differentiator. 👉 Service architecture is. Most consultants sell activities like deployments, governance setups, or migrations. But clients don’t actually buy those—they buy certainty, risk reduction, and measurable business results. The episode introduces a structured approach to building high-value, productized Microsoft 365 services that: Solve urgent, high-impact problems Deliver clear, measurable outcomes Provide repeatable frameworks and assets Position the consultant as a strategic partner (not a vendor) The result: instead of competing on price, clients compete to work with you.

Most organizations believe efficiency improvements come from better tools or faster processes. But the biggest gains rarely come from new software. They come from architectural decisions. In this episode of the M365 FM Podcast, we explore how organizations can architect efficiency at scale using Microsoft’s automation ecosystem. The conversation reframes platforms like Power Platform not as simple app-building tools, but as distributed decision engines that execute governance and workflow decisions across the enterprise every day. When designed properly, these systems can generate enormous operational efficiency—sometimes saving hundreds of thousands or even millions of dollars annually.

Compliance processes are often treated as manual administrative work—slow, repetitive, and prone to human error. But modern organizations can transform compliance into an automated, traceable workflow system using Microsoft’s automation platform. In this episode, we explore how Power Automate can be used to engineer smarter compliance processes by turning manual approvals, documentation checks, and policy enforcement into automated workflows. Instead of relying on spreadsheets, emails, and ticket queues, organizations can design systems that automatically enforce governance rules and capture compliance evidence in real time. The result is faster operations, stronger audit trails, and reduced administrative overhead.

Most Microsoft consultants never break out of commodity consulting. They compete on hourly rates, implementation speed, and certifications—yet struggle to position themselves as strategic advisors. In this episode of the M365 FM Podcast, we explore the blueprint for becoming a high-value Microsoft consultant by focusing on architecture, strategic impact, and business transformation rather than basic implementation work. Instead of selling hours, elite consultants engineer architectural necessity—solutions that organizations depend on to operate securely, efficiently, and at scale.

Artificial intelligence is no longer a productivity experiment. With Microsoft Copilot embedded across Microsoft 365, organizations are entering a new operational reality where AI participates directly in daily work—summarizing meetings, generating documents, analyzing data, and automating workflows. But adopting Copilot isn’t just about enabling a feature in Word, Excel, or Teams. It’s an enterprise transformation mandate. In this episode of the M365 FM Podcast, we explore why Copilot adoption forces organizations to rethink architecture, governance, and operating models. When AI systems gain access to enterprise data, identity systems, and collaboration platforms, they effectively become participants in decision-making and knowledge workflows. That shift changes everything.