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

The Model is the Vulnerability: Securing Copilot with Entra ID and Zero Trust

1 h 12 min · 31. maj 2026
episode The Model is the Vulnerability: Securing Copilot with Entra ID and Zero Trust cover

Beskrivelse

Microsoft Copilot is transforming how organizations access, analyze, and act on information. But while most security conversations focus on AI models, hallucinations, and prompt engineering, the real risk often lives somewhere else entirely. The model is not the vulnerability. The vulnerability is the identity layer, the permissions model, and the governance framework sitting underneath it.In this episode of the M365 FM Podcast, we explore why Microsoft Copilot doesn't create new security problems—it exposes the ones that already exist. From excessive SharePoint permissions and forgotten group memberships to semantic indexing and AI-powered data discovery, Copilot amplifies every weakness hiding inside your Microsoft 365 environment. If your permissions are broken, AI simply makes those problems easier to find. UNDERSTANDING THE LETHAL TRIFECTA One of the biggest risks in enterprise AI is what security researchers call the "Lethal Trifecta." When these three conditions exist together, organizations become highly vulnerable to AI-driven attacks: • Access to sensitive enterprise data • Exposure to untrusted content such as emails, Teams messages, and SharePoint comments • The ability for AI systems to communicate or take action on behalf of usersWhen these elements combine, prompt injection attacks can move from theoretical risk to real-world business impact. WHY PROMPT INJECTION CHANGES EVERYTHING Prompt injection is not a software bug. It is a consequence of how large language models process information. AI systems cannot reliably distinguish between instructions and data, creating opportunities for attackers to hide commands inside documents, emails, websites, and collaboration platforms.We examine real-world examples including ShareLeak and other Microsoft Copilot vulnerabilities that demonstrated how hidden instructions embedded in content can influence AI behavior. You'll learn why prompt injection remains one of the most critical security challenges facing enterprise AI deployments today. SECURING COPILOT WITH ENTRA ID Identity is the new security perimeter. In a world where AI can access everything a user can see, protecting identities becomes more important than protecting networks.In this episode, we cover:• Phishing-resistant MFA with FIDO2 and Windows Hello for Business • Conditional Access policies designed specifically for Copilot • Risk-based authentication using Entra ID Protection • Continuous Access Evaluation (CAE) and real-time session revocation • Device-bound token protection for high-value users and workloadsThese controls create a stronger foundation for securing AI access before users ever interact with Copilot. ZERO TRUST FOR AI Zero Trust is not a product. It is a design pattern.We break down how Zero Trust principles apply directly to Microsoft Copilot, including least privilege access, continuous verification, identity-first security, and assuming breach. You'll learn why permission cleanup is often the most important Copilot security project your organization will undertake and how over-permissioned SharePoint sites can become major exposure points once semantic search enters the picture. DATA GOVERNANCE, LABELS, AND DLP Security does not stop at identity. Effective Copilot governance requires a strong data protection strategy.This episode explores:• Sensitivity labels and AI-aware data classification • Encryption rights and EXTRACT permissions • BlockContentAnalysisServices controls • Purview Data Loss Prevention (DLP) for Copilot and Copilot Chat • Site scoping and semantic index exclusions • Double Key Encryption (DKE) for highly sensitive contentYou'll discover how organizations can control not only who accesses data, but also whether AI is allowed to analyze it. AGENT IDENTITIES AND THE FUTURE OF AI GOVERNANCE As autonomous AI agents become more common, traditional identity models begin to break down. We discuss Microsoft's Entra Agent ID and why AI agents require a dedicated governance model separate from users and applications.Learn how organizations can manage agent lifecycles, standardize permissions through identity blueprints, and establish guardrails for non-human identities operating inside Microsoft 365. DETECTION, RESPONSE, AND AI SECURITY OPERATIONS No security framework is complete without monitoring and response capabilities.We examine how Microsoft Sentinel, Purview, Defender, and Entra ID work together to detect suspicious AI activity, investigate prompt injection attacks, and automate containment actions. From session revocation playbooks to AI-focused audit logging and Data Security Posture Management (DSPM), you'll gain a practical blueprint for operating Copilot securely at enterprise scale. KEY TAKEAWAYS The most important lesson is simple: Copilot is not creating security problems. It is exposing governance problems that have existed for years.Organizations that succeed with AI will be the ones that :• Treat identity as the primary security boundary • Clean up permissions before large-scale AI deployment • Implement Zero Trust principles across users, agents, and data • Continuously monitor and govern AI interactionsIf you're planning, deploying, or securing Microsoft Copilot, this episode provides a practical framework for building a resilient, identity-first AI security strategy. 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].

Kommentarer

0

Vær den første til at kommentere

Tilmeld dig nu og bliv en del af M365.FM - Modern work, security, and productivity with Microsoft 365-fællesskabet!

Kom i gang

1 måned kun 9 kr.

