Skip to main content

Stop managing several accounts

POST 
/api/v1/ManagedUser/DeleteMultiple

Removes the listed managed users so the accounts are no longer managed, and removes their scheduled jobs. Entries the caller is not permitted to unmanage and entries that no longer exist are skipped. For accounts managed through a resource group, the managed user record is still removed, but the scheduled jobs, the credential and the host user are left as they are. The response gives two counts, but the first count reflects the records the call changed rather than strictly the number of accounts, so check the accounts afterward if you need an exact result.

Permission required: Administrator, or a delegated user with the Unmanage permission on the credentials. The caller must have signed in with multi-factor authentication.

Caution: This call takes effect immediately. For accounts that have no dependencies, it also removes their credentials from credential access policies and renames the stored credential by appending its id.

Request​

Responses​

Returns two counts, item1 and item2. item1 is the number of records changed, which can differ from the number of accounts unmanaged; item2 is the number of listed ids minus item1.