Copilot Studio Agent Register: Start Yours Before Sprawl Hits

In May 2026, Microsoft quietly made the single most consequential governance change the Copilot Studio platform has ever shipped. Every new agent now receives a Microsoft Entra Agent ID automatically, and organizations can no longer opt out. The identity surface for AI agents, which used to live as scattered app-registration service principals buried in Azure, is now a tenant-wide, first-class directory layer that exists whether governance teams are ready for it or not.

That change makes a Copilot Studio agent register operationally possible for the first time. It also makes one urgently necessary. Agents counts in most enterprise tenants are still small enough to inventory cleanly. In 6 to 12 months, they will not be. The window to build the register while ownership is still traceable is open now, and it is narrower than most IT leaders think.

TL;DR

A Copilot Studio agent register is a tenant-wide, authoritative inventory of every Copilot Studio agent, its owner, its data access, and its lifecycle state, built on top of the automatic Entra Agent ID that every new agent now receives. Build it while agent counts are small, before sprawl forces expensive retroactive clean-up.

Key Takeaways

As of May 2026, Copilot Studio automatically creates a Microsoft Entra Agent ID for every new agent, and the opt-out has been removed. Every agent is already in your directory.
Gartner projects 40% of enterprise applications will feature task-specific AI agents by the end of 2026, up from less than 5% in 2025. The sprawl curve is steep and immediate.
The register is an operating artifact, not a tooling project. A schema, named owners, a review cadence, and clear quarantine triggers matter more than the admin UI.
Reconciliation across Entra Object ID, Power Platform Item ID, and Dataverse bot records is still manual. The register is the authoritative crosswalk.
Register discipline is achievable without full Microsoft Agent 365 licensing. Mid-market organizations can run a credible register on Entra and Copilot Studio inventory alone.

What Actually Changed in May 2026

Before this spring, a Copilot Studio agent authenticated through an app-registration service principal that your platform team either created manually or inherited silently. Most tenants ended up with a long tail of orphaned service principals attached to agents that no longer existed, no durable link between the identity and the business owner, and no clean way for security to ask "what can this agent reach?"

The new model replaces that pattern. According to Microsoft Learn, Copilot Studio automatically creates a Microsoft Entra Agent ID for each new agent you create, and starting May 2026 all new agents have Microsoft Entra Agent IDs with no option to opt out. Each identity is a child of a single tenant-wide Agent Identity Blueprint, and each one is directly governable with Conditional Access, audit logging, sponsorship, and lifecycle policies in Microsoft Entra ID Governance.

That is the quiet part worth saying out loud: the identity plane is no longer optional, no longer manual, and no longer invisible. It exists in every tenant that touches Copilot Studio. Whether it is useful depends entirely on whether a register sits on top of it.

Why the Register Is a Count Problem, Not a Scale Problem

The common wisdom treats AI governance as a scale problem. Build the registry when you have hundreds of agents and the pain becomes undeniable. That framing is wrong in a specific and expensive way.

Governance of agents is a count problem. The register you build at 30 agents is cheap, clean, and defensible. The register you build at 300 is a retroactive forensics exercise. Owners have left the organization. Processes have moved. Connector permissions have drifted. The data classifications nobody captured at creation now have to be inferred from behavior.

Governance of agents is a count problem, not a scale problem: the register you build at 30 agents is cheap and defensible, and the one you build at 300 is a retroactive forensics exercise.

The urgency is not theoretical. Gartner projects that 40% of enterprise applications will feature task-specific AI agents by the end of 2026, up from less than 5% in 2025. IDC forecasts a tenfold increase in agent usage by 2027. Gartner has separately projected that more than 40% of agent projects will be abandoned by 2027, with governance and ROI failures as the dominant causes. Meanwhile Deloitte's 2025 global AI governance survey found that only 23% of organizations have a formal AI governance framework in place.

Translation: the agents are coming faster than the policies. The identity layer that Microsoft just shipped is the one piece of infrastructure that lets you catch up. The register is how you use it.

The BabyBots Agent Register Schema

A register that only mirrors what Entra captures is a feature tour, not a governance artifact. The fields that make the register useful are the ones Entra does not populate for you. These are the fields BabyBots recommends capturing from day one.

Register Fields and Why Each One Matters

Agent name

Purpose: Human-readable identifier used across the business.
Source: Copilot Studio.
Owner of the field: Maker at creation, verified by platform team.

