M365.FM - Modern work, security, and productivity with Microsoft 365

In this episode of the M365 FM Podcast, Mirko Peters welcomes Areti Iles, Microsoft MVP, Head of Professional Services at Telefonica Tech’s AI Business Solutions Division, community leader, mentor, conference organizer, and one of the most respected voices in AI governance, compliance, Dynamics 365, and Power Platform. Together, they explore enterprise transformation, Agentic AI, leadership, responsible AI adoption, and the future of work in an AI-powered world. Areti shares her remarkable journey from working in IT support to becoming a trusted leader responsible for delivering complex Microsoft technology solutions across global organizations. What started as an introduction to Microsoft Dynamics CRM evolved into a career spanning consulting, solution architecture, project leadership, executive management, and AI strategy. Her story demonstrates how curiosity, continuous learning, and community involvement can transform a career and create opportunities far beyond what many professionals initially imagine.HOW DIGITAL TRANSFORMATION CAREERS ARE BUILTOne of the recurring themes throughout the conversation is that successful careers are rarely planned from the beginning. Areti explains how many of the most important opportunities in her career emerged unexpectedly. From becoming a consultant to leading professional services teams, she highlights the importance of stepping outside comfort zones, embracing uncertainty, and applying for roles even when you do not meet every requirement. She also discusses the leadership lessons she learned while transitioning from technical delivery into executive leadership. Moving from building solutions to overseeing entire delivery organizations provided new perspectives on strategy, customer relationships, business value, and organizational transformation. WHY ENTERPRISE PROJECTS SUCCEED OR FAIL Drawing from years of experience leading Dynamics 365, Power Platform, ERP, and AI projects, Areti explains that technology is rarely the reason projects fail. Instead, the biggest challenges often include:Lack of stakeholder engagementPoor change managementInsufficient executive sponsorshipUnrealistic expectationsLimited SME availabilityScope creepWeak user adoption strategiesShe emphasizes that go-live should never be considered the finish line. The true success of any transformation project is measured by business outcomes, adoption rates, productivity improvements, and long-term value realization after deployment.THE PEOPLE SIDE OF DIGITAL TRANSFORMATION A major takeaway from the episode is that technology projects are fundamentally people projects. Organizations often focus heavily on implementation while underestimating the effort required to prepare users for change. Areti discusses the importance of involving users early, gathering continuous fe

AI video generation is moving far beyond simple prompts.Most creators approach AI filmmaking by treating every tool as an isolated experience. They generate images in one platform, create video in another, and hope everything magically works together. The result is familiar to anyone experimenting with AI movies today: characters change appearance between shots, motion becomes distorted, scenes lose continuity, and production costs spiral through endless regeneration cycles.In this episode of M365 FM, Mirko Peters explores why successful AI filmmaking isn't about prompts—it's about architecture.Discover how Microsoft Copilot, Seedance 2.0, and Higgsfield each play a distinct role in a modern AI movie production pipeline. Instead of relying on random generations, learn how to orchestrate character consistency, camera motion, scene continuity, and governance through a structured workflow that produces predictable and repeatable results.WHY MOST AI MOVIES FAILThe majority of AI-generated videos suffer from the same fundamental problem: inconsistency.A character created in one scene suddenly looks different in the next. Facial features drift, clothing changes, backgrounds morph, and camera movement introduces visual artifacts that break immersion. Most creators blame the models themselves, but the real issue is usually a lack of orchestration.This episode examines why character drift happens, how motion complexity impacts render quality, and why successful AI productions require more than just clever prompting. You'll learn how professional AI creators think about reference packs, continuity management, and system design rather than relying on trial and error generation.THE ROLE OF COPILOT AS AN AI DIRECTORMost people use Copilot as a writing assistant.What if it became your director instead?Learn how Copilot can orchestrate an entire AI production pipeline by generating parametric shot lists, managing character definitions, enforcing continuity standards, and grounding every scene in structured project assets.Rather than creating random prompts, Copilot becomes the orchestration layer that ensures every tool in the workflow follows the same production blueprint.Topics include:Parametric shot planningCharacter anchor documentationAI production governanceMetadata-driven filmmakingSEEDANCE AND CHARACTER CONSISTENCYCharacter consistency remains one of the biggest challenges in AI filmmaking.The episode explores how Seedance 2.0 approaches identity preservation through Character References (Cref), role-based image design, reference packs, and prompt binding strategies. Learn why most character failures occur long before rendering starts and how structured reference management dramatically improves results.Discover practical techniques for creating identity anchors, managing character drift, and maintaining visual consistency

The Power Platform is entering a new era.For years, Power Apps has been known as one of Microsoft's flagship low-code platforms, enabling citizen developers and business users to build applications without traditional software development skills. But with the arrival of Power Apps Code Apps, AI-assisted development, GitHub integration, and modern frameworks like React and Vue, the boundaries between low-code and pro-code are rapidly disappearing.In this episode of M365 FM, Mirko Peters sits down with Microsoft MVP Carike Botha to explore how Power Apps Code Apps are transforming application development and what this means for citizen developers, professional developers, IT teams, and organizations embracing AI-driven innovation.From SharePoint and InfoPath to Copilot, Agents, and Code Apps, Carike shares her journey through the Microsoft ecosystem and explains why the future belongs to builders who understand both business processes and modern development practices.WHAT ARE POWER APPS CODE APPS?Power Apps Code Apps represent one of the biggest shifts in the Power Platform ecosystem. Instead of relying solely on traditional canvas app design, developers can now use natural language, modern web technologies, and AI-assisted development experiences to create powerful applications faster than ever before.Carike explains how Code Apps bridge the gap between citizen development and professional software engineering by combining the simplicity of low-code development with the flexibility of modern coding frameworks. The result is a new development model that enables both business users and experienced developers to collaborate on enterprise-ready solutions.Whether you're building internal business applications, automating manual processes, or creating new user experiences, Code Apps are redefining what's possible inside the Microsoft ecosystem.FROM LOW-CODE TO PRO-CODEOne of the biggest themes in this conversation is the evolving relationship between citizen developers and professional developers.For years, organizations viewed low-code and pro-code as separate worlds. Today, those worlds are converging. AI, natural language development, GitHub integration, and modern tooling are creating entirely new opportunities for collaboration between business users and technical teams.Carike discusses why low-code does not mean low discipline, why governance matters more than ever, and how organizations can empower innovation without sacrificing security, compliance, or maintainability.Key topics include:Power Apps Code Apps and AI-driven developmentCitizen Developers vs Professional DevelopersReact, Vue, and modern application architectureGovernance, security, and enterprise readinessAI, COPILOT, AND THE FUTURE OF DEVELOPMENTArtificial Intelligence is changing everything.From Copilot Studio and AI Agents to Model Context Protocol (MCP) Se

Most organizations are building chatbots because they're easy to deploy, easy to demonstrate, and relatively inexpensive to operate. But while chatbots can answer questions, they rarely transform how work gets done. The organizations creating the biggest impact with AI are focusing on something entirely different: codifying expertise into digital twins that can reason, diagnose, and guide decision-making.In this episode of M365 FM, Mirko Peters explores why the future of enterprise AI isn't about better conversations—it's about better logic. You'll learn why most organizations are optimizing the wrong layer of the technology stack and how digital twins can capture expert knowledge, automate decision frameworks, and drive measurable business outcomes.WHAT'S THE DIFFERENCE?A chatbot answers questions. A digital twin helps make decisions.While both technologies may use the same underlying AI models, they solve fundamentally different problems. Chatbots focus on information retrieval and conversational experiences. Digital twins focus on workflows, diagnostics, business processes, governance, and operational outcomes.In this episode, you'll discover:Why most AI projects fail to move beyond pilot programsThe difference between conversational AI and decision intelligenceHow organizations can codify expert knowledge into reusable logicWhy workflow understanding matters more than prompt engineeringBUILDING AI THAT THINKSMost expertise inside an organization exists as tribal knowledge. The best employees know how to diagnose problems, evaluate risks, identify patterns, and make decisions—but that logic rarely exists in documentation.Learn how to transform expert reasoning into structured decision frameworks using Microsoft Copilot Studio, Dataverse, Microsoft Graph, Logic Apps, and Power Automate. Discover how Topics, Tools, and Knowledge Sources combine to create intelligent systems that can support and scale operational decision-making.You'll learn:How diagnostic agents differ from traditional chatbotsWhy logic-bots create greater business value than FAQ botsHow to build auditable and explainable AI systemsThe role of workflow intelligence in modern enterprisesTHE DIGITAL TWIN FRAMEWORKCreating a digital twin isn't about deploying technology first. It begins with understanding how work actually happens inside your organization.Mirko walks through a practical framework that helps organizations move from observation to implementation, including process discovery, workflow modeling, simulation, governance, and operationalization.Key areas covered include:Process mining and workflow discoveryWorkflow twins and governance twinsSimulation and what-if scenario planningMeasuring business outcomes and ROICOPILOT STUDIO, GOVERNANCE, AND ENTERPRISE AI

In this episode of the M365 Podcast, host Mirko Peters sits down with Microsoft MVP and Copilot Engineer Isha Kapoor for an in-depth conversation about one of the most important topics facing organizations today: how to successfully scale Microsoft Copilot Studio in large enterprise environments.While many demonstrations of AI agents and Copilot Studio focus on building solutions in just a few minutes, the reality inside large organizations is dramatically different. Enterprises operating in highly regulated industries such as banking, government, healthcare, and financial services must navigate complex requirements around security, governance, compliance, deployment pipelines, data protection, auditing, and operational control before AI solutions can reach production.Drawing from her experience leading Copilot Studio implementations for large financial institutions and enterprise organizations, Isha shares practical insights into what it really takes to move from AI experimentation to enterprise-scale deployment. The discussion explores real-world governance models, deployment strategies, security controls, data residency requirements, responsible AI practices, and lessons learned from deploying AI agents at scale.ENTERPRISE AI IS MORE THAN BUILDING AGENTSOne of the biggest misconceptions surrounding AI is that building an agent is the difficult part. In reality, creating an AI agent in Microsoft Copilot Studio can often be accomplished within minutes. The true challenge begins when organizations attempt to deploy those agents safely into production environments that contain sensitive business data and mission-critical processes.Isha explains how enterprise organizations must establish strict governance frameworks that control where development occurs, who can access environments, how agents are reviewed, and how they move through deployment pipelines. Without these controls, organizations risk exposing sensitive information, creating compliance issues, or deploying agents that behave unpredictably.The conversation highlights why AI projects require the same rigor as enterprise application development, including change management, operational ownership, security reviews, approval processes, and ongoing monitoring.KEY TOPICS DISCUSSED IN THIS EPISODE• Microsoft Copilot Studio governance strategies• Enterprise AI deployment pipelines and ALM practices• Data Loss Prevention (DLP) policies for AI agents• Security and compliance requirements in regulated industries• Responsible AI implementation and monitoring• AI agent lifecycle management and operational controls• Power Platform integration with Copilot Studio• Future trends in Microsoft 365 Copilot and enterprise AIBUILDING A GOVERNANCE-FIRST COPILOT STUDIO STRATEGYA major focus of the episode is the importance of governance before innovation. Rather than allowing

The era of prompt engineering is rapidly coming to an end. For years, organizations have focused on crafting better prompts, refining instructions, and teaching employees how to interact with AI tools. While that approach delivered early productivity gains, it is becoming increasingly clear that prompting is not the future of enterprise AI. The next evolution is agent orchestration—an intelligent ecosystem where specialized AI agents collaborate, reason, and execute workflows autonomously.In this episode of M365FM, we explore why the traditional chatbot model has reached its limits and how Microsoft's emerging Copilot ecosystem is paving the way for a new operating model built around autonomous agents. We dive deep into the concept of the Copilot Agent Fabric, a framework that moves organizations from manual prompting toward outcome-driven automation powered by AI orchestration.WHYPROMPTING IS NO LONGER ENOUGHMost organizations still treat Copilot as a smarter search box. Users ask questions, receive answers, and manually decide what to do next. While useful, this model creates a productivity ceiling because every workflow depends on human supervision and prompt quality.Key challenges with the chatbot model include:Prompt quality varies dramatically between usersAI adoption often plateaus after initial excitementWorkflows remain dependent on manual interventionOrganizations struggle to scale AI outcomes consistentlyProductivity gains fail to compound over timeThe future isn't about asking better questions. It's about designing systems where AI agents own and execute complete business outcomes.UNDERSTANDING THE COPILOT AGENT FABRICThe Copilot Agent Fabric represents a fundamental architectural shift. Instead of relying on a single AI assistant to handle everything, organizations deploy specialized agents focused on specific business domains and outcomes.Within this model:Agents own clearly defined responsibilitiesWork is routed intelligently between specialistsContext is isolated to improve reasoning qualityBusiness workflows become autonomousOutcomes become measurable and repeatableThis approach transforms AI from a reactive assistant into an operational layer that continuously executes business processes.THE THREE PILLARS OF AGENT ORCHESTRATIONThe Copilot Agent Fabric is built upon three foundational components:EVENTSEvents act as triggers that initiate workflows.Examples include:New customer inquiriesIncoming emailsContract requestsApproval deadlinesService ticketsREASONINGSpecialized agents process information within their domain of expertise.Benefits include:Reduced hallucinationsImproved decision qualityBetter g

