How to clear out the SCIM record for a de-provisioned account?
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
After a managed account has been de-provisioned, the Atlassian Account will remain on a deactivated state and will remain to be locked by the user provisioning feature. There will be cases where that account needs to be re-activated but should remain out of the provisioning scope. ie. The account is required for Trello or Bitbucket access.
To allow manual reactivation by organization administrators, the managed account can be unlocked by removing the underlying SCIM record ( - ACCESS-1021Getting issue details... STATUS ). The following procedure can be used to achieve this.
Retrieve the SCIM ID of the de-provisioned account.
SELECT * FROM users;
If you're suggesting the use of SQL
INSERT UPDATE DELETEoperations please include the following warning:
Alwaysyour data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.