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

resource/private-network/references/custom-template-adaptation.md

Custom Template Adaptation

For the EXTEND path — when the user has existing Bicep or Terraform templates.

Instructions

  1. Read the user's existing template files. Understand the resource graph: what's defined, how resources reference each other, what naming conventions are used.

  2. Analyze the template against the user's requirements (from intake.md) and the Foundry private networking documentation validated in the intake step. Identify:

    • Resources already present and correctly configured
    • Resources present but misconfigured (wrong settings, missing properties)
    • Resources missing entirely
    • Dependency or wiring issues (e.g., PEs referencing wrong subnet, DNS zones not linked)
  3. Present findings to the user as a gap analysis table: resource, status (✅ present / ⚠️ misconfigured / ❌ missing), and what needs to change. Include any issues found.

  4. Propose an end-to-end plan to address all gaps — ordered by dependency. Explain what will be added, what will be modified, and why. Never overwrite existing modules — add alongside and reference existing resources.

  5. Wait for user approval before making any changes.

  6. Implement the approved changes. After implementation, the flow continues to Step 4 (Pre-Deployment Validation) in the main workflow.

Retry Safety

⚠️ If a deployment fails after the capability host step starts, Azure Container Apps leaves a legionservicelink service association on the agent subnet that cannot be removed. On retry, use a new subnet or new VNet — never reuse the same agent subnet.