Microsoft Copilot can reason, summarize, and interact with enterprise data, but when real business logic enters the picture, many organizations quickly discover the limitations of standard connectors and low-code workflows. Complex orchestration, multi-system validation, advanced calculations, and enterprise-grade integrations often push Power Platform beyond its comfort zone.In this episode of M365 FM, we explore how developers can extend Copilot using Azure Functions, OpenAPI, API Management, and modern cloud architecture patterns to build plugins that are scalable, secure, and production-ready.WHY LOW-CODE HITS A WALLStandard connectors are excellent for simple integrations, but enterprise workloads require much more than moving data between systems.We discuss why connector chains become difficult to maintain, how latency compounds across multiple services, and why low-code expressions eventually become a bottleneck for complex business scenarios. You'll learn where traditional Power Platform approaches begin to break down and why pro-code extensions become necessary.AZURE FUNCTIONS AS THE EXECUTION LAYERAzure Functions provide the computational engine behind advanced Copilot experiences.This episode explores:• HTTP-triggered functions and serverless architectures• C# isolated worker models• Dependency injection and enterprise development patterns• Reusable libraries and type-safe code• Integration with Power Platform through custom connectorsLearn how Azure Functions become the bridge between conversational AI and real business execution.THE FLEX CONSUMPTION ADVANTAGEPerformance matters when users expect instant responses.We break down:• Cold start challenges in serverless environments• Consumption vs Premium plans• Flex Consumption architecture• Always Ready instances• Cost versus performance tradeoffsYou'll discover why Flex Consumption has become the preferred deployment model for many enterprise Copilot workloads.OPENAPI: THE LANGUAGE OF AI INTEGRATIONYour OpenAPI specification is more than documentation. It becomes the contract between your code and the large language model.We discuss how to:• Design AI-friendly operation descriptions• Create effective parameter schemas• Improve function discovery by Copilot• Avoid operation collisions• Build OpenAPI contracts optimized for LLM reasoningA well-designed specification often determines whether Copilot uses your function successfully or ignores it entirely.BUILDING HIGH-PERFORMANCE FUNCTIONSFast plugins create better user experiences.This episode covers:• Async programming patterns• Connection pooling strategies• Singleton services and dependency management• ReadyToRun publishing• Lazy initialization techniques• Mem

Microsoft Copilot is transforming how organizations access, analyze, and act on information. But while most security conversations focus on AI models, hallucinations, and prompt engineering, the real risk often lives somewhere else entirely. The model is not the vulnerability. The vulnerability is the identity layer, the permissions model, and the governance framework sitting underneath it.In this episode of the M365 FM Podcast, we explore why Microsoft Copilot doesn't create new security problems—it exposes the ones that already exist. From excessive SharePoint permissions and forgotten group memberships to semantic indexing and AI-powered data discovery, Copilot amplifies every weakness hiding inside your Microsoft 365 environment. If your permissions are broken, AI simply makes those problems easier to find.UNDERSTANDING THE LETHAL TRIFECTAOne of the biggest risks in enterprise AI is what security researchers call the "Lethal Trifecta." When these three conditions exist together, organizations become highly vulnerable to AI-driven attacks:• Access to sensitive enterprise data• Exposure to untrusted content such as emails, Teams messages, and SharePoint comments• The ability for AI systems to communicate or take action on behalf of usersWhen these elements combine, prompt injection attacks can move from theoretical risk to real-world business impact.WHY PROMPT INJECTION CHANGES EVERYTHINGPrompt injection is not a software bug. It is a consequence of how large language models process information. AI systems cannot reliably distinguish between instructions and data, creating opportunities for attackers to hide commands inside documents, emails, websites, and collaboration platforms.We examine real-world examples including ShareLeak and other Microsoft Copilot vulnerabilities that demonstrated how hidden instructions embedded in content can influence AI behavior. You'll learn why prompt injection remains one of the most critical security challenges facing enterprise AI deployments today.SECURING COPILOT WITH ENTRA IDIdentity is the new security perimeter. In a world where AI can access everything a user can see, protecting identities becomes more important than protecting networks.In this episode, we cover:• Phishing-resistant MFA with FIDO2 and Windows Hello for Business• Conditional Access policies designed specifically for Copilot• Risk-based authentication using Entra ID Protection• Continuous Access Evaluation (CAE) and real-time session revocation• Device-bound token protection for high-value users and workloadsThese controls create a stronger foundation for securing AI access before users ever interact with Copilot.ZERO TRUST FOR AIZero Trust is not a product. It is a design pattern.We break down how Zero Trust principles apply directly to Microsoft Copilot, including least pri

Most organizations believe their AI costs are predictable.They look at the Microsoft invoice, see the $30-per-user Copilot add-on, multiply it by headcount, and assume they understand what enterprise AI is costing them.They don’t.In this episode, Mirko Peters breaks down the hidden financial architecture underneath Microsoft Copilot, Azure OpenAI, Copilot Studio, Security Copilot, and agentic AI systems. What looks like a simple licensing model is actually a layered consumption economy built on tokens, compute, orchestration loops, verification labor, governance overhead, and hidden operational waste.This episode explains why many organizations are dramatically underestimating what enterprise AI actually costs — and why some deployments are quietly bleeding millions of dollars through zombie licenses, idle token waste, poorly governed agents, and low-adoption rollouts.More importantly, the episode explores how organizations can stop the bleeding and build a sustainable, measurable, ROI-driven AI strategy going into 2026.THE REAL COST OF COPILOTThe $30 Copilot license is not the real cost of enterprise AI.It is the entry fee.Mirko explains how Microsoft’s licensing strategy changed dramatically between 2024 and 2026 through price increases, removal of Enterprise Agreement discounts, bundled AI suites, and consumption-based billing models.The conversation explores:E3 and E5 licensing inflationMicrosoft’s E7 Frontier Suite strategyThe end of traditional volume discount leverageAI becoming a fixed operational costThe shift toward bundled dependency ecosystemsThis section explains why organizations often discover the real financial impact of AI during renewal cycles rather than during pilot deployments.TWO BILLING SYSTEMS AT THE SAME TIMEOne of the biggest problems in enterprise AI today is that Microsoft effectively runs two billing models simultaneously.The first is traditional seat-based licensing.The second is variable consumption-based billing driven by tokens, compute units, and AI workload execution.This episode explains how products like Copilot Studio, Azure OpenAI, Security Copilot, and GitHub Copilot blur these billing systems together, creating fragmented visibility across multiple invoices and reporting platforms.Mirko explores how a single AI interaction can trigger:M365 licensing costsCopilot Credit consumptionAzure OpenAI token usageSecurity Compute Unit overagesAgent orchestration costsThe result is a financial model most organizations cannot fully observe in real time.WHAT TOKENS ACTUALLY COSTThis episode provides one of the clearest explanations available of how token economics work inside enterprise AI systems.Mirko breaks down:Input tokensOutput tokensContext windowsReasoning token

Most low-code developers inside the Microsoft ecosystem still spend their days building screens.Canvas apps, forms, navigation layers, Power Fx formulas, galleries, and buttons have defined the Power Platform development model for years. That approach solved real business problems and helped organizations move faster than traditional software development ever could.But the platform underneath those screens has changed.Microsoft is shifting the center of innovation away from UI-first development and toward AI-first orchestration. Copilot Studio is no longer just a chatbot builder or a conversational wrapper around Power Platform. It is becoming the reasoning layer that sits above flows, APIs, connectors, knowledge systems, and enterprise business processes.In this episode, Mirko Peters breaks down one of the biggest architectural shifts happening inside Microsoft 365 right now: the movement from screen-based low-code development toward managed business logic, declarative orchestration, and agentic AI systems.This conversation explores what Microsoft actually changed, why the old canvas model created structural problems at scale, and how Copilot Studio is redefining what enterprise developers, architects, and AI teams need to understand going into 2026.THE OLD LOW-CODE MODELFrom 2018 through 2024, Power Apps Canvas dominated the Microsoft low-code ecosystem.The value proposition was simple. Business users needed solutions quickly, traditional development teams moved too slowly, and low-code developers could bridge the gap between business requirements and delivery speed.Canvas apps worked because they allowed organizations to rapidly build internal applications without waiting for large engineering projects.But the architecture underneath those apps had a hidden flaw.Business logic lived directly inside screens.Validation rules, formulas, variables, conditional formatting, and workflow decisions became tightly coupled to the UI itself. Over time, organizations created sprawling Power Platform estates filled with duplicated logic, disconnected formulas, and applications that became nearly impossible to maintain at enterprise scale.This episode explains why the original low-code model eventually collapsed under the pressure of governance, scalability, and maintainability.THE PLATFORM SHIFTThe shift happening inside Microsoft’s ecosystem is not theoretical.It is visible in Microsoft’s release waves, developer tooling, Copilot investments, and architecture guidance.Mirko explains how Microsoft moved the center of innovation toward Copilot Studio, declarative agents, orchestration systems, and AI-first workflow models.Canvas apps are not disappearing. Microsoft is still supporting Power Apps and continuing to improve the platform.But support and strategic investment are not the same thing.The discussion explores how tools like the M365 Agent Toolkit and Copilot-first orchestration patterns re

Most organizations believe they have an AI problem when the real issue is their knowledge architecture. Microsoft Copilot deployments are exposing a deeper enterprise challenge: organizations cannot reliably structure, govern, connect, or retrieve the knowledge they already own. Employees still spend enormous amounts of time searching across SharePoint, Teams, OneDrive, emails, project workspaces, and disconnected business systems trying to find information that technically already exists somewhere inside the tenant.In this episode, Mirko Peters explains why successful enterprise AI deployments in 2026 depend less on the language model itself and far more on the semantic architecture underneath it. This deep technical conversation explores how organizations can design scalable Microsoft CoWork IQ and knowledge graph architectures that transform Copilot from a basic search experience into a trusted enterprise intelligence layer capable of reasoning across organizational knowledge.THE ENTERPRISE KNOWLEDGE PROBLEMHybrid work dramatically increased knowledge fragmentation inside organizations. Institutional knowledge that once moved naturally through conversations, office interactions, and proximity is now scattered across disconnected systems, duplicated documents, forgotten Teams channels, and poorly governed SharePoint environments.This episode explores why modern organizations struggle with discoverability, semantic consistency, and AI readiness even after years of digital transformation investments. Mirko explains why enterprise AI systems fail when organizational context is weak and why generative AI has fundamentally changed what employees expect from enterprise knowledge systems.UNDERSTANDING MICROSOFT GRAPH & THE SEMANTIC INDEXMost organizations misunderstand what Microsoft Graph actually is. This episode explains how Microsoft Graph functions as a relationship and context engine connecting people, documents, meetings, identities, permissions, and collaboration signals across Microsoft 365.The conversation breaks down the three architectural layers powering modern Copilot experiences:The Microsoft Graph relationship layer, the Semantic Index for Copilot, and Fabric semantic models.Mirko explains how these systems work together to create meaning-aware retrieval experiences that allow AI systems to reason across organizational relationships rather than simply searching files by keyword.WHY COPILOT DEPLOYMENTS UNDERDELIVERMany organizations experience the same deployment pattern after rolling out Copilot. Early demos create excitement, but production usage slowly exposes retrieval problems, governance gaps, outdated citations, overshared content, and weak answer quality.This episode explains why these failures are usually not model problems. They are architecture problems caused by weak metadata structures, inconsistent governance, poor permissions hygi

Enterprise Resource Planning (ERP) modernization is no longer just a technology initiative — it is a business transformation journey that directly impacts people, processes, culture, and long-term growth. In this episode of the M365 FM Podcast, Mirko Peters sits down with Alicia King, Microsoft MVP, Pre-Sales Engineering Director at RSM US LLP, speaker, and ERP transformation expert, to explore what truly makes ERP projects successful. Drawing from more than 100 ERP transitions across 40+ countries, Alicia shares practical insights on Dynamics 365 Finance & Supply Chain, executive alignment, AI adoption, change management, data quality, and why leadership plays the biggest role in modernization success.WHY ERP MODERNIZATION IS REALLY ABOUT PEOPLE Alicia explains that ERP projects are often treated as technology deployments when they are actually people transformation programs. Organizations frequently focus too much on software capabilities while underestimating the importance of trust, communication, and cultural alignment. According to Alicia, successful ERP modernization starts with understanding where the company wants to go and aligning leadership, teams, and implementation partners around a shared vision. She emphasizes that businesses are not buying ERP systems simply to install software — they are investing in a better way to serve customers, improve visibility, and create scalable operations for future growth. DYNAMICS 365 FINANCE & SUPPLY CHAIN EVOLUTION The conversation dives deep into how Microsoft Dynamics 365 Finance & Supply Chain has evolved over the years. Alicia discusses the transition from AX 2009 to AX 2012 and ultimately to Dynamics 365, highlighting how Microsoft transformed the platform into a more connected and holistic ERP ecosystem. Instead of relying heavily on disconnected third-party applications, organizations can now manage finance, manufacturing, warehouse management, asset management, project operations, and supply chain workflows inside one integrated platform. She also explains how Microsoft’s acquisition strategy helped consolidate critical ERP functionality directly into the Dynamics 365 core application, reducing complexity while improving visibility and operational efficiency. THE BIGGEST ERP IMPLEMENTATION MISTAKES One of the strongest themes throughout the episode is the importance of executive alignment and realistic expectations. Alicia explains that many ERP projects fail because organizations underestimate the operational impact of transformation and overload employees who already manage full-time responsibilities. She stresses that ERP success requires strong project managers, transparent communication, proactive risk management, and leadership teams that actively support the change initiative. Without clear alignment between CIOs, CFOs, CEOs, and business leaders, ERP implementations can quickly become fragm

