Rediger

Configure Zoom for automatic user provisioning with Microsoft Entra ID

This article describes the steps you need to perform in both Zoom and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and deprovisions users to Zoom using the Microsoft Entra provisioning service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Microsoft Entra ID.

Capabilities supported

  • Create users in Zoom
  • Remove users in Zoom when they don't require access anymore
  • Keep user attributes synchronized between Microsoft Entra ID and Zoom
  • Single sign-on to Zoom (recommended)

Prerequisites

The scenario outlined in this article assumes that you already have the following prerequisites:

Step 1: Plan your provisioning deployment

  1. Learn about how the provisioning service works.
  2. Determine who's in scope for provisioning.
  3. Determine what data to map between Microsoft Entra ID and Zoom.

Add Zoom from the Microsoft Entra application gallery to start managing provisioning to Zoom. If you have previously setup Zoom for SSO you can use the same application. However, we recommend that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 3: Define who is in scope for provisioning

The Microsoft Entra provisioning service allows you to scope who is provisioned based on assignment to the application, or based on attributes of the user or group. If you choose to scope who is provisioned to your app based on assignment, you can use the steps to assign users and groups to the application. If you choose to scope who is provisioned based solely on attributes of the user or group, you can use a scoping filter.

  • Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.

  • If you need extra roles, you can update the application manifest to add new roles.

Step 4: Configure automatic user provisioning to Zoom

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users in TestApp based on user assignments in Microsoft Entra ID.

Configure automatic user provisioning for Zoom in Microsoft Entra ID

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Entra ID > Enterprise apps > All applications.

    Screenshot of the Enterprise applications blade.

  3. In the applications list, select Zoom.

    Screenshot of the Zoom link in the Applications list.

  4. Select the Provisioning tab.

    Screenshot of the Manage options with the Provisioning option called out.

  5. Select + New configuration.

    Screenshot of New configuration.

  6. Under the Admin Credentials section, select OAuth2 Authorization Code Grant. Enter https://api.zoom.us/scim in Tenant URL, select Authorize, make sure that you enter your Zoom account's Admin credentials. Select Test Connection to ensure Microsoft Entra ID can connect to Zoom. If the connection fails, ensure your Zoom account has Admin permissions and try again.

    Screenshot of the Zoom provisioning Token.

    Note

    You have two options for your Authentication Method: Bearer Authentication and OAuth2 Authorization Code Grant. Make sure that you select OAuth2 Authorization Code Grant. Zoom no longer supports the Bearer Authentication method

  7. Select Create to create your configuration.

  8. Select Properties on the Overview page.

  9. Select the Edit icon to edit the properties. Enable notification emails and provide an email to receive quarantine notifications. Enable Accidental deletions prevention. Select Apply to save the changes.

    Screenshot of Provisioning properties.

  10. Select Attribute Mapping in the left panel and select users.

  11. Review the user attributes that are synchronized from Microsoft Entra ID to Zoom in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Zoom for update operations. If you choose to change the matching target attribute, you need to ensure that the Zoom API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Zoom
    userName String ✓ ✓
    active Boolean
    name.givenName String
    name.familyName String
    emails[type eq "work"] String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department String
    userType String

  12. To configure scoping filters, refer to the instructions provided in the Scoping filter article.

  13. Use on-demand provisioning to validate sync with a small number of users before deploying more broadly in your organization.

  14. When you're ready to provision, select Start Provisioning from the Overview page.

Step 5: Monitor your deployment

Once you configure provisioning, use the following resources to monitor your deployment:

  1. Use the provisioning logs to determine which users are provisioned successfully or unsuccessfully
  2. Check the progress bar to see the status of the provisioning cycle and how close it's to completion
  3. If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states the application provisioning quarantine status article.

Connector limitations

  • Zoom only allows a maximum of 9,999 basic users today.

Change log

  • 05/14/2020 - Supports for UPDATE operations added for emails[type eq "work"] attribute.
  • 10/20/2020 - Added support for two new roles Licensed and on-premises to replace existing roles Pro and Corp. Support for roles Pro and Corp is removed in the future.
  • 05/30/2023 - Added support for new authentication method OAuth 2.0.

Additional resources

Related content

  • Last updated on