AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

microsoft-foundry

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent, managed harness agent, Copilot harness, voice agent, create/update/invoke/evaluate agent, add tool to agent, agent insights, batch/continuous eval, continuous monitoring, agent CI/CD, optimize/improve prompt, optimize agent instructions, Agent Optimizer, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare).

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--microsoft-foundry at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 151

foundry-agent/create/references/tools/managed-harness-agent/tool-toolbox.md

Toolbox

Attach an existing Foundry Toolbox to a Managed Harness Agent through an authenticated direct MCP tool. Manage the Toolbox and connection separately; the Agent consumes their published values.

Resolve the exact Toolbox version

Create or update the Toolbox only when explicitly requested, following Foundry Toolbox. Resolve the intended version's exact MCP endpoint:

azd ai toolbox show <toolbox-name> \
  --version <version> \
  --project-endpoint "<project-endpoint>" \
  --output json

Use the returned endpoint, including /versions/<version>/mcp?api-version=v1. Do not substitute a default or unversioned endpoint.

Create or reuse the authentication connection

The Toolbox endpoint requires a matching project connection:

  • category/kind: RemoteTool / remote-tool
  • auth type: UserEntraToken / user-entra-token
  • audience: https://ai.azure.com
  • target: exactly the versioned MCP endpoint
  • metadata: type=toolbox_MCP, Toolbox name, and Toolbox version

The released CLI supports this shape:

azd ai connection create <connection-name> \
  --kind remote-tool \
  --target "<versioned-toolbox-mcp-endpoint>" \
  --auth-type user-entra-token \
  --audience https://ai.azure.com \
  --metadata type=toolbox_MCP \
  --metadata toolboxName=<toolbox-name> \
  --metadata toolboxVersion=<version> \
  --project-endpoint "<project-endpoint>"

Reuse an existing connection only when all fields match. Do not overwrite or repoint a connection used by another Toolbox version; create a distinct connection instead.

Attach the Toolbox

Use the connection's short name as project_connection_id:

tools:
  - type: mcp
    server_label: <toolbox-name>
    server_url: <versioned-toolbox-mcp-endpoint>
    project_connection_id: <connection-name>
    require_approval: always

The connection target and server_url must match exactly. Keep require_approval: always unless the user explicitly chooses a different policy. Do not fall back to a connectionless Toolbox MCP entry.

This is separate from generic MCP authoring.