Index of every page on this site: llms.txt
All skills
microsoft avatar

/microsoft-foundry

@0d60658
by microsoftmicrosoft/skills3.2k stars
373
Run it yourself

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).

Use this Skill: https://skilld.dev/gh/microsoft/skills/microsoft-foundry

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

foundry-agentcreatereferencesmanaged-harness-agent.md

≈904 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Managed Harness Agent Authoring

A Microsoft Foundry Managed Harness Agent is a Prompt Agent configured with the Foundry-managed Copilot harness. This skill uses azd to author and deploy it:

services:
  assistant:
    host: azure.ai.agent
    kind: prompt
    name: assistant
    model: gpt-5-mini
    instructions: Help the user.
    harness:
      type: microsoft_copilot_preview

Use REST field names, normally snake_case, inside tools[]. azd strictly validates the harness and Copilot toolset; most other nested tool fields pass through to Foundry.

Compatibility

  • New authoring uses microsoft_copilot_preview and, when declared, microsoft_copilot_toolset_preview.
  • Existing github_copilot_preview and github_copilot_toolset_preview values remain accepted.
  • Preserve the exact harness and toolset discriminator values already present, including mixed existing definitions. Do not migrate them during read, edit, save, redeploy, or revision flows.
  • Author defaultConfig in azure.yaml; azd translates it to REST default_config only at the API boundary.
  • Both discriminator families use Foundry-Features: MicrosoftCopilot=V1Preview. Do not retry with the legacy GitHubCopilot=V1Preview header.

Direct tools

Prefer direct tool definitions unless the user explicitly requests a Toolbox:

tools:
  - type: web_search
  - type: code_interpreter

Read Managed Harness Agent Tools for the supported tools, required fields, connections, and per-tool authoring references.

Toolbox attachment

A Managed Harness Agent prefers direct tools. When the user explicitly requests a Toolbox, manage it separately with azd ai toolbox, create or reuse a matching authenticated project connection, then attach its exact versioned MCP endpoint as a direct tool:

tools:
  - type: mcp
    server_label: research-tools
    server_url: https://<account>.services.ai.azure.com/api/projects/<project>/toolboxes/<toolbox>/versions/<version>/mcp?api-version=v1
    project_connection_id: <toolbox-connection>
    require_approval: always

The connection must be RemoteTool with UserEntraToken, audience https://ai.azure.com, and target exactly equal to server_url. See Toolbox for creation, reuse, metadata, and validation. Do not use connectionless Toolbox MCP.

Skill attachment

Create and version Skills separately with azd ai skill. Reference an existing Foundry Skill by name and immutable version:

skills:
  - name: issue-triage
    version: "3"

For a local Skill, upload it first:

azd ai skill create issue-triage \
  --file ./skills/issue-triage/ \
  --project-endpoint "<project-endpoint>" \
  --output json

Use the returned version in azure.yaml. For updates, run azd ai skill update and replace the pinned version.

Do not declare host: azure.ai.skill in this phase: that would make azd deploy manage the Skill lifecycle.

Validation

After deploy, read the published definition and verify:

  • kind remains prompt.
  • New definitions use microsoft_copilot_preview; existing definitions retain their authored Copilot harness discriminator.
  • Direct tools retain their authored fields.
  • Existing Copilot toolset discriminators remain unchanged.
  • The versioned Toolbox MCP endpoint and matching project_connection_id remain in the direct mcp tool.
  • Skill references retain both name and version.

Managed Harness Agents, ordinary Prompt Agents, and Hosted Agents are not converted in place.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

3 warningstoday4 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill provides a comprehensive suite of tools for managing AI agents and models on Microsoft Foundry. It includes security considerations such as the dynamic execution of user-provided Python scripts for model evaluation and the processing of production traces for dataset creation. These features are aligned with the skill's primary purpose and include appropriate user warnings and human-in-the-loop review steps to mitigate risk. See the detailed analysis for additional context.

  • Sockettoday

    2 alerts: gptSecurity, gptAnomaly

  • Snyktoday

    Risk: MEDIUM · 2 issues

  • Runlayer9mo

    36/36 files flagged

Signed by skilld at 0d60658. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 days ago
metadata
{
  "author": "Microsoft",
  "version": "1.2.36"
}

README badge

README badge for microsoft/skills/microsoft-foundry