Entra Agent ID (Object ID)

Purpose: Durable directory identifier for Conditional Access, audit, and lifecycle policies.
Source: Microsoft Entra ID.
Owner of the field: Identity team.

Power Platform Item ID

Purpose: Links the directory identity to the Copilot Studio agent object.
Source: Power Platform admin center or Dataverse.
Owner of the field: Platform team.

Dataverse bot record ID

Purpose: Links to the underlying bot entity for runtime diagnostics and ALM.
Source: Dataverse.
Owner of the field: Platform team.

Environment

Purpose: Governance zone (dev, test, production, sandbox).
Source: Power Platform.
Owner of the field: Platform team.

Business owner

Purpose: Named accountable executive or line manager in the business.
Source: Intake process.
Owner of the field: Governance lead.

Sponsor

Purpose: Human user tied to the Entra Agent ID for access and lifecycle. Transfers to manager on departure.
Source: Entra ID Governance.
Owner of the field: Identity team.

Sponsoring process

Purpose: The business process the agent serves. Enables ROI measurement and impact assessment.
Source: Intake process.
Owner of the field: Business owner.

Data classifications touched

Purpose: Sensitivity tiers the agent can reach. Drives DLP and Conditional Access scoping.
Source: Intake and Purview.
Owner of the field: Security.

Connector risk tier

Purpose: Aggregate risk score across the agent's connectors and actions.
Source: Platform team scoring model.
Owner of the field: Platform team.

Downstream workflows

Purpose: Power Automate flows, Logic Apps, or other agents that depend on this one. Decommission blast radius.
Source: Intake and dependency scan.
Owner of the field: Platform team.

Collection

Purpose: Governance grouping (by business unit, data sensitivity, or lifecycle stage).
Source: Agent Registry.
Owner of the field: Governance lead.

Lifecycle stage

Purpose: Pilot, production, deprecated, quarantined, decommissioned.
Source: Platform team.
Owner of the field: Platform team.

Review cadence

Purpose: Frequency the business owner must re-attest to purpose and access.
Source: Policy.
Owner of the field: Governance lead.

Decommission trigger

Purpose: The condition that ends the agent's life (process retired, owner departed, risk threshold breached).
Source: Policy.
Owner of the field: Governance lead.

Dependent agents

Purpose: Other agents that call or are called by this one. Multi-agent accountability.
Source: Dependency scan.
Owner of the field: Platform team.

The schema is the artifact. The admin UI is the surface. Confuse those and the register becomes a screenshot gallery instead of an operating record.

The Reconciliation Reality

Here is the operational truth most feature-tour articles skip. The Entra Agent ID, the Power Platform Item ID, and the Dataverse bot record do not join automatically. An agent has one of each, and no built-in query returns all three in a single row. Platform admins who have tried to cross-walk them for an audit know the friction.

The register is where that cross-walk lives. Three practical mechanics tend to work:

Pull Entra Agent IDs via Microsoft Graph on a scheduled cadence and write them to the register's identity column.
Pull Copilot Studio agent inventory from the Power Platform admin API (or the Agent Registry in Microsoft 365 admin center if you have E7 or Agent 365) and match on display name and tenant object metadata.
Query Dataverse directly for the bot table and link by Power Platform Item ID.

Automate the join. The moment the register depends on a human stitching three exports together in a spreadsheet, it stops being authoritative within a quarter.

Agent Collections Are a Governance Primitive

Agent collections look like folders in the Microsoft 365 admin center. Treating them as folders is a mistake. Collections are the governance lens through which the register is operated. They determine which policies apply, who reviews which agents, and how quarantine behavior cascades.

Three collection taxonomies tend to work for enterprise tenants:

By business unit: clearest ownership, matches budget and audit boundaries, easiest for business owners to self-navigate.
By data sensitivity: cleanest for security and Conditional Access scoping, especially for agents touching regulated data.
By lifecycle stage: useful as an overlay (pilot, production, deprecated) for platform operations.

Most organizations end up with business unit as the primary axis and data sensitivity as the overlay. Pick the taxonomy on day one. Retrofitting it after 200 agents are already in flat collections is the kind of work that gets quietly abandoned.

Ownership and Operating Cadence

A register without an owner and a rhythm is a document. The register becomes real only when four roles and three cadences are named explicitly.

Four Roles That Must Exist

