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

Your PowerShell Scripts Are Obsolete

1 h 12 min · 28 de may de 2026
Portada del episodio Your PowerShell Scripts Are Obsolete

Descripción

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 exists * Assign licenses * Configure mailbox settings * Send notifications The 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 dynamically * Correlate data across systems * Adapt to unexpected conditions * Decide what action makes sense next This 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 request * Build a plan dynamically * Execute the required tools * Evaluate the results * Adapt if assumptions fail Unlike traditional scripts, agents do not panic when something unexpected happens. If an API throttles requests, if a device is missing compliance data, or if a user record is incomplete, the agent recalculates its next move rather than terminating the workflow entirely. This creates systems that are dramatically more resilient, scalable, and adaptive than deterministic automation. SEMANTIC KERNEL AS THE ORCHESTRATION ENGINE One of the most important concepts discussed in this episode is Semantic Kernel and its role in orchestrating AI-driven automation across Microsoft 365 environments. Semantic Kernel is not simply a PowerShell wrapper. It acts as the reasoning layer between large language models and enterprise tooling. By exposing PowerShell functions as structured plugins with descriptions, parameters, and expected outputs, administrators can teach AI systems when and why tools should be used.  WHAT SEMANTIC KERNEL ENABLES Semantic Kernel allows organizations to: * Turn PowerShell cmdlets into AI-callable tools * Build multi-step adaptive workflows * Dynamically orchestrate Microsoft Graph operations * Enable contextual reasoning instead of static execution The result is a shift from traditional “runbook automation” toward intelligent orchestration systems capable of handling ambiguity and complexity. MICROSOFT GRAPH BECOMES THE ENTERPRISE DATA FABRIC Microsoft Graph sits at the center of this new architecture. Rather than querying disconnected systems independently, autonomous agents use Graph as the unified interface across Microsoft 365 services including Azure AD, Intune, Exchange, Teams, SharePoint, and more. This creates a powerful operational model where agents can correlate information across multiple workloads simultaneously. An agent troubleshooting a Teams access issue may automatically: * Verify Azure AD identity health * Check Conditional Access policies * Inspect Intune compliance states * Review mailbox synchronization * Analyze Teams licensing assignments Instead of forcing administrators to manually jump between dashboards, the agent builds a complete operational picture automatically. WHY SECURITY MODELS MUST EVOLVE One of the most critical discussions in this episode centers around authentication and identity governance. Traditional automation relies heavily on long-lived service principals with broad tenant-wide permissions. That model becomes extremely dangerous once autonomous systems begin operating continuously at scale. The future moves toward: * Just-in-time authentication * Task-scoped tokens * Managed identities * Continuous Access Evaluation (CAE) * Policy-driven authorization Rather than giving agents permanent access to an entire tenant, modern systems issue short-lived credentials scoped to specific operations. This dramatically reduces blast radius if a system is compromised. HUMAN-IN-THE-LOOP GOVERNANCE Autonomous does not mean uncontrolled. The episode strongly emphasizes that enterprise AI systems must operate within strict governance boundaries. Low-risk operations may execute autonomously, while high-risk actions require explicit human approval. Examples of autonomous operations include: * Reading compliance states * Gathering diagnostic data * Checking mailbox configurations * Verifying user licenses Examples requiring approval include: * Resetting MFA methods * Modifying Conditional Access * Deleting users or devices * Assigning privileged permissions This creates a collaborative operational model where agents accelerate diagnostics and execution while humans retain authority over high-impact decisions. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

Comentarios

0

Sé la primera persona en comentar

¡Regístrate ahora y únete a la comunidad de M365.FM - Modern work, security, and productivity with Microsoft 365!

Prueba gratis

Empieza 7 días de prueba

$99 / mes después de la prueba. · Cancela cuando quieras.

  • Podcasts solo en Podimo
  • 20 horas de audiolibros al mes
  • Podcast gratuitos

Todos los episodios

635 episodios