Derefter 99 kr. / måned · Opsig når som helst.

  • Podcasts kun på Podimo
  • 20 lydbogstimer pr. måned
  • Gratis podcasts

Alle episoder

647 episoder

episode Infrastructure as Code, DevOps & the Future of Azure with Maik van der Gaag [MVP] cover

Infrastructure as Code, DevOps & the Future of Azure with Maik van der Gaag [MVP]

What does it really take to build secure, scalable, and automated cloud environments in Microsoft Azure? In this episode of M365 FM, Mirko Peters sits down with Microsoft Azure MVP Maik van der Gaag to explore Infrastructure as Code, DevOps culture, Terraform, Bicep, GitHub, Azure automation, cloud governance, and the growing impact of AI on modern platform engineering. Drawing from more than 15 years of experience helping organizations modernize their technology landscapes, Maik shares practical lessons from real-world cloud transformations, enterprise Azure deployments, and large-scale automation projects. The conversation starts with Maik's journey from traditional software development and SharePoint projects into Azure cloud architecture, eventually becoming CTO at 3fifty and later Head of Technology for the Microsoft business at Data Balance. Along the way, he reflects on building technical communities, organizing user groups, and what he has learned from years of helping professionals navigate the rapidly changing cloud landscape. THE STATE OF AZURE, CLOUD & HYBRID INFRASTRUCTURE As organizations continue to evaluate cloud-first strategies, Maik discusses the shift he is seeing toward hybrid cloud and sovereign cloud models. While many organizations remain committed to Microsoft Azure, others are balancing public cloud investments with private datacenters and local infrastructure. The discussion explores how geopolitical concerns, compliance requirements, and business continuity planning are influencing modern cloud architecture decisions. Key takeaways: * Why hybrid cloud is growing again * The rise of sovereign cloud discussions * Azure versus on-premises infrastructure * Cloud transformation challenges * Enterprise cloud strategy trends * Security considerations for modern workloads INFRASTRUCTURE AS CODE EXPLAINED  Infrastructure as Code (IaC) has become one of the most important practices in cloud engineering. Maik breaks down the concept in simple terms, explaining how infrastructure can be represented as code, version-controlled, automated, and deployed consistently across environments. Rather than manually creating virtual machines, databases, networking components, and cloud resources, organizations can define their entire environment through reusable code. This approach reduces human error, improves consistency, accelerates deployments, and creates repeatable infrastructure patterns across development, testing, and production environments. Topics covered: * What Infrastructure as Code actually means * Why manual deployments create problems * Reducing configuration drift * Version control for infrastructure * Automation and repeatability * Cost savings through standardization TERRAFORM VS BICEP One of the most practical parts of the discussion focuses on Terraform and Microsoft Bicep. Maik explains the strengths and weaknesses of both approaches and why the right choice depends heavily on organizational requirements. While Bicep offers a streamlined Azure-focused experience and serves as an abstraction layer for ARM templates, Terraform provides multi-cloud flexibility across Azure, AWS, Google Cloud, Cloudflare, and many other platforms. The conversation also explores state management, extensibility, and the growing capabilities of modern Infrastructure as Code tooling. Key takeaways: * Terraform vs Bicep * ARM templates and Azure deployments * State management concepts * Multi-cloud infrastructure strategies * Infrastructure extensibility * Choosing the right tool for your organization DEVOPS IS NOT A TOOL One of the strongest messages from this episode is Maik's belief that DevOps is fundamentally about culture, processes, and collaboration rather than technology alone. Many organizations mistakenly focus on tools while ignoring the organizational changes required to achieve DevOps success. Maik explains why successful DevOps teams combine developers, operations professionals, security experts, and business stakeholders into integrated teams focused on delivering value. The discussion also covers Azure DevOps, GitHub Enterprise, GitOps, DevSecOps, and how organizations can build more effective engineering cultures.  Topics discussed: * DevOps as culture versus technology * Why organizations struggle with DevOps * Azure DevOps vs GitHub * GitOps explained * DevSecOps principles * Building self-organizing teams SECURITY, GOVERNANCE & SECRETS MANAGEMENT Security remains a recurring theme throughout the conversation. Maik highlights one of the most common mistakes organizations make when moving to Azure: assuming cloud environments are automatically secure. The episode explores identity management, Microsoft Entra ID, MFA, Key Vault, managed identities, federated credentials, GitHub Actions, governance strategies, and best practices for protecting enterprise cloud environments. Key takeaways: * Azure security fundamentals * Managing secrets securely * Microsoft Entra ID considerations * Key Vault best practices * Federated identity credentials * Cloud governance and compliance AI, GITHUB COPILOT & THE FUTURE OF CLOUD ENGINEERING Artificial Intelligence is impacting every area of technology, including cloud engineering and Infrastructure as Code. Maik shares how GitHub Copilot and AI-assisted development have dramatically accelerated his daily work. Rather than writing every Terraform or Bicep template manually, AI can generate infrastructure code in seconds. However, Maik stresses a critical point: engineers must still understand, validate, and review every line of AI-generated code. Organizations that blindly trust AI outputs risk introducing security issues, configuration errors, and operational challenges. The discussion covers practical AI adoption, prompt engineering, code validation, AI governance, and how engineers can use AI responsibly without losing critical technical expertise.  Topics covered: * GitHub Copilot for Infrastructure as Code * AI-assisted cloud engineering * Validating AI-generated code * Prompt engineering techniques * Responsible AI adoption * Future skills for cloud professionals CAREER ADVICE FOR CLOUD ENGINEERS The episode concludes with practical advice for professionals looking to start their Infrastructure as Code journey. Maik explains why understanding the "why" behind automation matters more than simply learning a tool and shares recommendations for choosing between Terraform and Bicep based on organizational needs. His final message is simple but powerful: do the things you love, stay engaged with the community, continue learning, and never assume technology is as easy as it first appears. Whether you're a Cloud Architect, Azure Administrator, DevOps Engineer, Platform Engineer, Security Professional, Infrastructure Engineer, IT Consultant, Microsoft MVP, or technology leader, this episode delivers valuable insights into the technologies, practices, and mindsets shaping the future of cloud computing. 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].

