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/prompt-agent/tool-work-iq.md

Tool — Work IQ (preview)

Connect an agent to the user's Microsoft 365 work context — email, meetings, files, chats — through Work IQ. Work IQ runs as an A2A peer; every request runs in the context of the signed-in user and honors all Microsoft 365 permissions and sensitivity labels.

🚦 Toolbox creation gate: before creating a toolbox/connection, you MUST read the boundary rules in create-hosted.md → Toolbox creation boundary and follow them, then continue with the rest of this file.

Toolbox shape

{
  "type": "work_iq_preview",
  "project_connection_id": "<workiq-connection-name>"
}

Requirements

  • A RemoteA2A project connection targeting https://workiq.svc.cloud.microsoft/a2a/, authType=OAuth2, BYO Entra app only (no managed OAuth).
  • Scopes: api://workiq.svc.cloud.microsoft/WorkIQAgent.Ask + offline_access. A Global Administrator must grant tenant-wide admin consent for WorkIQAgent.Ask (Work IQ app ID fdcc1f02-fc51-4226-8753-f668596af7f7).
  • Each calling end-user must hold a Microsoft 365 Copilot license.
  • The Work IQ service principal must be pre-provisioned in the tenant (one-time, via Graph Explorer); see the public doc.
  • VNet integration is not supported — the Foundry project must not use a VNet-restricted endpoint.

References

For the full Entra app setup, ARM connection-creation payload (category: RemoteA2A), and troubleshooting, see Work IQ tool documentation.