episode Steps to Microsoft 365 Copilot Extensibility with Gautam Sheth [MVP] artwork

Steps to Microsoft 365 Copilot Extensibility with Gautam Sheth [MVP]

In this episode of the M365 Show, host Mirko Peters sits down with Gautam Sheth, a five-time Microsoft MVP, Microsoft 365 developer, open-source contributor, and one of the key maintainers behind some of the most widely used community tools in the Microsoft ecosystem. Gautam has spent years helping organizations build, automate, and extend Microsoft 365 solutions while contributing to projects such as PnP PowerShell, PnP Core SDK, and other community-driven initiatives that thousands of developers rely on every day.The conversation explores the evolution of Microsoft 365 development, the growing importance of Microsoft Graph, the rise of Microsoft 365 Copilot Extensibility, and how artificial intelligence is fundamentally changing the way software is designed, developed, deployed, and maintained. Gautam shares real-world insights from his work with enterprise customers, open-source communities, and modern AI-driven development workflows.Whether you're a Microsoft 365 developer, SharePoint consultant, Teams developer, solution architect, IT professional, or simply curious about the future of AI-powered software development, this episode offers practical guidance and valuable perspectives on where the Microsoft ecosystem is heading next. FROM SHAREPOINT DEVELOPER TO MICROSOFT 365 EXPERT Gautam begins by sharing his professional journey through the Microsoft ecosystem. Starting in the traditional SharePoint server-side development world, he witnessed firsthand the industry's shift toward cloud-first architectures and Microsoft 365 services.Over the years, the Microsoft development landscape has evolved dramatically. What once revolved around SharePoint Server customization and farm solutions has transformed into a modern ecosystem powered by SharePoint Online, Microsoft Teams, Microsoft Graph, Power Platform, and now Microsoft 365 Copilot.Gautam discusses how developers have had to continuously adapt their skills while embracing new technologies and development models. His story serves as a reminder that successful developers remain lifelong learners who evolve alongside the platforms they support. WHY OPEN SOURCE MATTERS IN THE MICROSOFT ECOSYSTEM One of the most fascinating parts of the discussion focuses on open-source software and community-driven innovation.Gautam explains how projects like PnP PowerShell emerged because developers needed capabilities that weren't fully addressed by Microsoft's first-party tools. Instead of waiting for new features to arrive, community contributors built solutions that filled important gaps and helped developers become more productive.The conversation highlights how open-source projects often move faster than traditional software releases, enabling developers to experiment, innovate, and solve real-world business challenges more effectively.Listeners will gain a deeper understanding of: • How open-source projects complement Microsoft's official tooling. • Why community-driven innovation continues to thrive within Microsoft 365. • The role contributors play in improving developer experiences. • How developers can participate in and benefit from open-source communities. • Why collaboration remains one of the most powerful forces in modern software development. UNDERSTANDING PNP POWERSHELL AND PNP CORE SDK For many Microsoft 365 professionals, PnP PowerShell and PnP Core SDK have become essential tools.Gautam explains how these tools simplify common Microsoft 365 operations, automate administrative tasks, and provide more developer-friendly experiences when working with SharePoint, Teams, OneDrive, Microsoft Graph, and other Microsoft 365 services.The discussion covers why organizations continue to adopt PnP solutions and how these community-maintained tools help address real-world challenges encountered by developers and administrators every day.He also provides behind-the-scenes insight into what it takes to maintain libraries used by thousands of organizations worldwide and how community contributions help drive continuous improvement. THE ROLE OF MICROSOFT GRAPH IN MODERN DEVELOPMENT No discussion about Microsoft 365 development would be complete without Microsoft Graph.Gautam describes Microsoft Graph as the central API layer powering nearly every Microsoft 365 experience. From SharePoint and Teams to Outlook and Planner, Microsoft Graph serves as the connective tissue that enables developers to build integrated business solutions.The conversation explores:How Microsoft Graph has evolved over time.The benefits of Graph-first development.Challenges developers face when working directly with APIs.How SDKs simplify Graph development.The future role of Graph in AI-powered applications.As Microsoft continues investing heavily in AI and Copilot experiences, Graph remains one of the most important technologies developers should understand. WHY COPILOT EXTENSIBILITY IS A GAME CHANGER One of the major themes throughout the episode is Microsoft 365 Copilot Extensibility.Gautam explains why extensibility represents one of the biggest opportunities for developers in the Microsoft ecosystem today. Organizations are increasingly looking for ways to customize Copilot experiences, connect business data, integrate external systems, and create AI-powered workflows tailored to their unique needs.The discussion examines:How Copilot extensibility works.Why enterprises are investing in custom AI experiences.The role of Microsoft Graph and Microsoft 365 services in Copilot.Opportunities for developers entering the space.How extensibility can unlock significant business value.According to Gautam, developers who invest in learning Copilot extensibility today are positioning themselves for one of the fastest-growing areas in enterprise technology. AI-POWERED DEVELOPMENT IS CHANGING EVERYTHING Artificial Intelligence is no longer a future concept—it is becoming a core part of the software development lifecycle.Gautam discusses how AI tools have evolved from simple autocomplete systems into sophisticated development assistants capable of generating code, reviewing pull requests, identifying issues, and accelerating delivery cycles.The conversation explores how AI helps developers:Write code faster.Prototype applications more efficiently.Debug complex issues.Generate documentation.Improve development productivity.Reduce repetitive tasks.At the same time, Gautam emphasizes that AI should be viewed as an accelerator rather than a replacement for technical expertise. AI ASSISTANTS VS AGENTIC AI One of the most insightful moments of the episode focuses on the difference between AI assistants and Agentic AI.While traditional AI assistants help users complete individual tasks, Agentic AI systems can perform entire workflows with limited human intervention.Examples include:Creating development branches.Writing application code.Running automated tests.Reviewing code quality.Generating pull requests.Executing end-to-end workflows.This distinction is becoming increasingly important as organizations explore new ways to automate software development and operational processes. GITHUB COPILOT AND THE FUTURE OF SOFTWARE ENGINEERING GitHub Copilot has rapidly become one of the most influential AI tools available to developers.Gautam shares his perspective on how GitHub Copilot has evolved from a coding assistant into a complete AI development platform.The discussion covers:GitHub Copilot agents.Model selection strategies.Cloud-based development workflows.AI-assisted pull request reviews.Repository automation.Future trends in AI-powered software engineering.He also discusses how developers can maximize the value of GitHub Copilot while maintaining strong engineering standards and code quality. SECURITY, GOVERNANCE, AND COMPLIANCE IN THE AGE OF AI As organizations adopt AI technologies, security and governance concerns continue to grow.Gautam explains why governance remains critical regardless of how advanced AI systems become.Key topics include:Authentication design.Permission management.Least-privilege security models.Compliance requirements.Data governance.Auditing and monitoring.Responsible AI implementation.Organizations that successfully combine innovation with governance will be best positioned to realize the benefits of AI while minimizing risk. THE FUTURE OF MICROSOFT 365 DEVELOPMENT Looking ahead, Gautam predicts continued growth in AI-powered development, Copilot extensibility, agent-based workflows, and intelligent automation.While technologies continue to evolve rapidly, he believes several principles remain unchanged:Strong technical fundamentals matter.Developers should understand the code they ship.AI should enhance—not replace—engineering judgment.Continuous learning remains essential.Community collaboration drives innovation.These principles will continue guiding successful developers regardless of which tools become popular in the future. RAPID FIRE HIGHLIGHTS During the rapid-fire round, Gautam shares some personal favorites and predictions:His current favorite development tool is Claude Code.He believes Copilot CLI deserves more attention from developers.Debugging remains one of the most underrated skills in software engineering.Documentation continues to be one of the best ways to learn new technologies.He predicts that AI will dramatically reshape software development over the coming years.His advice to developers is simple: learn AI-assisted development now and become comfortable working alongside intelligent tools. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

