Exercise - Reassign an active agent's owner
An already-active Agent Builder agent in Relecloud's Registry still has its original owner assigned, but that person has since left the team.
Important
Prerequisites for this exercise:
- A Microsoft 365 tenant with AI Administrator (or Global Administrator) access.
- An already-active Agent Builder or Copilot Studio agent pre-seeded for the lab, with a second account available to become the new owner.
Task 1: Reassign the agent's owner
- Sign in to the Microsoft 365 admin center at admin.microsoft.com, go to Copilot > Agent Registry (or the equivalent surface in your tenant), and open the active agent whose owner has left.
- Select Manage > Reassign owner (or the equivalent action in your tenant's Registry actions menu).
- Select the new team member as the agent's owner, and confirm the change.
- Reload the agent's details page and confirm the new owner now shows as the agent's owner of record.
Task 2: Confirm the previous owner's access is removed
- If your lab allows it, sign in as (or review the permissions of) the previous owner's account.
- Confirm they no longer have owner-level management access to this specific agent—reassignment doesn't just add a new owner alongside the old one, it replaces the owner of record.
- Reflect: This is exactly the kind of ongoing Registry curation the one-time onboarding process never covers—agents that are already active still need their ownership kept current as people change roles or leave, the same way you'd update ownership on any other governed resource.
You've now reassigned an active agent's owner to a current team member and confirmed the previous owner's access was removed—closing a gap the initial onboarding flow was never designed to catch.