Microsoft Copilot gives answers that sound confident, polished, and intelligent. But in many enterprise environments, those answers are still incomplete, generic, or entirely wrong. The problem usually is not the model itself. The problem is grounding.In this episode, Mirko Peters breaks down the hidden architecture problem behind enterprise AI deployments and explains why most organizations are building Copilot on the wrong foundation from the start. If Copilot cannot access the systems where your company’s real knowledge lives, it cannot reason over the information your teams actually depend on every day.WHY COPILOT DOESN’T KNOW WHAT YOUR BUSINESS KNOWSLarge language models are trained on public information. Your organization’s real intelligence lives somewhere else entirely.Critical operational knowledge is spread across systems like ServiceNow, Salesforce, Jira, Confluence, GitHub, SharePoint, internal databases, and legacy applications that Copilot cannot automatically access out of the box.That creates what Mirko calls the “Grounding Gap” — the distance between what Copilot can see and what your organization actually knows.Without grounding, Copilot defaults to generic responses. And generic AI responses quickly become a trust problem inside enterprise environments.THE REAL REASON USERS STOP TRUSTING COPILOTMost AI adoption problems are not caused by poor prompting. They are caused by poor architecture.When users repeatedly receive answers that feel vague, incomplete, or disconnected from operational reality, confidence disappears fast. Once teams stop trusting the AI, adoption quietly dies.This episode explains why grounding quality matters more than prompt engineering and why enterprise AI success depends on feeding the model the right organizational context before a response is ever generated.GRAPH CONNECTORS VS PLUGINSOne of the biggest architectural decisions organizations face is choosing between Graph Connectors and Plugins.Mirko explains why these two models solve completely different problems:Plugins are designed for actions and real-time transactionsGraph Connectors are designed for organizational knowledge retrievalPlugins call live APIs at runtimeConnectors extend the Microsoft 365 Semantic IndexPlugins create operational workflowsConnectors create grounded AI reasoningMost organizations instinctively start with Plugins because they appear faster and simpler to deploy. But for enterprise knowledge retrieval, Connectors are almost always the better long-term architecture.INSIDE THE MICROSOFT 365 SEMANTIC INDEXThis episode goes deep into how the Microsoft 365 Semantic Index actually works.Rather than functioning like a traditional search engine, the Semantic Index creates a pre-computed semantic map of organizational knowledge using embeddin

Enterprise search is broken — and most organizations still don’t realize why. The problem is no longer storage. It’s no longer indexing. And it’s definitely no longer about adding more servers to your search infrastructure. The real issue is latency between reality and discoverability. In this episode of the M365FM Podcast, we explore why traditional enterprise search models are collapsing under the pressure of modern AI workflows and how Microsoft Graph API discovery is fundamentally rewriting the rules of semantic search performance. Most enterprise environments still rely on scheduled crawlers and periodic indexing jobs that scan SharePoint, Teams, Exchange, and file repositories on fixed intervals. But modern work doesn’t happen on schedules anymore. It happens continuously — through Teams chats, Loop components, collaborative Excel sessions, live meetings, Copilot interactions, and high-velocity organizational signals. By the time legacy crawlers finish scanning enterprise data, the organization has already changed again. This creates what we call the “staleness gap” — the dangerous period where employees, executives, and AI systems are making decisions using outdated context. And once semantic search systems start serving stale information into AI pipelines, retrieval becomes a liability instead of an advantage. In this episode, we break down the architectural shift from pull-based discovery to event-driven discovery powered by the Microsoft Graph API. Instead of forcing search engines to continuously crawl massive repositories looking for changes, Graph discovery allows systems to subscribe to organizational events in real time. The result is sub-second freshness, massively reduced infrastructure overhead, and AI systems that actually understand what is happening right now — not what happened six hours ago. We also explore why this transformation goes far beyond search performance. Modern enterprise AI now depends on live context, security-aware retrieval, GraphRAG architectures, delta query synchronization, semantic lineage tracking, and compliance-aware ingestion pipelines. This episode dives deep into the future of enterprise intelligence systems and explains why Graph-based discovery is becoming the foundational layer for next-generation semantic infrastructure.IN THIS EPISODEWhy traditional enterprise search architectures are failingThe hidden cost of stale semantic indexesHow Graph API delta queries eliminate full crawlsThe shift from “Pull” discovery to “Subscribe” discoveryWhy semantic search performance is now measured in millisecondsHow GraphRAG changes retrieval reasoning across enterprise dataThe security risks of vector stores and semantic leakageWhy security trimming becomes critical in AI retrieval systemsHow live meeting intelligence transforms organizational decision-makingThe future of real-time enterprise kno

Building multi-tenant SaaS on Power Pages changes the way architects think about Dataverse scalability. Most developers traditionally viewed Power Pages as a portal platform intended for forms, authentication, and moderate business applications. Enterprise-scale SaaS workloads were assumed to require fully custom Azure infrastructure and external databases. Elastic Tables challenge that assumption by introducing Cosmos DB-backed storage directly inside Dataverse, allowing Power Pages to support large-scale operational workloads while preserving the familiar Dataverse developer experience.WHY STANDARD DATAVERSE TABLES HIT LIMITS Standard Dataverse tables are optimized for relational transactional workloads such as CRM systems, account management, and business processes. They perform extremely well for structured business entities but begin struggling under workloads dominated by telemetry ingestion, event logging, audit history, and append-heavy operational data. As tenant counts grow, noisy-neighbor effects appear because all tenants compete for the same relational backend resources. The architecture problems become especially visible when SaaS platforms start accumulating massive volumes of operational records. Bulk write operations slow down, storage costs increase rapidly, and query performance degrades under high-ingestion scenarios. These are not flaws in Dataverse itself but rather signs that the workload no longer aligns with the strengths of Azure SQL-backed storage.Azure SQL excels at relational workloadsOperational SaaS data behaves differentlyMulti-tenant contention creates performance issuesStorage costs rise quickly at scaleELASTIC TABLES AND COSMOS DB Elastic Tables replace the underlying SQL engine with Azure Cosmos DB while preserving the same Dataverse APIs, security model, and Power Pages integration patterns developers already know. From the outside, the experience still feels like standard Dataverse development. Underneath, however, the storage model becomes horizontally scalable and partition-aware. Cosmos DB distributes records across logical partitions using PartitionId values. This enables Elastic Tables to scale write throughput horizontally rather than relying on a single database instance. Microsoft specifically designed Elastic Tables for telemetry, event streams, operational logging, and large append-heavy workloads that traditionally break relational systems at scale.Horizontal partitioning improves scalabilityBulk ingestion becomes dramatically fasterTTL support enables automatic data expirationDataverse APIs remain unchanged for developersPERFORMANCE DIFFERENCES THAT MATTER Elastic Tables dramatically outperform standard tables during batch operations such as CreateMultiple and UpdateMultiple requests. Community benchmarks showed improvements ranging between

For years, PowerShell scripts were the backbone of enterprise automation. Administrators built massive libraries of scripts to onboard users, manage licenses, provision devices, configure mailboxes, and automate repetitive operational tasks across Microsoft 365. Those scripts worked because enterprise environments were relatively predictable. Inputs were structured, workflows followed a fixed path, and administrators could usually anticipate the most common failure scenarios ahead of time. That model is now collapsing under the weight of modern cloud complexity. Enterprise environments have become dynamic systems filled with constantly changing APIs, hybrid infrastructures, compliance policies, device states, conditional access rules, and unpredictable user behavior. Traditional automation struggles because scripts are deterministic by design. They can only execute the logic that developers explicitly coded into them. The moment an environment behaves differently than expected, the script either breaks or requires another layer of conditional logic to keep functioning. Modern enterprise IT problems are no longer simple execution problems. They are reasoning problems.WHY DETERMINISTIC LOGIC NO LONGER SCALES Most PowerShell automation today is built around predefined workflows:Check if a user existsAssign licensesConfigure mailbox settingsSend notificationsThe problem is that real enterprise operations almost never follow clean workflows anymore. Tickets arrive as messy natural-language requests filled with incomplete context, ambiguous symptoms, and multiple overlapping problems. One issue may involve Azure AD, Intune, Conditional Access, Exchange Online, and SharePoint simultaneously. Instead of executing a fixed sequence, modern systems need to:Interpret context dynamicallyCorrelate data across systemsAdapt to unexpected conditionsDecide what action makes sense nextThis is where autonomous agents fundamentally change the architecture of automation.THE SHIFT FROM SCRIPTS TO REASONING AGENTS The future of enterprise automation is not about replacing PowerShell. It is about transforming PowerShell into an intelligent execution layer controlled by reasoning systems capable of understanding goals, interpreting environments, and dynamically orchestrating workflows. Autonomous agents introduce a completely different operational model. Instead of hardcoding every possible decision tree into a script, agents analyze the current situation and determine which tools should be used based on live context. These systems do not simply “run commands.” They reason about the problem itself. HOW AGENTS ACTUALLY THINK An autonomous workflow typically follows a repeating loop:Analyze the ticket or requestBuild a plan dynamicallyExecute the requ

For decades, enterprises built their digital workplaces around folders, directories, and deeply nested hierarchies. The assumption was simple: if information was organized into the right structure, people would always be able to find it. But in 2026, that assumption is collapsing under the weight of modern data complexity. Work no longer starts with navigation. It starts with context. This episode explores why traditional folder structures are becoming obsolete and how graph-based architecture is redefining the future of Microsoft 365, SharePoint, and enterprise collaboration. Instead of organizing files by location, modern systems organize information by meaning, relationships, and intent. The result is a complete shift away from static hierarchies toward intelligent connected knowledge networks.THE NAVIGATION MYTH Most organizations still accept “folder hell” as a normal part of work. But the cost is enormous. Research shows employees spend nearly nineteen percent of their day simply searching for information across folders, drives, and disconnected repositories. That represents a massive productivity tax hidden inside everyday collaboration. The problem is not just speed. Folder structures force users to remember where another human decided to save something years earlier. That creates constant cognitive overload and turns collaboration into an exercise in digital archaeology.WHY FOLDERS FAIL AT SCALEDeep hierarchies overwhelm human memoryFile duplication creates conflicting versions of truthTeams waste time navigating instead of creatingInformation becomes trapped inside organizational silosThe traditional directory model assumes data belongs in one place at one time. Modern enterprise information does not work that way anymore.THE COLLAPSE OF STATIC HIERARCHIES A single document today often serves multiple purposes simultaneously. A contract may represent a legal record, a revenue event, a project milestone, and a customer relationship artifact all at once. Traditional folders force organizations to choose one “correct” location, even though the data naturally exists across multiple business dimensions. That limitation creates one of the biggest enterprise problems in modern collaboration systems: duplication. When users cannot decide where a file belongs, they create copies. Those copies slowly diverge, producing conflicting versions of the truth across departments and workflows. What begins as organization eventually becomes fragmentation. The folder model was designed for physical filing cabinets. Enterprise data is no longer physical. It is relational.THE RISE OF MICROSOFT GRAPH AND SEMANTIC ARCHITECTURE This episode dives deep into the rise of Microsoft Graph and semantic indexing as the foundation of next-generation information architecture. Instead of treating files as isolated ob

The future of work is evolving faster than ever before, and in this exciting episode of the M365 podcast, Microsoft MVP Fabio Bonolo joins Mirko Peters for an in-depth conversation about AI, Microsoft Copilot, modern workplace transformation, productivity, leadership, and the rapidly changing world of work. Fabio brings a unique mix of technical expertise, business strategy, leadership experience, and community passion to the discussion, making this episode essential listening for IT professionals, business leaders, Microsoft 365 enthusiasts, and anyone trying to navigate the AI-powered workplace revolution. Fabio Bonolo is a Microsoft MVP, Team Leader Productivity at isolutions Switzerland, international speaker, and passionate advocate for helping organizations unlock the full value of Microsoft 365 and AI technologies. During the episode, Fabio shares his personal journey from sales executive to one of the most recognized voices in the Microsoft modern work ecosystem. His transformation accelerated during the rise of Microsoft Copilot in 2023, when he realized AI was going to fundamentally change how organizations work, collaborate, and innovate. One of the strongest themes throughout the conversation is that the future of work is no longer just about technology — it is about empowerment, mindset, culture, and helping people adapt confidently to change. Fabio explains that organizations are entering a completely new era where employees will spend less time clicking through applications and more time guiding, observing, and collaborating with AI-powered agents and automation systems. According to Fabio, the rise of autonomous AI agents and Copilot experiences represents one of the biggest workplace shifts in modern history.KEY TOPICS COVERED IN THIS EPISODEThe evolution of Microsoft Copilot and AI in the workplaceWhy AI adoption is changing digital transformation foreverThe future of productivity in hybrid work environmentsLeadership and communication during AI transformationChange management strategies for Microsoft 365 adoptionBuilding successful Copilot adoption programsThe role of company culture in AI readinessEmpowerment, employee growth, and workplace innovationData quality and governance for Microsoft CopilotHow modern organizations should approach AI educationFabio also discusses how organizations continue to underestimate the importance of change management when implementing Microsoft Copilot and AI technologies. Many businesses rush into AI adoption without preparing their employees, defining use cases, or establishing proper governance structures. Fabio emphasizes that successful AI transformation requires ongoing training, workshops, communication, and long-term investment in employee education. Organizations that simply purchase Copilot licenses without a strategy often struggle to generate real business impa

The future of work is no longer a distant concept — it is happening right now. In this powerful episode of the M365 podcast, Microsoft MVP Onyinye Madubuko joins Mirko Peters to explore how organizations can successfully design hybrid workplaces that improve collaboration, employee experience, and productivity using Microsoft 365, Microsoft Teams, Viva Insights, and AI-powered tools like Microsoft Copilot. Onyinye shares her remarkable journey from engineering and communications into the Microsoft ecosystem, where she now helps organizations transform digitally through modern workplace strategies. With nearly 15 years of IT experience, she explains how businesses often underutilize their Microsoft licenses and fail to unlock the true value of tools already available to them. This episode dives deep into the practical side of hybrid work adoption, digital transformation, AI readiness, and employee productivity in modern organizations. One of the standout conversations focuses on employee experience in hybrid work environments. Onyinye explains how Microsoft Viva Insights can help employees manage focus time, reduce burnout, and improve work-life balance through AI-driven recommendations and productivity insights. She highlights how organizations can empower employees rather than monitor them, using data responsibly to create healthier workplace habits and more effective collaboration patterns.KEY TOPICS DISCUSSED IN THIS EPISODEDesigning inclusive Microsoft Teams Rooms for hybrid collaborationImproving employee productivity with Viva InsightsAI-powered meeting experiences with Microsoft CopilotReducing meeting fatigue and improving workplace cultureCopilot adoption strategies and rollout best practicesChange management for Microsoft 365 transformationWomen in tech and building intentional communitiesCertification paths and Microsoft Learn opportunitiesThe episode also explores the technical and human side of Microsoft Teams Rooms. Onyinye explains why meeting room design matters more than ever in hybrid work scenarios. From camera placement and lighting to acoustics and accessibility, she shares practical recommendations organizations should consider when creating modern meeting spaces that support both in-office and remote employees equally. Artificial Intelligence is another major focus throughout the discussion. Onyinye breaks down how Microsoft Copilot is changing the way people collaborate, summarize meetings, generate insights, and automate repetitive tasks. She emphasizes that successful AI adoption is not just about deploying licenses — it requires governance, security assessments, training, and strong change management processes. Organizations that ignore data governance and oversharing risks may struggle to maximize the value of Copilot in Microsoft 365 environments.MICROSOFT COPILOT ROLLOUT BEST PRACTICES<ul

