What is Toolbox in Microsoft Foundry?
Toolbox provides a centralized way to manage and share tools in Microsoft Foundry. Without such a layer, agents connect directly to tools, APIs, MCP servers and other services, requiring separate configuration, authentication and governance for each implementation. As the number of agents grows, this leads to duplicated effort, inconsistent behavior, fragile production deployments and additional operational overhead.
With Toolbox, you define a curated set of tools once and expose them through a single MCP-compatible endpoint that agents consume across frameworks and runtimes. Credentials, governance, observability and access control are managed centrally, and tool implementations can be updated without changing agent code.
Toolbox is in public preview; the tool search and skills features are explicitly marked as preview in the Microsoft documentation.
Core Features
One endpoint for all tools: The agent connects to a single MCP-compatible endpoint and discovers every tool at runtime. Tools can be added, removed or reconfigured without changing agent code or redeploying.
Centralized authentication: The toolbox handles credential injection, token refresh and policy enforcement at runtime using Microsoft Entra ID and OAuth identity passthrough, so consuming agents don’t manage per-tool credentials.
Governance by default: Guardrails in the sense of Responsible AI policies apply to tool inputs and outputs and are enforced at the toolbox level.
Versioning: Create and test a new toolbox version, then promote it to default. All consuming agents pick up the version automatically.
Tool search and skills (preview): Tool search keeps large tool collections manageable; skills package multi-step workflows as versioned, immutable capabilities.
Typical Use Cases
Many agents, shared tools: Microsoft describes an onboarding agent that combines a knowledge base, REST API, long-running agent, skills and an MCP server. Without central management, every additional agent re-implements the same integrations.
Central secret management: Instead of equipping every agent with its own credentials, the toolbox manages credentials and token refresh.
Consistent governance: Guardrails and access controls apply uniformly across all agents that use a toolbox.
Scaling tool catalogs: Toolboxes can hold hundreds of tools without flooding the model’s context window.
Benefits
- Reuse of tools across agents, frameworks and runtimes
- Significantly reduced configuration and secret handling per agent
- Consistent security and operational practices through toolbox-level guardrails
- Tool updates without changing or redeploying agents
- Manageable token cost and better tool selection with large tool collections
Integration with innFactory
As a Microsoft Solutions Partner, innFactory supports you in building agent platforms on Microsoft Foundry: scoping and curating toolboxes, connecting your own MCP servers and OpenAPI services, designing governance with guardrails, and defining versioning and promotion processes.
Contact us for a no-obligation consultation on Toolbox in Microsoft Foundry and agent architectures on Azure.
Typical Use Cases
Technical Specifications
Frequently Asked Questions
What is a toolbox in Microsoft Foundry?
A toolbox is a central management unit for agent tools in Microsoft Foundry. You define a curated set of tools once and expose them through a single MCP-compatible endpoint that agents can consume across frameworks and runtimes.
Can only Foundry agents use a toolbox?
No. Toolboxes are created and managed in Microsoft Foundry but aren't limited to Foundry-based agents. Any MCP-compatible runtime or client can use a toolbox, including custom agents built with Microsoft Agent Framework, LangGraph or your own code.
What problem does tool search solve?
As the number of tools grows, token cost increases, context window capacity shrinks and tool selection accuracy declines. Tool search therefore hides tools by default and exposes only two meta-tools: tool_search to find relevant tools and call_tool to invoke them. Critical tools can be pinned and frequently used tools auto-pinned. Microsoft marks tool search as preview.
What is the difference between tools and skills?
Tools define what an agent can do. Skills define how it performs a task: they package reusable, multi-step workflows as capabilities that agents invoke like any other tool. Skills are versioned and immutable, and agents discover and load them automatically through MCP resources at startup. Microsoft marks skills as preview.
How does versioning work?
You create a new toolbox version, test it and then promote it to default. Every agent that points to the toolbox picks up the promoted version automatically, with no code changes and no redeployment.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of Azure (official documentation). This page does not represent an offer by Azure.
