Skip to main content

Configure automated lifecycle policies for Microsoft Entra Agent ID

Implementation Effort: Medium - Requires defining policy scope, lifecycle rules, notifications, and enforcement actions with agent sponsors.
User Impact: Medium - Disabling or deleting an identity can interrupt its agent and dependent business processes.

Overview​

Microsoft Entra Agent ID lifecycle policies address identities that remain active after their work ends or their accountable representatives leave. Periodic reconfirmation, minimum sponsor requirements, and inactivity monitoring help determine whether an identity should remain active.

This supports Verify explicitly through recurring confirmation of purpose and accountability, Use least privilege access by retiring unjustified identities, and Assume breach by reducing unattended access. The companion inactive-agent guidance covers inactivity-specific considerations.

Prerequisites​

  • Lifecycle Workflows Administrator or AI Administrator access.
  • The applicable lifecycle-policy licensing and feature availability.
  • A defined agent scope, policy owner, notification recipients, and fallback recipients for identities without an accountable representative.
  • Sponsor/owner participation and an approved nonproduction pilot with recovery arrangements.

Limitations​

  • The feature is in preview and is not recommended for production workloads.
  • When policy scopes overlap, the highest-priority matching custom policy applies; the default inactivity policy is evaluated last. A violation of any enabled rule can start notification and enforcement.
  • Actions can disable an identity, soft-delete it, or disable it before later deletion. Grace periods and deletion delays affect when those actions occur.
  • Notifications alone do not prevent retirement; the underlying violation must be addressed.
  • Reconfirmation requires at least a 30-day interval; a saved policy is not immediate evidence of enforcement.
  • These policies govern Entra agent identities, not Agent 365 registry cleanup, resource-permission reviews, sponsor mover/leaver workflows, source-platform cleanup, or incident containment.

Reference​