11. juni 202652 min
episode How to Architect Low-Cost AI Agents in the Microsoft Cloud cover

How to Architect Low-Cost AI Agents in the Microsoft Cloud

Most organizations think their AI costs are driven by model pricing.They're wrong.The biggest cost problems in Microsoft AI environments often have nothing to do with GPT-5, Azure OpenAI, or Copilot licensing. Instead, they come from hidden architectural decisions that quietly multiply costs behind the scenes.In this episode, we break down the real economics of building AI agents in Microsoft Azure, Microsoft 365, Copilot Studio, and Azure AI Foundry. You'll learn why some organizations spend thousands of dollars per month on AI while others deliver the same business outcomes for a fraction of the cost.We explore the three hidden taxes affecting nearly every enterprise AI deployment: the Context Tax, the Reasoning Tax, and the Autonomous Tax. Together, these invisible costs can turn a successful proof-of-concept into a budget crisis.More importantly, you'll learn how to eliminate them. THE PROMISE VS THE INVOICE Microsoft has made AI easier to deploy than ever before.Copilot appears inside Teams, Outlook, Word, PowerPoint, and Microsoft 365. Azure AI Foundry simplifies model deployment. Copilot Studio allows low-code agent development. Power Platform integrates AI into business processes.But simplicity often hides complexity.The moment you build a custom Copilot Studio agent, connect SharePoint knowledge sources, invoke Azure OpenAI models, or trigger autonomous workflows, you enter a world of consumption billing where every token, action, and retrieval operation has a cost.In this episode, we uncover how Microsoft's AI billing layers actually work and why understanding them is the foundation of any successful AI architecture. THE THREE HIDDEN TAXES OF ENTERPRISE AI Most organizations unknowingly pay three separate AI taxes.The Context TaxPoor retrieval design floods prompts with irrelevant content.Instead of retrieving only the information needed to answer a question, many RAG implementations pull dozens of documents into the prompt, dramatically increasing token consumption while often reducing answer quality.The Reasoning TaxMany organizations route every request to their most expensive model.Simple FAQ requests, classifications, and summarizations frequently run on frontier models when smaller and cheaper models could deliver identical outcomes.The Autonomous TaxAutonomous agents never sleep.Background workflows, Graph grounding, Power Automate actions, and event-driven agents continue consuming credits long after employees have logged off.When these three taxes combine, AI spending can spiral out of control. UNDERSTANDING COPILOT STUDIO COSTS Copilot Studio has become one of the most powerful tools in the Microsoft ecosystem.It also introduces new consumption models that many organizations underestimate.We discuss: * Copilot Credits * Capacity Packs * Pay-As-You-Go billing * Graph Grounding costs * Agent actions * Autonomous triggers * AI Builder transitions * The November 2026 licensing changes Understanding these mechanics is essential before deploying large-scale business agents. THE NOVEMBER 2026 AI BUILDER DEADLINE One of the most important dates in Microsoft's AI roadmap arrives on November 1st, 2026.On that date, seeded AI Builder credits disappear.Organizations currently relying on included AI Builder capacity may discover that previously "free" AI workloads suddenly become billable.We explain: * What changes in November 2026 * Which workloads are affected * How to prepare before the deadline * Why many organizations could face unexpected costs * How to build a transition strategy today THE COST ARCHITECTURE FRAMEWORK Reducing AI costs isn't about buying cheaper models.It's about designing better architectures.The framework discussed in this episode focuses on four core engineering principles:Semantic CachingAvoid generating answers that already exist.Using Azure API Management and vector similarity search, organizations can dramatically reduce repeat LLM calls while improving response times.Prompt CompressionMost prompts are larger than they need to be.We explore Microsoft's LLMLingua framework and how prompt compression can reduce token consumption without reducing answer quality.Model RoutingNot every request deserves GPT-5.Azure AI Foundry's Model Router enables intelligent routing between GPT-5 Nano, GPT-5 Mini, and larger frontier models based on task complexity.Capacity OptimizationLearn when Pay-As-You-Go pricing makes sense and when Provisioned Throughput Units (PTUs) become financially attractive. AZURE AI FOUNDRY AND MODEL ROUTING One of the most exciting developments in Microsoft's AI stack is model routing.Instead of selecting a single model for every task, organizations can allow the platform to automatically choose the most cost-effective model for each request.We explore: * GPT-5 Global * GPT-5 Mini * GPT-5 Nano * Azure AI Foundry Model Router * Multi-model architectures * Cost optimization strategies * Enterprise deployment patterns The result is often substantial cost reductions with little or no impact on user experience. AZURE COST MANAGEMENT FOR AI You can't optimize what you can't measure.This episode walks through practical techniques for monitoring AI costs using: * Azure Cost Management * Azure Monitor * Log Analytics * Kusto Query Language (KQL) * Azure Copilot * Resource Tagging * Cost Classification Frameworks Learn how to identify cost anomalies before they become budget problems. BUILDING A GOVERNANCE MODEL FOR AI Technology alone won't solve cost challenges.Organizations need governance.We discuss: * Cost Classes (Gold, Silver, Bronze) * Chargeback Models * Platform Team Responsibilities * Citizen Developer Governance * Budget Controls * Consumption Caps * AI Service Catalogs * Quarterly Review Processes Without governance, cost optimization efforts rarely survive long-term. THE 90-DAY IMPLEMENTATION ROADMAP To help organizations move from theory to execution, this episode presents a practical 90-day roadmap.Days 1–30: AuditGain visibility into your AI costs.Days 31–60: Quick WinsDeploy caching, retrieval optimization, and budget controls.Days 61–90: Architecture TransformationImplement compression, model routing, governance, and long-term optimization.The roadmap provides a practical path toward sustainable AI economics. REAL-WORLD CASE STUDY We conclude with a detailed case study showing how a support agent architecture was redesigned using the techniques discussed throughout the episode.The results demonstrate how: * Retrieval optimization reduced prompt size * Semantic caching eliminated redundant requests * Model routing lowered inference costs * Governance prevented future cost drift The outcome was a dramatic reduction in operating costs while maintaining service quality and user satisfaction. WHO SHOULD LISTEN? This episode is designed for: * Microsoft 365 Administrators * Copilot Administrators * Azure Architects * Enterprise Architects * IT Leaders * CIOs * CTOs * AI Engineers * Platform Engineers * Power Platform Professionals * Copilot Studio Developers * FinOps Teams * Cloud Financial Management Teams * Security & Governance Professionals If you're building AI solutions on Microsoft technologies, this episode provides a practical blueprint for controlling costs without sacrificing innovation. 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].

