With the introduction of Lifecycle Management of Inactive Identities in March 2024, SailPoint provided a more robust means for marking identities as Active, Inactive Short-Term, and Inactive Long-Term. By introducing this capability, administrators have an alternative option to the previously used AI mappings to accomplish managing these lifecycle states. As of May 15th, 2026, SailPoint will formally sunset the use of this method of management.
Who is affected?
All IdentityNow and Identity Security Cloud customers who have not already adopted the Lifecycle Management of Inactive Identities capability and marked their identities as Active, Inactive Short-Term, and Inactive Long-Term will be impacted by this deprecation. As SailPoint sees signs of adoption through our metrics and data, we will slowly migrate customers off of these AI mappings on a quarterly basis. Thirty (30) days prior to migration, SailPoint will send an email from [email protected] before taking migration actions.
Action Required
IDN and ISC administrators should work to adopt the Lifecycle of Inactive Identities capability within the 2025 and early 2026 calendar year in order to not be impacted by this deprecation.
Resources are available detailing how the capability works and how to configure these states within IDN and ISC.
Thank you for this announcement. I already started using “identityState” for my LifeCycleStates. Would you mind elaborating a bit more on the AI mappings? Is ISC using AI to understand which are the inactive/terminated identity in tenants without the “identityState” configuration?
Hi @TheOneAMSheriff, glad to read that you already started using Identity States in your Identity Profiles. Happy to explain the AI mappings, but to be clear this is not something you need to understand for this migration. In effect, you have already done the hard part by using Identity States.
Our AI products previously used Lifecycle States to determine what identities to provide AI insights for. Now that ISC has introduced Identity States, we are moving to use that field to determine what identities to provide insights for. Our AI features remain the same, ensuring that we are only processing relevant identities.
So, to answer your question directly, AI does not itself infer active/inactive status based on any algorithms.
Hi @VadimTeterin, if you have onboarded in the last 6-9 months you are most likely not using AI Mappings for your Lifecycle State.
You can check yourself by looking at your Identity Profiles and going to the Lifecycle Management section. If it looks like the screenshot below you are using the newer identity States. In particular, if you have been assigning Inactive (short-term) Identity States to Lifecycle States, you are using the new framework. However, if you don’t see Inactive (short-term) or Inactive (long-term) radio buttons, that would imply you are using the old Lifecycle States framework.
