A Copilot Studio agent owned by a disabled user

Copilot Studio agent is owned by a disabled user account.

Disabling an account does not reassign what it owns, so the agent keeps pointing at someone who is gone: nobody is accountable for it, and the review and cleanup paths run through the owner. Agents built during a proof of concept and left behind are the common case.

This reports the ownership gap and does not claim the agent is broken. Whether it still works depends on how each of its tools connects, and Pathix reads that much, recording each tool's connection reference and whether it runs on its maker's credentials or the caller's; whether the credential behind a connection still works is not read.

List bot rows with their owner and join the owner to systemuser, filtering to disabled accounts. Exclude the platform's built-in SYSTEM and INTEGRATION accounts, which are stored disabled by design.

Reassign the agent to an active owner, preferably a service account or a team, or delete it if it is no longer wanted; add agent reassignment to offboarding alongside flows and apps.

This is a security finding that carries no SOC 2, ISO 27001, NIST 800-53 or CMMC reference. That is a decision rather than an omission. Pathix maps a finding to a control only where the mapping is defensible to an assessor, and a stretched one would undermine every mapping that is real.

• A disabled user account that still holds security roles
• A disabled user who still has records shared with them
• A flow or workflow owned by a disabled user
• An AI Builder model or prompt owned by a disabled user