Most organizations still believe syncing SharePoint libraries directly into File Explorer is the best way to give users easy access to files. It feels familiar. It feels productive. But beneath the convenience lies one of the most overlooked architectural problems inside modern Microsoft 365 environments. Folder syncing is quietly creating data sprawl, governance chaos, security blind spots, and massive operational complexity across the enterprise. This episode breaks down why traditional sync-based collaboration models are becoming unsustainable in large-scale Microsoft 365 deployments and why SharePoint Shortcuts may actually be accelerating the problem instead of solving it.THE HIDDEN COST OF SYNCING At first glance, syncing folders appears harmless. Users get local access to files, offline availability, and a familiar desktop experience. But the moment organizations scale beyond a few hundred users, synchronization begins to introduce architectural instability. Every synced library creates another distributed endpoint copy of enterprise data. That means governance policies, retention rules, sensitivity labels, and compliance boundaries suddenly become much harder to enforce consistently across devices. What was originally designed for convenience slowly transforms into uncontrolled data replication.KEY PROBLEMS COVEREDData duplication across unmanaged endpointsSync conflicts and versioning chaosBroken governance and retention visibilitySecurity gaps caused by distributed file accessThe problem is not SharePoint itself. The problem is treating cloud-native collaboration like an old file server mapped drive.THE SHAREPOINT SHORTCUT ILLUSION Microsoft introduced SharePoint Shortcuts as a cleaner alternative to massive library synchronization. The idea sounds elegant: instead of syncing entire sites, users simply create shortcuts to important folders inside OneDrive. But shortcuts create their own layer of confusion. This episode explores how shortcuts blur ownership boundaries, create inconsistent user experiences, and make governance dramatically more difficult at scale. Users often lose visibility into where data actually lives, which team owns the content, and which policies apply to the files they are accessing. The result is an enterprise environment where nobody fully understands the true structure of the information architecture.WHY SHORTCUTS CREATE STRATEGIC RISKUsers mistake shortcuts for actual file ownershipData lineage becomes harder to trackGovernance policies lose contextual clarityPermission inheritance becomes increasingly fragileThe shortcut model optimizes convenience while quietly undermining long-term information architecture discipline.THE ENTERPRISE DATA SPRAWL PROBLEM One of the biggest themes in this episo

The world of enterprise communication has transformed dramatically over the last two decades — from traditional PBX systems and on-premises infrastructure to cloud collaboration, AI-powered meetings, and Microsoft Teams. In this episode of the M365 FM podcast, Mirko Peters is joined by Microsoft Teams MVP Carsten Lund Meilbak for an in-depth conversation about the evolution of collaboration technology and what the future of communication looks like inside Microsoft 365. Carsten shares his fascinating journey from the early days of PBX systems and telephony infrastructure to working with Microsoft Lync, Skype for Business, Teams Voice, Microsoft Teams Rooms, and AI-powered communication experiences. With decades of hands-on experience in unified communications, Carsten provides unique insights into how enterprise voice and collaboration platforms have evolved — and why Microsoft Teams has become the center of modern workplace communication.THE JOURNEY FROM PBX TO MICROSOFT TEAMS Before Microsoft Teams became the standard for collaboration, organizations relied heavily on traditional PBX systems, physical telephony hardware, and complex on-premises deployments. Carsten discusses how Microsoft disrupted the communication market with Lync and Skype for Business, even when those early products lacked many enterprise-grade capabilities at the beginning. The episode explores how unified communications slowly evolved from experimental cloud services into the fully integrated collaboration ecosystem we know today. THE EVOLUTION OF LYNC, SKYPE FOR BUSINESS, AND TEAMS The migration journey from Lync to Skype for Business and eventually Microsoft Teams was not always smooth. Mirko and Carsten revisit the challenges organizations faced during the transition period, including feature limitations, hybrid deployments, migration complexity, interoperability issues, and user adoption struggles. The discussion highlights how Microsoft gradually transformed Teams from a lightweight collaboration platform into a fully enterprise-ready communication solution. The episode also reflects on the unique era when companies had to operate both Skype for Business and Teams simultaneously — creating confusion around meetings, chat platforms, and collaboration workflows during Microsoft’s cloud transition. HOW COVID ACCELERATED THE CLOUD TRANSFORMATION One of the biggest turning points in modern collaboration came during the COVID-19 pandemic. Organizations that once planned slow, cautious migrations to the cloud suddenly had to enable remote work at massive scale almost overnight. Carsten explains how the pandemic dramatically accelerated Teams adoption and forced businesses to rethink collaboration, meetings, connectivity, VPN infrastructure, and hybrid work strategies. The conversation explores how Teams became the backbone for communication during one of the most disruptive workplac

The workplace is changing faster than ever — and AI is now becoming part of the team. In this episode of the M365 FM podcast, Mirko Peters sits down with Microsoft MVP Vesa “Vesku” Nopanen to explore how Microsoft Copilot, AI agents, Loop, and Copilot Pages are reshaping collaboration inside Microsoft 365. From practical adoption challenges to the future of AI coworkers, this episode dives deep into how organizations are moving from traditional teamwork toward a new era of AI-first collaboration.THE SHIFT FROM TEAM-FIRST TO AI-FIRST WORK For years, collaboration inside Microsoft 365 focused on Teams, SharePoint, and connected productivity experiences. But the rise of Copilot has accelerated a major transformation: AI is no longer just a tool — it is becoming an active participant in modern workflows. Mirko and Vesku discuss how quickly organizations have moved into this new AI-powered reality and why many companies still underestimate how disruptive Microsoft Copilot will become over the next few years. WHAT IS “COPILOT COWORK”? One of the central topics of the episode is Microsoft’s evolving “Copilot Cowork” concept. Instead of simply generating text or summarizing meetings, AI is increasingly acting like a digital coworker — helping employees organize information, automate repetitive tasks, assist decision-making, and collaborate across projects. The discussion also explores emerging Microsoft concepts such as:Copilot CoworkWorker IQCopilot SkillsAI AgentsAI DelegationVesku explains how these ideas could fundamentally change the way organizations think about productivity, teamwork, and knowledge work inside Microsoft 365. THE HUMAN SIDE OF AI ADOPTION Technology adoption is never only about technology. Mirko and Vesku discuss why many employees still feel uncertain or even nervous about AI inside the workplace. For some, AI represents productivity and opportunity. For others, it raises concerns about job security, trust, governance, and organizational change. The episode explores why AI literacy and strong adoption programs are becoming essential for successful Copilot deployments across enterprises.GOVERNANCE IN THE AGE OF AI As AI systems gain access to more organizational data, governance becomes more important than ever. The conversation explores how businesses must rethink:Permissions and access controlInformation architectureData qualityKnowledge organizationCompliance and securityResponsible AI usageWithout structured and trustworthy information, even the best AI experiences can produce poor results.KNOWLEDGE MANAGEMENT IS CHANGING One of the most fascinating discussions in the episode focuses on the future of knowledge management inside Microsoft 365. Organizations now manage information

Most Power Platform automations are failing for one simple reason: they were built for a world that no longer exists. Traditional low-code systems depend on rigid “if-then” logic, clean data, and predictable inputs. But modern enterprise data is chaotic, unstructured, and constantly changing. The result is what many organizations are experiencing right now — brittle automations that collapse the moment reality gets messy. This episode explores the massive architectural shift happening across the Power Platform ecosystem as AI transforms automation from deterministic logic into probabilistic design. Instead of asking, “Is this exactly correct?” modern systems ask, “How likely is this to be correct?” That subtle change is rewriting how enterprise workflows are designed, governed, and scaled.THE DEATH OF DETERMINISTIC AUTOMATION For years, enterprise automation depended on exact matches and structured logic. If a field matched perfectly, the flow continued. If a single character changed, the system failed. That worked when business data lived inside carefully structured databases. But today, most enterprise information exists in emails, PDFs, Teams chats, voice transcripts, and unstructured documents. Traditional Power Automate flows struggle in this environment because they cannot understand context or intent. A deterministic system sees “Invoice 202” and “Inv-202” as completely unrelated values. AI-powered systems see similarity instead of exactness. That shift changes everything.KEY TOPICS COVEREDWhy rigid low-code automations keep breakingThe rise of probabilistic workflow designHow confidence scores redefine governanceWhy fuzzy matching matters more than exact matchingThe future of automation is not about perfection. It is about resilience.THE RISE OF CONFIDENCE-BASED ROUTING One of the biggest changes AI introduces into Power Platform design is the concept of the confidence score. Instead of binary true-or-false logic, AI models return probabilities that quantify uncertainty. That means workflows can finally understand doubt instead of pretending certainty always exists. This episode breaks down the architecture behind confidence-based routing and explains how modern Power Platform solutions now separate actions into Green, Yellow, and Red confidence zones. High-confidence outputs move automatically. Medium-confidence results trigger human review. Low-confidence outputs are rejected or escalated before they damage production systems.WHY CONFIDENCE SCORES MATTERThey expose uncertainty instead of hiding itThey reduce silent automation failuresThey align business risk with automation logicThey enable scalable human-in-the-loop governanceThis is the foundation of what the episode calls the “Approximate Enterprise” — a world where systems are designe

Most IT leaders still believe Microsoft 365 native redundancy equals protection. It doesn’t. High Availability was designed to keep services running, not to recover your business after a destructive attack. The same synchronization engine that delivers collaboration at cloud speed can also replicate corruption, ransomware, and deletion events instantly across your environment. In 2026, the biggest threat isn’t infrastructure failure. It’s the assumption that synchronization equals safety. The reality is brutal. When ransomware hits a tenant, Microsoft 365 replication works perfectly. Every encrypted file, every malicious edit, and every destructive change is synchronized across SharePoint, OneDrive, and Teams before security teams can react. Native redundancy protects uptime, not integrity. And attackers know it.THE SYNCHRONIZATION TRAP Modern cloud environments are built around real-time replication. That speed is excellent for productivity but catastrophic during a cyberattack. The moment a malicious script starts modifying data, the platform distributes those changes everywhere. What most organizations think is “backup” is often just another synchronized copy of compromised data. The 501-version attack proves how dangerous this design really is. Many administrators believe version history acts like a recovery vault. It doesn’t. Versioning is simply metadata attached to a file. If attackers perform enough automated edits, the clean versions disappear permanently. Using Microsoft Graph API automation, ransomware groups can wipe recovery history across thousands of files in minutes.KEY RISKS INSIDE THE SYNC TRAPVersion history can be overwritten intentionallyRecycle Bin protections can be bypassed or emptiedGraph API automation accelerates tenant-wide destructionRecovery points remain connected to production identity systemsThe problem isn’t that Microsoft 365 is broken. The problem is that it performs exactly as designed. The sync engine does not understand intent. It simply moves data faster than humans can respond.THE SINGLE IDENTITY FAILURE Most organizations unknowingly place production data and backup systems behind the same identity perimeter: Microsoft Entra ID. That means one compromised Global Admin account can potentially access both the live environment and the “protected” recovery environment. At that point, your backup isn’t isolated. It’s just another room inside the same burning building. This is where the modern ransomware model becomes devastating. Attackers no longer focus only on passwords. They target OAuth consent flows, application registrations, and persistent tokens that bypass MFA entirely. Once malicious applications receive broad Graph API permissions, they can manipulate production data and backup repositories simultaneously.WHY NATIVE IMMUTABILITY FAILSShared identit

Microsoft Copilot is not just another productivity tool. It is a structural stress test for your entire Microsoft 365 environment. Most organizations still operate under a legacy “open by default” mindset built for human navigation, but AI changes the equation completely. Copilot can surface sensitive files, forgotten SharePoint content, orphaned Teams channels, and years of overshared documents within seconds. The challenge is not whether Copilot respects permissions—it does. The real problem is that most enterprise permissions were never designed for machine-speed retrieval. In this episode, we break down why governance—not licensing—is now the single most important factor in successful Copilot deployment.WHY “OUT-OF-THE-BOX” SECURITY ISN’T ENOUGH Many organizations assume Copilot is secure because it only shows users content they already have access to. But decades of poor SharePoint hygiene, inherited permissions, and “Everyone except external users” groups have created a massive visibility gap inside most tenants. AI eliminates obscurity. Sensitive documents hidden deep inside legacy sites are no longer difficult to find. Copilot can instantly synthesize and summarize information that employees were never actively searching for before. This episode explains how oversharing becomes exponentially more dangerous in the AI era and why organizations must move from “trust by default” to “verify by context.” KEY TOPICS COVEREDThe “Oversharing Multiplier” and why legacy SharePoint permissions are now a major AI riskHow indirect prompt injection attacks like EchoLeak and Reprompt change enterprise security modelsWhy traditional DLP is no longer enough for AI-powered workflowsHow Microsoft Purview becomes the governance backbone for Copilot deploymentsTHE NEW AI ATTACK SURFACE Copilot introduces a completely new category of enterprise risk. Instead of malware or traditional exploits, organizations now face natural-language attacks that manipulate AI behavior through documents, emails, and embedded instructions. The episode explores how Retrieval-Augmented Generation (RAG) pipelines can unintentionally process malicious instructions hidden inside business content. We discuss why prompt injection is becoming the “SQL injection” of the generative AI era and how enterprises must rethink security boundaries around prompts, context windows, and AI interactions themselves. RISK-TIERED DEPLOYMENT STRATEGIES Turning Copilot on for everyone at once is one of the biggest mistakes organizations make. Instead, successful enterprises are following a tiered rollout model. Tier 0 focuses entirely on remediation and data cleanup before any licenses are assigned. Tier 1 introduces Copilot to low-risk technical users and Centers of Excellence. Tier 2 expands adoption to broader business units like sales and marketing, while Tie