11. juni 20261 h 23 min
episode Copilot Studio, Dataverse MCP & The Future of Agentic AI in Microsoft 365 with Nathan Rose [MVP] cover

Copilot Studio, Dataverse MCP & The Future of Agentic AI in Microsoft 365 with Nathan Rose [MVP]

The Microsoft AI landscape is evolving at an incredible pace, and few people are closer to the transformation than Microsoft Business Applications MVP Nathan Rose. In this episode of M365 FM, host Mirko Peters welcomes Nathan for an in-depth conversation about Copilot Studio, Dataverse MCP (Model Context Protocol), Business Skills, Agentic AI, Microsoft 365 Copilot, and the future of intelligent business applications across the Microsoft ecosystem.Nathan shares his journey from the early Microsoft Dynamics CRM 2011 days to becoming a leading Power Platform Solution Architect and community voice. Along the way, he explains how the transition from traditional low-code development to AI-powered application development is reshaping careers, organizations, and enterprise software architecture. For anyone working with Microsoft 365, Power Platform, Dynamics 365, Azure AI, Copilot Studio, Dataverse, or Microsoft Copilot, this episode provides valuable insights into where the industry is heading. THE EVOLUTION FROM LOW-CODE TO AGENTIC AI The conversation begins with Nathan's experience in the Microsoft Power Platform community and how low-code tools such as Power Apps, Power Automate, Dataverse, and Power Virtual Agents opened the door for people from non-traditional technical backgrounds. As AI becomes increasingly integrated into Microsoft's platform strategy, Nathan explains why organizations are moving beyond traditional workflows and into a new era of Agentic AI.Rather than simply automating predefined processes, modern AI agents can reason, make decisions, discover tools, interact with business data, and perform complex actions autonomously. Nathan discusses why Copilot Studio is becoming one of the most important platforms in the Microsoft ecosystem and how natural language is rapidly replacing traditional development approaches.Key topics include: * Low-code vs Agentic AI * Copilot Studio evolution * Microsoft Power Platform innovation * AI-powered business applications * Prompt engineering and AI workflows * Future skills for Microsoft professionals WHAT IS DATAVERSE MCP AND WHY DOES IT MATTER? One of the most valuable parts of the discussion focuses on Dataverse MCP (Model Context Protocol), one of Microsoft's most exciting new technologies for enterprise AI solutions.Nathan explains why MCP should not simply be viewed as "the new API." Instead, MCP enables AI agents to understand context, discover capabilities, reason about data, and dynamically select the tools needed to complete a task. Using a memorable comparison, Nathan describes APIs as Spotify playlists while MCP acts more like a live DJ that continuously adapts to the environment and audience.The conversation explores how Dataverse MCP allows AI agents to interact with Microsoft Dataverse, Dynamics 365, customer records, business processes, opportunities, support cases, and enterprise data without requiring the extensive custom integrations organizations traditionally needed.Key takeaways: * Understanding Model Context Protocol (MCP) * MCP vs traditional APIs * Context-aware enterprise AI * Dataverse integration strategies * Intelligent tool discovery * Microsoft AI architecture DATAVERSE: MORE THAN JUST A DATABASE Many organizations still view Dataverse as simply another database. Nathan explains why this perspective misses the bigger picture.Dataverse serves as Microsoft's intelligent business data platform, providing a unified data layer that connects Power Apps, Power Automate, Dynamics 365, Copilot Studio, Microsoft 365 Copilot, and AI agents. Instead of managing disconnected systems and endless integrations, organizations can leverage Dataverse as a common data foundation that simplifies development, governance, security, and AI adoption.The discussion highlights why Dataverse is becoming increasingly important as organizations deploy AI agents that require access to customer data, operational information, business processes, and enterprise knowledge.Topics covered: * Dataverse architecture * Unified business data platforms * Dynamics 365 integration * Enterprise data management * AI-ready data foundations * Modern application development BUSINESS SKILLS: THE NEXT GENERATION OF ENTERPRISE AUTOMATION Nathan also introduces Dataverse Business Skills, one of the most promising emerging capabilities for Copilot Studio and AI agents.Business Skills allow organizations to define reusable business logic and procedures that agents can discover and execute dynamically. Rather than modifying, testing, and redeploying entire agents every time a process changes, organizations can update individual skills that become immediately available to AI systems through Dataverse MCP.This creates a more scalable architecture for enterprise AI, reduces deployment complexity, and enables business teams to contribute directly to automation initiatives.Key discussion points: * What Business Skills are * Microservices for AI agents * Scalable enterprise automation * Business-user driven AI development * Dynamic agent capabilities * Future Microsoft AI architecture GOVERNANCE, COMPLIANCE AND SHADOW AI No AI discussion is complete without addressing governance, compliance, security, and risk management.Mirko and Nathan discuss the growing challenge of Shadow AI, where employees use external AI tools such as ChatGPT, Claude, Perplexity, and other generative AI platforms outside corporate governance frameworks. Rather than attempting to block AI adoption completely, Nathan argues that organizations should focus on education, visibility, governance, and responsible AI implementation.The conversation also explores Microsoft's growing investments in AI governance, agent management, security controls, compliance frameworks, and enterprise oversight capabilities.Key takeaways: * AI governance best practices * Managing Shadow AI * Enterprise AI security * Responsible AI adoption * Microsoft governance capabilities * Compliance in the age of AI THE FUTURE OF COPILOT STUDIO AND MICROSOFT AI Looking toward the future, Nathan predicts that organizations will eventually operate hundreds or even thousands of specialized AI agents. These agents will handle repetitive work, automate business processes, surface insights, manage customer interactions, and support employees across departments.The discussion explores how Copilot Studio, Microsoft 365 Copilot, Dataverse MCP, Business Skills, AI orchestration, and emerging technologies from Microsoft Build are creating the foundation for this future. Nathan also shares why he believes human expertise, creativity, relationships, and strategic thinking will become even more valuable as AI takes over routine administrative tasks.Whether you are a Microsoft 365 administrator, Dynamics 365 consultant, Power Platform developer, Solution Architect, AI strategist, business leader, or technology enthusiast, this episode offers practical insights into the technologies that will define the next generation of enterprise software. IN THIS EPISODE YOU'LL LEARN * How Copilot Studio is transforming enterprise AI * Why Dataverse MCP is a game changer for business applications * The role of Business Skills in scalable agent architectures * How Agentic AI differs from traditional automation * Why governance and Shadow AI matter more than ever * The future of Microsoft 365 Copilot and AI agents * How organizations can prepare for an AI-first future * Why Dataverse is becoming the foundation of Microsoft's AI strategy * Emerging trends from Microsoft Build * Skills Microsoft professionals should focus on next 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].

