Microsoft Copilot Studio: Agent ownership reassignment

Originally posted by Microsoft Sep 30, 2025 Uncategorized 0 Comments

Starting October 2025, Global and AI Administrators can reassign ownership of shared agents in Microsoft Copilot Studio and M365 Agents Toolkit to licensed users. The new owner gains full control and access; the previous owner loses all rights. Rollout occurs in two phases during October 2025.

Introduction:

Starting in October 2025, Global Administrators and AI Administrators will gain the ability to reassign ownership of shared agents created within the organization. This update improves administrative control and ensures continuity in agent management, especially when employees transition or leave.

This message is associated with Microsoft 365 Roadmap ID 502867.

When this will happen:

How this affects your organization:

Who is affected: Global Administrators and AI Administrators managing agents in Copilot Studio (Lite and full) and M365 Agents Toolkit.

What will happen:

• Admins can reassign ownership of shared agents to another user.
• Ownership can only be reassigned to users with an active Microsoft 365 Copilot license.
• The new owner will receive full edit and delete permissions.
• The new owner will gain access to any uploaded files associated with the agent.
• The previous owner will lose all access, including read-only rights.
• Phase 1 (Early October): Applies to agents created in Copilot Studio (Lite).
• Phase 2 (Late October): Applies to agents created in Copilot Studio (full) and M365 Agents Toolkit.

What you can do to prepare:

Screenshot 1 – Admin view for reassigning agents to a new owner: 

View image in new tab

Screenshot 2 – New owner’s view showing the agent available for editing:

 View image in new tab

• Review shared agents in your environment.
• Plan reassignment workflows for agents tied to departing or transitioning employees.
• Ensure reassigned users have active Microsoft 365 Copilot licenses.
• Communicate this change to helpdesk or support teams.
• Update internal documentation if needed.

Compliance considerations:

Message ID: MC1162291