What do we do about ownerless agents?

That’s a genuine concern, and you’re not alone. Agents outlive their makers the way shared mailboxes used to — except these ones still answer questions and can hold permissions.

Here’s what’s happening. Shared agents become ownerless when the creator is deleted from the organisation. The Microsoft 365 admin centre Agent Registry surfaces an Agents without owners count and a one-click filter so you can triage. From there, admins can assign a new owner, block, or delete (capabilities vary by platform — Agent Builder / Copilot Studio shared agents are the main reassignment path). Separately, Microsoft Entra Agent ID guidance pushes human sponsors and owners, registration of agents, naming conventions, and periodic access reviews so orphaned identities don’t accumulate. Registry experiences are converging under Agent 365 while Entra remains the identity foundation — expect portal names to keep shifting.

This is Second Law for organisational AI: an agent barely “exists” as a controlled asset without a second copy of accountability — a living human owner (and ideally a sponsor) in the register. Steady before scale means Pane 04 Security and GRC own the reclaim path before makers multiply ghosts.

Practical options:

1. Triage the ownerless queue this week. Filter Agents without owners; block anything with no business contact; reassign the rest to a named service owner with a Copilot licence where required. Fast and visible.
2. Standing lifecycle rule. No production share without owner + purpose + reclaim date; quarterly review of inactive or orphaned agents; Entra lifecycle workflows for sponsor hand-off when people leave (where licensed / available). Moderate effort; stops the next leavers wave.
3. Hard freeze on new shared agents until the backlog is zero. Theoretically clean; politically costly if useful agents are collateral. Use as a time-boxed escalation, not a lifestyle.
4. Ignore ownerless until there’s an incident. Quiet until it isn’t. I’d discourage this.

The caution: Blocking a SharePoint- or Foundry-built agent may mainly remove it from Copilot Chat, not delete every file on the site — read the platform notes before you assume “blocked” means gone. Entra Agent ID and Agent 365 features may still be preview or Frontier-gated in your tenant; verify licence and rollout before promising sponsors to the board.

I’d suggest a two-slide story for leadership: slide one is today’s ownerless count and actions (block / reassign); slide two is the standing rule — every shared agent needs an owner in the register the way every privileged account needs one. Sprawl shrinks when reclaim is boring and routine.

Good on you for noticing before the audit does — you’ll sleep better when every agent has a name attached.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer