As Copilot Autopilot enters private preview this week, Microsoft has made something quietly mandatory that most developers haven’t fully processed: every Copilot Studio and Foundry agent now requires its own Microsoft Entra identity. Since July 2026, the opt-out is gone. Your AI agents are no longer just app registrations — they are directory objects with email addresses, OneDrive storage, and a position on the org chart. If you built Copilot Studio agents before May 2026, those are still running on legacy identities. Microsoft is pushing you to migrate them, and the governance gap between migrated and unmigrated agents is worth understanding before Autopilot expands further.
What an Entra Agent Identity Actually Is #
Microsoft Entra Agent ID is a new identity type — distinct from a user, a group, or a service principal. Copilot Studio began auto-creating these identities for all new agents on March 18, 2026. Since July 2026, the opt-out was removed, making it mandatory for every new agent across Copilot Studio and Microsoft Foundry.
For Foundry Autopilot agents specifically, an Entra Agent ID comes with a full productivity license: a dedicated Exchange mailbox, calendar, OneDrive storage, Teams access, and an entry in the organizational directory. The agent shows up the way a human employee does — not as a generic service account. Actions taken by the agent are attributed to that specific identity in the audit log, not to a shared registration that could be any of a dozen agents you have deployed. That attribution is the real win here. Shared service accounts for agents are a security antipattern that enterprises have known about for years with human identities — every action is ambiguous, every audit is a guessing game. Per-agent identities fix that. The governance overhead is real, but the alternative is unattributable access at scale across 30 million M365 Copilot seats.
Legacy Agents Are Still Running Without It #
If your team deployed Copilot Studio agents before May 2026, those agents are likely still operating on legacy app-registration identities. Microsoft has not set a hard enforcement deadline publicly, but Message Center notice MC1462458 documents the migration requirement and calls it “recommended.” Given that the opt-out for new agents was removed in July, enforcement for existing agents is coming. The migration path runs through the Power Platform admin center or through PowerShell using the Power Platform APIs. Once migrated, agents appear under Agent IDs in the Entra admin center, where you can apply Conditional Access policies, set lifecycle rules, and run access reviews — the same controls you would apply to a user account. Agents still on legacy registrations are invisible to these controls, which means no Conditional Access, no attributable audit trail, and a governance gap that Defender XDR for AI cannot fully close.
Org-Wide Publishing Now Requires Registry Approval #
Publishing a Copilot Studio agent to your entire organization now requires IT sign-off through the Agent Registry in the M365 admin center. The path is: M365 admin center > Agent 365 > Agent registry. Unapproved agents simply do not surface to users at org scope.
This is a new constraint that landed alongside the Autopilot preview launch. Previously, org-wide publishing was more permissive. If your team is used to shipping agents to the org without an IT approval step, that workflow no longer works. Build the registry approval step into your agent deployment pipeline now. Both Copilot Studio and Foundry agents appear in the registry, giving IT a single place to inventory, approve, and disable agents across the tenant.
The New Cost Line: UBB for Every Agentic Feature #
Starting with the Copilot overhaul announced September 25, agentic features — Cowork, Code, and Autopilot — run on usage-based billing, not the flat per-user license that covers everyday Copilot chat. Copilot Credits cost $0.01 each and are consumed by context retrieval, tool calls, model inference, and session duration. The meter runs during context retrieval, not just generation — a task that feels like ten seconds of work may have spent most of that time reading email threads and file contents.
Foundry Autopilot agents also carry the cost of a productivity license per agent. At the governance layer, Agent 365 is $15 per user per month as a standalone add-on. Teams that do not set spending caps before Autopilot reaches their tenant will see billing surprises. The M365 admin center cost management dashboard supports tenant-level, group-level, and user-level spending limits. Set them now, before preview expands.
What to Configure Before Autopilot Reaches Your Org #
- Inventory your agents. Check which Copilot Studio agents have Entra Agent IDs and which are on legacy app registrations. The Entra admin center Agent IDs section is the authoritative list.
- Migrate legacy agents. Use the Power Platform admin center or the MC1462458 migration path. Waiting for a hard enforcement deadline leaves governance gaps open in the meantime.
- Apply Conditional Access to agent identities. Once migrated, agents are subject to the same Conditional Access framework as users. Apply location restrictions, device compliance where applicable, and schedule access reviews.
- Review the Agent Registry. Ensure that agents intended for org-wide deployment are approved. Unapproved agents are invisible to users at org scope.
- Set UBB spending limits. In the M365 admin center, configure tenant- and group-level caps before Autopilot begins consuming Copilot Credits in your environment.
The move to agent-first identities is the correct architectural decision. Agents that act through shared service accounts or borrowed credentials create audit ambiguity that security teams have spent years trying to eliminate in the human-identity layer. Applying the same model to AI agents is overdue. The friction of migrating and governing these identities is the price of that accountability — and it is a price worth paying before Autopilot exits preview and starts acting on behalf of your organization around the clock.