Power Fx is the formula language that powers Microsoft Power Apps and an increasing number of experiences across the Microsoft Power Platform. For anyone familiar with Excel, Power Fx provides a natural transition into app development by using familiar formula concepts instead of traditional programming languages. In this episode of Microsoft Knowledge Nuggets on M365.FM, Mirko Peters explains Power Fx in plain English, showing how formulas can control text, colors, visibility, calculations, navigation, and business logic inside modern business applications. Whether you're an Excel user, Power Apps beginner, citizen developer, or IT professional, this episode demonstrates how Power Fx enables low-code application development without requiring years of programming experience.

FROM EXCEL FORMULAS TO BUSINESS APPLICATIONS
One of the greatest strengths of Power Fx is its familiar spreadsheet mindset. Instead of writing complex code, developers create formulas that respond automatically as users interact with an application. The episode explains how Excel formulas translate into Power Apps properties, allowing labels, buttons, text boxes, galleries, and forms to update dynamically based on user input. Rather than thinking about individual spreadsheet cells, Power Apps developers work with controls and properties that continuously respond to changing business data, creating interactive applications that feel intelligent while remaining easy to maintain.

USING POWER FX TO CREATE DYNAMIC USER EXPERIENCES
Business applications are built around rules, and Power Fx provides the logic behind every interaction. The discussion explores properties such as Text, Visible, Color, and OnSelect, demonstrating how formulas determine what users see and what happens when they interact with buttons, forms, or screens. Listeners learn how applications automatically show or hide controls, validate information, display notifications, navigate between screens, and provide immediate feedback without requiring traditional software development. The result is a responsive user experience that adapts naturally to business processes.

CONNECTING POWER APPS TO BUSINESS DATA
Modern applications rarely exist without data. This episode explains how Power Fx works with business information stored in SharePoint, Microsoft Dataverse, SQL Server, Excel, and other supported data sources. Core functions such as Filter, Sort, LookUp, and Patch allow developers to retrieve, organize, search, create, and update business records while keeping applications responsive and easy to understand. The episode also introduces the concepts of tables, records, columns, and galleries, helping beginners understand how business data flows through a Power Apps solution.

VARIABLES, COLLECTIONS, AND REUSABLE BUSINESS LOGIC
As applications grow, developers need efficient ways to manage state and reuse business rules. Mirko explains how variables temporarily store information during a user's session, while collections manage groups of records before saving them to permanent storage. The discussion also covers reusable Power Fx functions that prevent duplicated logic and simplify long-term maintenance. By organizing formulas properly, developers can build scalable business applications that remain easier to troubleshoot, update, and extend as organizational requirements evolve.

WHY POWER FX IS THE FUTURE OF LOW-CODE DEVELOPMENT
Microsoft continues expanding Power Fx across the Power Platform, making it a core skill for citizen developers, business analysts, consultants, and enterprise application builders. Rather than replacing professional developers, Power Fx enables organizations to build business applications faster while allowing experienced developers to focus on more complex scenarios. The episode concludes with practical advice for beginners, encouraging listeners to start with simple formulas, build one feature at a time, and gradually develop confidence using Power Fx to automate business processes, improve productivity, and transform ideas into working applications.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

Heather Cook shares her remarkable journey from studying theater to becoming one of Microsoft's most influential community leaders. Her Microsoft story began more than 25 years ago when she joined the original SharePoint "Tahoe" project, helping write the very first customer case studies that introduced SharePoint to the world. From there, she built a career around customer advocacy, event production, marketing, and community engagement, eventually becoming a Microsoft MVP before joining Microsoft full-time. Heather explains how storytelling, creativity, and relationship-building have shaped every stage of her career and why communication skills remain just as valuable as technical expertise in today's AI-driven world.

WHY STRONG COMMUNITIES OUTLAST TECHNOLOGY
Technology constantly changes, but great communities continue to grow because they are built around people rather than products. Heather discusses how her theater background taught her the importance of collaboration, shared purpose, and creating memorable experiences. She reflects on witnessing the birth of the SharePoint community, where MVPs, consultants, Microsoft engineers, partners, and customers naturally came together to help one another. The conversation explores why becoming a Microsoft MVP is ultimately about giving back, why consistency matters more than perfection for content creators, and how podcasts, newsletters, blogs, and events all contribute to building trust over many years rather than overnight. 

INSIDE MICROSOFT'S COMMUNITY, ADOPTION, AND EVENTS STRATEGY
Heather provides an inside look at Microsoft's SCALE organization and explains how teams responsible for Studio, Community, Adoption, Learning, and Events work together to help organizations successfully adopt Microsoft technologies. She introduces initiatives including Microsoft Tech Community, Adoption.microsoft.com, Microsoft 365 Champions, the Microsoft Global Community Initiative (MGCI), CommunityDays.org, and Microsoft's worldwide learning programs. The discussion covers how event organizers can work more closely with Microsoft, why CommunityDays.org is the central hub for Microsoft ecosystem events, how Microsoft supports community-led conferences around the world, and why adoption always requires much more than simply deploying new technology. 

