Skip to content
AI Agent Access Control

Remove the agent's identity and access when the agent is retired

Check 26 of 30: Remove the agent's identity and access when the agent is retired. Leftover identities from retired agents keep their permissions and nobody is watching them. Tying the identity to the agent's lifecycle removes the access with the agent.

The whole checklist ยท The map

Why it matters

Leftover identities from retired agents keep their permissions and nobody is watching them. Tying the identity to the agent's lifecycle removes the access with the agent.

How, in each cloud

AWS
none found on 2026-11-10
Google Cloud
Use agent identity, which Google documents as tied to the lifecycle of the agent.
Azure
Use a system-assigned managed identity, which is deleted when the container app is deleted.

What the documentation says

  • "is tied to the lifecycle of the agent, making agent identity a more" (source)
  • "A system-assigned identity is tied to your container app and is deleted when your container app is deleted." (source)

Sources

  1. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident, read 10 Nov 2026
  2. learn.microsoft.com/en-us/azure/container-apps/managed-identity, read 10 Nov 2026

Last reviewed 16 Nov 2026.