IdentityNow Account is Enabled While Loopback Source Account Disabled

Hello Everyone,

I find a strange issue from this below event in ISC.

Our current configuration is that we included the loopback source (named *SailPoint) accounts to be enabled in active LCS and disabled in inactive LCS. This identity’s previous LCS was inactive and now active which is expected. However, the IdentityNow account is enabled and the loopback source account is still disabled. The assumption is that both IdentityNow and loopback accounts (which are ideally the same) should be enabled.



Has anyone else encountered this behavior before? Any pointers on what could cause this mismatch between IdentityNow and loopback source account statuses?

Hello @varshini303

Please ensure the ‘loopback’ within your Account Correlation policy is aiming to the IdentityNow account. Share an update after it