Naming the Swarm
A governance-first naming convention for your fleet of M365 Copilot agents.
“Battle-tested in production environments.”
The situation
You licensed Copilot Studio. Makers started building. Six months later you pull the Agent Registry export and it is four thousand rows of New Agent, cr8a3_copilot1, and Copilot final (2). You cannot tell a read-only personal helper from a finance agent touching confidential data.
Here is the part that hurts: the system name locks the moment the agent is created. No rename fixes it. The convention has to be right the first time.
What this is
Agent naming looks cosmetic and is actually a governance control. The name is the one field that surfaces in every inventory, every audit log, and every mention box in Teams. This is the convention, and the reasoning that makes it defensible to whoever asks.
What is inside
- The naming convention itself
- The reasoning behind each field, so you can defend it
- What to do about the agents already named badly
Who it is for
- Platform owners standing up Copilot Studio before makers scale
- Governance leads who have to answer inventory questions
Who it is not for
- Estates with a handful of agents and no plans to grow. The problem this solves is a scale problem.
Questions people actually ask
We already have four thousand badly named agents. Is it too late?
For those agents, the schema name is locked and the book says so plainly rather than pretending otherwise. What it gives you is the convention going forward and the triage approach for the existing estate.
Is the convention specific to Copilot Studio?
The field structure is shaped by what Copilot Studio exposes in its registry, so yes in the specifics. The governance argument transfers to any agent platform with an inventory.
Buying this with a company card?
Most buyers expense it. Your receipt email carries a Generate link that opens an invoice generator: add your billing address, put your legal company name and any reference your finance team needs in the Additional notes box, and download the PDF. If you have an EU VAT number, enter it at checkout and no VAT is charged. Here is the approval email, so you do not have to write one.
Subject: Approval request: Naming the Swarm ($39, one-time) Hi [Manager], I would like to expense a one-time $39 purchase: Naming the Swarm by Kesslernity. What it is: A governance-first naming convention for your fleet of M365 Copilot agents. What we get: - The naming convention itself - The reasoning behind each field, so you can defend it - What to do about the agents already named badly Why it is worth it: it is a one-time purchase with future updates included, and it costs less than an hour of any consultant we would otherwise ask. The author publishes the open-source Copilot prompt library that Microsoft's CMO for AI at Work cited as "battle-tested in production environments". A downloadable invoice is available from the purchase receipt for expenses. [Your name]
Naming the Swarm
A governance-first naming convention for your fleet of M365 Copilot agents.
Get it for $39Licensed, not sold. The full License & Terms apply. Kesslernity is an independent publisher: this is independent analysis, not affiliated with, sponsored by, or endorsed by Microsoft. It is practitioner guidance, not professional, legal, or financial advice.
Often bought alongside
Govern Your Agents
One agent, two governance problems. Naming the Swarm plus the Agent Instruction Block guide.
$47→Agent Instruction Block Design Guide
Write agent instructions that behave. The fiftieth user gets the same result you did on day one.
$19→Copilot Agent Pack, Vol. 1
Six governed Copilot Studio agents, finished for governance rather than for a demo.
$49→