--- title: "Microsoft Foundry" slug: "microsoft-foundry" updated: 2026-11-15T17:24:54Z published: 2026-11-15T17:24:54Z canonical: "docs.plainid.io/microsoft-foundry" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.plainid.io/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft Foundry PlainID supports Microsoft Foundry as an AI agent platform in the Integrations Workspace. A Microsoft Foundry Policy Orchestration Point (POP) connects to a Foundry project and discovers the AI agents built there, along with the tools and connections those agents use. Discovered agents appear in the Agent Registry, and their tools and connections appear as vendor objects in the POP and on the Access Graph. The POP reads from Microsoft Foundry and never changes it. It doesn't enforce Policies inside Foundry or deploy Policies back to it. The integration provides three capabilities: - **Agent discovery:** the POP registers each agent in the project in the Agent Registry, with its identity, owner, kind, model, version, runtime URL, and assigned tools. You use these agent identities when you author Policies for specific user-agent combinations. - **Tool discovery:** the POP discovers the tools assigned to each agent and groups them by tool type, such as web search, Model Context Protocol (MCP), or Agent2Agent (A2A). - **Connection discovery:** the POP discovers the project connections that tools use to reach external systems, including each connection's type, target URL, and authentication method. Each POP connects to one Foundry project. To discover several projects, create a POP for each one. See [Microsoft Foundry POP Setup](/v1/docs/mf-pop-setup) for more information. See [Configuring Microsoft Foundry](/v1/docs/configuring-microsoft-foundry) for the Azure setup. ## Discovered Objects | Foundry object | Where it appears | Description | | --- | --- | --- | | Agent | Agent Registry | An AI agent in the Foundry project. The Platform registers it with the attributes listed below. | | Tool | POP **Vendor Objects**, Access Graph | A capability an agent can invoke. The Platform creates one object per tool type, for example `web_search` or `mcp`. | | Connection | POP **Vendor Objects**, Access Graph | A project connection that a tool uses to reach an external system, with its own authentication method. | Custom tools, such as MCP and A2A tools, reference a project connection. Built-in tools, such as web search, use no connection and appear as a tool type only. Each connection name is unique within a project. ## Agent Attributes The Platform maps each discovered agent to the default Agent Registry attributes: | Attribute | Value | | --- | --- | | Agent ID | The agent's Microsoft Entra agent identity ID. | | Display Name | The agent's name in Foundry. | | Description | The description of the agent's current version. | | Status | The status of the agent's current version. | | Vendor | `Microsoft Foundry` | | Owner | The identity that created the agent's Azure resource. | | Tags | The metadata of the agent's current version. | | Creation Date | When the agent's current version was created. | | Origin | The name of the POP that discovered the agent. | The Platform also populates these Microsoft Foundry attributes: | Attribute | Description | | --- | --- | | Foundry ID | The agent's ID in Microsoft Foundry. | | Kind | The agent kind: `prompt`, `hosted`, or `workflow`. | | Source | The origin of the agent's code. | | Version | The agent's current version. | | Model | The model the agent uses. Populated for `prompt` agents only. | | Runtime URL | The URL that invokes the agent. | | Inbound Auth Type | The authentication method required to invoke the agent. | | Inbound OAuth Provider | The OAuth provider that authenticates callers of the agent. | | Assigned Tools | The tools assigned to the agent. Multi-value. | You can't edit these attributes in the Platform. Each discovery refreshes them from Foundry. ## Tool and Connection Attributes | Object | Attribute | Description | | --- | --- | --- | | Tool | Tool Type | The tool type, for example `web_search`, `mcp`, or `a2a_preview`. | | Connection | Connection ID | The connection's ID in the Foundry project. | | Connection | Display Name | The connection's name. | | Connection | Type | The connection category, for example `AzureOpenAI`, `AzureBlob`, `CognitiveSearch`, `CosmosDB`, `ApiKey`, `CustomKeys`, or `RemoteTool_Preview`. | | Connection | Target URL | The URL of the service the connection reaches. | | Connection | Credential Type | The authentication method, for example `ApiKey`, `AAD` (Microsoft Entra ID), `SAS`, `CustomKeys`, `None`, or `AgenticIdentityToken_Preview`. | | Connection | Tool Type | The tool type the connection belongs to. | The Platform records only the credential type of each connection, never the keys or tokens themselves. ## Access Graph The Access Graph shows what each POP discovered: - The **Protection** lane shows the POP with the Microsoft Foundry logo, under the POP's name. - The **Assets** lane shows one bubble per tool type, with a generic Asset icon. A dashed line connects the POP to each tool type. - When you select a tool type, a second **Assets** lane shows its connections. Each connection card shows the connection type as a tag. For example, if discovery finds tools of type `web_search` and `mcp`, the **Assets** lane shows two bubbles. Selecting `mcp` shows the MCP connections in the second **Assets** lane.