Best Practice for Converting AD lastLogonTimestamp on Uncorrelated Accounts

In Active Directory sources, the lastLogonTimestamp attribute is stored in Windows FileTime format. We need to convert this value into a human‑readable date format specifically for uncorrelated accounts.

While this conversion can be handled using a Transform for identity attribute values, the same approach does not apply to uncorrelated accounts, as they do not yet have an associated identity. Additionally, unlike SailPoint IIQ, we do not have access to a Resource Object Customization Rule to perform this transformation.

Could you please advise on the recommended approach to handle this conversion for uncorrelated accounts?

@AkhilTeja_Edulabavi indeed, I don’t see anywhere in the SailPoint ISC Rules Guide where this is supported - and transforms are all about getting the right value into the identity attribute.

I wonder if it may be possible to convert it first on the AD side to calculate and replace the timestamp value? Or store the result as an addtional account attribute, and add that to the source schema?

Perhaps trigger the conversion using a workflow that targets your AD source to run a Powershell script, and then performs an aggrgegation?

Hi @paul_patti ,

Thank you for the information, we have built the custom solution for this activity as per the requirements.