{"podcast":{"title":"M365.FM a Microsoft MVP Podcast by Mirko Peters","slug":"m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214","podcast_index_feed_id":7311214,"rss_url":"https://www.spreaker.com/show/6704921/episodes/feed","website_url":"https://www.m365.fm","image_url":"https://d3wo5wojvuv7l.cloudfront.net/t_rss_itunes_square_1400/images.spreaker.com/original/dcd2a8cc504197846a71af23bbeb0707.jpg","author":"Mirko Peters - Microsoft 365, Teams, SharePoint, and Copilot for IT Pros","episode_count":989,"summary":"M365.FM is a podcast about Microsoft 365, Microsoft Copilot, AI, Modern Work, security, governance, Power Platform, Azure, and the technologies shaping the future of work.Hosted by Microsoft MVP Mirko Peters, M365.FM brings together Microsoft MVPs, Microsoft employees, product experts, architects, developers, and community leaders from around the world.Each episode goes beyond announcements and hype to explore what Microsoft technologies mean in practice. From Microsoft 365 Copilot and AI agents to Teams, SharePoint, Power Platform, Microsoft Fabric, Entra, Purview, security, governance, adoption, and automation, M365.FM focuses on real-world experience, implementation, strategy, and lessons learned.Expect expert interviews, technical deep dives, practical explainers, and conversations with people building, implementing, and shaping the Microsoft ecosystem.If you work with Microsoft 365, Copilot, AI, Modern Work, or the Microsoft Cloud, M365.FM helps you understand what matters, what works, and what is coming next.Hosted by Mirko Peters, Microsoft MVP. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/supp…","last_synced_at":"2026-09-17T20:22:41.104701+00:00","page_url":"https://stenobird.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214"},"episode":{"title":"THE DEATH OF THE PROXY: Architecting Dataverse for the Agent Fabric","slug":"the-death-of-the-proxy-architecting-dataverse-for-the-agent-fabric","published_at":"2026-07-26T07:00:03+00:00","page_url":"https://stenobird.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214/the-death-of-the-proxy-architecting-dataverse-for-the-agent-fabric","show_page_url":"https://stenobird.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214","url":"https://www.spreaker.com/episode/the-death-of-the-proxy-architecting-dataverse-for-the-agent-fabric--73163763","audio_url":"https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/73163763/the_death_of_the_proxy_architecting_dataverse_for_the_agent_fabric.mp3","summary":"For years, Microsoft's recommended architecture for connecting AI assistants like Claude Desktop to Dataverse relied on a local STDIO proxy. It was simple, easy to install, and perfectly suited for individual developers experimenting with AI-powered workflows. But enterprise AI has evolved. Organizations are no longer connecting a single assistant to a single application. They're connecting hundreds—or even thousands—of AI agents across multiple clients, platforms, and business systems. That architectural shift changes everything. This episode explains why the traditional proxy model has reached its limits, why Streamable HTTP fundamentally changes enterprise AI integration, and how Dataverse is evolving from the database behind Power Apps into the governed data backbone for the entire Agent Fabric. WHY THE STDIO PROXY WAS CREATED The original STDIO proxy solved a very specific problem. Early MCP clients like Claude Desktop needed a simple way to communicate with cloud services while running locally on a developer's machine. Instead of exposing an internet-facing endpoint, developers launched a local process that translated communication between the AI client and Dataverse. The advantages were obvious: Simple installation No HTTP server required No certificates Minimal infrastructure Isolated execution per user For individual developers, this architecture worked remarkably well. Every proxy was independent, failures affected only one user, and deployment required little more than installing a small application. The problem wasn't that the proxy stopped working. The problem was that enterprise AI completely outgrew the assumptions behind it. THE PROXY SCALING PROBLEM The proxy architecture assumes one developer. Modern enterprises operate very differently. Instead of on…","meta_description":"For years, Microsoft's recommended architecture for connecting AI assistants like Claude Desktop to Dataverse relied on a local STDIO proxy. It was simple…","key_points":[],"chapters":[],"topics":[],"duration_seconds":3583,"processing_state":"not_requested","actions":[{"name":"request_transcript","method":"POST","url":"https://stenobird.com/v1/public/podcasts/m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214/episodes/the-death-of-the-proxy-architecting-dataverse-for-the-agent-fabric/transcription-requests","description":"Idempotently request low-priority transcript generation for this episode."},{"name":"read_markdown","method":"GET","url":"https://stenobird.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214/the-death-of-the-proxy-architecting-dataverse-for-the-agent-fabric.md","description":"Read the agent-friendly Markdown representation of this episode resource."}]}}