I går57 min
episode The SLM Revolution: How Small Models Are Fixing Copilot’s Biggest Flaw cover

The SLM Revolution: How Small Models Are Fixing Copilot’s Biggest Flaw

What if Microsoft's biggest AI breakthrough isn't a larger model?What if the future of Microsoft Copilot, enterprise AI, and Microsoft 365 productivity isn't powered by trillion-parameter frontier models at all?What if the real innovation is happening in the opposite direction?In this deep-dive episode, we explore one of the most important shifts happening in artificial intelligence today: the rise of Small Language Models (SLMs) and why they may be the key to solving Copilot's most significant architectural challenge.For years, the AI industry operated under a simple assumption: bigger models are better models. More parameters meant more intelligence, more capability, and better outcomes. That assumption helped fuel the rise of GPT-4, Claude, Gemini, and other frontier AI systems that transformed how organizations think about productivity and automation.But enterprise reality is revealing a different story.Most Microsoft 365 users are not asking AI to solve theoretical physics problems or write novels. They're summarizing email threads in Outlook. They're extracting action items from Teams meetings. They're generating document summaries in Word. They're classifying files in SharePoint. They're asking simple questions about company information, policies, procedures, and project documentation.These are narrow, repetitive, high-volume tasks.And increasingly, organizations are discovering that using the world's largest AI models for every single request may be the wrong architecture entirely.In this episode, we unpack why enterprises are rethinking their AI strategy and why Small Language Models are emerging as one of the most important developments in the Microsoft ecosystem. WHY COPILOT'S BIGGEST PROBLEM ISN'T THE LICENSE PRICE When organizations evaluate Microsoft 365 Copilot, most discussions begin with licensing costs.The conversation typically focuses on per-user pricing, deployment budgets, and ROI calculations.But in reality, the license is only the beginning.Behind every Copilot interaction sits an AI inference engine processing prompts, generating responses, and consuming computational resources. Every email summary, every meeting recap, every generated draft, and every document analysis triggers an AI workload.Multiply those requests across thousands of employees, hundreds of departments, and millions of interactions each month, and a hidden cost begins to emerge.The challenge isn't simply licensing.It's architecture.We explore how large-scale AI deployments create operational costs that most organizations fail to anticipate and why enterprises are beginning to adopt model portfolios rather than relying on a single AI model for every workload. THE HIDDEN COST OF FRONTIER MODELS Enterprise AI spending isn't just growing.It's becoming unpredictable.As AI adoption increases, organizations are seeing inference costs, compute requirements, and cloud consumption expand far beyond original expectations.In this episode, we examine: * Why AI costs scale differently than traditional software licensing * The economics of AI inference and token consumption * How routine Microsoft 365 tasks create massive AI workloads * Why enterprise AI budgets are becoming increasingly difficult to forecast * How organizations are reducing costs through hybrid model strategies You'll learn why some enterprises are achieving dramatic cost reductions by routing routine tasks to smaller models while reserving premium models for high-complexity scenarios. THE LATENCY PROBLEM NOBODY TALKS ABOUT Cost is only part of the story.Speed matters.Users expect AI to feel instant.If an employee clicks "Summarize this email thread" and waits several seconds for a response, the experience quickly becomes frustrating. When delays become common, adoption slows. When adoption slows, ROI disappears.We explore how Small Language Models dramatically reduce latency and why response times measured in milliseconds rather than seconds can fundamentally change how employees interact with AI-powered tools.The discussion covers: * User adoption psychology * Real-world Copilot usage patterns * Why latency kills productivity gains * Edge AI deployments * Local inference strategies * The relationship between performance and user trust THE DATA SOVEREIGNTY CHALLENGE For many organizations, the biggest concern isn't cost or performance.It's control.Where is your data actually processed?Who has access to it?What happens when AI workloads cross geographic boundaries?What does compliance look like in a world where AI systems may process information across multiple regions and multiple providers?This episode takes a detailed look at: * Microsoft Copilot Flex Routing * EU Data Boundary considerations * GDPR implications for AI workloads * Cross-border processing concerns * Sovereign AI strategies * Regulatory requirements in healthcare, finance, government, and critical infrastructure We explain why data sovereignty is rapidly becoming one of the most important conversations in enterprise AI and why local AI processing is gaining momentum across regulated industries. INTRODUCING MICROSOFT'S PHI FAMILY Microsoft isn't simply talking about Small Language Models.They're building them.The Phi family represents Microsoft's strategic investment in efficient, highly capable AI models designed for real-world deployment scenarios.We take a deep dive into: * Phi-3 Mini * Phi-3 Small * Phi-3 Medium * Phi-3.5 * Phi-3 Vision * Mixture-of-Experts architectures * On-device AI * Edge AI workloads You'll discover why these models are attracting so much attention and how Microsoft is positioning them as a core component of the future AI stack. CAN SMALL MODELS REALLY COMPETE? One of the biggest misconceptions in AI is that smaller models automatically mean lower quality.The reality is far more nuanced.In this episode, we examine benchmark results, real-world workloads, enterprise deployment scenarios, and the growing evidence that Small Language Models can outperform expectations when applied to the right tasks.We discuss: * MMLU performance * Instruction-following benchmarks * Summarization workloads * Document processing * Email drafting * Meeting recap generation * Knowledge retrieval * Enterprise search The goal isn't replacing frontier models.The goal is using the right model for the right job.AZURE LOCAL AND THE SOVEREIGN AI FUTUREAzure Local may become one of the most important platforms in Microsoft's AI strategy.As organizations demand greater control over where AI runs and how data is processed, local AI infrastructure is becoming increasingly attractive.We explore how Azure Local enables organizations to: * Run AI workloads closer to their data * Reduce latency * Improve compliance * Support disconnected environments * Enable edge AI deployments * Build sovereign AI architectures Whether you're operating in manufacturing, healthcare, government, defense, finance, or energy, this section provides practical insights into the future of local AI infrastructure. THE RISE OF MODEL ROUTING Perhaps the most important idea discussed in this episode is the concept of model routing.The future isn't GPT-4 versus Phi.The future is GPT-4 and Phi working together.Instead of asking which model is best, organizations are beginning to ask which model is best for each specific task.This shift introduces a new architectural pattern where: * Small models handle routine requests * Large models handle complex reasoning * Routing engines determine the optimal destination * Costs decrease * Performance improves * Governance becomes easier We explain why many experts believe this model portfolio approach represents the next evolution of enterprise AI. BUILDING A MICROSOFT 365 AI STRATEGY Technology alone is not enough.Successful AI adoption requires governance, architecture, operating models, security frameworks, and long-term planning.In the final section, we outline practical guidance for IT leaders, architects, Microsoft 365 administrators, security professionals, and business decision-makers who want to prepare for the next generation of AI-powered workplaces.You'll learn how to: * Identify suitable SLM workloads * Build hybrid AI architectures * Evaluate deployment options * Improve governance controls * Reduce AI operating costs * Increase employee adoption * Prepare for Microsoft's evolving AI roadmap 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].