AI, CONTENT CREATION, AND THE HUMAN SIDE OF TECHNOLOGY
Artificial intelligence is changing the way creators work, but Heather believes AI should strengthen human creativity rather than replace it. She discusses using AI to accelerate newsletters, writing, research, and content production while emphasizing that authenticity remains the most valuable asset any creator has. The conversation also explores imposter syndrome, encouraging creators to publish their work confidently because every podcast, article, or presentation becomes part of a lasting knowledge archive. Heather also shares her passion for Women in Technology initiatives, inclusive communities, mentorship, and creating opportunities for future leaders throughout the Microsoft ecosystem. 

RAPID FIRE INSIGHTS
During the quick-fire round, Heather recommends Facilitator as a Microsoft 365 feature everyone should explore, highlights custom Copilot agents as one of today's most exciting AI capabilities, and continues to praise SharePoint as one of Microsoft's most innovative platforms. She identifies maintaining a simple to-do list as one of the most underrated productivity habits, credits The Tipping Point by Malcolm Gladwell as an influential book in her career, and recognizes community leaders such as Caruana Gatimu and Donna Sarkar for their impact on the Microsoft ecosystem. She also encourages future community builders to listen first, understand people's needs, and only then begin creating solutions that genuinely serve their audiences. 

BUILD RELATIONSHIPS THAT LAST
Heather closes with a message that reaches far beyond Microsoft technologies. Be curious, keep experimenting, continue learning, and never stop building meaningful relationships with other people. Products will evolve, AI will continue transforming the workplace, and new technologies will constantly emerge, but authentic human connections remain the foundation of every successful career and every thriving community. As Heather reminds listeners, the word "unity" exists inside the word "community"—a simple idea that perfectly captures why the human side of technology will always matter most.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

Microsoft Purview Data Lifecycle Management helps organizations control how long information should be kept, when it should be reviewed, and when it should be securely deleted. Instead of allowing emails, Teams chats, SharePoint documents, OneDrive files, and other Microsoft 365 content to accumulate indefinitely, lifecycle management ensures every piece of information follows a defined business, legal, or regulatory process. This reduces storage costs, minimizes compliance risks, improves search efficiency, and ensures outdated or unnecessary information is removed in a controlled manner rather than remaining in the environment forever.

UNDERSTANDING THE DATA LIFECYCLE
Every piece of business information follows a natural lifecycle. It is created, actively used, retained for business or legal purposes, reviewed when necessary, and eventually disposed of once it no longer provides value. Microsoft Purview supports this complete journey through retention settings that prevent premature deletion while also ensuring content is not kept longer than necessary. Organizations can choose to retain content, delete content after a defined period, or combine both approaches by retaining information first and automatically deleting it later. A successful lifecycle strategy always begins by understanding why information exists before deciding how long it should remain.

RETENTION POLICIES VS. RETENTION LABELS
Retention Policies provide organization-wide rules that apply to entire Microsoft 365 locations such as Exchange Online mailboxes, SharePoint sites, OneDrive accounts, or Microsoft Teams chats. They are ideal when large amounts of similar content require identical retention behavior. Retention Labels, on the other hand, apply directly to individual emails or documents. This allows important business records, such as signed contracts or official agreements, to receive different retention periods than drafts or everyday working documents stored in the same location. Labels may be applied manually by users or automatically by Microsoft Purview based on predefined conditions, creating much more granular control over business-critical information.

SCOPES, CONFLICT RESOLUTION, AND RETENTION LOGIC
Microsoft Purview determines where retention rules apply by using either static scopes or adaptive scopes. Static scopes target specific users, mailboxes, or SharePoint sites, making them suitable for stable environments. Adaptive scopes automatically include users or locations based on Microsoft Entra ID attributes such as department or job title, significantly reducing administration in large organizations. When multiple retention rules overlap, Purview follows predictable conflict rules. Retention requirements always take priority over deletion, longer retention periods override shorter ones, and item-level retention labels can override broader location-based policies. This ensures organizations never delete information that must legally or operationally remain available. 

HOW ALL THE COMPONENTS WORK TOGETHER
Data Lifecycle Management works by combining policies, labels, scopes, and automated retention into one consistent governance framework. A general retention policy can protect everyday content across Microsoft 365 while retention labels provide special treatment for important records. Adaptive scopes ensure policies automatically follow organizational changes, and retention continues to protect required content even if users accidentally delete files or emails. It is also important to understand that lifecycle management only controls how long information exists. It does not determine who can access content or how it is is shared. Those responsibilities belong to Microsoft Purview Sensitivity Labels and Data Loss Prevention (DLP), which complement lifecycle management as part of a complete Microsoft Purview governance strategy. 

BEST PRACTICES FOR BUILDING A RETENTION STRATEGY
A successful Data Lifecycle Management implementation starts with understanding where information is stored across Exchange Online, SharePoint, OneDrive, Microsoft Teams, and AI-generated content. Business owners should define why each type of information exists, how long it must be retained, and what should happen when that retention period expires. Begin with broad, low-risk retention policies before introducing more granular retention labels for specialized records. Use adaptive scopes where organizational structures frequently change, clearly document every retention policy, carefully test automatic deletion before enabling it in production, and regularly review overlapping rules with compliance, legal, records management, and business stakeholders. By following this structured approach, organizations can reduce compliance risk while ensuring information remains available for exactly as long as it is needed—and no longer.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

