Notes from the trenches of real projects. What worked, what didn't, and why — no marketing spin.
Microsoft rebuilt Copilot Studio at Build 2026: a four-surface agent model, Skills as Markdown, a Memory surface, a new agentic orchestrator, a new workflow designer, and convergence with Microsoft Foundry. What changed, what it means for the patterns in Parts 1 and 2, and how to think about the move.
Microsoft rebuilt Copilot Studio at Build 2026: a four-surface agent model, Skills as Markdown, a Memory surface, a new agentic orchestrator, a new workflow designer, and convergence with Microsoft Foundry. What changed, what it means for the patterns in Parts 1 and 2, and how to think about the move.
Four end-to-end scenarios on different orchestration patterns, a starter MCP server inventory, and the ten anti-patterns that recur in production Copilot Studio deployments.
A long-form, end-to-end foundation for building multi-agent systems in Microsoft Copilot Studio — when to split, the five surfaces, four patterns, and the two open standards (MCP and A2A) that make the whole thing composable.
How Teams Phone Agent's out-of-the-box voice experience and custom Copilot Studio voice agents bring conversational AI to Microsoft Teams Phone — capabilities, call-flow design, setup, gating, and consumption billing in the Frontier preview.
A practitioner's reference for Power Platform core, Copilot Studio, Dataverse, Dynamics 365 Contact Center, and Dynamics 365 Customer Service.
Part 2 of a two-part guide to managing and securing Power Platform environments within Microsoft 365 — Copilot Studio governance, agent authentication, ALM and pipelines, solution checker, licensing, and change management.
Microsoft MVP & MCT | Low Code Hacker | Copilot, Copilot Studio, Power Platform & Azure Architect
I’m a Microsoft MVP focused on agentic AI, intelligent agents, and enterprise AI solutions. Using Microsoft Copilot Studio and Azure AI Foundry, I design and build systems that help people and organizations work smarter. This blog is a collection of field notes, practical insights, and real-world experiences—from architecture and orchestration patterns to lessons learned along the way. Your feedback is always welcome—let’s continue the conversation.