I går1 h 27 min
episode Mastering ALM for Power Platform: From Citizen Development to Enterprise Delivery with Parvez Ghumra [MVP] cover

Mastering ALM for Power Platform: From Citizen Development to Enterprise Delivery with Parvez Ghumra [MVP]

What separates successful Power Platform implementations from those that become difficult to manage, impossible to scale, and increasingly risky to maintain?In this in-depth episode of the M365 Podcast, host Mirko Peters welcomes Microsoft MVP Parvez Ghumra for a comprehensive discussion on Application Lifecycle Management (ALM), enterprise delivery, governance, DevOps, CI/CD, and the future of Microsoft Power Platform development. With more than a decade of experience helping organizations implement enterprise-grade Power Platform, Dynamics 365, and Azure solutions, Parvez shares practical lessons learned from real-world projects spanning government organizations, universities, enterprises, and global businesses.As Microsoft continues to position Power Platform as the leading low-code platform for digital transformation, organizations face a growing challenge: how do you empower citizen developers while maintaining the governance, security, quality, and operational standards required by enterprise environments? This episode explores exactly that challenge and provides listeners with practical guidance for scaling Power Platform responsibly. THE JOURNEY FROM TRADITIONAL SOFTWARE ENGINEERING TO LOW-CODE DEVELOPMENT Before becoming one of the leading voices in Power Platform ALM, Parvez began his career in traditional software engineering. During the conversation, he shares his journey through ASP.NET development, C#, SQL Server, enterprise application architecture, and Dynamics CRM before eventually becoming a specialist in Application Lifecycle Management and enterprise Power Platform delivery.Parvez explains why traditional software engineering principles remain just as relevant today as they were twenty years ago. While low-code and no-code platforms simplify development, the underlying concepts of architecture, source control, deployment automation, testing, security, scalability, and governance have not disappeared. Instead, they have become even more important as organizations accelerate development and enable larger numbers of makers to build business solutions.Listeners will discover why understanding software engineering fundamentals can significantly improve the quality, reliability, and scalability of Power Platform solutions. WHAT IS APPLICATION LIFECYCLE MANAGEMENT (ALM) AND WHY DOES IT MATTER? Application Lifecycle Management is often misunderstood as simply moving solutions between environments. In reality, ALM represents a complete framework for managing software from initial development through testing, deployment, governance, maintenance, and ongoing improvement.Parvez breaks down ALM into practical concepts that both technical and non-technical audiences can understand. He explains how source control, deployment pipelines, testing environments, automated releases, rollback capabilities, and governance frameworks work together to create predictable and reliable software delivery processes.The conversation explores why organizations that neglect ALM often experience: * Deployment failures * Uncontrolled solution growth * Security risks * Production outages * Poor collaboration between teams * Lack of visibility into changes * Difficult maintenance and support challenges At the same time, listeners learn how a well-designed ALM strategy creates confidence, consistency, repeatability, and quality across the entire software delivery lifecycle. UNDERSTANDING ENVIRONMENTS, SOLUTIONS, AND SOURCE CONTROL One of the most valuable sections of the episode focuses on explaining core Power Platform concepts in language that business leaders and stakeholders can understand.Parvez provides practical analogies for development environments, testing environments, and production environments, helping listeners understand why separation between these stages is critical. He also explains the true purpose of Power Platform solutions and why they are much more than simple containers for transporting customizations.The discussion covers: * Development environments * Test environments * Production environments * Managed solutions * Unmanaged solutions * Solution dependencies * Solution layering * Publishers and managed properties * Source control integration * Version management * Release management Whether you are a Power Platform maker, architect, administrator, or business sponsor, these concepts provide a foundation for building scalable and maintainable solutions. WHEN SHOULD ORGANIZATIONS IMPLEMENT ALM? Many organizations ask the same question: Should we think about ALM from day one, or can it wait until later?Parvez provides a nuanced answer based on years of consulting experience. For enterprise-scale projects supporting thousands of users, he argues that ALM should be considered non-negotiable and should be designed before development begins. For smaller initiatives and proof-of-concept projects, organizations may choose a lighter approach initially while still planning for future growth.The discussion highlights how organizations can evolve their ALM maturity over time without introducing unnecessary complexity too early.Listeners gain valuable guidance on: * ALM maturity models * Enterprise adoption strategies * Governance planning * Development team structures * Maker enablement * Scaling low-code solutions * Enterprise architecture considerations IS POWER PLATFORM READY FOR ENTERPRISE SOFTWARE DELIVERY? Despite being widely known as a low-code platform, Power Platform has evolved into a sophisticated enterprise application platform capable of supporting mission-critical business workloads.Parvez discusses how Power Platform has matured through its Dynamics CRM heritage and explains how capabilities such as Dataverse, Model-Driven Apps, enterprise integrations, Azure services, and advanced governance features make enterprise-grade delivery possible.The conversation explores how organizations are using Power Platform for: * Enterprise business applications * Process automation * Customer engagement solutions * Employee experience platforms * Data management * AI-powered business processes * Large-scale digital transformation initiatives Listeners gain a realistic perspective on both the strengths and limitations of the platform when deployed at scale. THE EVOLUTION OF CI/CD FOR POWER PLATFORM Continuous Integration and Continuous Delivery have undergone significant transformation within the Power Platform ecosystem.Parvez explains how the early days of ALM required deep expertise in Azure DevOps, source control systems, and deployment tooling. He contrasts that with today's landscape, where features such as Power Platform Pipelines, Native Git Integration, GitHub Actions, and the Power Platform CLI have dramatically lowered the barrier to entry.The discussion explores: * CI/CD best practices * Deployment automation * Build pipelines * Release pipelines * Power Platform CLI * Git repositories * Automated testing * Quality gates * Build artifacts * Enterprise deployment strategies Listeners learn how modern tooling is making professional software delivery practices accessible to both makers and experienced development teams. AZURE DEVOPS VS GITHUB ACTIONS: WHICH SHOULD YOU CHOOSE? One of the most practical sections of the episode focuses on comparing Azure DevOps and GitHub Actions.Having implemented enterprise ALM solutions using both platforms, Parvez provides a balanced comparison of their strengths, weaknesses, and ideal use cases.Topics covered include: * Azure DevOps Boards * Work item management * GitHub Actions workflows * Source control strategies * Enterprise DevOps practices * Integration with Jira * Pipeline flexibility * Developer productivity * GitHub Copilot integration * Future Microsoft investments As Microsoft continues to expand GitHub's capabilities and introduces AI-powered development experiences, understanding these differences becomes increasingly important for technology leaders and architects. REAL-WORLD ENTERPRISE ALM SUCCESS STORIES Parvez shares practical examples from customer projects where organizations successfully transformed manual deployment processes into modern, automated ALM solutions.These stories illustrate the measurable benefits organizations can achieve through proper implementation of: * Source control * Deployment automation * Environment management * Governance frameworks * Release pipelines * Automated quality controls * Team collaboration processes The discussion demonstrates how even organizations with limited DevOps experience can successfully adopt enterprise-grade delivery practices. GOVERNANCE IN THE AGE OF CITIZEN DEVELOPMENT As Power Platform adoption grows, governance becomes one of the most important considerations for organizations.The conversation explores how businesses can balance innovation with control while empowering makers to build solutions safely and responsibly.Parvez discusses: * Environment strategies * Security models * Microsoft Entra ID integration * Data protection * Access control * Power Platform governance * Center of Excellence evolution 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].

9. juni 202652 min