In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP, educator, technical storyteller, and community leader Karinne Diamond Bessette to explore one of the biggest productivity challenges in the modern workplace: information chaos. Between OneNote, Loop, Teams, Copilot, Planner, Whiteboard, Outlook, and SharePoint, employees today have more places than ever to store ideas, tasks, meeting notes, project updates, and collaborative content. The result? Many organizations struggle to decide where information should actually live and how to keep everything organized, searchable, and actionable.THE EVOLUTION OF MICROSOFT 365 COLLABORATIONKarinne shares her journey from support engineering and operations into the world of enablement, technical storytelling, and Microsoft 365 advocacy. Her experience helping both technical and non-technical users gives her a unique perspective on how collaboration tools should work in real-world environments. Throughout the episode, she repeatedly emphasizes the importance of translating technology into something humans can actually understand and use effectively. One of the central themes in the discussion is the growing complexity of the Microsoft 365 ecosystem. What once started as a productivity suite focused on Word, Excel, and Outlook has evolved into a massive connected collaboration platform with overlapping tools, AI integrations, and constantly changing workflows. Karinne explains that while flexibility is valuable, it also creates a major challenge for users trying to decide where to create notes, how to manage information, and how to avoid duplication.WHY ONENOTE STILL MATTERSThe conversation dives deeply into the evolution of note-taking itself. Karinne explains how she originally moved from scattered text files on her desktop into OneNote because it allowed her to centralize and search information more effectively. However, she also introduces one of the most memorable quotes of the episode: “OneNote is where notes go to die.” The problem, according to Karinne, is not that OneNote is bad. The issue is that many users capture information inside notebooks but never revisit it, organize it properly, or connect it to actionable workflows. Important ideas often disappear into large personal notebook structures without reminders, visibility, or collaboration.HOW LOOP IS CHANGING TEAMWORKThis naturally leads into one of the episode’s biggest topics: Microsoft Loop. Karinne explains why Loop has become one of her favorite tools inside the Microsoft ecosystem. She describes Loop as a bridge between email, Teams, tasks, and collaborative content. Rather than creating multiple copies of information across different applications, Loop allows users to maintain a single shared component that stays synchronized everywhere it appears. This creates what she calls a “single source of truth” experience for

In this deeply human and thought-provoking episode of the m365.fm podcast, Mirko Peters sits down with workplace transformation expert Janet Robb to discuss one of the biggest hidden challenges of the AI revolution: anxiety. While most conversations around AI focus on productivity, automation, Copilot, prompts, and innovation, this episode focuses on the emotional reality many employees and IT professionals are silently experiencing every single day. Together, Mirko and Janet explore AI overload, workplace culture, digital stress, fear of being left behind, communication gaps, social pressure, learning fatigue, and the emotional side of modern digital transformation. This episode is not about hype — it is about people.THE HUMAN SIDE OF AI ADOPTIONOne of the strongest themes throughout the conversation is the fact that organizations often focus heavily on technology while forgetting the emotional impact AI is having on employees. Janet explains how many people currently feel overwhelmed by:Constant AI announcementsEndless new toolsRapid platform changesInformation overloadNew terminologyPressure to “keep up”Fear of becoming irrelevantThe discussion highlights how AI adoption is not only a technical transformation but also a psychological one. Janet repeatedly emphasizes that many employees are quietly carrying stress, fear, shame, uncertainty, and guilt while pretending they understand everything happening around them.THE PROBLEM WITH AI TERMINOLOGYOne of the most fascinating parts of the episode focuses on language itself. Janet explains how AI has introduced an explosion of new terms, acronyms, buzzwords, and phrases that many people simply do not understand. Instead of creating inclusion, organizations often unintentionally exclude employees by assuming everyone already knows what terms like:AgentsPrompt engineeringFoundation modelsMLOpsRAGLLMsVector databasesCopilot orchestrationactually mean. The conversation highlights how dangerous assumptions can become in digital transformation projects. Janet shares how her own experience with dyslexia taught her the importance of asking questions without shame and why organizations need to create safe environments where employees feel comfortable saying:“I don’t understand.”WHY WORKPLACE CULTURE MATTERS MORE THAN TECHNOLOGYA major topic throughout the episode is the relationship between AI tools and workplace culture. Janet explains that technology itself is not necessarily the biggest problem. Instead, many organizations fail because the culture around technology adoption is unhealthy. The episode explores:Fear-based culturesPressure to performAI guiltUnrealistic expectationsProductivity anxiet

In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP, MCT, cloud security expert, and community leader Martin Dimovski to explore one of the most important topics in modern enterprise IT: securing AI workloads and MLOps environments inside the Microsoft Cloud. Together, they dive deep into secure-by-design architecture, AI security risks, DevSecOps, Prompt Injection attacks, identity protection, Microsoft Defender, GitHub Advanced Security, and the future of AI-driven cyber threats. Martin shares his personal journey from IT support engineer into cloud security and AI security architecture, explaining how years of experience in infrastructure, Azure, DevOps, and Microsoft technologies ultimately pushed him toward cybersecurity and AI governance. The discussion highlights why AI security is no longer optional and why organizations that move too fast without proper security foundations could face major problems in the coming years.WHY AI SECURITY MATTERS NOW MORE THAN EVER One of the strongest themes throughout this episode is the speed at which organizations are deploying AI systems without fully understanding the security implications behind them. Martin explains that many companies are currently:Deploying AI solutions rapidlyExperimenting with LLM integrationsBuilding AI agentsCreating cloud-native AI workloadsUsing open-source AI modelsIntegrating APIs into production environmentsBut at the same time, organizations often forget the security fundamentals that should protect these environments. The conversation explores how AI introduces completely new attack surfaces while simultaneously amplifying existing security problems.WHAT “SECURE-BY-DESIGN” REALLY MEANS A major focus of the episode is understanding the concept of secure-by-design architecture. Martin explains that security should never be added after development is complete. Instead, security conversations must begin at the very first design phase of any application or AI project. The discussion covers:Threat modelingArchitectural reviewsIdentity securityAuthentication planningSecure pipelinesInfrastructure protectionSecure APIsData governanceMartin shares why collaboration between developers, architects, DevOps engineers, and security teams is absolutely essential for building resilient AI systems. One of the key takeaways:Security teams should not become blockers for innovation — they should become partners in building secure systems.UNDERSTANDING MLOPS & DEVSECOPS For listeners newer to AI infrastructure topics, Martin breaks down the differences between:DevOpsDevSecOpsMLOpsSecure AI pipelinesThe episode explains how machine learning operations combine inf

In this episode of the m365.fm podcast, Mirko Peters sits down with cybersecurity expert Viktor Hedberg to explore one of the most critical — and misunderstood — areas of enterprise IT security: Active Directory tiering, privileged access, identity protection, and defending modern hybrid environments. With years of experience in incident response, offensive security, Active Directory hardening, and enterprise defense at Truesec, Viktor brings practical, real-world insights into how organizations can dramatically improve their security posture before attackers exploit their weaknesses. The conversation begins with Viktor sharing his personal journey into cybersecurity. Unlike many traditional security professionals, Viktor did not come from a university background. Instead, he worked his way from helpdesk and system administration into consultancy and incident response, gaining deep technical knowledge of Windows, Active Directory, infrastructure, and enterprise security along the way. That hands-on experience became the foundation for understanding both how to secure systems and how attackers compromise them.WHY ACTIVE DIRECTORY IS STILL A MASSIVE TARGET One of the strongest themes throughout the episode is the fact that Active Directory is far from dead. Despite the rise of Microsoft Entra ID, cloud-first environments, and SaaS adoption, Active Directory still remains the backbone of identity and access management in countless organizations worldwide. Viktor explains why attackers continue targeting Active Directory environments:Cached credentialsPassword hashes stored locallyKerberos ticketsOverprivileged accountsWeak administrative separationPoor tiering implementationExcessive lateral movement opportunitiesThe discussion highlights how many organizations unknowingly expose highly privileged accounts simply by allowing administrators to sign into workstations, laptops, and servers without restrictions. Viktor explains that in many environments, compromising a single endpoint can ultimately lead to full domain compromise because of how Windows authentication and credential storage work internally.UNDERSTANDING AD TIERING A major focus of the episode is understanding the concept of Active Directory administrative tiering. Viktor breaks down how organizations can separate systems and administrative responsibilities into different security tiers to limit credential exposure and reduce the blast radius during an attack. The discussion explores:Tier 0 systemsTier 1 serversEndpoint administrationDomain controllersEntra Connect serversPKI infrastructureAdministrative boundariesCredential isolationOne of the key lessons from the episode is that organizations often underestimate which systems actually belong in Tier 0. Viktor expl

In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP Evi van der Velden to discuss one of the most underestimated topics in modern IT: simplicity. Together, they explore Microsoft 365 governance, Copilot adoption, metadata, SharePoint, user adoption, digital stress, AI readiness, and why organizations often make technology far more complicated than it needs to be. Evi shares her unique journey into the Microsoft ecosystem, moving from leisure management and event organization into the world of Microsoft 365, user adoption, and governance. In just five years, she became a recognized Microsoft MVP and one of the strongest voices in the community around practical Microsoft 365 adoption and simplification strategies. The conversation focuses heavily on the human side of technology and why successful Microsoft 365 environments are not built only through technical configurations, but through communication, training, governance, and helping users understand how to work smarter.WHY MICROSOFT 365 FEELS OVERWHELMING One of the biggest themes in this episode is the increasing complexity of the Microsoft ecosystem. Evi explains how Microsoft 365 has evolved far beyond Word, Excel, and PowerPoint into a massive connected platform including Teams, SharePoint, OneDrive, Power Platform, Copilot, Viva, and many other services. While the platform offers incredible flexibility and possibilities, many organizations struggle because users simply do not understand how the tools work together. The discussion explores:Information overloadTool fatigueUser confusionRapid feature changesAI disruptionGovernance complexityEvi shares why simplicity is not about removing functionality, but about helping users focus on the right tools and the right workflows for their daily work.THE REAL VALUE OF SHAREPOINT One of the most interesting parts of the episode is Evi’s passion for SharePoint. While many people still think of SharePoint as only a document management platform, Evi explains why she sees SharePoint as the engine behind the entire Microsoft 365 ecosystem. The conversation dives into:SharePoint ListsDocument librariesMetadataPower Platform integrationPower AppsPower AutomateLifecycle managementKnowledge managementEvi shares practical examples of how SharePoint can be used as a flexible front-end for business solutions and automation without creating unnecessary technical complexity.WHY COPILOT ADOPTION OFTEN FAILS The discussion naturally shifts toward Microsoft Copilot and AI adoption. Evi explains that many organizations still approach Copilot completely wrong. They buy licenses, provide one training session, and then expect employees to magically change the way they work. According to Evi, succes

In this episode of the m365.fm podcast, Mirko Peters sits down with Craig White, double Microsoft MVP, AI Platform Lead, governance specialist, and co-host of the Power Platform Panic Room podcast. With more than twenty years of experience across SQL Server, SharePoint, Microsoft 365, Power Platform, and Copilot Studio, Craig shares deep insights into governance, citizen development, AI readiness, scalable Power Platform adoption, and the future of low-code inside the Microsoft ecosystem. This conversation goes far beyond generic Power Platform discussions. Instead, it focuses on the real-world operational challenges organizations face when trying to scale Power Platform safely while still empowering makers and enabling innovation.WHY GOVERNANCE SHOULD ENABLE — NOT BLOCK One of the strongest themes throughout the episode is Craig’s philosophy around governance. He explains why governance should never be about stopping people from building solutions. Instead, governance should create guardrails that allow organizations to innovate safely at scale. Craig shares how many companies still approach Power Platform with fear, often worrying that citizen developers will create chaos, expose data, or bypass IT processes. But according to Craig, the real danger is not enabling users at all. When organizations completely block innovation, shadow IT simply moves outside the organization. The discussion explores why governance frameworks should feel almost invisible for makers while still protecting the organization through:Environment strategiesData Loss Prevention policiesSecurity boundariesAPI governanceControlled connectorsLifecycle managementCraig explains that the goal is not to remove freedom but to create safe paths for innovation.THE REALITY OF POWER PLATFORM GOVERNANCE Craig highlights how unique Power Platform governance really is compared to traditional Microsoft technologies. Unlike older systems where access was centrally controlled, Power Platform arrived enabled by default. Many organizations never realized employees already had access to build apps, flows, automations, and AI solutions for years. This creates a completely different governance challenge. Craig explains how organizations often discover thousands of apps, flows, and automations already running inside their tenant before governance processes even exist. The episode explores why governance maturity starts with visibility and understanding what already exists inside the environment. The discussion also dives into:Default environment risksTenant settingsEnvironment provisioningDLP policiesGovernance automationConnector restrictionsEnterprise administrationAI, COPILOT & THE NEXT EVOLUTION OF POWER PLATFORM The conversation naturally shifts toward AI and Copilot

