Cannot Delete a Copilot Studio Agent? Check Dependencies and Permissions

Official documentation checked October 14, 2026.

A disabled Delete action or a failed deletion in Copilot Studio needs a diagnosis of the specific agent, environment, and error. There is no general-purpose “force delete” that safely bypasses dependencies. Do not delete an entire solution, all channel connections, or unrelated identity resources just to make one agent disappear.

1. Confirm what you are deleting and preserve what is needed

Record the environment ID, agent ID and name, owner, agent type, and any solution that contains it. Check whether you need permanent deletion or merely a change to how users discover and access the agent. Obtain the owner’s approval and identify connected processes that would stop working.

For an agent using the standard harness, Microsoft’s solution export procedure can preserve supported agent components. Export the appropriate unmanaged solution and include required dependencies, then validate an import in a separate suitable environment. An export is not a complete backup of every channel setting, connection, identity, or operational record. Do not promise recovery until the actual recovery method has been tested.

2. Use the documented deletion path for your agent type

Microsoft’s standard-harness agent deletion instructions use this web-app path:

1. Open Agents and select the exact agent in the correct environment.
2. On the top menu bar, open the three-dot menu next to Settings, then choose Delete.
3. Read the confirmation, enter the agent name, and select Delete agent only when the approved target is correct.

Deletion is permanent. This documented path does not require a universal Published-to-Stopped toggle or removal of every channel first. Classic Teams chatbots and other agent experiences have different interfaces; if the controls do not match, identify the experience before proceeding. Capture the actual error rather than repeatedly attempting unrelated removal steps.

3. Resolve solution dependencies without deleting unrelated data

Being included in a solution does not automatically make an agent a managed component. Check the solution type and layers. In Power Apps, select the correct environment, open Solutions, and inspect the relevant component. Use Show Dependencies where available to identify what requires it. A dependency must be resolved at its source with the dependent application’s owner, not bypassed. See Microsoft’s dependency tracking explanation.

For an unmanaged solution, removing a component from that solution is not necessarily deleting it from the environment. Deleting the unmanaged solution container leaves its customizations in place. For a managed solution, do not assume you can export it as a backup: installed managed solutions cannot be exported. Microsoft also warns that uninstalling one can remove custom tables and their data, or data in its custom columns. See managed and unmanaged solution behavior.

When a managed component should be retired, involve the solution publisher. Microsoft’s recommended approach is a planned solution upgrade that excludes the component in the source solution, after checking target-environment dependencies. An ordinary update does not remove omitted components. Test the upgrade and review its full deletion scope before production; uninstalling the entire solution is not a routine fix for one stuck agent.

4. Investigate access failures and verify the result

For a permissions error, have the environment administrator check the user’s actual access and privileges for this agent and operation. Do not assign broad administrative roles simply because a generic checklist names them. Record the timestamp, environment and agent IDs, and any correlation or operation ID for the support case.

Microsoft documents a separate failure where Conditional Access prevents cleanup of agent-related app registrations or service principals. Ask the identity and Power Platform administrators to investigate that specific failed operation. Any manual cleanup must identify the exact affected resources and their dependencies; do not disable Conditional Access or delete similarly named enterprise applications as a shortcut.

After a reported successful deletion, refresh the correct environment and verify the agent’s absence and the expected effect on its approved distribution points. If it reappears, compare IDs and check deployment/import history with the release owner. Re-creation or an incomplete operation needs evidence, not a blanket 24-hour wait or another solution deletion. Preserve the error and involve Microsoft support when the supported workflow remains blocked.