Zoom Logs connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Zoom Logs ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Zoom account plans does the connector require?
The connector requires a Zoom Pro, Business, Enterprise, or Education account. Zoom's report APIs aren't available on Basic (free) accounts.
Which tables does the connector support?
The connector supports two prebuilt report tables:
activity_logs— user sign-in and sign-out activity.operation_logs— admin and user activity, such as adding a new user, changing account settings, and deleting recordings.
For the full schemas, see Destination table schemas.
How far back can the connector ingest data?
Activity and operation logs are retained by Zoom for a rolling 6-month window. Data older than 6 months can't be ingested.
Should I use a personal Zoom account or a service account?
Use a shared service account in Zoom. If the Zoom user who created the OAuth app leaves your organization, the connector might stop working.
Which authentication methods does the connector support?
The connector supports Zoom Server-to-Server OAuth (M2M) only. OAuth U2M and basic authentication aren't supported.
What is the source schema for Zoom Logs tables?
All Zoom Logs source tables are available under the default source schema.