Notes from the trenches of real projects. What worked, what didn't, and why — no marketing spin.
Microsoft now hosts the code that Copilot and other AI tools build. For architects, that moves governance from the build tool to the runtime. Here is what that changes, what it does not solve, and what to design before the first AI-built app goes viral.
Microsoft's October 15, 2026 announcement gives Copilot Studio agents their own accounts, shared business process memory, and triggers. I argue that organizations should treat each agent like a service account with a job description and decide early which agents they want to own.
Part two of a short, living series on Copilot and agent costs. Where Microsoft 365 Copilot services, Copilot Studio, and Foundry agents show their costs, which controls stop spending, and how to build chargeback across three admin experiences.
Part one of a short, but living series on what Copilot and agents cost. What the Copilot license costs, how Copilot Credits work, which features use them, and what Microsoft has announced next.
A practitioner's reference for Power Platform core, Copilot Studio, Dataverse, Dynamics 365 Contact Center, and Dynamics 365 Customer Service.
A deep dive into the rebuilt Copilot Studio — its natural-language authoring surface, the new agentic orchestrator, Memory, Microsoft IQ, and the rise of SKILL.md as an open, behavior-as-code pattern for enterprise agents.
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.
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.
