Skip to content

Zoom Integration

The Zoom integration connects your organization’s Zoom account to Fencer for identity management and SaaS security scanning. Once connected, Fencer syncs your Zoom users — including their roles, groups, and login activity — and runs security checks against your account settings to identify misconfigurations such as missing meeting passcodes, disabled waiting rooms, and unprotected cloud recordings.

  • A Zoom admin or owner in your Zoom account to authorize the connection. The account must allow third-party application access via OAuth.
  • A valid Fencer subscription and the Administrator role in Fencer.
  • To sync identities, a Fencer plan that includes Identities.

When you connect Zoom, Fencer initiates an OAuth 2.0 flow that requests read-only access to your account settings, users, roles, and groups. After authorization, Fencer stores encrypted OAuth tokens and creates a SaaS account asset representing your Zoom account under Posture > SaaS.

Fencer then starts two jobs: an identity sync that imports all Zoom users (active, inactive, and pending) with their roles, groups, and login history, and a SaaS security scan that evaluates your account settings against a set of security checks. Both repeat automatically: the identity sync every night, and the scan on your scan schedule — every day on plans with daily scans, otherwise every Monday.

  1. Go to Admin > Integrations.
  2. Click the Zoom card under Available Integrations.
  3. Read the summary, click Continue, then click Connect Zoom.
  4. You are redirected to Zoom’s authorization page. Sign in with a Zoom admin account, review the requested permissions and click Allow.
  5. After authorization, you are redirected back to Fencer. The integration is now active and your Zoom account appears as a connected SaaS account.

A Zoom connection has no settings to edit. Connecting the same Zoom account again updates the existing connection instead of adding a second one.

In Admin > Integrations, click Remove (the trash icon) on the Zoom connection’s card, then confirm with Remove. Fencer clears the stored tokens, removes the connection, and removes the Zoom identities it synced and the Zoom vendor record the integration added.

Once connected, Fencer runs the following SaaS security checks against your Zoom account:

CheckSeverityWhat it detects
Missing meeting passcodesHighPasscodes are not required for new meetings, scheduled meetings, or PMI meetings. Anyone who obtains a Meeting ID can join without a passcode.
Unprotected cloud recordingsHighShared cloud recordings do not require a passcode. Anyone with the link can view recordings that may contain sensitive content.
Personal Meeting ID for meetingsMediumAccount is configured to use static Personal Meeting IDs (PMIs) instead of auto-generated random Meeting IDs, making meetings easy to discover.
Waiting room disabledMediumParticipants join immediately without host approval, allowing uninvited attendees to access meeting content.
Join before hostMediumParticipants can join meetings before the host, creating an unsupervised window for interaction.
Unrestricted screen sharingMediumAll participants can share their screen, allowing anyone — including uninvited attendees — to broadcast content.
Removed participants can rejoinMediumEjected participants can re-enter meetings immediately, forcing repeated removal.
In-meeting file transfer enabledMediumParticipants can send files through meeting chat, bypassing email security controls.

The integration syncs Zoom users into Fencer’s identity management system. Each user record includes:

  • Email and display name
  • Role (mapped from Zoom role assignments)
  • Status (Active, Inactive, or Pending)
  • Groups (Zoom group memberships)
  • Last login timestamp
  • Account creation date

Users in all statuses (active, inactive, and pending) are synced so you can identify stale or unused accounts. They appear on the Vendor Identities tab of Posture > Identities. The sync runs when the integration is first connected and again every night; to run it straight away, click Sync Identities on Posture > Identities.

  • “Failed to fetch Zoom account info. Please ensure you have sufficient permissions.” — The authorizing account does not have sufficient permissions. Re-authorize with an account that has admin privileges.
  • Token refresh failures — If the OAuth refresh token becomes invalid (for example, after revoking access in the Zoom App Marketplace), click Reconnect (the refresh icon) on the Zoom connection’s card to authorize Fencer again.