In this episode of the m365.fm podcast, Mirko Peters sits down with Ralph Rivas (MVP), also known as the “Copilot Junkie,” to explore the current reality of Microsoft Copilot, AI adoption, governance, automation, and enterprise readiness. Together they go far beyond the marketing demos and discuss what organizations actually need to do to make AI successful inside Microsoft 365. Ralph shares his journey from early SharePoint days into the Power Platform and Microsoft 365 ecosystem, explaining how governance and architecture became critical long before AI entered the conversation. The discussion highlights why many organizations still underestimate the importance of data governance, permissions, security, and information architecture before rolling out Copilot or autonomous agents. The conversation also dives into why Microsoft intentionally released Copilot early, how the platform has matured over time, and why Copilot today is becoming one of the strongest enterprise AI solutions because of its deep integration across Outlook, Teams, SharePoint, Excel, and the broader Microsoft 365 ecosystem.WHY AI GOVERNANCE IS NOW A BUSINESS REQUIREMENT One of the biggest topics in this episode is governance. Ralph explains why AI does not create governance problems — it exposes the problems organizations already had. The episode explores how organizations often rush into Copilot deployments without properly reviewing permissions, oversharing risks, compliance requirements, or security controls. Once AI gains access to enterprise content, weak governance quickly becomes visible. Mirko and Ralph discuss:AI governance strategiesSecurity readiness before Copilot rolloutShadow AI and uncontrolled ChatGPT usageMicrosoft Purview and complianceResponsible AI policiesEnterprise data protectionRalph emphasizes that organizations must prepare their environments before enabling AI at scale and explains why governance teams are now more important than ever.COPILOT STUDIO, AGENTS & MICROSOFT FOUNDRY The episode takes a deep technical turn into Copilot Studio, autonomous agents, MCP integrations, and Microsoft Foundry. Ralph explains the differences between:Copilot StudioCustom CopilotsAutonomous AgentsMicrosoft FoundryAzure AI architecturesThe discussion covers when organizations should use low-code AI solutions versus enterprise Azure-based architectures and why Copilot Studio is rapidly evolving into a serious enterprise automation platform. The conversation also explores the future of autonomous agents and why “human in the loop” governance remains critical as AI systems become more proactive and capable of making decisions independently.LOW-CODE, PRO-CODE & THE FUTURE OF DEVELOPMENT Another major topic is the changing relationship between low-code and

Artificial Intelligence is rapidly transforming the Microsoft 365 ecosystem. Organizations everywhere are deploying Microsoft Copilot, experimenting with AI agents, automating workflows, and integrating intelligent systems into their daily operations. But while companies are rushing toward AI adoption, most are overlooking one critical reality: their governance policies were never designed for AI. In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft Regional Director, MVP, collaboration strategist, and governance expert Christian Buckley to explore why traditional Microsoft 365 governance approaches are no longer enough in an AI-driven world. This conversation goes far beyond generic AI discussions and dives deep into the operational challenges organizations now face around permissions, compliance, information architecture, metadata, lifecycle management, Copilot readiness, and responsible AI adoption.WHY AI CHANGES GOVERNANCE COMPLETELY For years, governance inside Microsoft 365 focused primarily on collaboration management, SharePoint permissions, Teams provisioning, compliance controls, and external sharing. But AI changes the entire equation. Christian explains how tools like Microsoft Copilot can now surface information across multiple systems instantly, making old governance gaps far more visible than ever before. Content that technically existed inside Microsoft 365 for years — but remained difficult to discover — can suddenly become accessible through AI-powered discovery experiences. That creates major risks for organizations with:Poor permissions managementOvershared Teams environmentsBroken SharePoint inheritanceUnmanaged OneDrive contentInconsistent metadata structuresAccording to Christian, AI does not create governance problems. It exposes the governance problems organizations already had.THE HIDDEN DANGER OF PERMISSIONS SPRAWL One of the biggest topics throughout the episode is permissions sprawl inside Microsoft 365 environments. Over the years, many organizations accumulated forgotten sharing links, legacy SharePoint permissions, unused Teams workspaces, stale guest accounts, and poorly managed collaboration sites. Before AI, much of this remained hidden because users rarely searched deeply enough to accidentally discover sensitive information. But AI changes discoverability completely. Christian compares this shift to the original impact of Microsoft Delve, where users suddenly realized how much information they already had access to without understanding it beforehand. With Copilot and AI-powered search experiences, this effect becomes dramatically larger because intelligent systems can aggregate information, summarize documents, identify relationships, and surface hidden content instantly. This makes governance maturity one of the most important foundations for successful AI adoption. <br

Artificial Intelligence is moving faster than almost any technology wave we have seen before. Every week brings new models, new copilots, new frameworks, new AI agents, and endless promises about autonomous systems replacing repetitive work across the enterprise. But beneath all the hype lies a deeper engineering problem. Too many organizations are building AI systems with Large Language Models at the center of everything — while completely ignoring architecture, orchestration, state management, observability, governance, and deterministic engineering principles. In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft AI MVP, CTO, international speaker, and author Karthikeyan VK to discuss one of the most important realities of enterprise AI today: why most AI agent architectures are fundamentally flawed from an engineering perspective. This conversation goes far beyond AI hype and dives deep into what actually matters when building scalable, reliable, enterprise-grade AI systems with Microsoft Azure AI Foundry, orchestration patterns, memory management, evaluation pipelines, multi-agent architectures, and domain-specific AI solutions.WHY MOST AI AGENTS ARE BUILT WRONG According to Karthikeyan, one of the biggest mistakes organizations make today is trying to use Large Language Models for everything. Instead of treating the LLM as a reasoning engine or orchestration layer, many teams try to make the model itself perform every business operation directly. The result is often a probabilistic system attempting to replace deterministic engineering. And that creates serious reliability problems. Karthikeyan explains that enterprise systems cannot behave unpredictably. If an AI system returns different results for the same financial transaction, customer workflow, or approval process, organizations immediately lose trust. That is why AI agents must still be engineered like traditional enterprise software systems — with architecture, orchestration, retries, validation, observability, and governance built into the foundation. THE REAL ROLE OF LLMs IN ENTERPRISE SYSTEMS One of the strongest insights from the episode is the distinction between probabilistic and deterministic systems. Large Language Models are probabilistic by nature. They generate outputs based on probability distributions, context windows, and token prediction patterns. Enterprise workflows, however, are often deterministic:Financial calculationsInventory managementIdentity systemsCompliance workflowsERP integrationsSecurity processesAccording to Karthikeyan, organizations should stop trying to make LLMs replace deterministic engineering logic. Instead:The LLM should act as the reasoning layerDeterministic tools should execute workflowsBusiness logic should remain controlledOrchestration should dri

The retirement of Exchange Web Services (EWS) marks one of the biggest transitions in Microsoft messaging development in nearly two decades. For organizations still relying on legacy Exchange integrations, migration is no longer optional — it is urgent. In this episode of the m365.fm podcast, Mirko Peters sits down with longtime Exchange developer, Microsoft MVP, blogger, open-source contributor, and messaging expert Glen Scales to discuss the end of EWS, the future of Microsoft Graph, and what developers and organizations need to do right now before Microsoft permanently disables EWS in Exchange Online. With more than twenty years of experience building against Exchange APIs, Glen has lived through nearly every generation of Microsoft messaging development — from CDO and WebDAV to EWS, OAuth, and Microsoft Graph. His blog posts, GitHub repositories, Stack Overflow answers, and Substack articles have helped thousands of developers solve real-world Exchange and Microsoft 365 challenges. This conversation dives deep into API evolution, migration strategies, Graph limitations, mail architecture, authentication, throttling, notifications, synchronization, PowerShell automation, and the changing future of enterprise messaging development.WHY THE END OF EWS MATTERS Microsoft will retire Exchange Web Services in Exchange Online beginning in October 2026, with full removal completed in April 2027. That means:Applications using EWS against Microsoft 365 will stop workingOrganizations must identify legacy dependencies nowVendors and internal development teams need migration plans immediatelyOld synchronization models may need redesignsSecurity and permission models must be modernizedGlen explains that many organizations still do not realize how deeply EWS is embedded inside older enterprise applications, migration tools, CRM systems, provisioning systems, custom workflows, and legacy automation scripts. Some organizations may even discover unknown EWS dependencies years after original developers left the company.HOW EXCHANGE DEVELOPMENT EVOLVED One of the most fascinating parts of the episode is Glen’s perspective on the evolution of Exchange development itself. He describes how messaging development once represented some of the most advanced enterprise programming work available. Back in the early Exchange days, APIs like MAPI and EWS offered developers extremely deep access to mailbox data, calendar structures, public folders, and messaging workflows. Over time, Microsoft shifted toward:Cloud-first architectureREST APIsJSON payloadsOAuth authenticationGranular permissionsSecurity-first developmentWebhook-based integrationsMicrosoft Graph standardizationThis transition fundamentally changed how developers build integrations and applications around Mi

Behind every great Power BI solution is more than just dashboards and data models. There is logic, automation, storytelling, optimization, architecture, and most importantly — community. In this episode of the m365.fm podcast, Mirko Peters sits down with Bernat Agulló Roselló, Microsoft MVP, Senior BI Developer Partner at Sabrina, Tabular Editor contributor, organizer of the Power BI & Fabric Barcelona User Group, and one of the most passionate voices in the Power BI community today. From DAX optimization and semantic model automation to community building and multilingual collaboration, this conversation explores the technical depth and human side of modern Business Intelligence. Bernat shares his journey from Excel macros and reporting automation to becoming a recognized expert in DAX, Tabular Editor scripting, semantic modeling, and enterprise Power BI development. But this episode is not just about technology. It is also about curiosity, learning, international experiences, and the incredible role that community plays in shaping careers, opportunities, and innovation across the Microsoft Data Platform ecosystem.THE JOURNEY FROM EXCEL TO POWER BI Bernat’s BI journey started long before he officially realized he was working in Business Intelligence. While working with Excel macros inside manufacturing environments like Nissan, he was already building reporting automation, aggregating data from multiple sources, and solving business reporting challenges long before terms like “semantic modeling” or “data warehousing” became part of his vocabulary. Eventually, after reading Kimball’s Data Warehouse Toolkit and diving deeper into BI concepts, Bernat recognized that he had already been practicing many foundational Business Intelligence principles for years. This realization sparked a deeper passion for analytics, Power BI, DAX, automation, and semantic modeling that continues today. WHY DAX CHANGES EVERYTHING One of the strongest technical themes throughout the episode is DAX — Data Analysis Expressions — the language behind Power BI calculations and advanced analytics. According to Bernat, one of the biggest misconceptions people have about DAX is assuming it behaves like Excel formulas. In reality:DAX depends heavily on semantic modelsRelationships are criticalFilter context changes everythingMeasures and calculated columns behave fundamentally differentlyUnderstanding context transition is essentialBernat explains how learning the foundations of DAX and semantic modeling completely changes how developers approach Power BI solutions. He strongly recommends that anyone serious about Power BI eventually studies “The Definitive Guide to DAX” by Marco Russo and Alberto Ferrari — a book that fundamentally shaped his own understanding of the platform.THE POWER OF TABULAR EDITOR Another major focus of t

Deploying Microsoft Copilot is easy. Driving real adoption, measurable impact, and long-term behavioral change across an organization? That is the real challenge. In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP, Copilot Architect, adoption expert, and Copilot Team Lead at Billennium, Edyta Gorzoń, for a deep and highly practical conversation about what truly makes Copilot adoption successful inside modern organizations. While many companies focus heavily on licensing, governance, and technical rollout, Edyta explains why successful AI transformation is ultimately about people, communication, culture, and change management. Throughout the episode, she shares real-world lessons from customer projects, common mistakes organizations continue to make, and practical strategies that help companies move from simply deploying AI to genuinely transforming the way employees work. With more than a decade of experience in Microsoft technologies and a strong business background, Edyta brings a unique perspective to the AI conversation. Her focus is not just on technology itself, but on understanding users, organizational behavior, productivity patterns, communication strategies, and how businesses can create sustainable adoption models that actually deliver ROI.WHY COPILOT ADOPTION IS MORE THAN JUST TRAININGOne of the strongest themes throughout the episode is that Copilot adoption cannot be solved through generic feature-based training sessions alone. According to Edyta, many organizations mistakenly believe that purchasing Copilot licenses and scheduling a few training sessions automatically guarantees success. In reality, adoption requires a much broader strategy that includes governance, communication, behavioral change, scenario-based enablement, leadership involvement, and continuous support. She explains that organizations often experience temporary spikes in Copilot usage immediately after training sessions, only to see activity quickly decline again afterward. This happens because users never fully integrate AI into their daily workflows and routines. Building sustainable habits becomes far more important than simply delivering technical knowledge. CHANGE MANAGEMENT IS THE REAL DIFFERENTIATOR Edyta believes change management has become one of the most critical success factors for AI transformation projects. In previous Microsoft 365 adoption waves, organizations focused heavily on enabling tools like Teams, SharePoint, and OneDrive. But AI introduces entirely new emotional and cultural challenges:Fear of job replacementConcerns around data privacyDistrust in AI-generated contentResistance to changing workflowsUncertainty around productivity expectationsSome employees even feel that using AI is somehow “cheating” or replacing their own expertise. Because of this, Edyta emphasizes the importance of underst

