How to stop provisioning for inactive identities

[mohammedfavazhrb (Mohammed Favaz S A)]

Ok. Then removing those sticky entitlements is the only other option i think. or else it will try to add those entitlements which in turn will create the Create account event. Even if you tweak the create account provisioning policy, everyday create account event will be retried and will be failed.

if you need any help with sticky entitlements removal you can refer this discussion. it can be achieved via workflow.

Sticky Roles Removal for inactive accounts

Hi team, We are facing a challenge related to the nature of Roles being “sticky assignments” to the identity. We are currently using Roles for Access Requests. The decision to use Roles was made since we are using the “Service Catalog” integration and we wanted to avoid having two different tabs for both Roles and Access Profiles. Another team runs a dormancy process that disables accounts inactive for 90 days and deletes them after an additional 90 days. These accounts are not limited to ina…

AD Entitlement Provisioning to Inactive Identities

Hello All - I’ve noticed that IDN will continue to add AD entitlements that were requested via request center (sticky entitlements) to inactive identities if the entitlement is removed from the source account. What’s concerning is that if the AD account is deleted, IDN will recreated the AD user object in an active state and add the entitlement, despite an inactive LCS. I hope this is not the expected behavior?? How do we get IDN to release the sticky entitlements to prevent this?