AI Agent Fleet Register

Register a team of AI agents in one sheet: each agent's names, who sponsors it, who owns it and who can switch it off, checked against Microsoft Entra's naming advice and AWS Agent Registry's record rules. Export it as CSV or JSON, put the reviews in your calendar, and print the checklist for retiring one.

Your fleet

Paste the list or JSON from the AI agent team name generator, one agent per line.

Rules read October 19, 2026: Microsoft's Entra Agent ID best practices (a sponsor and a technical owner for every agent, display names prefixed by department or function, Environment, Department and DataSensitivity attributes, sponsor attestation every 6 to 12 months, a quarterly orphan check, certificates rotated at least yearly) and AWS Agent Registry (record names of 1 to 255 characters: letters, digits, _ - . and /, starting with a letter or digit). Kept in this browser only.

Retiring an agent: twelve steps

  1. Ask the sponsor to confirm the agent is no longer needed, and tell the people and agents that call it.
  2. Switch it off: set accountEnabled to false on its agent identity, or disable the blueprint to block every agent made from it. Microsoft
  3. Stop its schedules, triggers and heartbeats in the platform it runs on.
  4. Take down its agent card so other agents stop finding it.
  5. Remove its app role assignments. Microsoft Graph
  6. Revoke its delegated permission grants. Microsoft Graph
  7. Remove it from groups, administrative units and access packages.
  8. Rotate any secret it knew. Remove credentials from the blueprint only if no other agent uses them, since credentials live on the blueprint. Microsoft
  9. Export its sign-in and audit logs for as long as your compliance rules ask. Microsoft
  10. Mark its AWS Agent Registry record DEPRECATED so teams stop building on it. AWS
  11. Delete the agent identity. It moves to deleted items, where it can still be restored; delete it permanently once nothing breaks. Microsoft Graph
  12. Mark it decommissioned here, with the date, and keep the row.

FAQ

How do I keep track of all our AI agents?

Give every agent one row: its display name, a system name in one shape (Agent-Team-Job-env), the environment, a sponsor who answers for it, a technical owner, who can switch it off, how sensitive its data is and when it is next reviewed. Paste a team from the team name generator above, fill in the people, and export the sheet as CSV or JSON.

What should an AI agent registry record include?

At least the name, the environment, a sponsor and an owner. Microsoft's best practices for Entra Agent ID say every agent needs a sponsor and a technical owner from the day it is created, and suggest attributes such as Environment, Department and DataSensitivity for access policies. AWS Agent Registry takes record names of up to 255 characters.

How often should AI agents be reviewed?

Microsoft suggests the sponsor confirm every 6 to 12 months that each agent is still needed, a quarterly look for agents with no sponsor, old details or no activity, and rotating certificates at least once a year. The calendar file puts all three in your calendar.

How do I decommission an AI agent?

Confirm with the sponsor, switch the agent off, remove its access and credentials, keep its logs, mark its registry record deprecated, then delete it. The twelve-step checklist above is printable.

Is the register stored anywhere?

In this browser only. Export it as CSV or JSON to share it or keep a copy; nothing is sent anywhere.

Related

AI Agent Naming Convention for Teams AI Agent Team Name Generator Agent Rules Builder AI Agents Hub