Register owner: Typically the platform team lead. Accountable for the register's accuracy and the reconciliation pipeline.
Governance lead: Owns the policies, the schema, the collection taxonomy, and the decommission authority.
Identity team liaison: Owns the Entra Agent ID blueprint, sponsorship model, and Conditional Access scoping.
Business owner (per agent): Accountable for purpose, re-attestation, and the decision to retire.

Three Cadences That Keep It Honest

Weekly platform review: New agents triaged, owners confirmed, collections assigned, risk signals checked, quarantine triggered on anomalies.
Quarterly business re-attestation: Each business owner re-confirms purpose, data access, and continued need. Non-response is a decommission trigger.
Annual governance review: Schema, taxonomy, and policy refreshed against platform changes and the organization's AI maturity.

Quarantine and decommission authority deserve a separate note. Pre-agree with business sponsors that the governance lead can quarantine any agent that fails risk signals, loses its sponsor, or misses two attestation cycles. Negotiating that authority per incident is how governance programs stall.

The Mid-Market Execution Lane

Microsoft's full governance stack assumes you have purchased Microsoft 365 E7 or added Microsoft Agent 365. The licensed stack unlocks risk signals from Entra Identity Protection, Purview, and Defender flowing into the Agent Registry. It is powerful, and it is also a cost gate many mid-market organizations will not clear in year one.

Entra Agent ID (free with existing Entra licensing): gives you the directory objects, audit logging, Conditional Access targeting, and sponsorship. This is the foundation.
Copilot Studio inventory and Dataverse queries: gives you the agent-side records and the ability to reconcile.
A Dataverse table (or SharePoint list) that holds the BabyBots schema: gives you the register itself, with a Power Automate flow syncing identity and inventory on a weekly cadence.

You can add Agent 365 later when the business case is clear. What you cannot do later, cheaply, is reconstruct ownership for 400 agents whose makers left the organization. Build the register in the lane your licensing supports today.

The BabyBots Agent Register Maturity Ladder

The register that works at 30 agents is not the register that works at 3,000. Mapping your current state against a maturity ladder clarifies which practices to adopt now and which to defer.

Stage 0: Pre-Register (Under 20 Agents)

Reality: No inventory. Ownership is tribal knowledge. Service principals from the pre-May-2026 era still exist.
Priority: Export every existing agent from Copilot Studio, name an owner for each, and migrate legacy identities using Microsoft's documented path. There is no fully automated in-place migration from legacy service principals to Entra Agent IDs, so this is manual batch work. Do it now, while the batch is small.

Stage 1: Catalog (20 to 100 Agents)

Reality: Spreadsheet or SharePoint list. Named owners. No cadence.
Priority: Adopt the full BabyBots schema. Name the four roles. Start the weekly platform review. Define the collection taxonomy before growth forces an ugly retrofit.

Stage 2: Operate (100 to 500 Agents)

Reality: Authoritative register in Dataverse. Weekly review running. Quarantine triggers defined.
Priority: Automate reconciliation across Entra, Power Platform, and Dataverse. Begin quarterly business re-attestation. Add risk tiering to connectors. Evaluate Agent 365 licensing against observed risk and audit demand.

Stage 3: Automate (500+ Agents)

Reality: Graph API-synced register. Policy-driven collection assignment. SLA-based decommission.
Priority: Multi-agent dependency mapping. Automated risk-signal response. Integration with the broader AI governance operating model, including shadow AI remediation flows.

Most enterprise tenants are at Stage 0 or Stage 1 today. The ladder is not aspirational. It is a map of the next 18 months.

A 30/60/90-Day Execution Plan

If a steering committee asks what the register program looks like this quarter, this is a defensible answer.

Days 1-30: Baseline and Decisions

Export every Copilot Studio agent in every environment. Note the identity type (Entra Agent ID or legacy service principal).
Name a register owner, a governance lead, and an identity team liaison.
Decide the collection taxonomy (business unit as primary, data sensitivity as overlay is a safe default).
Stand up the register in Dataverse or SharePoint using the BabyBots schema.
Assign a business owner to every existing agent. Agents without an owner after 30 days enter quarantine.

Days 31-60: Operate and Reconcile

Start the weekly platform review. Triage every new agent within seven days of creation.
Build the Entra-to-Power-Platform-to-Dataverse reconciliation flow. Automate the join.
Define quarantine triggers and decommission authority in writing. Get sponsor sign-off.
Begin legacy service principal migration in batches of ten.

