Skip to content
Start with Identity
Concept

User Lifecycle Management

User lifecycle management is the automated creation, change and removal of a person's accounts and access as their relationship with an organization changes, driven by the joiner-mover-leaver events in an authoritative source such as the HR system. It is a core function of IGA and of most identity providers, and its standard transport to applications is SCIM.

Microsoft Entra lifecycle workflows are a concrete example of the three phases: a joiner "enters the scope of needing access", a mover "moves between boundaries within an organization", and a leaver "leaves the scope of needing access." Each phase triggers tasks, such as generating a first-day credential, changing group memberships or disabling the account, based on attributes like hire date or department.

Event Typical actions Common failure
Joiner Create accounts, assign birthright roles, issue first credential Day-one access granted by copying a colleague's permissions
Mover Add new-role access, remove old-role access Old access never removed, see mover entitlement accumulation
Leaver Disable accounts, revoke sessions and tokens, reassign owned resources Accounts in apps outside SSO and SCIM survive, becoming orphaned accounts

User lifecycle management is not the same as access certification: lifecycle automation acts on events as they happen, while access certification periodically checks that the result is still correct. You need both, because automation only covers the apps it is connected to. In UX and product design the same phrase means the customer journey from sign-up to churn; in identity it always means accounts and entitlements.

See also: user lifecycle management guide, provisioning, deprovisioning, SCIM provisioning implementation, top SCIM provisioning tools, orphaned account abuse

Last reviewed By SWI Community TeamSuggest a correctionHow we research