What happens when a regulator requests company records, HR launches an investigation, or legal teams need to preserve critical evidence? Searching through Outlook mailboxes, Teams chats, SharePoint sites, and OneDrive folders manually is slow, error-prone, and often impossible at enterprise scale. In this episode of Microsoft Knowledge Nuggets on M365.fm, Mirko Peters explains Microsoft Purview eDiscovery in plain English. You'll learn how organizations can securely discover, preserve, review, and export Microsoft 365 data using a structured, case-based process that supports legal investigations, compliance requests, internal audits, HR matters, and security incidents. Whether you're an IT administrator, Microsoft 365 consultant, compliance officer, security professional, or simply preparing for Microsoft certifications, this episode provides a practical introduction to one of the most important Microsoft Purview capabilities.

WHY eDISCOVERY MATTERS IN MICROSOFT 365
Modern work is scattered across multiple Microsoft services. Business conversations no longer live only in Outlook. Critical evidence may be spread across:

• Exchange Online emails
• Microsoft Teams chats and meetings
• SharePoint Online document libraries
• OneDrive for Business
• Microsoft 365 Groups
• Viva Engage conversations

During an investigation, missing even one location can result in incomplete evidence. Microsoft Purview eDiscovery provides a centralized process that helps organizations collect the right information while maintaining security, privacy, and governance. Instead of searching every mailbox and document library, organizations create structured cases that define exactly what should be searched and who may access the results.

HOW MICROSOFT PURVIEW eDISCOVERY WORKS
Rather than acting as a giant search engine, eDiscovery follows a carefully controlled workflow. The process begins by creating a case, which becomes the secure workspace for a specific investigation. Authorized users define the data sources, preserve evidence through Legal Hold when required, execute targeted searches, review the collected results, classify relevant documents, and finally export only the approved evidence. This structured workflow dramatically reduces risk compared to manually searching Microsoft 365 services while providing a clear audit trail for compliance and legal teams.

EXPLORE THE COMPLETE eDISCOVERY WORKFLOW
This episode explains every major component of Microsoft Purview eDiscovery, including:

• Creating investigation cases
• Selecting Exchange, Teams, SharePoint and OneDrive data sources
• Understanding Legal Hold
• Running targeted searches
• Using Keyword Query Language (KQL)
• Reviewing collected evidence
• Working with Review Sets
• Applying Tags
• Exporting evidence securely
• Managing permissions and access control
• Understanding Standard vs Premium eDiscovery

Every topic is illustrated using practical business scenarios that demonstrate how investigations typically unfold inside Microsoft 365 environments

LEGAL HOLD EXPLAINED
One of the most misunderstood concepts in Microsoft Purview is Legal Hold. A Legal Hold ensures that potentially relevant information remains preserved even if users delete emails, edit documents, or leave the organization during an active investigation. Unlike traditional retention policies, which enforce normal business record retention, Legal Hold protects data because of a specific legal or compliance matter. This episode explains:

• when Legal Hold should be used,
• how it differs from Microsoft 365 retention,
• why preservation must happen before searching,
• and why only authorized business stakeholders should decide when a hold is applied or released.

SEARCH SMARTER — NOT WIDER
Many administrators assume that searching the entire Microsoft 365 tenant is the safest option. In reality, enterprise investigations work best when searches remain focused. You'll learn how to:

• define relevant custodians,
• limit searches using date ranges,
• search by sender or recipient,
• use keywords effectively,
• understand Keyword Query Language (KQL),
• analyze search statistics,
• refine search queries iteratively,
• and avoid collecting unnecessary personal or business information.

The episode demonstrates why successful investigations begin with focused questions instead of massive searches.

REVIEW, CLASSIFY AND EXPORT EVIDENCE
Finding information is only the beginning. Microsoft Purview eDiscovery enables reviewers to examine search results, determine relevance, classify documents using tags, and prepare evidence for legal or compliance teams. You'll discover:

• what Review Sets are,
• how reviewers organize findings,
• when Premium review capabilities become valuable

<



Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

Mark Orr shares his extraordinary journey from serving three combat tours in Iraq as a United States Marine Corps radio and satellite communications specialist to becoming a Microsoft MVP, enterprise architect, and respected Microsoft security expert. He explains how military experience introduced him to networking, satellite communications, IP protocols, and infrastructure management before eventually leading him into Microsoft technologies, Microsoft Intune, Entra ID, automation, and cloud security. His career demonstrates how discipline, resilience, and continuous learning can create entirely new opportunities in enterprise IT.

WHY IDENTITY IS THE NEW SECURITY PERIMETER
Organizations often invest heavily in AI, Copilot, endpoint management, and advanced compliance while overlooking the single most important attack surface: identity. Mark explains why every security strategy should begin with protecting identities before implementing more advanced technologies. According to him, strong authentication, phishing-resistant credentials, and properly secured privileged accounts form the foundation upon which every modern Microsoft security solution depends. Without a secure identity layer, every additional security investment becomes significantly less effective.

WHY IDENTITY ATTACKS DOMINATE MODERN CYBERSECURITY
More than ever, attackers target identities instead of infrastructure. Mark explains that passwords remain one of the weakest links because people frequently reuse credentials across personal and business accounts. Once a password becomes compromised through another service, attackers often gain access to enterprise environments using the same credentials. This is why Microsoft continues pushing organizations toward passwordless authentication and phishing-resistant sign-in methods that dramatically reduce the attack surface. 

