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-openapi.md

OpenAPI

Expose an API through an inline OpenAPI 3.x document. Every callable operation needs an operationId.

Anonymous example:

tools:
  - type: openapi
    openapi:
      name: weather
      description: Weather service
      spec:
        openapi: 3.0.0
        info: { title: Weather, version: 1.0.0 }
        servers: [{ url: https://api.example.com }]
        paths: {}
      auth:
        type: anonymous

Supported auth paths:

| Auth | Configuration | Connection | |---|---|---| | Anonymous | type: anonymous | No | | Project connection | type: connection, connection_id: <name-or-id> | Yes | | Managed identity | type: managed_identity, audience: <resource-uri> | No; grant project identity RBAC |

For API-key authentication, create a connection only when explicitly requested:

azd ai connection create <connection-name> \
  --kind custom-keys \
  --target "https://api.example.com" \
  --custom-key x-api-key="<api-key>" \
  --project-endpoint "<project-endpoint>"

The key name must match the OpenAPI security scheme. Keep secrets out of azure.yaml.

Multiple OpenAPI tools should use distinct openapi.name and info.title values.