Account Recreated in AD

[margocbain (Margo Bain)]

This sounds like it could be a sticky entitlement.
If the AD account was moved to a different OU directly on AD, and the account still had some entitlements assigned which were assigned to the account through ISC, then SailPoint will re-provision the account to the old DN.

How to Handle Requestable Entitlements and Avoid Stickiness

Problem SailPoint will continue to add entitlements that were requested via request center to identities in every Identity Refresh / Manual processing. SailPoint would try to re-add the entitlements or even create the account if the account doesn’t exist for the user. Diagnosis SailPoint entitlements are sticky in nature, Once an entitlement has been assigned to an identity using access requests, it will be provisioned to the identity’s source account. If the entitlement is directly removed fro…

Some recommendations are available here:

New AD Account Created during AD Aggregation

Hi Folks, When we manually change “CN” value of user in Active Directory, during aggregation a new AD account got created for user. BUT when we change the samAccountname & UPN it didn’t created another AD account. How we can ensure another AD account should not get created when we do such changes & aggregation. Thanks in advance.