PASSWORDLESS AUTHENTICATION SHOULD BE EVERY ORGANIZATION'S FIRST GOAL
Mark has been running passwordless authentication since long before it became mainstream. Drawing on years of practical experience, he strongly recommends moving organizations toward Windows Hello for Business, passkeys, Microsoft Authenticator passwordless sign-in, and hardware security keys such as YubiKeys. Besides improving security, passwordless authentication actually creates a better user experience by eliminating forgotten passwords while protecting users from phishing attacks and credential theft.

COMMON MISTAKES WITH PRIVILEGED ACCOUNTS
One of the biggest security mistakes Mark repeatedly encounters is administrators using the same account for both daily productivity and privileged administration. He explains why administrative identities should always be isolated cloud-only accounts without Exchange mailboxes, Teams licenses, or normal productivity workloads. Separating privileged identities dramatically reduces phishing exposure and prevents attackers from gaining administrative access through compromised user activities.

ZERO TRUST IS A JOURNEY, NOT A DESTINATION
Zero Trust is often treated as a final objective, but Mark argues that organizations never truly "finish" Zero Trust. Instead, security teams should focus on continuously improving their security posture rather than waiting for perfection. He recommends combining compliant devices, known networks, phishing-resistant authentication, Conditional Access policies, and trusted administrator workstations while continuously strengthening remaining gaps over time. Progress matters far more than chasing an impossible end state. HOW MICROSOFT INTUNE AND MICROSOFT ENTRA ID WORK TOGETHER Rather than viewing Microsoft Intune and Microsoft Entra ID as separate products, Mark explains how both platforms complement each other to create a unified security architecture. Entra ID protects identities through authentication, Conditional Access, and role-based access control, while Intune continuously evaluates endpoint health using compliance policies, encryption, antivirus protection, Secure Boot, and device configuration. Together they allow organizations to grant access only when both the user identity and the device satisfy security requirements.

ENTRA PIM EXPLAINED
Privileged Identity Management (PIM) introduces the concept of Just-in-Time administration. Instead of permanently assigning highly privileged roles, administrators elevate only when necessary to complete a specific task. Mark explains how temporary elevation dramatically reduces security risks by minimizing the amount of time privileged permissions remain active. Organizations embracing least privilege significantly reduce the opportunity for attackers to abuse compromised administrative accounts.

WHY ADMINISTRATORS SHOULD STOP LEAVING ROLES ACTIVE
Many administrators prefer keeping privileged roles active throughout an entire workday because it feels more convenient. Mark argues that this convenience creates unnecessary risk. His recommendation is to activate administrative roles only when performing a specific task and deactivate them immediately afterward. Even where organizations permit longer elevation windows, he prefers limiting sessions to four hours or less to ensure elevated permissions never remain active while administrators are away from their workstations.

BUILDING INTREPID TO SIMPLIFY PRIVILEGED ACCESS
To solve the inconvenience of repeatedly activating multiple privileged roles, Mark developed Intrepid, a PowerShell tool that automates bulk activation of Microsoft Entra PIM roles while fully respecting Conditional Access policies and Authentication Context requirements. Every

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

Microsoft Fabric Apps are a new way to build modern, data-driven web applications directly inside Microsoft Fabric. Rather than managing servers, APIs, databases, authentication, and hosting separately, Fabric provides these services automatically, allowing developers and data professionals to focus on creating business applications instead of infrastructure. A Fabric App can either connect to an existing Power BI semantic model or include its own managed SQL database, making it suitable for everything from interactive dashboards to operational business applications. This significantly lowers the barrier to building enterprise-grade solutions while keeping security, governance, and scalability within the Microsoft ecosystem.

HOW MICROSOFT FABRIC APPS WORK
Every Fabric App combines several managed services into a single application platform. When you create a new app, Microsoft Fabric automatically provisions a SQL database, GraphQL API, Microsoft Entra ID authentication, and static web hosting. Developers no longer need to configure backend infrastructure manually. Instead, they can concentrate on designing user experiences, building forms, creating dashboards, and implementing business logic. Fabric handles the underlying platform, making application development significantly faster than traditional full-stack approaches. 

FABRIC APPS VS POWER BI
One of the biggest misconceptions is that Fabric Apps replace Power BI. They do not. Instead, both products solve different problems while sharing the same governed data foundation. Power BI remains Microsoft's leading business intelligence platform for analytics, reporting, dashboards, drill-through analysis, natural language queries, and executive reporting. Fabric Apps extend these capabilities by enabling custom web applications that can both display and write data. This makes them ideal for operational workflows such as inventory management, approval systems, CRM solutions, and internal business tools where users need to interact with data rather than simply analyze it. 

REAL-WORLD USE CASES FOR FABRIC APPS
Fabric Apps are designed for business scenarios that require custom user experiences while still leveraging trusted enterprise data. Organizations can build inventory management systems with write-back capabilities, HR onboarding portals, expense approval applications, operational dashboards, customer feedback systems, and rapid business prototypes. Because Fabric Apps can connect directly to Power BI semantic models, organizations reuse existing DAX calculations, relationships, and governance policies without rebuilding business logic. This creates a single source of truth across both analytical reports and operational applications. 

CURRENT LIMITATIONS OF MICROSOFT FABRIC APPS
Since Fabric Apps are currently in Public Preview, organizations should understand their current limitations before adopting them in production. Authentication currently supports only Microsoft Entra ID users, making the platform suitable for internal applications rather than customer-facing solutions. Applications also consume Microsoft Fabric Capacity Units (CUs), meaning performance and cost planning remain important considerations. In addition, advanced transactional scenarios, stored procedures, and highly complex business workflows may still require traditional development approaches. While AI-assisted development accelerates application creation, developers still benefit from understanding frontend technologies such as JavaScript and TypeScript. 

