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-fabric-iq.md

Tool — Fabric IQ (preview)

Connect an agent to Microsoft Fabric data — Ontology, Fabric data agents, and Power BI semantic models — through Fabric IQ. The agent delegates natural-language questions; Fabric IQ runs them against the enterprise ontology (NL2Ontology) and returns synthesized answers under the signed-in user's Fabric permissions.

Toolbox shape

{
  "type": "fabric_iq_preview",
  "project_connection_id": "<fabriciq-connection-name>",
  "server_label": "<short-lowercase-label>",
  "server_url": "https://<host>/v1/mcp/..."
}

server_url by Fabric item type

| Fabric item | server_url pattern | Supported auth | |---|---|---| | Ontology | https://{host}/v1/mcp/dataPlane/workspaces/{workspaceId}/items/{itemId}/ontologyEndpoint | BYO Entra app only | | Fabric data agent | https://{host}/v1/mcp/workspaces/{workspaceId}/dataagents/{dataAgentId}/agent | BYO Entra app or managed OAuth | | Power BI semantic model | https://{host}/v1/mcp/fabricaihub/integrations/m365 | BYO Entra app or managed OAuth |

Requirements

  • Microsoft Fabric license for both the developer and every calling end-user.
  • For Ontology / Power BI: Entra app with delegated Power BI permissions Item.Execute.All + Item.Read.All; tenant admin consent required. For Data Agent: DataAgent.Execute.All.
  • Each Fabric item must be published before it can be consumed through Fabric IQ.
  • VNet integration is not supported.
  • Tip: for Power BI semantic models, use latest models — measure/hierarchy reasoning benefits significantly.

References

For the full Entra app setup, connection-creation walkthrough, and troubleshooting, see Fabric IQ tool documentation.