Enhancement: Removing Inactive (long-term) Identities from Overnight Internal Synchronization Job

What’s New

Identities in the Inactive (long-term) lifecycle state are no longer included in the daily 1:00 AM CT synchronization job. This reduces overnight processing time, particularly for tenants with large numbers of terminated or archived identities.

What this means for you

• Faster completion of scheduled overnight jobs
• Reduced system resource consumption

What to know

• Identities in the Inactive (long-term) state are already excluded from regular identity processing. With this update, they will also be excluded from certain background maintenance jobs - in this case the SYNCHRONIZE_IDENTITIES job that keeps Search up-to-date.
• This internal maintenance job only keeps Search data in sync.
• As a result, details related to inactive identities (such as role or entitlement names) will no longer be up-to-date in Search if those names change after the identity becomes inactive. For example, if a role assigned to an inactive identity is renamed, the updated name will not appear when viewing that identity in Search.

For more details on identity states and processing, see Setting Up Lifecycle States and Processing Identity Data.

Who’s Affected

• Applies to: Inactive (long-term) identities
• Environments: All

Important Dates

• [2/16/26] – Available in Sandbox
• [2/23/26] – Available in Production

Resources

If you’d like to discuss this change or how refresh and provisioning work for you, feel free to schedule a meeting here: Calendly Link. This link will expire after 30 days.

To ask questions and learn more please visit the Developer Community.