Remove the agent's identity and access when the agent is retired
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
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)
- Previous: Test permission and policy changes in a dry run before enforcing them
- Next: Turn on organization-wide audit logging of control-plane actions
Related pages
- Turn on organization-wide audit logging of control-plane actions: the check, and how in AWS, Google Cloud and Azure
- Log reads and writes to the data the agent touches: the check, and how in AWS, Google Cloud and Azure
- Make every logged action traceable to the specific agent identity: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/container-apps/managed-identity, read 10 Nov 2026
Last reviewed 16 Nov 2026.