5 de jun de 202647 min
episode I building a Synthetic Market for M365 Strategy artwork

I building a Synthetic Market for M365 Strategy

What if you could test every major Microsoft 365 decision before making it?What if you could simulate governance changes, Copilot deployments, security investments, automation initiatives, and organizational transformation strategies before spending a single dollar?In this episode of M365 FM, Mirko Peters explores a groundbreaking approach to Microsoft 365 strategy: building a synthetic market of digital organizations to simulate decision-making, predict outcomes, and understand how governance choices impact AI adoption at scale.Using Azure AI Foundry, GraphRAG, synthetic company personas, and multi-agent simulations, Mirko created a virtual market consisting of 100 unique organizations. Each organization had its own governance model, collaboration patterns, security posture, identity architecture, and operational culture. The goal was simple: understand why some organizations successfully scale AI while others repeatedly fail despite investing in the same technology. WHY MOST AI ADOPTION FAILS The biggest obstacle to AI success isn't technology.It's governance.Most organizations approach AI adoption as a procurement exercise. They purchase licenses, launch pilot programs, measure usage, and expect business value to emerge automatically. The reality is far different. The simulation revealed that most AI initiatives fail because they are deployed into operating models that were never designed for AI-driven work.Throughout the episode, Mirko demonstrates how identity sprawl, collaboration chaos, automation debt, unclear ownership, and compliance theater create predictable failure patterns that appear in almost every organization.The surprising discovery wasn't that organizations fail.It was how consistently they fail. THE FIVE FAILURE PATTERNS After running more than 1,000 simulation iterations across 100 synthetic organizations, five governance patterns repeatedly emerged as the primary causes of AI adoption failure.These patterns include: * Identity Blind Spots * Collaboration Sprawl Without Lifecycle Management * Automation Without Governance * Ownership and Accountability Gaps * Compliance Theater Each pattern emerged at predictable stages of AI adoption and produced measurable business consequences, including stalled adoption, compliance incidents, security concerns, operational failures, and declining user trust.Most importantly, the simulation revealed exactly what successful organizations did differently. SYNTHETIC ORGANIZATIONS AND DIGITAL MARKETS Traditional strategy relies heavily on historical data and executive intuition.Synthetic markets introduce a different approach.By creating realistic digital representations of organizations, leadership teams can simulate future scenarios, test strategic assumptions, evaluate governance models, and predict outcomes before making investments.Mirko explains how Azure AI Foundry, GraphRAG, Knowledge Graphs, and Multi-Agent Systems were combined to create a virtual market where synthetic CISOs, Architects, Compliance Officers, and Business Leaders interacted with one another and made decisions under realistic constraints.The result was a living laboratory for Microsoft 365 strategy. THE GOVERNANCE-FIRST MODEL One of the most important findings from the simulation was that governance is not a constraint on innovation.Governance is the foundation that makes innovation possible.Organizations that treated governance as documentation consistently struggled. Organizations that treated governance as an operational system of ownership, automation, monitoring, and accountability consistently outperformed their peers.The episode explores how modern governance must evolve beyond policy documents and become embedded directly into the architecture of Microsoft 365 through automated controls, lifecycle management, access reviews, and operational guardrails.Topics covered include: * Identity Governance * Data Classification * Lifecycle Management * Automation Governance * Continuous Compliance THE IDENTITY READINESS FRAMEWORK Everything starts with identity.Before organizations can safely scale Microsoft Copilot, AI Agents, or Automation, they must understand who has access to what and why.The simulation showed that organizations with mature identity governance consistently achieved higher adoption rates, fewer security incidents, and faster time-to-value.Learn how identity cleanup, least privilege, access reviews, managed identities, and ownership models create the foundation for successful AI transformation. THE DATA, COLLABORATION, AND AUTOMATION LAYERS Once identity is under control, organizations must address the remaining governance layers.Mirko introduces a practical readiness framework that covers: * Data Classification and Protection * Collaboration Lifecycle Management * Workspace Ownership * Power Automate Governance * Logic Apps Governance * Environment Separation * Automation Monitoring Together, these capabilities create the operational foundation required for trustworthy AI systems. FROM GOVERNANCE TO INTELLIGENCE Most organizations try to deploy AI first and fix governance later.The simulation proved this approach repeatedly fails.Instead, successful organizations follow a clear adoption sequence:Identity → Data → Collaboration → Automation → IntelligenceOnly after the first four layers are operational should organizations scale Copilot, AI Agents, and intelligent automation.This sequence dramatically increases adoption success rates while reducing security incidents, compliance risk, and operational disruption. THE 90-DAY READINESS ASSESSMENT How ready is your organization for AI?To answer that question, Mirko introduces a practical readiness framework that evaluates five critical domains: * Identity Readiness * Data Readiness * Collaboration Readiness * Automation Readiness * Governance Readiness The resulting score provides a surprisingly accurate predictor of AI adoption success and helps organizations identify where they should focus before scaling AI initiatives. WHO SHOULD LISTEN? * Microsoft 365 Architects * CIOs and CTOs * Governance Leaders * Security Professionals * Compliance Teams * Enterprise Architects * Copilot Strategy Teams * AI Transformation Leaders * Digital Workplace Teams * Microsoft MVPs IN THIS EPISODE * Building synthetic organizations * Creating digital markets for strategy simulation * Azure AI Foundry and GraphRAG * Multi-Agent Systems * Microsoft 365 Governance * AI Adoption Models * Identity Governance * Copilot Readiness * Automation Governance * Compliance and Security * Digital Twins for Organizations * Strategic Simulation * Enterprise AI Adoption * Governance Operating Models KEY TAKEAWAYS * Governance predicts AI success more accurately than technology selection * Most AI failures are structural, not technical * Synthetic markets allow organizations to test decisions before implementation * Identity is the foundation of AI readiness * Governance should be automated, not documented * AI amplifies existing organizational weaknesses * Successful organizations build foundations before scaling intelligence * Governance is not a barrier to innovation—it enables innovation at scale The future of Microsoft 365 strategy won't be built on assumptions, best practices, or intuition alone.It will be built on simulation.The organizations that win with AI will increasingly test their decisions in synthetic environments before making them in the real world. Those that do will move faster, reduce risk, and create a significant competitive advantage in the age of intelligent work. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

