# Configuring Microsoft Foundry for Discovery
This page lists what you prepare in Microsoft Foundry and Microsoft Entra ID for the Microsoft Foundry Policy Orchestration Point (POP), including:
- An application registration
- A client secret
- Read access to the Foundry resource and project
- The project details
- An API key
You complete each step in Azure by following Microsoft's documentation, then enter the values in the POP. The POP only reads from Foundry, so the application never needs write access.
Prerequisites
Before you start, ensure you have:
- A Microsoft Foundry resource with the project you want to discover.
- Permission to register applications in Microsoft Entra ID.
- Permission to assign Azure roles on the Foundry resource and project, for example the Owner or User Access Administrator role.
- A PlainID Environment with a Policies Workspace.
Step 1: Register an Application
Register a single-tenant application in Microsoft Entra ID, for example plainid-foundry-discovery. Copy its Application (client) ID and Directory (tenant) ID.
See Register an application in Microsoft Entra ID for the steps.
Step 2: Create a Client Secret
Add a client secret to the application. Copy the secret's Value, not its Secret ID, and note its expiry date. Before the secret expires, create a new one and update the POP (see Rotating Credentials).
See Add a client secret for the steps.
Step 3: Grant Read Access
Assign the application these roles:
| Scope | Role | What it allows |
|---|---|---|
| The Foundry resource | Reader | Reading the project's connections and the identity that created each agent. |
| The Foundry project | Foundry User (formerly Azure AI User) | Reading the project's agents and their tool configuration. |
When you select members, assign access to a User, group, or service principal and choose the application from Step 1.
See Assign Azure roles using the Azure portal for the steps, and Role-based access control for Microsoft Foundry for more information on the Foundry roles.
Step 4: Collect the Project Details
| Value | Description |
|---|---|
| Subscription ID | The Azure subscription that contains the Foundry resource. |
| Resource Group | The resource group of the Foundry resource. |
| Account Name | The name of the Foundry resource. |
| Project Name | The name of the Foundry project. |
| Project Endpoint | The project endpoint, in the form https://<account-name>.services.ai.azure.com/api/projects/<project-name>. |
See Microsoft Foundry SDKs and endpoints for more information on the project endpoint.
Step 5: Get the API Key
Copy one of the two API keys of the Foundry resource. Keep the other key for rotation.
See Rotate keys for where to find the keys and how Azure rotates them.
Values for the POP
When you finish, you have every value the POP asks for:
| POP field | Source |
|---|---|
| Tenant ID | Step 1, Directory (tenant) ID |
| Client ID | Step 1, Application (client) ID |
| Client Secret | Step 2, the secret's Value |
| Subscription ID | Step 4 |
| Resource Group | Step 4 |
| Account Name | Step 4 |
| Project Name | Step 4 |
| Project Endpoint | Step 4 |
| API Key | Step 5 |
Next, create the POP. See [Microsoft Foundry POP Setup](LINK: Microsoft Foundry POP setup){target=_blank} for more information.
Rotating Credentials
You can change the Client Secret and API Key after you create the POP. All other fields are fixed at creation.
To rotate the client secret:
- Create a new client secret, as in Step 2.
- In the POP, replace the Client Secret with the new value and save.
- In Azure, delete the old secret.
To rotate the API key:
- In the POP, replace the API Key with the key you kept for rotation and save.
- In Azure, regenerate the key the POP used before. See Rotate keys for more information.
Troubleshooting
| Symptom | Cause | What to do |
|---|---|---|
| Discovery fails with an authentication error. | The Tenant ID, Client ID, Client Secret, or API Key is wrong, or the client secret expired. | Check the values against Steps 1, 2, and 5. Rotate the client secret if it expired. |
| Discovery succeeds but finds no agents. | The application lacks the Foundry User role on the project, or the POP points at another project. | Check the role assignment in Step 3 and the Project Name and Project Endpoint in the POP. |
| Agents appear without an Owner. | The application lacks the Reader role on the Foundry resource. | Assign the role as in Step 3, then run discovery again. |
| A tool type appears with no connections. | Built-in tools, such as web search, use no connection. | No action needed. |