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/deploy/references/container-deploy.md

Container Deploy Precheck

Complete every applicable check before running azd deploy.

1. Select and configure the build path

Follow the existing docker.remoteBuild configuration. If it is not set, default to remote build without asking. Use local build when the user explicitly requires the image to be built locally.

| Build path | When to use | azure.yaml | |------------|-------------|--------------| | Remote build | Existing configuration selects it, or no build path is configured | Under the service's docker block, set remoteBuild: true. | | Local build | Existing configuration selects it, or the user explicitly requires local build | Under the service's docker block, set remoteBuild: false. | | Pre-built image | The user supplies an existing image | Set the service-level image to a fully qualified image reference. Under the service's docker block, set imagePassthrough: true and remoteBuild: false. |

2. Validate azure.yaml

  • The intended azure.ai.agent service is clearly identified.
  • codeConfiguration: is absent and language: docker is present.
  • The selected build path matches the docker or image configuration.
  • Container CPU, memory, and declared protocols are supported.
  • azd env get-values shows the intended project, model deployment, and ACR. For an existing ACR, its name, endpoint, and resource ID identify the same registry.

3. Validate the container files and code

For remote and local builds:

  • The Dockerfile uses the correct build context, copies every required file, installs dependencies, and starts the agent server on port 8088.
  • .dockerignore excludes .env, credentials, virtual environments, caches, and other local-only files without excluding required application files.
  • The entry point and dependency files match the application source.

4. Validate the ACR connection

If azd provision created or connected the ACR, continue after provision succeeds. For an existing ACR, verify that the Foundry project has a Container Registry connection targeting it; otherwise, configure and provision the connection before deploy.