SHOULD YOU START LEARNING FABRIC APPS?
If you're already working with Microsoft Fabric or Power BI, Fabric Apps represent one of the most important additions to the Microsoft data platform. They expand what organizations can build without replacing existing reporting investments, allowing the same semantic models and governed datasets to power both analytics and business applications. The best way to get started is by enabling the Fabric Apps preview, experimenting with both the Blank App and Data App templates, and exploring how custom applications can extend your existing Microsoft Fabric environment. Learning the platform today will prepare you for the broader capabilities expected as Fabric Apps move toward general availability.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

Jess Stratton shares her unique career journey from independent Lotus Notes developer to one of the world's most recognized Microsoft 365 educators. After joining LinkedIn Learning, she created training for millions of learners while continuously adapting to Microsoft's rapidly evolving ecosystem. Today, as a Microsoft MVP, TEDx speaker, author, and founder of Nerd Girl Jess LLC, she focuses on helping organizations move beyond simply using Microsoft Copilot toward fundamentally changing the way people work. Her story highlights how continuous learning, curiosity, and community can create extraordinary career opportunities in technology.

WHY COPILOT ADOPTION FAILS IN MANY ORGANIZATIONS
Buying Microsoft Copilot licenses is only the beginning. Jess explains that many organizations invest heavily in AI but struggle to demonstrate measurable business value because employees are taught where Copilot's buttons are instead of learning how AI actually improves their daily work. Successful adoption requires showing employees practical productivity gains, helping them solve real business problems, and demonstrating why Copilot makes their jobs easier rather than simply introducing another piece of software. Organizations that focus on outcomes instead of features consistently achieve better long-term adoption.

HUMAN BEHAVIOR IS THE BIGGEST OBSTACLE
While many organizations assume governance or technology limits Copilot adoption, Jess believes the real challenge is people. Microsoft already provides strong governance capabilities, security controls, pilot programs, and enterprise protections. The real issue is convincing employees to change established habits and trust AI as part of their daily workflow. Until users understand how Copilot benefits their individual responsibilities, even the best technical deployment will fail to achieve widespread adoption.

TRAINING MUST EVOLVE BEYOND FEATURES
Traditional software training focuses on explaining menus and features. AI requires a completely different approach. Jess explains that modern Copilot training should answer a different question: How will this improve my work? Instead of showing every feature inside Word, Excel, Teams, or Outlook, trainers should demonstrate concrete productivity improvements, realistic business scenarios, and repeatable workflows that employees can immediately apply. Helping users experience small wins early dramatically increases long-term adoption.

THE POWER OF CUSTOM PROMPT GALLERIES
One of Jess's favorite new Microsoft Copilot capabilities is the ability for organizations to build department-specific Prompt Galleries. Rather than forcing employees to invent prompts from scratch, IT teams can provide reusable prompts tailored for HR, Finance, Marketing, Legal, Customer Service, Sales, or Operations. Because every company has unique terminology, business processes, and workflows, these curated prompts significantly reduce the learning curve while helping users experience immediate business value.

WHY MOST PEOPLE STILL PROMPT POORLY
Many users expect Copilot to generate perfect results after entering a single sentence. Jess explains that this misconception leads to disappointment. The best prompts clearly define four key elements: the goal, the business context, relevant source information, and detailed expectations about the desired output. Instead of simply asking Copilot to "write a report," users should specify the audience, tone, length, formatting, business purpose, and constraints. The more clearly expectations are communicated, the better Copilot performs.

CHOOSING THE RIGHT MODEL MATTERS
Modern Microsoft Copilot offers access to multiple AI models, yet many users leave the default setting unchanged. Jess encourages people to experiment with different models using identical prompts to understand how dramatically responses can differ. Some models prioritize reasoning, others creativity, while some focus on speed or factual consistency. Becoming an effective Copilot user increasingly requires understanding not only prompt engineering but also selecting the most appropriate model for each task.

AI SHOULD CHANGE THE WAY YOU WORK
One of the biggest mistakes organizations make is using AI to automate inefficient workflows instead of redesigning work itself. Jess believes Copilot gives businesses a rare opportunity to rethink long-established processes. Rather than recreating old manual habits with AI, organizations should simplify workflows, eliminate unnecessary steps, organize prompts, create reusable agents, and build scalable solutions that remain maintainable for years instead of becoming another layer of technical debt.

WHY PERSONALIZATION CHANGES EVERYTHING
Personalization is one of the most overlooked features inside Microsoft Copilot. Jess explains how users can customize writing styles, preferred formatting, Outlook tone, meeting summaries, PowerPoint branding, Teams meeting templates, and persistent memory to create much more natural outputs. Instead of generating generic AI content, Copilot can gradually learn how individuals communicate and present information, making AI-generated work feel significantly more authentic and personal.

MAKE COPILOT SOUND LIKE YOU
One of Jess's strongest messages is that AI should amplify your voice—not replace it. Too many LinkedIn posts, presentations, and emails already sound identical because users rely on generic prompts. She demonstrates how Outlook, Copilot Memory, Brand Kits, and writing preferences can help AI understand an individual's communication style. Users can even ask Copilot to analyze previous emails and automatically generate custom writing instructions that reflect their natural tone, vocabulary, and personality.