5 de jun de 20261 h 16 min
episode My Microsoft Copilot is now JARVIS: This is how I built it artwork

My Microsoft Copilot is now JARVIS: This is how I built it

Most people are using Microsoft Copilot completely wrong.They treat it as a smarter search engine, a better chatbot, or a productivity feature tucked away inside Outlook, Teams, or Word. They ask a question, get an answer, and move on to the next task.But that's not JARVIS.In this episode of M365 FM, Mirko Peters explores how Microsoft Copilot can evolve from a reactive assistant into a true operating system for work. Instead of simply responding to prompts, JARVIS combines memory, reasoning, orchestration, governance, and automation to create an AI system that understands how you work, remembers what matters, and proactively helps you get things done.The future of AI isn't better prompts.The future is architecture. WHY COPILOT FAILS AT AGENCY The biggest limitation of most AI systems isn't intelligence. It's memory.Every new chat starts from zero. The system doesn't remember your decisions, your communication style, your business priorities, or the lessons learned from previous projects. This forces users to repeatedly provide context and creates AI experiences that remain generic and reactive.Mirko explains why context windows are not memory, why chat interfaces are not workflows, and why true agency requires persistence, structure, and orchestration.Key concepts include: * Context vs Memory * Reactive vs Proactive AI * Copilot as a Feature vs Copilot as a Platform * The Architecture Gap THE JARVIS MODEL JARVIS is not a new AI model.It's an architectural pattern built on top of Microsoft Copilot that transforms AI from a tool into a system.The model consists of four foundational layers that work together to create agency, decision-making, and orchestration across Microsoft 365 and beyond.The four layers include: * Memory * Action * Reasoning * Governance Together, these layers create an AI operating system capable of understanding context, executing workflows, making decisions, and operating safely within organizational boundaries.THE MEMORY LAYERMemory is the foundation of everything.Most organizations focus on storing information. JARVIS focuses on storing operational knowledge. Instead of simply saving documents and conversations, the system captures how decisions are made, how work gets done, and which rules should guide future actions.Learn how structured SKILL.md files create reusable capabilities that allow Copilot to understand workflows, communication preferences, decision frameworks, stakeholder relationships, and organizational knowledge.Discover why memory isn't about storing data.It's about encoding behavior. COPILOT COWORK AND THE EXECUTION LAYER Microsoft's new Copilot Cowork capabilities fundamentally change how work gets executed.Rather than drafting content and waiting for manual action, Cowork orchestrates multi-step processes across Microsoft 365 applications. It can summarize meetings, draft communications, create presentations, schedule follow-ups, update systems, and coordinate workflows from a single goal.This episode explores how orchestration differs from assistance and why execution is the missing ingredient in most AI deployments.Topics covered include: * Copilot Cowork * Multi-Step Orchestration * Microsoft Graph * Human Approval Gates * Enterprise Automation AGENT FLOWS AND DECISION MAKING Traditional workflows follow predefined paths.Agent Flows introduce reasoning.Built on Power Automate and powered by Large Language Models, Agent Flows enable systems to evaluate context, identify exceptions, apply business rules, and choose the best path forward dynamically.Mirko explains how organizations can move beyond rigid automation and build systems capable of handling ambiguity, escalation paths, stakeholder sensitivity, compliance requirements, and real-world complexity.This is where automation becomes intelligence. GOVERNANCE, TRUST, AND CONTROL Every organization wants AI agency.Nobody wants uncontrolled automation.The episode explores why governance is the most important layer in any AI architecture. From permissions and policy enforcement to audit trails, observability, compliance, and human oversight, governance creates the boundaries that allow intelligent systems to operate safely.Learn why successful AI systems are not built on trust in the model itself but on trust in the architecture surrounding it.Topics include: * Governance by Design * Data Loss Prevention * Human-in-the-Loop Architecture * Auditability and Transparency * AI Risk Management MICROSOFT GRAPH AS THE BACKBONE At the center of the JARVIS architecture sits Microsoft Graph.Graph provides unified access to emails, meetings, Teams conversations, SharePoint documents, tasks, approvals, calendars, and organizational data. It becomes the nervous system that connects memory, workflows, reasoning, and execution.You'll learn how Graph enables grounding, orchestration, context awareness, and cross-platform automation while respecting permissions, governance policies, and security boundaries. THE FUTURE OF PROACTIVE AI Most AI waits for instructions.JARVIS doesn't.The episode explores how webhooks, background processes, heartbeat jobs, semantic search, grounding strategies, Work IQ, and multi-agent systems combine to create proactive intelligence that identifies opportunities, surfaces risks, and initiates actions before users even think to ask.This shift from reactive assistance to proactive orchestration represents one of the most important architectural transitions happening in AI today. IN THIS EPISODE * Why most Copilot implementations fail * The JARVIS architecture * Persistent memory and SKILL.md files * Copilot Cowork orchestration * Agent Flows in Power Automate * Microsoft Graph architecture * Grounding and contextual reasoning * Governance and compliance * Multi-agent orchestration * Work IQ and organizational intelligence * Proactive AI systems * Building AI operating systems WHO SHOULD LISTEN? * Microsoft 365 Architects * Copilot Studio Developers * IT Leaders * Enterprise Architects * AI Strategy Teams * Automation Specialists * Power Platform Developers * CIOs and CTOs * Digital Transformation Leaders * Microsoft MVPs and Community Builders KEY TAKEAWAYS * Copilot is not the product—the architecture is * Memory transforms assistants into systems * Skills outperform prompts * Orchestration creates real business value * Agent Flows enable intelligent automation * Governance is a prerequisite for agency * Microsoft Graph is the foundation of enterprise AI * The future belongs to proactive systems, not reactive assistants The organizations that win with AI won't have better prompts.They'll have better systems.JARVIS isn't about replacing people. It's about creating an intelligent operating system that amplifies human decision-making, automates orchestration, and continuously learns how work gets done.The future of Microsoft Copilot isn't a chatbot.It's an operating system for knowledge work. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

