Manage inactive agents
Implementation Effort: Medium - Requires reviewing identity activity, choosing an appropriate inactivity threshold, and coordinating with agent owners.
User Impact: Medium - Retiring an apparently inactive identity can interrupt a legitimate workload that runs infrequently.
Overview
Microsoft Entra Agent ID lifecycle policies can identify identities that have not received authentication tokens for longer than a configured duration. This helps retire agents left behind by completed projects while keeping inactivity decisions tied to business purpose.
This supports Verify explicitly through activity-based review and Use least privilege access by retiring unjustified identities. It complements automated lifecycle policies, focusing on inactivity rather than sponsor reconfirmation or registry cleanup.
Prerequisites
- Lifecycle Workflows Administrator or AI Administrator access and the applicable lifecycle-policy licensing.
- A defined agent scope, accountable representatives, and an inactivity threshold appropriate to workload schedules.
- Identity authentication evidence sufficient to distinguish inactivity from a telemetry gap.
- Notification recipients, grace periods, and recovery ownership agreed for a nonproduction pilot.
Limitations
- The feature is in preview and is not recommended for production workloads.
- Activity means identity authentication-token issuance, not language-model token consumption. Missing telemetry is not proof that an identity is unused.
- The highest-priority matching policy determines applicable rules. When multiple rules are enabled, a violation may not be caused by inactivity.
- Sponsor acknowledgment alone does not demonstrate fresh authentication activity.
- An owner or administrator must help re-enable a disabled identity; sponsors cannot do so themselves. Disabling an identity does not prove that every existing agent session has ended.