BUILDING YOUR OWN PROMPT LIBRARY
Rather than writing prompts repeatedly, Jess recommends creating a personal prompt library. Organizations should also identify enthusiastic Copilot champions within each department—not necessarily the most technical employees, but those who enjoy sharing knowledge with colleagues. These champions can continuously refine departmental prompts, reusable workflows, and business scenarios that make AI easier for everyone else to adopt. Over time, these libraries become valuable organizational assets that dramatically accelerate productivity.

HER FAVORITE COPILOT WORKFLOWS
Jess shares several real-world workflows she uses almost every day:

• Converting book chapters into complete PowerPoint presentations.
• Automatically creating realistic business scenarios for Microsoft 365 training.
• Generating fictional organizations, conversations, and Teams discussions for demonstrations.
• Building job descriptions, hiring documentation, and standard operating procedures for her growing business.
• Transforming existing documentation into presentation-ready content while preserving screenshots and instructional flow.

These examples demonstrate how Copilot becomes a creative business partner rather than simply a chatbot.

WHY POWERPOINT IS HER FAVORITE COPILOT EXPERIENCE
Among all Microsoft 365 applications, Jess currently finds the greatest value in PowerPoint Copilot. Once users understand slide masters, structured Word headings, templates, and reference documents, Copilot can rapidly generate professional presentations that require far less manual formatting than traditional workflows. While the feature has evolved significantly since its initial release, understanding its design principles is essential for consistently producing high-quality presentations. 

FINDING YOUR AI VOICE
Jess believes one of the biggest long-term challenges of AI is preserving authenticity. Older professionals already have years of writing samples that AI can learn from, but younger generations may increasingly rely on AI before developing their own communication style. Her advice is simple: continue writing, develop your own voice, and use Copilot to enhance—not replace—your personality. Authentic communication will become increasingly valuable as AI-generated content becomes more common. 

MANAGING AI OVERLOAD
Keeping up with Microsoft's AI announcements has become a full-time job. Jess openly discusses the growing challenge of information overload faced by trainers, consultants, and content creators. Rather than manually tracking every announcement, she recommends using AI itself to monitor product updates, summarize changes, and surface only the most relevant information. Building AI-powered learning workflows is becoming just as important as learning the products themselves. 

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

Microsoft Copilot has transformed how organizations interact with AI, making conversational experiences more accessible than ever. But while chat-based AI delivers immediate productivity gains, it does not provide the architectural foundation required for enterprise-scale autonomous agents. As organizations deploy more AI solutions across departments, they quickly encounter governance challenges, identity issues, fragmented integrations, and uncontrolled costs. Copilot is an excellent interface—but it is only one layer of a much larger AI ecosystem.

AGENT IDENTITY, GOVERNANCE, AND SECURITY FOR ENTERPRISE AI
One of the biggest challenges in enterprise AI is identity. Many organizations still allow AI agents to operate under shared service accounts or even employee credentials, making auditing nearly impossible. Every autonomous agent should have its own dedicated identity, least-privilege permissions, and complete traceability. Combined with centralized governance, organizations gain full visibility into who—or what—accessed sensitive data, ensuring compliance with standards such as GDPR, SOC 2, and industry-specific regulations. 

FROM RAG TO ONTOLOGIES: BUILDING AGENTS THAT UNDERSTAND BUSINESS CONTEXT
Traditional Retrieval-Augmented Generation (RAG) systems retrieve documents and generate answers based on matching text. While useful, they rarely understand how a business actually operates. Agent Mesh architectures replace document-centric reasoning with ontologies that model customers, products, suppliers, policies, and business relationships. Instead of searching for words, AI agents reason over structured knowledge, dramatically improving accuracy, consistency, and decision-making across the enterprise. 

THE AI LANDING ZONE: CENTRALIZED CONTROL FOR AGENT MESH
Scaling dozens or even hundreds of AI agents requires more than good prompts. Organizations need a dedicated AI Landing Zone that combines identity management, governance policies, model gateways, observability, cost controls, and centralized approval processes. Every model request flows through a governance layer where security, regional compliance, budget limits, and policy enforcement are applied automatically. This approach transforms isolated AI projects into a standardized enterprise platform capable of supporting large-scale autonomous operations. 

AGENT 365, OBSERVABILITY, AND FINOPS FOR RESPONSIBLE AI
Managing AI at scale requires complete operational visibility. A centralized control plane such as Agent 365 enables organizations to inventory agents, monitor usage, assign ownership, retire unused "ghost agents," and analyze every model invocation. Combined with comprehensive observability and FinOps practices, businesses can optimize token consumption, enforce budgets, detect abnormal behavior, and maintain continuous compliance while significantly reducing operational costs. 

THE FUTURE OF MICROSOFT AI: FROM COPILOT TO THE AGENT MESH
The next generation of enterprise AI is no longer about individual chatbots—it is about interconnected, governed, autonomous systems working together. Organizations that invest early in Agent Mesh architectures, centralized governance, ontology-driven reasoning, secure identities, and AI operating platforms will be able to scale hundreds of intelligent agents safely and efficiently. The future belongs to businesses that treat AI not as a feature, but as enterprise infrastructure capable of supporting continuous automation, intelligent decision-making, and long-term digital transformation.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

