The documentation states that the endpoint validates the input, processes the deletion request, and returns an asynchronous result with a tracking ID, and that it only works on sources of the “Connected” type. However, it doesn’t describe what happens to the account’s entitlements as part of that process.
My specific question: before sending the delete operation to the source, does this API trigger a bulk removal of the account’s entitlements — or does it simply issue the account deletion directly, leaving any entitlement cleanup to be handled separately?
It simply runs the delete operation on the connector. It will not perform any cleanup (removing entitlement, disabling account etc.) before deleting the account.
If you need to perform cleanup beforehand, you’ll need to handle that yourself by running the proper remove access API calls.
@originalmths Most likely it is not removing entitlements but You can try removing one account and check the provisioning logs what all attributes and operation going through. But in Identity profile there is one option remove all access and if you going through the process of terminate lifecycle then that will remove your entitlements for sure.