No agents found

No agents found inside an environment

What happened

Your Power Platform environments are connected and listed, you opened one, and AgentProof did not find any Copilot Studio agents inside it. 'No agents found' is shown inside a specific environment, not on the environments list.

Why it matters

You cannot build a compliance-readiness record for an agent AgentProof cannot see. An empty environment usually means the agents live in a different environment, the agents are not visible to the account you connected, or live agent discovery is still being enabled for your tenant. AgentProof only shows a true 'no agents' result once discovery has genuinely completed, so a momentary empty state during loading is not a real zero.

What to do next

1. Give the page a moment to finish loading before treating the count as final.
2. Confirm you opened the right environment; agents are scoped per environment, and another environment may hold the agent you are looking for.
3. Confirm in the Power Platform admin center that the environment actually contains Copilot Studio agents and that your account can see them.
4. While live agent discovery is being enabled, add the agent manually (describe what it does, who it talks to, and what it can act on) so you can still produce a readiness score and compliance-readiness record now.

What information to include

1. The exact environment name you opened.
2. Your workspace name.
3. Whether you can see the agent in Copilot Studio or the Power Platform admin center.
4. A brief description of the agent (what it does, who it talks to, what it can act on).

When to contact support

If you can see the agent in Copilot Studio or the Power Platform admin center but AgentProof still shows 'No agents found' in the correct environment, email [email protected] with the environment name and a description of the agent. Do not paste any tokens, links, or secrets.

Agents exist but are not visible to my account

What happened

You expect agents in an environment, but they do not appear because the account you connected cannot see them, or it lacks read access to the agent metadata.

Why it matters

AgentProof mirrors exactly what your signed-in account is permitted to see; it never elevates your permissions. If your account cannot read the agents, AgentProof will not invent them, so the list is honestly empty.

What to do next

1. Confirm the environment is the one that actually contains your published agents.
2. Confirm your account has read access to the agent metadata in that environment (a Dataverse role with read access).
3. If you have several accounts, reconnect and pick the account that can see the agents, then retry discovery.
4. To keep moving regardless, add the agent manually and assess it directly.

What information to include

1. Your workspace name and which environment you opened.
2. The account you connected with.
3. Whether your account has read access to the agent metadata in that environment.
4. A brief description of the agent you expected to see.

When to contact support

If the environment definitely contains an agent and your account has access but AgentProof still shows none, email [email protected] with your workspace name and which environment you opened. Do not include tokens or secrets.

Adding an agent manually while discovery is being enabled

What happened

Live agent discovery has not run for your tenant yet, but you want to produce a compliance-readiness record now.

Why it matters

Manual documentation is always available and is never removed. A manually added agent runs through the same scoring and improvement pipeline, so you get a real readiness score, an evidence, controls, and gaps summary, and a compliance-readiness record; live discovery simply pre-fills the agent list for you once enabled.

What to do next

1. Choose Add a non-Microsoft agent (or Add an agent manually).
2. Describe the agent in plain English: what it does, who it talks to, and what it can act on.
3. Answer the matching question packs and generate the compliance-readiness record. AgentProof labels it with the evidence basis you supply.
4. Re-run discovery later once it is enabled; nothing you do manually is lost.

What information to include

1. Your workspace name.
2. A brief description of the agent you added manually.
3. The step where report generation stopped, if it did.
4. Whether you want a status on live agent discovery for your tenant.

When to contact support

If manual assessment will not generate a report, or you want a status on live agent discovery for your tenant, email [email protected] with your workspace name. Your data is stored in the EU.