Stop wiring infrastructure, start building agents @MicrosoftDeveloper
Stop wiring infrastructure, start building agents  @MicrosoftDeveloper
Uploaded October 2026 | Updated November 2026, 1 day ago
Full episode: youtu.be/AMxLLFeUyRM
Foundry portal: https://aka.ms/foundry-portal

Introducing the Microsoft Copilot harness! Every agent project seems to start the same way containers, scaling, state, auth. Most of the time, you don't need any of it. You rebuild Sparkles as a prompt agent: a model, instructions, and the Cupcake Store MCP tools, defined once and versioned in Microsoft Foundry. No container, no server, no pipeline. Then you hit the edge where a prompt agent isn't enough, such as custom orchestration or your own framework, and move the same agent to a hosted agent. Callers still invoke it by name. By the end, you'll know which one to reach for first, and when to switch.

#copilot #harness #foundry #microsoft #ai
Stop wiring infrastructure, start building agentsWhat if you could customize your agent from a Chat Window🌎 Expanding Your Airspace | Extend your Copilot with Plugins, Work IQ Dev Tools and more!What was announced for developers on Windows at Build 2026?Your first AI agent is only a few lines of Python away.NET 11 Performance Update, Azure Resiliency & Multicloud DatabasesBuilding a Multi-Agent Workflow in Microsoft Fabric | DEM362The End of Index Maintenance? | Data ExposedInside Azures DDoS Defense | Behind the CodeKEYNOTE: From Copilot to Flight CaptainWhen prompting is not enough for your agentSecure AI Agents in Azure: AI Gateway, Tools, and Trust
Microsoft Developer |

Stop wiring infrastructure, start building agents

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER