# SCIM userType "Collaboration" rejected - How to provision "Unassigned without Meeting Basic" users?

**URL:** <https://devforum.zoom.us/t/scim-usertype-collaboration-rejected-how-to-provision-unassigned-without-meeting-basic-users/139015>\
**Category:** API and Webhooks\
**Created:** [December 1, 2025, 3:10pm UTC](https://devforum.zoom.us/t/scim-usertype-collaboration-rejected-how-to-provision-unassigned-without-meeting-basic-users/139015 "2025-12-01T15:10:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pimzino](https://avatars.discourse-cdn.com/v4/letter/p/f05b48/32.png) [@Pimzino](https://devforum.zoom.us/u/Pimzino)\
**Post date:** [December 1, 2025, 3:10pm UTC](https://devforum.zoom.us/t/scim-usertype-collaboration-rejected-how-to-provision-unassigned-without-meeting-basic-users/139015/1 "2025-12-01T15:10:02Z")

</div>

Hi all,

I’m hoping someone can help with this as Zoom Support haven’t been able to.

We’re provisioning users via SCIM from Azure AD/Entra ID and need to create users as “Unassigned without Zoom Meetings Basic” so we don’t eat into our Meeting Basic allocation (the 1:10 ratio). According to Zoom’s documentation, “Collaboration” should be a valid `userType` value for this, but when we send it the SCIM endpoint just rejects it with `AttributeValidationFailed`. Standard values like “Basic” and “Licensed” work fine.

I’ve also tried “None” which was rejected too.

I know `userType` is being deprecated in favor of the extension schema attributes (`urn:ietf:params:scim:schemas:extension:zoom:1.0:User`) like `zoomOneEntPremier`, `zoomOneBizPlus`, etc. But I can’t find any documentation on what the equivalent attribute or value would be for “Unassigned without Zoom Meetings Basic” users.

So my questions are:

1. Does “Collaboration” need to be enabled on our tenant somehow, or is it just not actually supported despite being documented?

2. If `userType` is deprecated, what’s the correct extension attribute to use for unassigned/collaboration users?

3. Has anyone actually managed to provision users without a Meeting Basic license via SCIM?

For now I’ve had to work around this by disabling SCIM’s create action entirely, removing the `userType` mapping, and using SAML Advanced Mapping to handle license assignment at first login instead. It works, but it’s clunky and means users don’t exist in Zoom until they actually log in for the first time.

Any help or pointers would be appreciated - feels like there’s a gap between what Zoom documents and what the SCIM endpoint actually accepts.

Thanks!