Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Agent Inventory feature provides administrators with tenant-wide visibility into all Copilot Studio custom agents and declarative agents in the organization, across environments. Agent Inventory data includes lifecycle and ownership metadata, configuration and capability adoption signals, governance indicators, and usage metrics.
Note
This article describes the current Agent Inventory experience. The previous experience is documented in the Copilot Agent Kit repository on GitHub in the AGENT_INVENTORY_V1.md file.
Dashboard
The Agent Inventory dashboard gives you a tenant-wide summary and drill-through navigation into the inventory. Select a tile, chart, or list item to open a filtered view in the agents grid.
Inventory context
The status row at the top of the dashboard shows the current state of the inventory:
- Whether the inventory is current, empty, or a sync is in progress.
- The percentage of records enriched with detailed configuration.
- The number of agents with limited details.
- The number of synchronized environments.
- The last successful synchronization time, when available.
Portfolio metrics
The metric tiles help you jump directly into important segments of the inventory:
- Number of agents
- Powered by
- Autonomous agents
- Draft agents
- Agents with knowledge
Select a tile to open the agents grid filtered to that segment. The Powered by tile groups agents into categories such as Standard, GitHub Copilot, and Copilot Chat.
Analytics and governance
The dashboard also includes charts and lists that help you spot patterns and risks:
- Portfolio growth with six-month and twelve-month ranges.
- Authentication distribution.
- Governance priorities requiring administrator review.
- Portfolio status distribution.
- Capability adoption across enriched agents.
- Top environments ranked by agent count.
- Agents to watch for records requiring attention.
Percentages depend on the environments for which the configured connection identities can retrieve agent data and detailed configuration. Learn more in Data collection modes.
Browse all agents
Select View full inventory from the dashboard to open the agents grid. Use the grid to find, group, and export inventory data.
You can filter, sort, and group by any column, add or remove columns to tailor the grid to your needs, and export the current view to Excel.
Agent details
Select an agent name from the grid to open Agent details. The header shows the agent identity, environment context, lifecycle status, ownership, and available actions. An information banner tells you whether the record has full Dataverse enrichment or only limited configuration details.
Overview tab
The Overview tab shows the agent summary and environment information, governance posture and signals, and a usage snapshot when usage history exists. If AI-generated descriptions are enabled and the agent is an eligible GitHub Copilot agent, an AI-generated description is also shown.
Components tab
The Components tab appears only when component data is available for the agent. Use this tab to explore the agent architecture in the Component map view, browse categorized content in the Component group view, expand one populated component group at a time, turn on Raw mode to inspect the JSON, or copy component JSON for investigation or support.
Usage tab
The Usage tab appears only when usage records exist for the agent. It includes:
- Month-to-date, the two preceding calendar months, last three months, and last six months ranges. Last six months is selected by default.
- Total Copilot credits and average credits per active week.
- Reported users and primary usage feature.
- Weekly credit trends.
- Usage highlights, credits by feature and channel, and recent usage records.
- An agent-specific Excel export.
Metadata tab
The Metadata tab is always available. Use it to inspect technical values such as agent ID and schema name, environment ID and URL, location and source identifiers, and the raw inventory fields used for diagnostics and integration.
Synchronize or refresh inventory data
Agent Inventory separates synchronization from dashboard refresh.
Sync agents
Select Sync agents when you need to collect the tenant inventory again. The sync follows the filters, environment groups, data collection mode, usage setting, and schedule saved in Configure Agent Inventory.
While a sync is running:
- The inventory status changes to Sync in-progress.
- Sync agents is disabled to prevent duplicate operations.
- Settings that could change the active sync configuration are unavailable.
- The dashboard reloads agent details, usage history, sync status, and last-synchronized information after the sync settles.
Refresh dashboard data
Select Refresh dashboard data to reload data already stored in the Agent Details and Agent Usage History tables. Refresh doesn't start an Agent Sync and doesn't rediscover environments or agents. Use it after a completed sync, or when the dashboard shows stale cached data.
Important
Agent synchronization doesn't use Copilot credits. Credits are used only when AI-generated descriptions are enabled and an eligible GitHub Copilot agent details page is visited.
Governance actions
Agent Inventory supports Reassign, Quarantine, and Unquarantine actions. Actions appear only when every selected agent is eligible.
Action availability
The Status column in the grid is populated during the last inventory sync and reflects the value coming from the Power Platform admin center (One Inventory data). Which actions are shown depends on how many records you select and their status.
| Action | Selection rule | Hidden when |
|---|---|---|
| Reassign | One or many records (up to a maximum of 50) can be selected. | Any selected agent isn't eligible for reassign. |
| Quarantine | One or many records in Draft or Available status (up to a maximum of 50) can be selected. | Any selected agent is Blocked or isn't eligible for quarantine. |
| Unquarantine | One or many records in Blocked status (up to a maximum of 50) can be selected. | Any selected agent is Draft, Available, or isn't eligible for unquarantine. |
If any selected record is incompatible with an operation, that operation is hidden from the command bar. Records whose Power Platform admin center context doesn't match the inventory environment aren't offered unsupported governance actions.
On the Agent details page, quarantine and unquarantine availability is based on the agent's live status, rather than the synced status displayed in the grid.
Reassign
Some organizations require agents to have owners for compliance purposes. The owner can edit the agent, publish updates, delete it, or share it with teammates according to their permissions.
Select Reassign and choose a user who has a Microsoft 365 Copilot license. For bulk reassignment, the dialog displays the selected environments, agents, current owners, and operation status. After reassignment completes, the reassignment status is shown as complete for each successfully processed agent.
Quarantine and unquarantine
Quarantine blocks an eligible agent. Unquarantine restores an eligible blocked agent. Confirmation dialog identifies the affected agents, environments, and statuses before an operation is submitted.
Bulk actions support up to 50 agents per operation and are available only when every selected record is eligible.
Configure Agent Inventory
Select Settings from the dashboard header to open Agent sync configuration. Use it to control which environments and agent types are collected, adjust inventory options, and set the synchronization schedule and collection mode.
Note
These in-app settings assume the required solution connection references are already set up. Learn more about wiring up the connection references in Configure Agent Inventory.
Environment types
Choose which environment types are scanned:
- Developer
- Default
- Sandbox
- Production
- Trial
- Teams
If you don't select an environment type, the system includes all environment types.
Agent types
Choose whether the inventory includes:
- Custom agents
- Declarative agents
If you don't select an agent type, the inventory includes all agent types.
Environment groups
Environment groups provide reusable sync scopes. As an administrator, you can:
- Create and edit a group.
- Select member environments by using environment type and region filters.
- Enable or disable the group.
- Delete a group that you no longer need.
If you don't enable a group, all environments allowed by the other settings are included.
Inventory options
Set the following options to control what the system collects during synchronization:
- Exclude system agents: Skips Microsoft-provided system agents during synchronization.
- Enable AI-generated description for GitHub Copilot agents: Allows description generation when an eligible agent details page is visited.
- Include usage metrics: Collects the retained 180-day usage window during synchronization.
Sync schedule and collection mode
Choose how synchronization runs and which data collection mode to use:
- One Inventory (Power Platform admin center): Combines admin center inventory with environment data for broader discovery and richer metadata.
- Standard (environments only): Retrieves inventory directly from accessible environments.
- Enable daily automatic sync: Runs Agent Inventory on the configured daily schedule.
Select Save to apply changes. Save is disabled when no setting changed, when a save is in progress, or when settings are unavailable during an active sync.
Tip
Use Refresh dashboard data after a completed sync when the dashboard needs to reload existing table data. Use Sync agents only when inventory collection must run again. Keep environment and agent filters as narrow as practical in very large tenants, and disable usage collection when 180-day usage analytics aren't required.
Data collection modes
The Data collection mode setting determines how the system discovers and collects agent records.
One Inventory mode (recommended)
When you set the collection mode to One Inventory, Agent Inventory uses One Inventory data:
- It retrieves agent data from One Inventory through the Power Platform admin center.
- It lists environments by using the Copilot Agent Kit - Power Platform for Admins V2 connection reference.
- It combines the One Inventory agent data with the environments list to construct environment details.
- For each environment, it loads agent details into Agent Inventory by merging agents fetched from the environment with the corresponding One Inventory data.
Use this mode when you require broader tenant discovery and richer Power Platform admin center metadata. Agents discovered through the admin center but inaccessible in their environment are still added with limited details.
Standard mode
When you set the collection mode to Standard, Agent Inventory uses the standard data collection approach:
- It lists all environments by using the Copilot Agent Kit - Power Platform for Admins connection reference (V1).
- It fetches agents for each environment.
- It loads agent data into Agent Inventory.
Use this mode when you want collection to rely only on accessible environments.
In both modes, Agent Inventory uses the Copilot Agent Kit - Dataverse connection reference to connect to each environment and gather detailed agent information, including metadata, feature usage, and configuration. The system retrieves detailed information only for environments where the configured account has system admin access.
Learn more about the full list of connectors used across the kit in Connector requirements.
Usage metrics
Agent Inventory can retain and display up to 180 days of agent usage data. To enable usage analytics:
- Ensure the required solution connections are configured and permitted by data policies.
- Open Agent sync configuration.
- Turn on Include usage metrics.
- Select Save.
- Select Sync agents, or wait for the daily automatic sync.
Usage data is stored in the Agent Details and Agent Usage History tables. An agent's Usage tab appears only when matching usage history records are available.
Configure the HTTP with Microsoft Entra ID connection
Usage metrics rely on the HTTP with Microsoft Entra ID (preauthorized) connector. The connection values depend on the cloud your tenant runs in. Use the Base Resource URL and Microsoft Entra ID Resource URI that match your cloud when you create the connection.
| Cloud | Base Resource URL | Microsoft Entra ID Resource URI |
|---|---|---|
| Commercial | https://licensing.powerplatform.microsoft.com/ |
https://licensing.powerplatform.microsoft.com/ |
| GCC | https://gov.licensing.powerplatform.microsoft.us/ |
https://gov.licensing.powerplatform.microsoft.us/ |
| GCC High | https://high.licensing.powerplatform.microsoft.us/ |
https://high.licensing.powerplatform.microsoft.us/ |
Permissions and connector requirements
The connection references in the solution limit and control visibility to the agents. For full tenant-wide visibility, configure the connection references with an account that has the Power Platform administrator role. To retrieve all feature-level details, that account also needs system administrator access to the relevant environments. You can use other accounts, but the visibility of the agent inventory is limited to the environments where the user has system admin access.
Agent Inventory relies on the following connectors, which the data policies applied to the environment must allow:
- Microsoft Dataverse
- Power Platform for Admins
- Power Platform for Admins V2
- HTTP with Microsoft Entra ID (preauthorized)
Learn more about the full list of connectors used across the kit in Connector requirements.
The following Dataverse tables store Agent Inventory data:
| Table | Purpose |
|---|---|
cat_agentdetails |
Discovered agents, metadata, capabilities, ownership, and synchronized status |
cat_agentusagehistory |
Retained usage dimensions and Copilot credit values |
cat_agentinventorysettings |
Inventory filters, mode, and feature settings |
cat_environmentgroups |
Reusable environment scopes |
cat_agentinventoryactionaudit |
Governance action tracking |
cat_copilotstudiokitlogs |
Feature and operation logging |