We have an issue in our tenant. ISC keeps trying to create an AD Account, which was successfully provisioned some time ago. Why ISC tries to create a second account, with exact attribute values of the original one?
How many ad sources are there in your environment and can you check the role criteria as well
@jsosa Can you check if the AD account is already associated in the Accounts page of the identity ?
Either account is not correlated to the Identity or the account is not aggregated due to accounts aggregation filters.
if the account has been already created (by checking the source):
- it can’t be correlated to the cube if ISC is trying to create it again
- and if its the exact same values, then you cannot be using a $(uniqueCounter)
First thing I would check is whether the AD account is actually correlated to the identity in ISC. Go to the identity and look at the Accounts section. If the AD account is not listed there, that is most likely the root cause.
ISC does not check the target system before provisioning. It relies on what is already linked to the identity. So if the account exists in AD but is not correlated in ISC, the platform treats it as missing and will keep trying to create it.