--- title: "POP Setup" slug: "ms-pop-setup" updated: 2026-11-15T17:28:37Z published: 2026-11-15T17:28:37Z canonical: "docs.plainid.io/ms-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 Agent 365 Registry Policy Orchestration Point (POP) in the Integrations Workspace. The POP connects to your Microsoft tenant, discovers the AI agents in your Microsoft Agent 365 registry, and shows them in the Platform as agent identities. ## Prerequisites Before you start, ensure you have: - A Microsoft Entra application with registry permissions, and its Tenant ID, Client ID, and Client Secret. See [Configuring Microsoft Agent 365](/docs/configuring-microsoft-365) for more information. ## Creating the POP **To create the POP:** 1. In the Integrations Workspace, create a new POP and select **Microsoft Agent 365 Registry**. See [Managing POPs](/v1/docs/managing-pops) for more information. 2. Enter the connection details described in the table below. 3. Set when discovery runs. 4. The Platform links the POP to **Agents** automatically. The POP doesn't link an Application or a Policies Workspace. 5. Save the POP. ### Connection Details | Field | Description | | --- | --- | | **Tenant ID** | The Directory (tenant) ID of your Microsoft Entra tenant. | | **Client ID** | The Application (client) ID of the application you registered. | | **Client Secret** | The client secret value you created. The Platform stores it in its secret store and masks it after you save. | You can change the **Client Secret** after you create the POP. **Tenant ID** and **Client ID** are fixed at creation. To connect a different tenant or application, create a new POP. ## Viewing Discovered Agents After discovery runs, open the POP and select **Vendor Objects** to see the agents the Platform discovered. Select an agent to see its details. The Platform also lists each agent in the Agent Registry Identities Workspace, where you use it in Policies. Each agent carries these attributes. Multi-value attributes can hold several values. | Attribute | Multi-value | Description | | --- | --- | --- | | `uid` | No | The agent's unique ID in PlainID. Required. | | `displayName` | No | The agent's name. Required. | | `description` | No | The agent's description. | | `vendor` | No | The vendor that provides the agent. Required. | | `owner` | No | The agent's owner. | | `publisher` | No | The agent's publisher. | | `status` | No | The agent's status in the registry. | | `isBlocked` | No | `true` when Microsoft blocked the agent. | | `isDeleted` | No | `true` when the agent was deleted from the registry. | | `isShadow` | No | **[TBD: definition.]** Required. | | `creationDate` | No | When the agent was created. | | `lastModifiedDate` | No | When the agent was last changed. | | `origin` | No | **[TBD]** | | `source` | No | **[TBD]** | | `kind` | No | **[TBD]** | | `model` | No | The model the agent uses. | | `runtimeUrl` | No | The URL where the agent runs. | | `appId` | No | The Microsoft application ID of the agent. | | `manifestId` | No | The ID of the agent's manifest. | | `blueprintId` | No | The ID of the blueprint the agent was created from. | | `agent365RegistryId` | No | The agent's ID in Microsoft Agent 365 Registry. | | `sourceAgentId` | No | The agent's ID in the system it came from. | | `assignedTools` | Yes | The tools assigned to the agent. | | `mcpConnectors` | Yes | The MCP connectors the agent uses. | | `endpointType` | Yes | **[TBD]** | | `capabilities` | Yes | The agent's capabilities. | | `actions` | Yes | The actions the agent can take. | | `channels` | Yes | The channels where the agent is available. | | `supportedHosts` | Yes | The hosts that support the agent. | | `tags` | Yes | The tags on the agent. | ## Rotating the Client Secret Microsoft client secrets expire. Replace the secret before it expires, or the POP stops discovering agents. **To rotate the Client Secret:** 1. Create a new client secret for the application in Microsoft Entra ID. See [Add and manage application credentials](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials) in the Microsoft documentation. 2. In the Integrations Workspace, select your POP and edit the connection details. 3. Enter the new value in **Client Secret** and save. 4. Delete the old secret in Microsoft Entra ID. ## Troubleshooting | Symptom | Cause | What to do | | --- | --- | --- | | The POP doesn't save or reports an authentication error. | The Tenant ID, Client ID, or Client Secret is wrong, or the secret expired. | Compare the values with the ones you collected in Step 4 of [Configuring Microsoft Agent 365](/docs/configuring-microsoft-365). Make sure you entered the secret's value, not its secret ID. Create a new secret if the old one expired. | | The POP connects, but no agents appear. | The application lacks the registry permission, or nobody granted admin consent. | Check that the application has the registry permission and that an administrator granted admin consent. See Step 3 of [Configuring Microsoft Agent 365](/docs/configuring-microsoft-365). | | An agent you deleted still appears. | The Platform keeps deleted agents and marks them. | Check the agent's `isDeleted` attribute. | ## Notes - The POP works in Learn mode: it reads the registry and never changes agents or settings in your Microsoft tenant. - The POP doesn't enforce Policies. An Authorizer enforces them where the agent acts. - New agents appear in the Platform after the next discovery run on your schedule.