GovernanceBeginner20 minDay 8 · Nov 17, 2026

Build an inventory of your agents and their owners

Use the Power Platform inventory to list every agent in your tenant, see who owns it and what it connects to, and flag the ones that need attention.

Today's task

In Who can build agents in your tenant? you looked at where agents can be built. Today you'll answer the next question: which agents actually exist, and who is responsible for each one? You'll export a list and mark every agent as keep, fix or retire.

You'll need: a Microsoft Entra role that can view the Power Platform inventory: Global administrator, Power Platform administrator, Dynamics 365 administrator, Global reader, AI administrator or AI reader. The two AI roles only see agent-related items, which is all you need here. Open the Power Platform admin center.

Checklist

  1. Open the inventory. Go to Manage > Inventory. It lists agents, apps, flows, connectors and environments. Agents built in Copilot Studio and in Microsoft 365 Copilot Agent Builder both appear. New or changed items usually show up within 15 to 20 minutes.
  2. Narrow to agents. You can filter the list by any column. For a shorter list, open Manage > Copilot Studio, which shows agents along with agent flows and workflows. Classic chatbots are not in the new inventory. Find them under Manage > Copilot Studio > Classic chatbots.
  3. Show the columns you need. Select the Add or remove columns icon next to the Search box. Add the owner, environment, creation date and connectors columns if they aren't visible.
  4. Look for the risky patterns. Use the filters to find:
    • agents in the default environment (select the Environment type column and choose Default)
    • agents owned by someone who has left or changed roles (filter the Owner column by name; the docs call these orphaned resources)
    • agents that use connectors you did not approve
  5. Open a few agents. Select an agent's name to open its details panel, with Overview, Connectors and Usage tabs. Check what it connects to and whether anyone still uses it.
  6. Export the list. Select Download in the command bar to save the whole inventory as a CSV file.
  7. Mark each agent. Add a column in a spreadsheet with Keep, Fix or Retire, plus a named business owner for each one you keep.

What to notice

  • The inventory is a starting point, not a verdict. It shows what exists. Only a person can say whether an agent is still needed.
  • Known gaps. Per the docs, the Modified on and Last modified by columns don't work for agents and show a dash. Draft agents are listed, but a published agent's details reflect its published version, so later unpublished changes don't show. Some agent details, including connectors, are still marked preview.
  • You can act from here. For a published agent that worries you, the command bar has a Block option. Blocking is reversible, and makers can still test the agent in Copilot Studio.

Governance tip: Every agent needs a named owner and a review date. If you can't name who is responsible for an agent, treat it as a candidate to block or retire, and repeat this check every quarter.

Go further

Rather have it built?

We build and govern Microsoft AI agents for businesses like yours.

If you'd rather skip the learning curve, Louder IT designs, builds and runs agents in Copilot Studio and Azure, with guardrails included.