Artificial Intelligence is moving faster than most organizations can keep up with. Every week introduces new models, new frameworks, new AI agents, and entirely new ways to build applications. But beyond the hype, one question matters most: how do enterprises actually build secure, scalable, production-ready AI solutions that create real business value? In this episode of the m365.fm podcast, Mirko Peters sits down with Jannik Reinhard — Microsoft MVP, architect, author, speaker, and AI innovator — for an in-depth conversation about Microsoft Foundry, enterprise AI architecture, agentic workflows, orchestration, governance, and the future of AI-powered applications. Jannik is deeply embedded in both the AI and security worlds. He has published more than 200 technical blog posts, speaks internationally at major conferences, contributes heavily to the community, and has built enterprise-grade AI systems used by over 120,000 employees inside BASF. His experience spans Microsoft Azure, Security, Endpoint Management, AI architecture, automation, and next-generation enterprise development. This episode is not another surface-level AI conversation. Instead, it explores the real technical and strategic challenges organizations face when moving from AI demos to fully operational enterprise AI platforms.WHY MICROSOFT FOUNDRY MATTERS For many people, Microsoft Foundry is still a relatively new concept. Jannik explains Foundry in simple but powerful terms: it provides organizations with a secure, enterprise-ready way to deploy and manage AI models inside Microsoft’s trusted cloud ecosystem. Through Foundry, organizations can:Deploy OpenAI and Anthropic models securelyUse enterprise-grade networking and encryptionIntegrate with Azure services and managed identitiesProtect against prompt injection attacksBuild AI agents and workflowsConnect models to business data securelyMonitor AI applications at scaleJannik emphasizes that Foundry is not just about model hosting. It becomes the orchestration layer that enables organizations to safely operationalize AI inside enterprise environments.AI IS NOT THE STRATEGY One of the strongest messages throughout the episode is that simply buying AI tools does not equal digital transformation. Jannik explains that many companies mistakenly believe purchasing Copilot licenses automatically gives them an AI strategy. In reality, organizations need much deeper thinking around business processes, governance, security, data quality, orchestration, and automation. According to Jannik, the most successful organizations are not the ones blindly following hype. They are the ones asking:Which business problems should AI solve?Where does AI create measurable value?How can AI improve workflows?Which processes should become autonomous?How can governanc

Artificial Intelligence is transforming the enterprise world faster than most organizations can adapt. Every company wants AI. Every executive wants Copilot. Every IT department is under pressure to modernize. But as AI adoption accelerates, one critical question continues to grow louder: how do organizations stay secure while embracing the future? In this deep-dive episode of the m365.fm podcast, Mirko Peters sits down with Danilo Nogueira from Microsoft to explore the rapidly evolving intersection of AI, security, compliance, insider risk, automation, and data governance. This conversation goes far beyond hype and marketing buzzwords. Instead, it delivers practical, real-world insights directly from someone working inside Microsoft’s security ecosystem every single day. Danilo currently works as a Senior Product Manager at Microsoft focused on Microsoft Purview, Insider Risk Management, Data Security, and AI-driven security experiences. With more than twenty years of experience across productivity, compliance, SharePoint, enterprise architecture, governance, and security, Danilo brings a rare perspective that combines deep technical knowledge with hands-on customer experience. Throughout the episode, Danilo explains why AI is fundamentally changing the way organizations must think about security. Traditional “block everything” approaches no longer work in modern cloud environments. Instead, organizations need visibility, monitoring, intelligent automation, and strong governance strategies that still allow employees to remain productive and innovative.THE REAL CHALLENGE OF AI ADOPTION One of the biggest misconceptions around AI adoption is that deploying Copilot or enabling AI tools automatically creates productivity gains. Danilo explains that many organizations are rushing into AI without understanding the security implications hidden underneath their existing environments. Oversharing in SharePoint, poorly managed permissions, weak governance strategies, uncontrolled file access, and missing classification policies can suddenly become massive risks once AI systems gain access to organizational data. What employees previously struggled to find manually can now be surfaced instantly through AI-powered discovery. This is why Danilo repeatedly emphasizes the importance of “AI readiness.” AI readiness is not about licensing. It is not about deploying a chatbot. It is about understanding your data, your permissions, your governance model, and your organizational culture before AI becomes deeply integrated into daily operations. WHY OVERSHARING IS THE BIGGEST RISK According to Danilo, oversharing remains one of the most dangerous and underestimated problems inside Microsoft 365 environments today. Many organizations have spent years granting broad permissions across SharePoint sites, Teams, file shares, and collaboration platforms without fully understanding the long-term consequences. No

In this episode of the m365.fm podcast, Mirko Peters sits down with Azure MVP and Microsoft Certified Trainer Vladimir Stefanovic to discuss one of the most underestimated topics in modern cloud architecture: Azure Governance at Scale. With more than twenty years of IT experience, Vladimir shares real-world lessons from enterprise cloud environments, large-scale Azure architectures, networking, identity, automation, and governance projects that either succeeded because of strong planning — or failed because of poor early decisions. The conversation starts with Vladimir’s journey from installing operating systems, configuring printers, and building small local networks to becoming a globally recognized Azure expert focused on governance, networking, infrastructure, and cloud strategy. He explains why understanding the foundations of infrastructure and networking is still critical today, even in a cloud-first and AI-driven world where many engineers jump directly into modern services without understanding the basics underneath.WHY GOVERNANCE MUST START ON DAY ZERO One of the core themes of this episode is that governance cannot be an afterthought. Vladimir explains why organizations often focus on applications, features, and rapid growth first, while governance, landing zones, permissions, automation, and security are pushed aside until systems become too large and too complex to fix easily. He compares poor cloud planning to building a house without designing the foundation first. The episode dives into:Why governance decisions become exponentially harder laterThe risks of unmanaged Azure growthWhy “temporary” environments often become permanent production systemsTHE REAL COST OF BAD AZURE DECISIONS Vladimir explains how early architectural mistakes can create enormous operational and financial problems later. From incorrect networking models and weak permission structures to unmanaged subscriptions and missing automation, the episode explores how technical debt grows inside cloud environments over time. The discussion also covers:Brownfield vs greenfield Azure environmentsWhy fast-growing companies struggle to redesign cloud architecturesThe operational impact of scaling without governanceWhy companies often prioritize new features over infrastructure stabilitySECURITY, COSTS & CLOUD CHAOS One of the strongest warning signs of weak governance is cloud chaos. Vladimir explains why security incidents and uncontrolled Azure costs are usually the first visible indicators that governance has failed. The conversation explores how organizations frequently underestimate governance because leadership often struggles to see immediate business value in preventive architecture work. The episode highlights:Why security breaches become business-critical eventsHow governance redu

In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP and MCT Nick Doelman to explore one of the most important technology shifts happening right now: the evolution of Agentic Coding and the future of AI-driven software development. From low-code platforms and Power Platform solutions to natural language interfaces and autonomous AI agents, this conversation dives deep into how developers, makers, consultants, and enterprise organizations must adapt to a completely new way of building business applications. Nick shares his incredible journey from programming on a Commodore 64 and working with C++ and Microsoft Dynamics CRM to becoming one of the leading voices in the Microsoft Power Platform ecosystem. He explains how his technical background, combined with years of real-world consulting and Microsoft experience, shaped his perspective on modern development, automation, governance, and AI-powered engineering.FROM TRADITIONAL DEVELOPMENT TO AI-POWERED ENGINEERING The conversation explores how software development has rapidly evolved over the past few years. Nick explains how Visual Studio Code, GitHub Copilot, Claude, MCP servers, and AI agents are transforming development workflows and dramatically increasing productivity. Instead of manually creating every field, table, and process inside Power Platform, developers can now use natural language prompts to generate data models, business logic, and application structures in minutes instead of hours. Nick also shares practical examples of how he now spends most of his time working with AI-assisted tooling rather than traditional development interfaces. The episode highlights how developers are increasingly collaborating with AI systems instead of simply writing code manually from scratch. WHAT AGENTIC CODING REALLY MEANS One of the central topics of this episode is the meaning of Agentic Coding. Nick explains why Agentic Development is much more than simple vibe coding or asking AI to generate random applications. Instead, it is a structured collaboration between humans and intelligent agents where developers guide, supervise, validate, and refine AI-generated solutions. The discussion breaks down how developers can:Build structured product requirement documents with AIGenerate reusable prompts and workflowsCreate data models through natural languageUse AI for testing, documentation, and architectureImprove application quality through iterative collaborationTHE FUTURE OF POWER PLATFORM Nick shares his vision for the future of Microsoft Power Platform and explains how tools like Power Apps, Power Pages, Dataverse, and Copilot Studio are evolving in the AI era. The discussion explores how Code Apps, Generative Pages, Single Page Applications, and AI-assisted development are changing the role of makers and enterprise developers. The epi

Finance departments are entering one of the biggest technological transformations in decades. Artificial Intelligence, autonomous agents, Copilot experiences, automation platforms, and modern ERP systems are rapidly changing how organizations manage accounting, reporting, forecasting, procurement, compliance, and financial operations. But what does this transformation actually look like inside real Dynamics 365 Finance & Operations environments? In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP and Microsoft Certified Trainer Billur Samdancioglu to explore the future of finance in D365FO, AI-powered business applications, Copilot experiences, autonomous agents, cloud ERP modernization, and how Microsoft is reshaping enterprise finance workflows. Billur Samdancioglu is a Dynamics 365 Finance & Operations expert, Microsoft MVP, Microsoft Certified Trainer, public speaker, and business applications specialist with deep experience helping organizations modernize financial systems and enterprise operations. Throughout the episode, Billur shares practical insights from working with enterprise customers, implementing D365FO projects, and helping finance teams navigate the growing impact of AI inside Microsoft business applications.HOW FINANCE TRANSFORMATION IS ACCELERATING The conversation begins with Billur sharing her journey into the Microsoft ecosystem and how Dynamics 365 Finance & Operations evolved into one of the most powerful ERP platforms inside modern enterprises. What was once viewed primarily as an accounting system has transformed into a fully connected digital operations platform capable of integrating finance, procurement, logistics, reporting, analytics, automation, and AI-driven decision support. Billur explains that many organizations are now facing increasing pressure to modernize legacy ERP systems because older platforms simply cannot keep pace with modern cloud expectations, automation requirements, AI integrations, compliance demands, and real-time reporting needs. Companies want faster processes, more visibility, better forecasting, lower operational overhead, and smarter financial insights — all while maintaining strong governance and security. One of the strongest themes throughout the episode is that finance modernization is no longer only about replacing software. It is about redesigning how finance teams actually work. AI is changing workflows themselves, not just the tools being used. WHAT COPILOT REALLY MEANS FOR D365FO A major focus of the discussion centers around Microsoft Copilot and how AI assistants are being integrated directly into Dynamics 365 Finance & Operations. Billur explains that Copilot is far more than a chatbot inside ERP systems. It represents a shift toward contextual AI assistance where users can interact with business systems using natural language rather than navigating deeply complex enterprise interfaces.

What does secure cloud automation actually mean in modern Microsoft environments? How can organizations automate user management, identity workflows, Microsoft 365 operations, and Azure infrastructure without creating massive security risks? And why is Microsoft Graph becoming one of the most important technologies every Microsoft administrator should understand? In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP Ahmed Uzejnovic to explore secure Azure automation, Microsoft Graph API, identity-driven automation, hybrid cloud infrastructure, PowerShell scripting, and the future of enterprise automation inside Microsoft ecosystems. Ahmed Uzejnovic is an IT automation and infrastructure specialist from Salzburg with a strong focus on PowerShell, Azure Automation, Microsoft Graph, identity security, hybrid environments, and enterprise-scale automation. Throughout the conversation, Ahmed shares practical real-world insights from building secure automation systems for onboarding, offboarding, identity synchronization, cloud governance, and operational management across hybrid Microsoft environments.HOW A SIMPLE USER OFFBOARDING SCRIPT STARTED EVERYTHING Ahmed’s automation journey started in local IT support where repetitive manual tasks quickly became impossible to ignore. One of the earliest examples he shares is user onboarding and offboarding. Administrators were spending multiple hours every day manually disabling accounts, updating systems, configuring permissions, handling Exchange tasks, and managing repetitive operational work. Instead of accepting repetitive manual work as “normal,” Ahmed started building small PowerShell scripts step-by-step to automate individual tasks. What began as tiny automation scripts eventually evolved into a fully automated user offboarding process that is still running successfully years later. This became the starting point for a much larger automation career focused on solving operational problems at scale. One of the strongest themes throughout the episode is Ahmed’s belief that automation is not really about scripts — it is about process thinking. Before automation can work effectively, organizations first need stable, repeatable, and clearly defined operational processes. Bad processes create bad automation. Good processes create scalable automation systems. WHY MICROSOFT GRAPH IS BECOMING ESSENTIAL FOR MODERN ADMINS A major focus of the episode is Microsoft Graph API and why it is rapidly becoming one of the most important technologies inside Microsoft 365 and Azure administration. Ahmed explains that Microsoft Graph is essentially the backend operating layer behind Microsoft cloud services. Nearly every action performed inside Microsoft 365 admin portals, Azure portals, Intune, Entra ID, Teams, and Exchange eventually translates into API calls against Microsoft Graph. The discussion explores how Microsoft administrato

What happens when AI starts building apps alongside developers? Are we entering a future where business users can create enterprise applications simply by describing what they want in plain language? And how will Power Apps evolve as generative AI, Copilot, and vibe coding completely reshape the development experience? In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP and Microsoft Certified Trainer Keith Atherton to explore the rapidly changing future of Power Apps, low-code development, AI-assisted app creation, and the next generation of business application development. Keith Atherton is a Power Platform Solution Architect at Capgemini, Microsoft MVP for Business Applications, Microsoft Certified Trainer (MCT), LinkedIn Learning instructor, public speaker, founder of the Power Platform Community High Five user group, podcast host, and mentor within the Women in Power Platform initiative. With a background in traditional software engineering using .NET and SQL Server before transitioning into Power Platform, Keith brings a unique perspective that combines enterprise architecture, low-code development, AI tooling, governance, and modern app design.FROM TRADITIONAL DEVELOPMENT TO LOW-CODE INNOVATION Keith shares how his career originally started in traditional software engineering using technologies like Visual Basic, .NET, and SQL Server before eventually moving into Power Platform. What immediately attracted him to Power Apps was speed. Instead of rebuilding the same application structures repeatedly in pro-code environments, Power Apps enabled him to create business solutions dramatically faster while still integrating with enterprise systems and Microsoft services. One of the most interesting moments in the conversation is when Keith explains that even before discovering Power Apps, he had already started building his own internal scaffolding systems to automate repetitive development tasks. That realization became his “aha moment” for Power Platform. Rather than manually creating forms, data models, grids, and business logic over and over again, low-code development allowed him to focus more on solving business problems instead of rewriting the same technical structures repeatedly. Mirko and Keith discuss how Power Apps has evolved far beyond simple drag-and-drop interfaces. What started as a low-code productivity platform is now becoming an AI-powered development ecosystem where prompts, screenshots, requirements documents, and conversational interactions can generate applications automatically. WHAT IS VIBE CODING AND WHY IS EVERYONE TALKING ABOUT IT? One of the biggest topics throughout the episode is “vibe coding” — the emerging trend where developers describe what they want using natural language while AI generates the application, code, or functionality automatically. Keith explains that vibe coding is fundamentally changing how software is b