Days 61-90: Mature and Measure

Run the first quarterly business re-attestation.
Add connector risk tiering. Score every agent.
Produce the first register report for the executive sponsor: total agents, agents without owners, agents in quarantine, risk-tier distribution, and decommission activity.
Decide whether Agent 365 licensing is justified by observed risk and audit demand.

Ninety days from a cold start is a credible timeline to Stage 1 maturity for most organizations. BabyBots typically runs the first 90 days as a managed service while the client's platform team ramps, then transitions ownership once the cadence is sustainable. This piece is the identity and inventory node in a broader Copilot Studio governance architecture that also covers environment zoning, DLP, and shadow AI remediation.

Frequently Asked Questions

What is the difference between an Entra Agent ID and a Copilot Studio agent register?

The Entra Agent ID is the automatic identity Microsoft assigns to every Copilot Studio agent in your directory. The register is the operating artifact you build on top of it: a tenant-wide record of each agent, its business owner, its data access, its lifecycle state, and the metadata Entra does not capture. Microsoft provides the identity. You own the register.

Can we build a Copilot Studio agent register without Microsoft Agent 365?

Yes. The Entra Agent ID, Copilot Studio inventory, and Dataverse are enough to run a credible register. Agent 365 and Microsoft 365 E7 add risk signals from Entra Identity Protection, Purview, and Defender, plus the Agent Registry UI in the Microsoft 365 admin center. Those are valuable, but they are an acceleration, not a prerequisite. Mid-market organizations should start the register in the lane their current licensing supports.

What happens to our legacy Copilot Studio agents that still use app-registration service principals?

They continue to function, but they do not benefit from the new identity governance surface. Microsoft provides a migration path, but there is no fully automated in-place migration. Expect to migrate in batches via Power Platform Advisor, PowerShell, or the Power Platform API. Do it while the inventory is small.

Who should own the agent register inside IT?

The register owner is typically the platform team lead, accountable for accuracy and reconciliation. The governance lead owns the schema, taxonomy, and decommission authority. The identity team owns the Entra Agent ID blueprint and sponsorship model. Business owners are accountable per agent. If these four roles are not named, the register will not survive the first quarter of growth.

How often should the register be reviewed?

Three cadences work: a weekly platform review for new agents and risk signals, a quarterly business re-attestation where each owner re-confirms purpose and access, and an annual governance review of schema and policy. Missing two consecutive attestation cycles should automatically trigger quarantine.

What is the single biggest mistake organizations make with agent governance?

Waiting. Treating the register as a problem for when agent counts become unmanageable. The economics run the other direction. Register discipline at 30 agents is cheap. Register reconstruction at 300 agents is expensive and incomplete. The May 2026 identity change gave every organization a clean starting point. The window to use it does not stay open.

Sources

Microsoft Learn: Manage Entra Agent IDs for Copilot Studio: https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-use-entra-agent-identities
Microsoft Learn: Migrate Copilot Studio agents to Microsoft Entra Agent ID: https://learn.microsoft.com/en-us/microsoft-copilot-studio/govern-migrate-api-entra-agent-identity
Microsoft Learn: Governing Agent Identities in Microsoft Entra ID Governance: https://learn.microsoft.com/en-us/entra/id-governance/agent-id-governance-overview
Microsoft Learn: Agent Registry in Microsoft 365 admin center: https://learn.microsoft.com/en-us/microsoft-365/admin/manage/agent-registry
Microsoft Learn: Governance and lifecycle actions for agents: https://learn.microsoft.com/en-us/microsoft-365/admin/manage/agent-actions
Gartner: 40% of Enterprise Apps Will Feature Task-Specific AI Agents by 2026: https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025
Deloitte 2025 Global AI Governance Survey, referenced via industry synthesis.

The Executive Takeaway

The identity layer is already in your tenant. The register is not. That gap is the entire governance opportunity for the next 12 months.

Automatic Entra Agent IDs are the first time Microsoft has handed enterprises a clean, directory-level foundation for AI agent governance. The organizations that use it well will treat the register as an operating artifact, define schema and ownership before growth demands them, and run the weekly cadence long enough for it to become unremarkable. The organizations that wait will find themselves, 18 months from now, trying to assign owners to agents whose makers left two re-orgs ago.

Build the register this quarter. Start with the agents you can still name owners for. The window closes quietly, one unmanaged agent at a time.