Agent registry integration for Copilot Studio

Microsoft Copilot Studio agents automatically appear in the agent registry when you create them—providing centralized visibility, governance, and management across your tenant. Administrators use the agent registry to discover, monitor, and control agents organization-wide.

This article explains how Copilot Studio agents integrate with the agent registry and what metadata is visible to administrators.

Agent registry

The agent registry is a centralized inventory of all agents in your Microsoft 365 tenant:

  • Single source of truth: View all agents across platforms (Copilot Studio, pro-code, non-Microsoft).
  • Tenant-wide visibility: Administrators see agents from all environments and teams.
  • Governance controls: Apply policies, permissions, and actions to agents.
  • Compliance tracking: Audit agent metadata, permissions, and usage.

The agent registry is accessed via Microsoft 365 admin center, and then select Agent 365.

The agent registry is different from the Power Platform admin center in that it provides tenant-wide visibility across all platforms, while the Power Platform inventory shows only Power Platform-specific apps within an environment.

How Copilot Studio agents appear in the registry

Copilot Studio agents register automatically when you create them.

Registration timing

Event Registry action
Create agent in Copilot Studio Agent appears in registry immediately
Update agent metadata Registry entry updated automatically
Delete agent Registry entry removed automatically

Visible metadata

Administrators see the following information for each Copilot Studio agent.

Basic information:

  • Agent name and description
  • Publisher information (creator email, organization)
  • Agent type (Copilot Studio app-based)
  • Creation and last modified dates
  • Agent ID (unique identifier)
  • Power Platform connectors used

Configuration details:

  • Deployment status
  • Enabled or disabled state
  • Version information (if applicable)

Governance metadata:

  • Pre-approval status via Power Platform policies
  • Applied data loss prevention (DLP) policies
  • Advanced connector policy compliance

Copilot Studio automatically syncs this metadata. No manual input required.

Agent registry vs. Power Platform app catalog

Copilot Studio agents appear in both the agent registry and the Power Platform app catalog, but each serves a different purpose.

Feature Agent registry Power Platform app catalog
Scope Tenant-wide, all agent platforms Environment-specific, Power Platform only
Purpose Governance, visibility, compliance Distribution, installation, environment management
Access Microsoft 365 admin center Power Platform admin center
Managed by Tenant administrators Environment administrators
Agent 365 integration Yes - observability, governance, controls No - Power Platform governance only

For developers, both registries show your Copilot Studio agents, but the agent registry provides the Agent 365 integration layer, including observability, governance controls, and compliance.

Registration lifecycle

Copilot Studio agents follow an automatic registration lifecycle.

1. Creation

When you create a Copilot Studio agent:

  • Entra identity provisioned automatically (see Agent identity integration)
  • Agent appears in registry within seconds
  • Metadata synced from Copilot Studio
  • Status: Active (pre-approved via Power Platform policies)

2. Updates

When you modify your agent:

  • Metadata changes (name, description): Registry updated automatically
  • Permission changes (new connectors): Registry updated, DLP policies re-evaluated
  • Configuration changes: Registry reflects current state

No manual re-registration required.

3. Deletion

When you delete a Copilot Studio agent:

  • Registry entry removed automatically
  • Entra identity deleted
  • All associated metadata cleaned up
  • Historical telemetry retained (see Observability integration)

Caution

Deletion is permanent and can't be undone.

Admin experience: Viewing Copilot Studio agents

Administrators access the agent registry from the Microsoft 365 admin center. Go to Microsoft 365 admin center > Agent 365 > Agent registry.

Available views:

  • All agents: See all agents across platforms
  • Filter by platform: Show only Copilot Studio agents
  • Filter by publisher: Show agents from specific teams or users
  • Filter by status: Show active, blocked, or reassigned agents

Agent details page:

  • View full agent metadata
  • See requested permissions and scopes
  • Review observability data (usage, performance, errors)
  • Apply governance actions (block, reassign, delete)

For detailed admin guidance, see:

Governance controls for Copilot Studio agents

Administrators can apply governance actions to Copilot Studio agents through the agent registry.

Block

Prevents an agent from being used organization-wide:

  • Agent remains in registry but becomes inactive
  • Users can't invoke or interact with the agent
  • Agent creator receives notification
  • Can be unblocked later by administrators

Reassign

Transfer agent ownership to a different user or team:

  • New owner gains full control and editing rights
  • Original owner loses access
  • Registry metadata updated with new publisher
  • Useful for team transitions or organizational changes

Delete

Removes an agent from the registry and tenant:

  • Agent builder agents: Agent owners can delete through the registry
  • Agents built within Copilot Studio: Require Power Platform environment admin permissions
  • Agent identity deleted from Entra ID
  • Registry entry removed
  • All configurations and metadata deleted
  • Historical telemetry retained for compliance

All governance actions are logged in Microsoft Purview for compliance tracking.

For more details on governance controls, see Manage agents.

Programmatic access: Graph API

Administrators can access agent registry data programmatically using Microsoft Graph APIs.

Available APIs:

  • List all agents: Retrieve complete inventory for compliance and reporting
  • Get agent details: Fetch metadata for a specific agent for auditing

Use cases:

  • Bulk agent management and automation
  • Integration with existing governance workflows
  • Custom reporting and analytics
  • Compliance auditing and monitoring

AI admin or Global admin role permissions are required for the use cases.

For API details, see Graph API for agent registry and agent details.

Developer considerations

As a Copilot Studio developer, keep these registry integration points in mind.

Metadata quality:

  • Use clear, descriptive agent names and descriptions (visible to admins)
  • Document connector usage and permissions in agent description
  • Keep agent metadata up-to-date

Permission transparency:

  • Administrators see all requested permissions in registry
  • Only add connectors you actually need
  • Understand Power Platform policies that govern connector usage

Observability integration:

  • Registry links to observability data (usage, performance, errors)
  • Administrators can monitor your agent's activity
  • Design agents with observability in mind (see Observability integration)

Governance awareness:

  • Agents can be blocked, reassigned, or deleted by administrators
  • Design agents to handle deactivation gracefully
  • Communicate with administrators about high-privilege connector needs

Next steps

  • Last updated on