Migrate Copilot Studio agents to Microsoft Entra Agent ID

On August 24, 2026, we initiated the gradual roll out of self-service migrations to Microsoft Entra Agent IDs for Copilot Studio agents in Power Platform Advisor. Beginning on September 2026, automatic migrations of agents without Entra Agent ID to Microsoft Entra Agent ID were also initiated. Copilot Studio agents created before May 2026 may still use legacy app-registration identities. We recommend migrating any of your remaining agents to Microsoft Entra Agent ID.

How does this affect me?
Migrating your agents to Microsoft Entra Agent ID helps your organization build, discover, govern, and protect agent identities across services by using a unified platform.

Key benefits include:

• Audit logging in Microsoft Entra ID.
• Agent lifecycle management.
• Integration with Entra ID Governance.
• Visibility of connector permissions as API permissions on the agent identity, so Entra and Microsoft 365 admins can see what an agent can do without opening Power Platform admin center.
• Ability to target those connector permissions with Microsoft Entra Conditional Access policies (for example, network location, device compliance, or risk conditions).

To find out if your agent has been migrated already been migrated or if there are any agents that remain to be migrated in your tenant, you can use the Advisor recommendation.

What action do I need to take?
We recommend identifying and migrating your eligible agents to Microsoft Entra Agent ID. To perform this mitigation, please follow the steps listed below:

1. Confirm that Power Platform inventory is enabled for your tenant.
2. In the Power Platform admin center, go to Actions > Recommendations > Active, and open Migrate Copilot Studio agents to Microsoft Entra Agent ID for enhanced agent governance.
3. In the recommendation pane, expand Why is this important?, and review the migration guidance.
4. Review the eligible agents. Use Suggested migration order and Migration notes to choose an initial pilot or the next migration batch. The table also provides information such as environment, environment type, owner, recent activity, and authentication method.
5. Select the checkbox next to each agent you want to migrate. You can select one agent or multiple eligible agents. The Migrate button becomes available and the action bar shows the number of agents selected.
6. Select Migrate, review the confirmation, and confirm the migration. Start with a small batch of noncritical agents.
7. Review the Action, Action state, and Action date columns for each selected agent. To review actions across recommendations, select the Action history tab.
8. Coordinate a validation window with the makers who own the agents.
9. After migration, validate each agent's channels, authentication, actions, connectors, flows, and integrations before migrating another batch.
10. Review Microsoft Entra sign-in logs and applicable Conditional Access results. If an agent does not pass validation, revert it before continuing.

This message is for awareness, and no action is required.

For more information, please visit Migrate Copilot Studio agents to Microsoft Entra Agent ID.