--- title: "POP Setup" slug: "mf-pop-setup" updated: 2026-11-15T17:24:22Z published: 2026-11-15T17:24:22Z canonical: "docs.plainid.io/mf-pop-setup" --- > ## 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. # POP Setup PlainID supports a Microsoft Foundry Policy Orchestration Point (POP) in the Integrations Workspace. The POP connects to a Microsoft Foundry project and discovers the AI agents, tools, and connections in it. See [Microsoft Foundry](/v1/docs/microsoft-foundry) for more information on what the POP discovers. Each Foundry project has one POP. ## Prerequisites Before you start, ensure you have: - The application credentials, project details, and API key from [Configuring Microsoft Foundry for Discovery](/v1/docs/configuring-microsoft-foundry). - A Policies Workspace in your PlainID Environment. ## Creating the POP **To create the POP:** 1. In the Integrations Workspace, create a new POP and select **Microsoft Foundry**. See [Managing POPs](/v1/docs/managing-pops) for more information. 2. Enter the connection details described in the table below. 3. Link a Policies Workspace. The Platform creates an Application for the POP and selects the Agent Registry as the linked Identities Workspace automatically. 4. Save the POP. 5. Run discovery. See [Managing POPs](/v1/docs/managing-pops) for running and scheduling discovery. ### Connection Details | Field | Description | | --- | --- | | **Tenant ID** | The Directory (tenant) ID of your Microsoft Entra ID application. | | **Client ID** | The Application (client) ID of your Microsoft Entra ID application. | | **Client Secret** | The client secret value of your Microsoft Entra ID application. | | **Subscription ID** | The Azure subscription that contains your Foundry resource. | | **Resource Group** | The Azure resource group of your Foundry resource. | | **Account Name** | The name of your Foundry resource. | | **Project Name** | The name of your Foundry project. | | **Project Endpoint** | The project endpoint, for example `https://acme-foundry.services.ai.azure.com/api/projects/acme-agents`. | | **API Key** | An API key of your Foundry resource. | All fields are required. The Platform stores the **Client Secret** and **API Key** as secrets and masks them in the UI. You can change the **Client Secret** and **API Key** after you create the POP. All other fields are fixed at creation. To connect to another project, create a new POP. ## Viewing Discovered Objects After discovery runs, you review what the Platform discovered in three places: - **Agent Registry** lists the discovered agents, with **Vendor** set to `Microsoft Foundry` and **Origin** set to the POP's name. - **Vendor Objects** in the POP lists the discovered tools and connections. Select one to see all its attributes. - **Access Graph** shows the POP in the **Protection** lane and its tool types and connections in the **Assets** lanes. ## Notes - Discovery only reads from Microsoft Foundry and never changes your agents, tools, or connections. - The Platform records only the credential type of each connection, never the keys or tokens themselves. - Each discovery refreshes the agent attributes from Foundry. You can't edit them in the Platform.