Microsoft Foundry pattern: version and deploy Toolboxes separately from agents behind stable endpoints
WirelessLife · x · 2026-11-11
A Microsoft community post by jfolberth lays out a practical pattern for agent tool governance in Microsoft Foundry: a Toolbox is a versioned collection of tools (web search, MCP server tools, third-party apps) exposed through a single MCP-compatible endpoint. The recommendation: define each Toolbox in its own azure.yaml, deploy it separately from project infrastructure and agents, pass environment-specific Bicep outputs through GitHub Actions, and promote changes behind the stable endpoint — so teams reuse approved tools across agents instead of rebuilding integrations (e.g., embedding Web IQ in every Finance agent). Also covers ownership questions for shared tool releases.
More from coding & agent
- Obsidian creator: make models replaceable cogs, don't chase the latest LLM — dSebastien · 2026-11-11
- Matt Pocock's "Home Repo" trick: one repo to run AI agents across many codebases — mattpocockuk · 2026-11-11
- Dev builds full dotnetconf Event Wall in a week with Copilot and Azure — DanWahlin · 2026-11-11
- Claude Code Wipes User's ~/Library: A Space in 'Application Support' Broke xargs Path Handling — PrajwalTomar_ · 2026-11-11
- Demo: training models to read K/V vector breadcrumbs left by other instances — Sauers_ · 2026-11-11
- iMessage agent with 3,000+ tools finds 760 startup jobs for $0.0578 in four calls — socialwithaayan · 2026-11-11