<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Toolboxes on Brian Swiger</title><link>https://www.mightybs.com/tags/toolboxes/</link><description>Recent content in Toolboxes on Brian Swiger</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Brian Swiger</copyright><lastBuildDate>Mon, 27 Apr 2026 17:43:00 -0400</lastBuildDate><atom:link href="https://www.mightybs.com/tags/toolboxes/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure AI Foundry Toolboxes: Define Your Agent Tools Once, Use Them Everywhere</title><link>https://www.mightybs.com/posts/2026-04-27-azure-ai-foundry-toolboxes-define-your-agent-tools-once-use-them-everywhere/</link><pubDate>Mon, 27 Apr 2026 17:43:00 -0400</pubDate><guid>https://www.mightybs.com/posts/2026-04-27-azure-ai-foundry-toolboxes-define-your-agent-tools-once-use-them-everywhere/</guid><description>&lt;p>As organizations scale their AI agent deployments, tool management becomes a bottleneck. Every agent wires its own tools, manages its own credentials, and duplicates integration code. Azure AI Foundry Toolboxes solve this by letting teams define tools once, manage authentication centrally, and expose everything through a single MCP-compatible endpoint that any agent framework can consume.&lt;/p>
&lt;p>Now in public preview, Toolboxes support built-in tools like Web Search, Code Interpreter, and Azure AI Search, plus open protocols like MCP, A2A, and OpenAPI. Best of all, they are framework-agnostic: Microsoft Agent Framework, LangGraph, GitHub Copilot SDK, and custom agents can all consume the same toolbox.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://www.mightybs.com/posts/2026-04-27-azure-ai-foundry-toolboxes-define-your-agent-tools-once-use-them-everywhere/featured.png"/></item></channel></rss>