Christiaan Brinkhoff shares the remarkable career path that took him from speaking at community events and writing technical blogs to becoming one of the key people behind Microsoft's modern cloud desktop strategy. After joining FSLogix, which was later acquired by Microsoft, he helped shape Azure Virtual Desktop before becoming part of the secret development team behind Windows 365. He discusses working in Redmond during one of the most transformative periods in Microsoft's history, contributing to innovations including Windows 365 Boot, Windows 365 Switch, the Windows App, multiple patents, and the evolution of Cloud PCs. Today, he continues driving innovation as VP of Product at Nerdio, helping organizations simplify enterprise endpoint management.

WHY CLOUD PCS ARE BECOMING THE FUTURE OF ENTERPRISE COMPUTING
Cloud PCs are no longer just a niche virtualization technology. Christiaan explains how Windows 365 fundamentally changes enterprise computing by moving Windows into the cloud while maintaining the familiar user experience. Instead of thinking about remote desktops as a complex virtualization platform, organizations can now manage Cloud PCs through Microsoft Intune just like traditional physical devices. This dramatically lowers the barrier to adoption while making remote work, device replacement, and endpoint security significantly easier to manage. 

AZURE VIRTUAL DESKTOP VS. WINDOWS 365
One of the biggest discussions in modern endpoint management is understanding where Azure Virtual Desktop ends and Windows 365 begins. Christiaan explains that Azure Virtual Desktop remains the highly customizable Platform-as-a-Service offering for organizations needing maximum flexibility, while Windows 365 delivers a fully managed Software-as-a-Service experience where Microsoft handles much of the underlying complexity. Rather than replacing each other, both services complement one another, allowing organizations to choose the right solution based on workloads, management capabilities, and business requirements. 

HOW COVID ACCELERATED THE CLOUD PC REVOLUTION
The pandemic completely transformed the adoption of virtual desktops. Christiaan reflects on how Azure Virtual Desktop evolved from a relatively small service into one of Microsoft's fastest-growing enterprise platforms almost overnight. Organizations suddenly needed secure remote access for thousands of employees, and Microsoft's virtualization technologies became a critical foundation for enabling remote work around the world. This massive adoption also created the demand for an even simpler cloud-native experience, ultimately accelerating the development and success of Windows 365. 

THE STORY BEHIND WINDOWS 365 BOOT AND WINDOWS 365 SWITCH
Few people know the design decisions behind some of Windows 365's most innovative features. Christiaan explains how Windows 365 Boot was created to remove the complexity of traditional virtual desktop logins by allowing users to boot directly into a Cloud PC. He also shares how Windows 365 Switch enables users to seamlessly move between their local device and their Cloud PC as naturally as switching between Windows virtual desktops. Both features were designed to hide technical complexity and create an experience that feels completely native to Windows users. 

WHY MICROSOFT INTUNE BECAME THE FOUNDATION OF WINDOWS 365
One of the smartest strategic decisions Microsoft made was integrating Windows 365 directly into Microsoft Intune rather than building an entirely separate management platform. Christiaan explains how this allows IT administrators to manage Cloud PCs using the same policies, security settings, compliance controls, and deployment processes they already use for physical devices. This unified management experience significantly reduced adoption barriers and made Windows 365 attractive to organizations of every size.

FROM COPILOT TO AGENTIC
AI Artificial intelligence is rapidly evolving beyond simple chat assistants. Christiaan believes today's Copilot experiences represent only the first generation of enterprise AI. The next stage is Agentic AI, where multiple specialized AI agents collaborate, automate workflows, communicate with systems, and execute complex business processes with minimal human intervention. Instead of interacting with one assistant, organizations will increasingly orchestrate entire teams of AI agents working together behind the scenes. WHY

THE FUTURE OF AI HAS ALMOST NO USER INTERFACE
One of the most thought-provoking ideas from the conversation is Christiaan's belief that the best AI interface may ultimately become almost invisible. Rather than navigating traditional menus and dashboards, users will simply describe what they want to accomplish while AI dynamically generates reports, dashboards, code, documentation, or management actions in real time. The focus shifts away from software interfaces toward outcomes, making enterprise software significantly more intuitive.

REINVENTING ENDPOINT MANAGEMENT WITH AI
Endpoint management is entering an entirely new era. Christiaan describes how AI will increasingly automate repetitive administrative work such as policy deployment, reporting, troubleshooting, compliance monitoring, and device lifecycle management. Instead of manually clicking through management consoles, IT administrators will interact with intelligent systems capable of understanding natural language and performing complex operations securely on their behalf. 

WHAT NERDIO IS BUILDING FOR THE AI ERA
At Nerdio, Christiaan is helping develop the next generation of endpoint management powered by AI. Rather than replacing Microsoft Intune, Nerdio focuses on simplifying complex management tasks, integrating AI-driven automation, and enabling administrators to manage Windows 365, Azure Virtual Desktop, and traditional endpoints through intelligent workflows. The long-term vision is an adaptive management platform capable of understanding business intent rather than simply executing predefined configuration steps. 

THE RISE OF THE AGENTIC USER
One of the most fascinating concepts discussed is Microsoft's emerging idea of the "Agentic User." Instead of every action being performed directly by a human administrator, organizations will increasingly authorize AI agents to execute tasks on behalf of users while respecting permissions, RBAC controls, and governance policies. This creates digital workers capable of securely performing routine administrative work while humans remain responsible for oversight and strategic decisions. 

