Recreate Copilot Studio agents with Microsoft Entra Agent ID
In brief
The article now distinguishes supported platform migration options from a separate manual recreate-and-deprecate process. New agents receive an Agent ID automatically, and the former tenant opt-in prerequisite is removed.
What Entra admins need to know
For older agents using legacy service principals, review platform migration options before manual recreation. If proceeding, reconfigure and test the replacement, then plan cutover and rollback before retiring the legacy agent.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
title: Recreate Copilot Studio agents with Microsoft Entra Agent ID
titleSuffix: Microsoft Entra Agent ID
description: Learn how to recreatePlan a manual recreation of Microsoft Copilot Studio agents with Microsoft Entra Agent ID for enhanced governanceID, validate the replacements, and security. No in-place migration path exists today.safely retire legacy identities.
ms.topic: how-to
ms.date: 06/15/11/05/2026
ms.custom: msecd-doc-authoring-1013
ai-usage: ai-assisted
#customer intent: As an IT admin or Copilot Studio maker, I want to understand how to recreate my Copilot Studio agents with Microsoft Entra Agent ID so that I can take advantage of agent-specific governance, Conditional Access, and audit capabilities.
Recreate Copilot Studio agents in Microsoft Entra Agent ID
Some older agents created in Microsoft Copilot Studio authenticate by using platform-managed service principals. Theseprincipals rather than agent identities. New agents could have been created before Copilot Studio began automatically creating agent identities for all new agents, which happened on March 18, 2026. These agents could have also been created before your organization opted in to thereceive an Agent ID automatically. For current lifecycle behavior, see Manage Microsoft Entra Agent IDs in Copilot Studio or if your organization opted out of creating agent identities..
These service principals let agents communicate with Azure Bot Service, Microsoft Teams, and Bot Framework skills, but Microsoft Entra treats these service principals as standard applications, not as AI agents. Adopting Microsoft Entra Agent ID gives you agent-specific governance, including Conditional Access policies, centralized audit logging, and lifecycle management.
This article describes the manual process of recreating Copilot Studio agents with Microsoft Entra Agent ID and decommissioning the legacy service principals. Because Copilot Studio manages the agent code, credentials, and deployment lifecycle, this process differs from custom-built agents. For agents where you own the code and identity configuration, see Migrate custom app registrations to Agent ID.
Prerequisites
Before you begin, make sure you meet the following requirements:
- One or more Copilot Studio agents that use legacy service principals, created before March 18, 2026 or before your tenant opted in to Microsoft Entra Agent ID.
- Access to the Copilot Studio admin center and the Microsoft Entra admin center.
- Agent ID Developer or Agent ID Administrator role in Microsoft Entra to manage agent identities.
- Microsoft Entra Agent ID integration enabled for your tenant in Copilot Studio.
- Familiarity with Microsoft Entra Agent ID key concepts
Prerequisites
Before you begin, make sure you meet the following requirements:
- One or more Copilot Studio agents that use legacy service principals and that you've selected for manual recreation after reviewing the platform migration options.
- Access to the Copilot Studio admin center and the Microsoft Entra admin center.
- Agent ID Developer or Agent ID Administrator role in Microsoft Entra to manage agent identities.
- Permission to create and configure replacement agents in the relevant Copilot Studio environment.
- Familiarity with Microsoft Entra Agent ID key concepts.
Licensing requirements
| Microsoft Entra Agent ID action | Create blueprint + agent identity through Graph API, update your code | Create a new agent with Microsoft Entra Agent ID integration enabled, then manually reconfigure | | Rollback strategy | Revert code to use old app registration | Keep the legacy agent active until the new agent is fully validated |
Because Copilot Studio manages the identity lifecycle, you candon't create a blueprint and agent identity directly as you would for a custom agent. There's no in-place conversion that transforms an existing service principal into an agent identity, and republishing an existing agent doesn't create an agent identity. Instead, you mustFor the manual recreation path described here, create a new agent in Copilot Studio with Microsoft Entra Agent ID integration enabled, manuallyStudio, reconfigure allits channels and connections, and then decommission the legacy agent. Use the platform documentation for supported migration of an existing agent.
Review the process phases
|---|---|---|
| Low | No sign-in activity in 30+ days, no active conversations, agent in draft or unpublished state. | Candidate for cleanup. Decommission the agent and its service principal directly; no migration needed. |
| Medium | Some recent conversation activity, noncritical business function, identifiable owner. | Candidate for recreation with Microsoft Entra Agent ID. Proceed through Phase 3 with standard validation. |
| High | Active daily conversations, production business workflows dependent on the agent, integrated with Teams or customer-facing channels. | Don't recreate at this time. SeeReview supported platform migration options and the safeguards for production-critical agents. before choosing manual recreation. |
The 30-day sign-in threshold is based on Microsoft Entra's default retention period. If your organization has extended audit log retention (through Microsoft Sentinel or another SIEM), adjust thresholds accordingly.
Production-critical agents
For Copilot Studio agents with high usage, don't recreate them until Microsoft provides an official automatedcheck the current platform migration path. There's no automated migration path, and theoptions before considering manual recreation. Manual recreation process carries significant risk for production agents. Maintain these service principals as-isKeep the existing agent active until you have an official automated migration path is available.approved cutover and rollback plan and have validated the replacement.
The risks specific to high-usage Copilot Studio agents include:
Phase 3: Recreate the agent with Microsoft Entra Agent ID
For medium-usage Copilot Studio agents, complete the following seven-step recreation procedure:
Use this documentation as your checklist to re-establish every item on the new agent.
Step 3: Confirm the recreation decision
Confirm with the agent owner that manual recreation, rather than a supported platform migration, is appropriate. Agree on test channels and a rollback path before configuring the replacement. New Copilot Studio agents receive an Agent ID automatically; don't look for an opt-in setting or create a separate blueprint.
Step 4: Create a new agent with Microsoft Entra Agent ID
In Copilot Studio, create a new agent. This new agent receives a native agent identity during provisioning. Recreate the agent's topics, knowledge sources, and configuration to match the legacy agent.
- Unpublish or delete the agent in Copilot Studio. This step ensures the platform stops authenticating on behalf of the agent.
- Remove API permissions from the old app registration.
- Follow the Copilot Studio identity lifecycle guidance for platform-managed credentials. Don't change those credentials independently of the platform lifecycle.
- Delete the app registration (enters 30-day soft-delete).
- After 30 days, confirm permanent deletion or hard-delete if needed.
| Symptom | Likely cause | Resolution |
|---|---|---|
| New Agent ID doesn't appear in Microsoft Entra admin center after creating the agent | The identity hasn't been located or provisioning needs investigation. | Check Settings > Advanced > Metadata > Entra Agent ID in Copilot Studio and use that ID to locate the identity. If the ID is missing, contact Copilot Studio support before creating another replacement. |
| Agent stops responding after switchover | Channel configurations still reference the old SP's application ID. | Update channel configurations to reference the new agent's identity. Check Teams app manifest and web chat embed codes. |
| Connection reference errors | Connectors were authorized against the old SP and need reauthorization with the new identity. | Reauthorize each connection reference in Copilot Studio using the new agent's identity. |
| Power Automate flows fail | Flows reference the old SP's application ID or service principal. | Update flow connections and triggers to use the new agent's identity. |
@@ -1,9 +1,9 @@ --- title: Recreate Copilot Studio agents with Microsoft Entra Agent ID titleSuffix: Microsoft Entra Agent ID-description: Learn how to recreate Microsoft Copilot Studio agents with Microsoft Entra Agent ID for enhanced governance and security. No in-place migration path exists today.+description: Plan a manual recreation of Microsoft Copilot Studio agents with Microsoft Entra Agent ID, validate the replacements, and safely retire legacy identities. ms.topic: how-to-ms.date: 06/15/2026+ms.date: 11/05/2026 ms.custom: msecd-doc-authoring-1013 ai-usage: ai-assisted #customer intent: As an IT admin or Copilot Studio maker, I want to understand how to recreate my Copilot Studio agents with Microsoft Entra Agent ID so that I can take advantage of agent-specific governance, Conditional Access, and audit capabilities.@@ -11,23 +11,23 @@ ai-usage: ai-assisted # Recreate Copilot Studio agents in Microsoft Entra Agent ID -Some agents created in Microsoft Copilot Studio authenticate by using platform-managed service principals. These agents could have been created before Copilot Studio began automatically creating agent identities for all new agents, which happened on March 18, 2026. These agents could have also been created before your organization opted in to the [Microsoft Entra Agent ID integration with Copilot Studio](/microsoft-copilot-studio/admin-use-entra-agent-identities) or if your organization opted out of creating agent identities.+Some older agents created in Microsoft Copilot Studio authenticate by using platform-managed service principals rather than agent identities. New agents receive an Agent ID automatically. For current lifecycle behavior, see [Manage Microsoft Entra Agent IDs in Copilot Studio](/microsoft-copilot-studio/admin-use-entra-agent-identities). These service principals let agents communicate with Azure Bot Service, Microsoft Teams, and Bot Framework skills, but Microsoft Entra treats these service principals as standard applications, not as AI agents. Adopting Microsoft Entra Agent ID gives you agent-specific governance, including Conditional Access policies, centralized audit logging, and lifecycle management. This article describes the manual process of recreating Copilot Studio agents with Microsoft Entra Agent ID and decommissioning the legacy service principals. Because Copilot Studio manages the agent code, credentials, and deployment lifecycle, this process differs from custom-built agents. For agents where you own the code and identity configuration, see [Migrate custom app registrations to Agent ID](migrate-custom-app-registrations-to-agent-id.md). -> [!IMPORTANT]-> At this time, there is no automated or in-place migration path to convert an existing Copilot Studio agent's service principal to an agent identity. To use Microsoft Entra Agent ID with Copilot Studio, you must **create a new agent** with the Agent ID integration enabled, manually reconfigure the agent, and then decommission the legacy agent. This article describes that recreate-and-deprecate process.- ## Prerequisites +> [!IMPORTANT]+> Before choosing manual recreation, review the current [Copilot Studio migration options](/microsoft-copilot-studio/govern-migrate-api-entra-agent-identity). This article covers a separate recreate-and-deprecate process, not the platform's self-service migration procedure. Manual recreation creates a new agent with new identity and channel references; keep the legacy agent available until you validate its replacement.+ Before you begin, make sure you meet the following requirements: -- One or more Copilot Studio agents that use legacy service principals, created before March 18, 2026 or before your tenant opted in to Microsoft Entra Agent ID.+- One or more Copilot Studio agents that use legacy service principals and that you've selected for manual recreation after reviewing the platform migration options. - Access to the **Copilot Studio admin center** and the **Microsoft Entra admin center**. - **Agent ID Developer** or **Agent ID Administrator** role in Microsoft Entra to manage agent identities.-- Microsoft Entra Agent ID integration enabled for your tenant in Copilot Studio.+- Permission to create and configure replacement agents in the relevant Copilot Studio environment. - Familiarity with [Microsoft Entra Agent ID key concepts](key-concepts.md). ### Licensing requirements@@ -52,7 +52,7 @@ Copilot Studio agents require a different approach than custom agents: | **Microsoft Entra Agent ID action** | Create blueprint + agent identity through Graph API, update your code | Create a new agent with Microsoft Entra Agent ID integration enabled, then manually reconfigure | | **Rollback strategy** | Revert code to use old app registration | Keep the legacy agent active until the new agent is fully validated | -Because Copilot Studio manages the identity lifecycle, you can't create a blueprint and agent identity directly as you would for a custom agent. There's no in-place conversion that transforms an existing service principal into an agent identity, and republishing an existing agent doesn't create an agent identity. Instead, you must create a new agent in Copilot Studio with Microsoft Entra Agent ID integration enabled, manually reconfigure all channels and connections, and then decommission the legacy agent.+Because Copilot Studio manages the identity lifecycle, don't create a blueprint and agent identity directly as you would for a custom agent. For the manual recreation path described here, create a new agent in Copilot Studio, reconfigure its channels and connections, and then decommission the legacy agent. Use the platform documentation for supported migration of an existing agent. ## Review the process phases @@ -95,13 +95,13 @@ Classify each Copilot Studio agent by its usage level to determine the migration |---|---|---| | **Low** | No sign-in activity in 30+ days, no active conversations, agent in draft or unpublished state. | Candidate for cleanup. Decommission the agent and its service principal directly; no migration needed. | | **Medium** | Some recent conversation activity, noncritical business function, identifiable owner. | Candidate for recreation with Microsoft Entra Agent ID. Proceed through Phase 3 with standard validation. |-| **High** | Active daily conversations, production business workflows dependent on the agent, integrated with Teams or customer-facing channels. | **Don't recreate at this time.** See [Production-critical agents](#production-critical-agents). |+| **High** | Active daily conversations, production business workflows dependent on the agent, integrated with Teams or customer-facing channels. | Review supported platform migration options and the safeguards for [production-critical agents](#production-critical-agents) before choosing manual recreation. | The 30-day sign-in threshold is based on Microsoft Entra's default retention period. If your organization has extended audit log retention (through Microsoft Sentinel or another SIEM), adjust thresholds accordingly. ### Production-critical agents -For Copilot Studio agents with high usage, **don't recreate them until Microsoft provides an official automated migration path**. There's no automated migration path, and the manual recreation process carries significant risk for production agents. Maintain these service principals as-is until an official automated migration path is available.+For Copilot Studio agents with high usage, check the current platform migration options before considering manual recreation. Manual recreation carries significant risk for production agents. Keep the existing agent active until you have an approved cutover and rollback plan and have validated the replacement. The risks specific to high-usage Copilot Studio agents include: @@ -113,7 +113,7 @@ The risks specific to high-usage Copilot Studio agents include: ## Phase 3: Recreate the agent with Microsoft Entra Agent ID > [!WARNING]-> In-place migration of an existing Copilot Studio service principal to a Microsoft Entra Agent ID-native agent identity isn't supported. You must create a new agent in Copilot Studio with Microsoft Entra Agent ID integration enabled. Configuration, channels, and internal IDs don't carry over automatically.+> This manual recreation procedure creates a new agent; it doesn't convert the existing agent in place. Configuration, channels, and internal IDs don't carry over automatically. For **medium-usage** Copilot Studio agents, complete the following seven-step recreation procedure: @@ -133,13 +133,13 @@ Before making any changes, document: Use this documentation as your checklist to re-establish every item on the new agent. -### Step 3: Enable Microsoft Entra Agent ID integration+### Step 3: Confirm the recreation decision -Ensure your tenant opts in to Microsoft Entra Agent ID integration for Copilot Studio. Verify this setting in the **Copilot Studio admin center** or through your tenant's feature settings.+Confirm with the agent owner that manual recreation, rather than a supported platform migration, is appropriate. Agree on test channels and a rollback path before configuring the replacement. New Copilot Studio agents receive an Agent ID automatically; don't look for an opt-in setting or create a separate blueprint. ### Step 4: Create a new agent with Microsoft Entra Agent ID -In Copilot Studio, create a new agent with the Microsoft Entra Agent ID integration enabled. This new agent receives a native agent identity during provisioning. Recreate the agent's topics, knowledge sources, and configuration to match the legacy agent.+In Copilot Studio, create a new agent. This new agent receives a native agent identity during provisioning. Recreate the agent's topics, knowledge sources, and configuration to match the legacy agent. > [!NOTE] > Republishing or re-registering an existing agent does **not** create a Microsoft Entra agent identity. You must create a new agent to get a Microsoft Entra Agent ID-native agent identity.@@ -220,7 +220,7 @@ To decommission the legacy service principal, follow these steps: 1. **Unpublish or delete the agent in Copilot Studio.** This step ensures the platform stops authenticating on behalf of the agent. 1. Remove API permissions from the old app registration.-1. Delete or rotate client secrets and certificates on the old app registration.+1. Follow the [Copilot Studio identity lifecycle guidance](/microsoft-copilot-studio/admin-use-entra-agent-identities) for platform-managed credentials. Don't change those credentials independently of the platform lifecycle. 1. Delete the app registration (enters 30-day soft-delete). 1. After 30 days, confirm permanent deletion or hard-delete if needed. @@ -230,7 +230,7 @@ The following table lists common issues you might encounter during the recreate- | Symptom | Likely cause | Resolution | |---|---|---|-| New Agent ID doesn't appear in **Microsoft Entra admin center** after creating the agent | Agent ID integration might not be enabled for your tenant. | Verify tenant opt-in for Agent ID integration. Try creating the agent again. If the issue persists, contact Copilot Studio support. |+| New Agent ID doesn't appear in **Microsoft Entra admin center** after creating the agent | The identity hasn't been located or provisioning needs investigation. | Check **Settings** > **Advanced** > **Metadata** > **Entra Agent ID** in Copilot Studio and use that ID to locate the identity. If the ID is missing, contact Copilot Studio support before creating another replacement. | | Agent stops responding after switchover | Channel configurations still reference the old SP's application ID. | Update channel configurations to reference the new agent's identity. Check Teams app manifest and web chat embed codes. | | Connection reference errors | Connectors were authorized against the old SP and need reauthorization with the new identity. | Reauthorize each connection reference in Copilot Studio using the new agent's identity. | | Power Automate flows fail | Flows reference the old SP's application ID or service principal. | Update flow connections and triggers to use the new agent's identity. | 