Ayer1 h 16 min
episode Leading AI, Delivering Transformation, and Building Community with Areti Iles [MVP] artwork

Leading AI, Delivering Transformation, and Building Community with Areti Iles [MVP]

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 BUILT One 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 engagement * Poor change management * Insufficient executive sponsorship * Unrealistic expectations * Limited SME availability * Scope creep * Weak user adoption strategies She 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 feedback, creating ownership within the business, and ensuring employees understand not only how new systems work but why they matter. Successful transformation requires: * Executive buy-in * Strong communication plans * User engagement * Continuous feedback loops * Effective training * Long-term adoption strategies Without these elements, even technically successful projects can fail to deliver business value. UNDERSTANDING AGENTIC AI AI dominates today's technology conversations, but many professionals still struggle to understand what Agentic AI actually means. Areti provides a practical explanation, describing Agentic AI as a collection of autonomous systems capable of planning, making decisions, and executing actions to achieve specific goals. Unlike traditional AI assistants that simply respond to prompts, agents can independently perform tasks, orchestrate workflows, and interact with systems on behalf of users.  HOW AI IS CHANGING THE WAY WE WORK The discussion explores how AI is fundamentally changing the relationship between humans and technology. Historically, people sat at the center of business systems, making every decision and driving every process. Agentic AI introduces a future where humans increasingly manage exceptions while intelligent systems handle routine activities autonomously. Topics discussed include: * Autonomous workflows * AI-powered decision making * Human oversight * AI trust and governance * Organizational readiness * Workforce transformation * Future operating models Areti explains that while the technology is exciting, organizations must remain thoughtful about how much autonomy they grant to AI systems. AI STRATEGY VS BUSINESS STRATEGY One of the most insightful moments of the conversation centers around a common mistake organizations make when adopting AI. According to Areti, AI should never become the strategy itself. Instead, organizations should focus on their business objectives and use AI as a tool to achieve them more effectively. She warns against implementing AI simply because competitors are doing so and encourages leaders to begin with business problems rather than technology solutions. This perspective is especially important as organizations rush to adopt emerging AI capabilities without clearly defining the outcomes they hope to achieve. AI  GOVERNANCE, COMPLIANCE, AND RESPONSIBLE AI  As AI adoption accelerates, governance and compliance have become board-level concerns. Areti provides an in-depth overview of the evolving regulatory landscape and explains why organizations must begin preparing now rather than waiting for regulations to mature. She discusses the growing importance of AI inventories, risk classification, governance frameworks, human oversight, documentation, and auditability. Key governance priorities include: * AI inventories * Risk assessments * Human oversight * Transparency * Monitoring * Documentation * Data protection * Compliance reporting Organizations that establish these foundations early will be better positioned to innovate responsibly and scale AI initiatives successfully. NAVIGATING THE EU AI ACT The European Union AI Act remains one of the most significant regulatory developments in artificial intelligence. During the discussion, Areti explains: * What the AI Act means for businesses * Which organizations may be affected * Why AI literacy matters * How compliance requirements are evolving * What leaders should prioritize today She stresses that organizations should not view compliance as a barrier to innovation but rather as an opportunity to build trustworthy and sustainable AI practices. MICROSOFT'SAPPROACH TO RESPONSIBLE AI  The conversation also explores how Microsoft technologies can help organizations implement secure and compliant AI solutions. Areti discusses the role of: * Microsoft Purview * Microsoft Defender * Azure AI Foundry * Compliance Manager * Data Loss Prevention * AI Monitoring * Security Controls Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

