Entra ID - signInActivity attributes not populating

Hi Team,

I’m trying out the supported sign-in activity attributes mentioned in the following Enhancement post:

I’m unable to get the account attributes to actually populate with sign-in activity using the attributes provided. This is what I’ve found while using a VA based Azure Active Directory connector:

  • Adding any new attributes to the account schema with the signInActivity.<attribute_name> format results in none of the new attributes being populated.
  • Adding signInActivity to the account schema does provide a value of [object Object] indicating there is a signInActivity object.
  • Adding lastSignInDateTime and lastNonInteractiveSignInDateTime without the signInActivity. prefix does populate the fields with dates, but lastSuccessfulSignInDateTime does not.

I’ve tried creating a new Azure Active Directory connector in case I had some connector attribute set that was preventing the sign-in activity from being pulled, but even with a new default connector, adding attributes with the signInActivity.<attribute_name> format doesn’t seem to work.

Has anyone else had any luck getting these attributes to work? I’m working on an automation that specifically needs the last successful login date, which is unfortunately the only attribute that doesn’t work with either new or old formatting.

Hello, the doc is wrong.

But i still can`t get the lastSuccessfulSignInDateTime and i dont know why even though the attribute is populated.

@dinesh_mishra do you have any tips on this?

Hi,

I added the different attributes in the EntraID connector schema (with signInActivity prefix) and it works as expected.

Make sure your service account has the AuditLog.Read.All permission as mentioned in Sailpoint documentation (Last Login for Accounts)

Are you using the Entra ID SaaS connector or VA connector? I’ve already made sure AuditLog.Read.All was granted to the service principal in Entra ID and it unfortunately didn’t make a difference.
image

The EntraID SaaS connector

1 Like

I’ve raised a ticket with SailPoint support to see if there is a solution to this issue

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.