# Can not disassociate the user with managed domain

**URL:** <https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740>\
**Category:** API and Webhooks\
**Created:** [March 26, 2019, 11:05am UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740 "2019-03-26T11:05:23Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinay\_Kumar](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vinay_kumar/32/533_2.png) [@Vinay\_Kumar](https://devforum.zoom.us/u/Vinay_Kumar)\
**Post date:** [March 26, 2019, 11:05am UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740/1 "2019-03-26T11:05:23Z")

</div>

We recently enabled Managed Domains on our instance and since then whenever we try to delete a account, we get:

{“code”:1107,“message”:“Can not disassociate the user with managed domain”}

What is the supported method/REST API for deleting users from a Managed Domain?

---

<div class="post-metadata">

**Author:** ![Vinay\_Kumar](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vinay_kumar/32/533_2.png) [@Vinay\_Kumar](https://devforum.zoom.us/u/Vinay_Kumar)\
**Post date:** [March 26, 2019, 11:12am UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740/2 "2019-03-26T11:12:46Z")

</div>

Payload:  
**DELETE: [https://api.zoom.us/v2/users/userid?access\_token=xxxx](https://api.zoom.us/v2/users/userid?access_token=xxxx)**

---

<div class="post-metadata">

**Author:** ![Vinay\_Kumar](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vinay_kumar/32/533_2.png) [@Vinay\_Kumar](https://devforum.zoom.us/u/Vinay_Kumar)\
**Post date:** [March 27, 2019, 7:40am UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740/3 "2019-03-27T07:40:21Z")

</div>

Please can I get an update here as we are lagging behind on user account removals for users who have left the company. For a large enterprise this is very critical both from security perspective and license management.

Cheers  
VK

---

<div class="post-metadata">

**Author:** ![Vinay\_Kumar](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vinay_kumar/32/533_2.png) [@Vinay\_Kumar](https://devforum.zoom.us/u/Vinay_Kumar)\
**Post date:** [March 28, 2019, 10:16am UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740/4 "2019-03-28T10:16:55Z")

</div>

1. DELETE call without any action parameter, which works for deleting users under a non-managed domain. This in-turn executes a **disassociate** action, which is not supported for users under a managed domain
2. DELETE call with explicit **action=delete** is required to delete users under managed domain

Please can we have this documented on Zoom Support docs.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Champ](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonathan_champ/32/45_2.png) [@Jonathan\_Champ](https://devforum.zoom.us/u/Jonathan_Champ)\
**Post date:** [April 3, 2019, 8:41pm UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740/5 "2019-04-03T20:41:33Z")

</div>

I had a similar problem because it defaults to disassociate. The actions are documented here: [https://marketplace.zoom.us/docs/api-reference/zoom-api/users/userdelete](https://marketplace.zoom.us/docs/api-reference/zoom-api/users/userdelete)

---

<div class="post-metadata">

**Author:** ![TimZoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timzoom/32/978_2.png) [@TimZoom](https://devforum.zoom.us/u/TimZoom)\
**Post date:** [April 25, 2019, 7:36pm UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740/6 "2019-04-25T19:36:56Z")

</div>

I am glad you figured this out! Apologies for not seeing this right away. Our system looks for threads with only one post, but since you replied to your own post, our system did not pick this up for a reply. Our apologies and we will look for ways to improve this.

As mentioned by @Jonathan_Champ if you do not include an action, we will default to “disassociate.” This can be seen on the right-hand side of the docs as seen below.

 ![38%20PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/1X/187d13e66208d9a21979b409a6f9e045259a77f0.png)

If there are defaults for query params or other fields, they will always be in the validations section of that field. Please keep that in mind as it will mitigate these issues in the future.

If you have any questions, please let me know.

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 6:14pm UTC](https://devforum.zoom.us/t/can-not-disassociate-the-user-with-managed-domain/3740/7 "2020-08-21T18:14:25Z")

</div>

Closed on August 21, 2020, 6:14pm UTC