What does modern .NET development really look like in 2026? How has the ecosystem evolved from traditional Windows desktop applications with WPF to cloud-native ASP.NET services, microservices, and high-performance gRPC communication? In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP Gábor Ruzsinszki to explore the past, present, and future of .NET development — from legacy enterprise applications to scalable modern backend architectures. Gábor Ruzsinszki is a Microsoft MVP in Developer Technologies specializing in C#, software architecture, and modern .NET development. Before becoming a professional software architect, Gábor originally worked as an IT and programming teacher, helping students learn algorithms, databases, software engineering, and development fundamentals. That strong educational background shines throughout the episode as he breaks down complex technical concepts into practical, understandable insights for developers at every level.THE EVOLUTION OF .NET DEVELOPMENT The episode begins with Gábor sharing his personal journey into software development and how he first became interested in C# and the .NET ecosystem. Starting with Delphi programming before transitioning into C and C++, he eventually discovered C# during university and immediately recognized its potential as a more modern and developer-friendly language. Since then, he has spent more than a decade building applications with .NET across desktop, backend, and enterprise systems. Mirko and Gábor dive deep into how the .NET ecosystem has transformed over the years. What started as a Windows-focused framework has evolved into a high-performance, truly cross-platform development ecosystem capable of powering cloud-native applications, Linux services, microservices, APIs, web applications, IoT systems, and enterprise-scale backend infrastructures. Gábor explains why modern .NET is faster, cleaner, and significantly more flexible than earlier versions of the framework. One particularly fascinating discussion focuses on performance improvements inside recent .NET releases. Gábor shares a real-world example where upgrading an enterprise application from an older version of .NET to .NET 9 reduced processing time from forty-five minutes down to twenty-five minutes without major code changes — purely because of framework-level optimizations and performance improvements from Microsoft. WHY WPF STILL MATTERS IN ENTERPRISE DEVELOPMENT Even though WPF (Windows Presentation Foundation) is now more than fifteen years old, many enterprise organizations still rely heavily on it for business-critical applications. Gábor explains why WPF became such a dominant desktop UI framework and why it remains relevant even today. Its powerful XAML-based architecture, flexibility, mature tooling inside Visual Studio, and massive community knowledge base still make it valuable for Windows-focused enterprise ap

The Microsoft ecosystem is evolving faster than ever. Between AI, Copilot, automation, low-code development, cloud platforms, and the growing Power Platform ecosystem, many professionals are asking the same question: How do you actually build a long-term career in Microsoft technologies today? In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP and Microsoft Certified Trainer Nathalie Leenders to explore the journey from certifications and exams to real-world expertise, consulting experience, and community leadership. Nathalie Leenders is widely known in the Microsoft community for her deep technical knowledge, her passion for Power Platform, her educational content, speaking engagements, and her strong presence within the Microsoft ecosystem. But her path into technology was not a traditional “developer from day one” story. Nathalie shares how she originally worked in IT service management and support roles before gradually moving into SharePoint, workflows, InfoPath, Power BI, and eventually Power Platform development. Her story is a powerful reminder that successful careers in tech rarely follow a perfectly straight line.HOW CURIOSITY AND LEARNING CREATED A MICROSOFT CAREER One of the strongest themes throughout this episode is curiosity. Nathalie explains how her willingness to continuously learn new technologies became the foundation of her success. Long before Power Platform became the global phenomenon it is today, she was already experimenting with SharePoint Designer workflows, automation scenarios, and business process optimization. When the opportunity arose to join an automation-focused team, she embraced the challenge even before fully understanding all the technical requirements. Rather than waiting until she felt “ready,” Nathalie learned by building real solutions in real environments. She discusses how tutorials, Microsoft Learn, YouTube videos, community content, and experimentation helped her grow into a Power Platform consultant capable of solving enterprise-scale problems. She also highlights how visual learning played a major role in her development and why practical hands-on work remains essential in modern IT careers. THE REAL VALUE OF MICROSOFT CERTIFICATIONS IN 2026 Are Microsoft certifications still worth it in 2026? Nathalie gives an honest and balanced perspective on certifications, exams, and technical learning paths. She explains that certifications themselves are not magic career shortcuts, but they can absolutely help people learn structured knowledge, build confidence, and open career opportunities when combined with practical experience. A major part of the conversation focuses on PL-400, one of the most advanced Power Platform certifications available. Nathalie shares how she intentionally challenged herself with the difficult Power Platform Developer certification early in her career, despite being told it might be “too

PowerShell has become one of the most important automation tools in the Microsoft ecosystem, and in this episode of the m365.fm podcast, Mirko Peters welcomes Microsoft MVP Harm Veenstra to discuss why automation is no longer optional for modern IT teams. Harm shares his journey from helpdesk technician to automation specialist and explains how PowerShell transformed the way he approaches Microsoft 365, Azure, Exchange, Teams, Intune, and enterprise administration.WHY POWERSHELL BECAME ESSENTIAL FOR MODERN IT During the conversation, Harm explains how PowerShell stopped being “just scripting” and became a creative problem-solving platform. Once IT professionals understand the logic behind PowerShell objects, properties, and automation workflows, repetitive manual tasks can be replaced with scalable and consistent processes. Harm highlights that automation is not only about saving time — it is about improving reliability, reducing human errors, and allowing IT teams to focus on more valuable work instead of endless click-ops. The episode also explores how PowerShell evolved alongside Microsoft technologies. From the early Exchange Server days to today’s Microsoft Graph integrations, automation is now deeply connected to nearly every Microsoft cloud service. Harm explains how Microsoft Graph APIs and PowerShell modules give administrators complete control across Microsoft 365 and Azure environments. AUTOMATING MICROSOFT 365 AT SCALE One of the biggest topics in the episode is large-scale automation inside enterprise environments. Harm shares practical examples from real consulting projects where PowerShell was used to automate user onboarding, Microsoft 365 migrations, permissions management, account provisioning, Google Workspace to Microsoft 365 transitions, Teams meeting migrations, and hybrid identity processes. The discussion highlights how repetitive tasks like creating users, assigning licenses, configuring devices, syncing identities, and managing permissions become far more efficient when automated correctly. Harm explains that the true value of automation appears when organizations need consistent results across hundreds or thousands of users and devices. MICROSOFT GRAPH, APIs, AND MODERN AUTOMATION Mirko and Harm spend significant time discussing Microsoft Graph and why it has become one of the most powerful platforms for automation in Microsoft 365. Harm explains how administrators can monitor Graph API calls, discover backend actions performed inside admin portals, and use PowerShell to fully automate workflows that previously required manual configuration. The episode also covers how vendors outside the Microsoft ecosystem increasingly provide PowerShell modules for their products, making PowerShell a universal automation language across cloud platforms, infrastructure services, and enterprise tools. SECURITY, GOVERNANCE, AND SC

In this episode of the M365FM Podcast, Mirko Peters sits down with Microsoft MVP Alan Cox to explore one of the biggest security and governance challenges facing enterprises today: securing Microsoft Copilot before AI begins surfacing sensitive organizational data at scale. The conversation dives deep into Microsoft Purview, Data Loss Prevention, Insider Risk Management, AI governance strategy, and why organizations must rethink permissions, sharing, and compliance before rolling out Copilot broadly.AI DOES NOT CREATE RISK — IT EXPOSES IT Alan explains that Copilot itself is not the true danger. Instead, AI exposes the hidden weaknesses already living inside most Microsoft 365 environments. Overpermissioned SharePoint sites, forgotten Teams channels, excessive sharing, and missing governance controls suddenly become visible the moment AI can summarize and retrieve information instantly. The biggest mistake organizations make is assuming that because employees technically already had access to the data, there is no additional risk. In reality, Copilot dramatically accelerates discoverability. Data that once remained buried inside folders and old conversations can suddenly surface through a single prompt. WHAT MICROSOFT PURVIEW REALLY IS Alan breaks Microsoft Purview down into simple terms. At its core, Purview is about protecting organizational data and bringing hidden risks into focus. Instead of viewing governance purely as restriction and compliance enforcement, he frames governance as a proactive strategy designed to prevent future incidents before they happen. He simplifies Purview into three foundational areas:Data Loss PreventionRetentionSensitivity LabelingThese three pillars ultimately determine what Copilot can access, process, summarize, or expose across Microsoft 365 workloads.INSIDER RISK IS NOW AN AI PROBLEM One of the most important themes in the discussion is how Insider Risk Management changes in the age of generative AI. Alan explains that most insider threats are not malicious attacks. Most incidents happen because employees unintentionally expose sensitive information without understanding the consequences. AI amplifies this problem because natural language prompts make it easier than ever to retrieve information from across the organization. Insider Risk Management helps organizations detect suspicious access patterns, risky prompts, unusual sharing activity, and abnormal behavior before those actions become full-scale incidents. DSPM FOR AI CHANGES GOVERNANCE A major focus of the episode is Microsoft’s evolving DSPM for AI capabilities. Alan explains how Microsoft is consolidating AI governance features into centralized dashboards that simplify policy creation for Copilot protection. Organizations can now deploy controls that restrict AI access to sensitive information

In this episode of the M365FM Podcast, Mirko Peters sits down with Microsoft MVP and adoption strategist Carina de Vries to unpack one of the biggest failures in enterprise AI rollouts: Most organizations are deploying AI tools before understanding how people actually work. While the industry obsesses over prompts, copilots, and new features, Carina argues that successful AI adoption has almost nothing to do with technology alone. It is about behavior. It is about communication. And most importantly, it is about making users genuinely happy in their daily work. This episode breaks down Carina’s ninety-day AI adoption framework, her philosophy around simplifying technology instead of endlessly adding features, and why most Microsoft 365 rollouts fail because organizations forget the human side of transformation. If your Copilot rollout feels chaotic, your users are resistant, or your organization keeps buying AI licenses without measurable engagement, this episode is your blueprint for fixing it.FROM SECRETARY TO MICROSOFT MVP Carina’s path into technology did not begin in IT. It started as a secretary helping colleagues troubleshoot printers, Outlook issues, Excel formulas, and workplace applications. That early experience shaped her entire philosophy around adoption:Technology only matters if it helps people do their jobs better. Over time, she transitioned into application management, workplace modernization, and eventually user adoption consulting after seeing firsthand how poorly organizations handled change management. Instead of focusing purely on technical implementation, she became obsessed with understanding:Why users resist technologyWhy training alone failsWhy communication matters more than documentationHow habits form around digital toolsWhy employees need emotional clarity before technical clarityThat eventually led to the creation of Workspace Heroes, her company focused entirely on Microsoft 365 adoption strategy.THE REAL PROBLEM WITH AI ADOPTION According to Carina, most organizations make the same critical mistake: They buy AI before understanding workflows. During the conversation, she openly agrees that companies are purchasing AI solutions without first understanding how people actually operate inside the business. This creates a dangerous pattern:Leadership buys Copilot licensesIT enables the technologyUsers receive mandatory trainingAdoption stalls almost immediatelyWhy? Because AI is not just another software rollout. Copilot changes behavior. And behavior takes time. Carina explains that successful Copilot adoption is not about teaching features. It is about helping users build repeatable daily habits around AI-assisted work.WHAT IS A “HAPPY USER”? One of the most powerful moments in the episode happens when Mirko a

In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP Thomas Sandsør for a refreshingly honest and deeply human conversation about CRM, business applications, AI, customer relationships, and the future of Microsoft Dynamics 365. But this is not another highly technical “which button should you click” discussion. Instead, Thomas shares nearly 20 years of real-world experience working with CRM systems and explains why successful CRM projects have far more to do with people, culture, leadership, and trust than with technology itself. From failed implementations and change management struggles to AI agents, sales psychology, customer service workflows, and the future of human interaction in business software — this episode dives into the realities behind modern CRM projects.FROM SOCCER GOALKEEPER TO “THE CRM KEEPER” Thomas shares the story behind his well-known nickname “The CRM Keeper,” combining his background as a soccer goalkeeper with his long-standing passion for Dynamics CRM. What began as a dream of becoming a professional football player eventually transformed into a career helping organizations build stronger customer relationships through technology. Throughout the episode, Thomas reflects on how lessons from sports — teamwork, leadership, collaboration, discipline, and understanding personalities — still influence the way he leads teams and approaches CRM projects today. WHY CRM IS REALLY ABOUT PEOPLE — NOT SOFTWARE One of the strongest themes throughout the episode is the idea that CRM implementations are fundamentally human projects. Thomas explains how, early in his career, he believed technology alone could solve business problems. Over time, however, he realized that even the best CRM platform fails if people do not trust, understand, or embrace the change behind it. The conversation explores:why many CRM projects failthe importance of change managementhow leadership impacts adoptionwhy company culture mattersthe psychology behind user behaviorthe challenge of getting teams invested in transformationAs Thomas puts it, CRM is not simply about deploying software — it is about changing how people work together.AI, COPILOT & THE FUTURE OF CRM The discussion also dives deep into AI and the future of Dynamics 365. Thomas shares both excitement and skepticism around the rapid rise of AI agents, Copilot experiences, automation, and prompt-based workflows. While AI is clearly improving productivity and reducing repetitive work, he also raises important questions around trust, governance, data quality, and whether businesses are truly ready for fully autonomous systems. The episode explores:AI-assisted sales workflowsCRM agents and automationthe future of user interfacesprompt-driven business applicationsAI-