AI TROUBLESHOOTING IS CLOSER THAN YOU THINK
When discussing the future of technical support, Christiaan explains that AI already has the capability to analyze logs, identify patterns, detect root causes, and recommend solutions much faster than human administrators. The remaining challenge is securely connecting these AI capabilities with enterprise management systems so that intelligent troubleshooting can move beyond recommendations and begin performing autonomous remediation where appropriate. WHY 

THE NEXT OPERATING SYSTEM MAY LOOK COMPLETELY DIFFERENT
According to Christiaan, Windows itself is beginning a significant transformation. As increasingly powerful NPUs and AI accelerators become standard hardware, more AI workloads will execute locally instead of exclusively in the cloud. Combined with advances in AI-first interfaces, the traditional desktop may gradually evolve into a much more conversational, adaptive, and context-aware operating environment where users interact primarily through intelligent assistants instead of conventional applications. 

GRAPH API, MCP, AND THE FUTURE OF ENTERPRISE AUTOMATION
Graph API remains a critical foundation for Microsoft's ecosystem, but Christiaan expects Model Context Protocol (MCP) and AI orchestration technologies to become increasingly important. Rather than replacing Graph, MCP can build upon it, allowing intelligent agents to securely interact with enterprise systems through standardized interfaces while dramatically expanding automation possibilities across Microsoft 365 and beyond. 

WHY COMMUNITY STILL MATTERS
Despite working on some of Microsoft's most important cloud technologies, Christiaan repeatedly returns to one message: everything started with community. Blogging, presenting at user groups, sharing knowledge, and helping others opened career opportunities that ultimately led to Microsoft. He encourages listeners to contribute to the community, continuously learn, and remain curious because those investments often create opportunities that cannot be planned in advance

RAPID FIRE INSIGHTS
During the quick-fire round, Christiaan shares several personal preferences and predictions:

• Windows 365 over Azure Virtual Desktop
• Microsoft Intune over Configuration Manager
• AI Agents over traditional Copilot assistants
• Graph API over PowerShell
• Microsoft Teams over Outlook
• Discipline as the most important success habit

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.

A successful Microsoft 365 Copilot deployment begins long before licenses are assigned. Organizations should first define measurable business outcomes, identify high-value use cases, and secure executive sponsorship across IT, security, finance, and business leadership. Rather than treating Copilot as another software rollout, enterprises need an AI operating model that aligns governance, adoption, security, and ROI with real business processes. Starting with targeted scenarios creates faster wins while reducing risk and establishing a repeatable framework for future AI initiatives.

ASSESS MICROSOFT 365 READINESS BEFORE ENABLING COPILOT
One of the biggest mistakes organizations make is assuming their Microsoft 365 tenant is AI-ready simply because they own the licenses. Before deployment, businesses should assess identity management, SharePoint permissions, Teams collaboration spaces, OneDrive sharing, Microsoft Entra ID, Conditional Access, and overall information architecture. Existing oversharing, outdated permissions, unmanaged guest accounts, and poor data ownership become significantly more visible once Copilot can surface enterprise knowledge through natural language. A structured readiness assessment identifies critical risks before they become security incidents during rollout. 

SECURE YOUR DATA WITH GOVERNANCE, PERMISSIONS, AND MICROSOFT PURVIEW
Microsoft 365 Copilot never creates new permissions—it simply works with the permissions users already have. That makes governance, Microsoft Purview, sensitivity labels, Data Loss Prevention, lifecycle management, and permission cleanup essential parts of every deployment. Organizations should prioritize high-risk content, establish clear ownership of SharePoint sites and Teams, implement strong information protection policies, and continuously review access rights. AI success depends as much on data quality and governance as it does on the underlying technology. 

RUN A CONTROLLED COPILOT PILOT BEFORE SCALING ACROSS THE ENTERPRISE
Enterprise AI should expand through carefully planned pilot programs instead of company-wide deployments. Successful pilots focus on repeatable business workflows, measurable productivity improvements, and clearly defined success criteria. Business owners, IT, security, and finance should jointly evaluate business outcomes, adoption rates, governance findings, and user feedback before approving additional rollout phases. Every pilot should generate practical lessons that improve future deployments rather than simply proving that Copilot can generate content. 

DRIVE MICROSOFT 365 COPILOT ADOPTION WITH CHANGE MANAGEMENT
Technology alone does not transform an organization—people do. Successful Copilot adoption requires executive communication, role-based enablement, workflow-specific training, AI champions, ongoing coaching, and continuous learning. Employees need practical guidance on when to trust Copilot, when human review remains mandatory, and how AI supports rather than replaces professional judgment. Measuring adoption should focus on changed business behavior and improved workflows instead of simple prompt counts or login statistics. 

MEASURE COPILOT ROI AND BUILD A SCALABLE ENTERPRISE AI PLATFORM
The true return on Microsoft 365 Copilot comes from measurable business improvements rather than AI usage alone. Organizations should track workflow efficiency, quality improvements, reduced rework, employee productivity, governance maturity, and financial outcomes across every deployment phase. A successful rollout creates more than a productive workforce—it establishes the governance, architecture, operating model, and organizational experience required to scale future AI capabilities such as Copilot Studio, AI agents, Microsoft Graph integrations, and enterprise automation.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.