Account Schema:
Enable JSON:
{
“id”: “$plan.uniqueId$”,
“user_fname”: “$plan.firstname$”,
“user_lname”: “$plan.lastname$”,
“user_email”: “$plan.mail$”,
“user_status”: “active”
}
I do have the provisioning policy configured for all the above attributes being passed in with the $plan syntax. This goes for both Enable and Disable, I have the provisioning policies configured for both. I have also tried replacing $plan.uniqueId$ with $plan.nativeIdentity$ since that would be the same attribute. Either way, this JSON body works for the Disable Account operation with the only difference being active vs inactive being passed in that last entry.