3 de jun de 20261 h 6 min
episode The Architecture of AI Movies: Copilot, Seedance & Higgsfield artwork

The Architecture of AI Movies: Copilot, Seedance & Higgsfield

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 FAIL The 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 DIRECTOR Most 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 planning * Character anchor documentation * AI production governance * Metadata-driven filmmaking SEEDANCE AND CHARACTER CONSISTENCY Character 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 across multiple scenes and production stages.Key concepts include: * Character Reference (Cref) * Identity Anchors * Master Reference Packs * Character Drift Prevention HIGGSFIELD AND CINEMATIC MOTION Great visuals mean nothing without believable movement.Higgsfield introduces advanced camera controls and motion systems that enable creators to generate cinematic movement using techniques familiar to filmmakers and directors of photography.The discussion explores camera presets, motion references, cinematic language, motion complexity thresholds, and the hidden technical limitations that influence render quality.You'll learn why more motion doesn't always create better results and how understanding motion thresholds can dramatically reduce failed generations and wasted credits.Topics covered include: * Motion Control Workflows * Camera Presets * Dolly, Arc, Orbit, and Crane Movements * Motion Reference Mapping * Cinematic Camera Language THE THREE-TOOL AI MOVIE WORKFLOW The real breakthrough happens when these tools work together.This episode introduces a practical architecture that combines Copilot, Seedance, and Higgsfield into a repeatable production system. Copilot manages planning and orchestration, Seedance handles character identity and visual consistency, and Higgsfield controls motion and cinematic execution.Instead of treating AI generation as a creative guessing game, the workflow creates a structured process that can scale from a single scene to a full production.Learn how to: * Build AI movie production pipelines * Create repeatable generation workflows * Scale from single shots to full narratives * Reduce regeneration cycles and production costs GOVERNANCE FOR AI FILMMAKING Professional production requires more than creativity.As AI filmmaking becomes increasingly sophisticated, governance, documentation, version control, and quality management become essential parts of the workflow.Mirko explores concepts such as Production Bibles, Character Documents, Configuration Tracking, Review Gates, Audit Trails, and Quality Standards that help teams maintain consistency across large-scale AI productions.These practices transform AI filmmaking from experimentation into a repeatable business process. THE FUTURE OF AI CINEMA We are moving away from prompt engineering and toward production architecture.The next generation of creators won't succeed because they write better prompts. They'll succeed because they understand systems, workflows, governance, and orchestration. AI filmmaking is becoming less about generating individual clips and more about coordinating entire creative pipelines.Whether you're creating social content, marketing videos, educational content, corporate productions, or narrative films, understanding how AI tools work together will become a critical competitive advantage. IN THIS EPISODE * Why AI movies fail * Character drift and identity consistency * Copilot as a production orchestrator * Seedance 2.0 character workflows * Higgsfield motion systems * Parametric prompt frameworks * Reference pack management * Motion artifact thresholds * AI production governance * Multi-scene continuity * Quality assurance frameworks * AI filmmaking economics * Production planning and orchestration * The future of AI-generated cinema WHO SHOULD LISTEN? * AI Creators * Filmmakers * Content Creators * Marketing Teams * Video Producers * Creative Directors * Microsoft Copilot Users * Prompt Engineers * Digital Storytellers * AI Enthusiasts * Production Teams * Innovation Leaders KEY TAKEAWAYS * AI movies are built through orchestration, not prompts * Character consistency requires structured reference management * Copilot can function as a production director * Motion complexity directly impacts output quality * Governance is essential for scalable AI production * Repeatable workflows outperform creative guesswork * Successful AI filmmaking is becoming an architectural discipline The future of AI filmmaking belongs to creators who understand systems, workflows, and orchestration. The question is no longer which AI video model is best. The question is how well you can connect them together into a production pipeline that consistently delivers professional results. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

3 de jun de 20261 h 8 min