Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

AD accounts getting deleted after provisioning by its own

asharma
Regular Contributor II
Regular Contributor II

Hi Team

Automatedly provisioned AD accounts self-deleting post-provisioning, please help and suggest.

Regards

5 REPLIES 5

armaanzahir
Valued Contributor
Valued Contributor

Hi @asharma 

Can you check which system is doing the de provisioning? (IGA or Target AD)

In case of IGA, are there tasks for deletion created? Can you check the source of those tasks.

Please elaborate the issue a bit more. 

Regards,
Md Armaan Zahir

asharma
Regular Contributor II
Regular Contributor II

Provisioning is done by IGA only however Disable task is not created for those accounts.

armaanzahir
Valued Contributor
Valued Contributor

Then, it's better to check with the Target application team if there are controls active on the OU that are triggering this action on the target. 

If there are no disable/remove account tasks in pending or completed state for those accounts, then IGA won't be the cause of deletion of those accounts.

 

Regards,
Md Armaan Zahir

asharma
Regular Contributor II
Regular Contributor II

I was looking at the createaccountJSON and found that we are passing customproperty30::userAccountControl#String, whereas we are not defining anything about useraccesscontrol accept enable and disable account JSON. 

Are we missing or are we passing useraccesscontrol value correctly in createaccountjson

asharma
Regular Contributor II
Regular Contributor II

above one is for account attribute not for create accountjson, apologies for the confusion.