Google Drive Audit 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 Google Drive Audit Logs ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports a single source table, drive, which contains Google Drive audit activity events from the Google Workspace Admin SDK Reports API. For its schema, see Supported source tables.
Is ingestion incremental?
Yes. The connector ingests drive incrementally, using the event_time field as the cursor. When no start datetime is configured, the connector backfills the previous 180 days by default. See Google Drive Audit Logs connector limitations.
How far back can the connector ingest data?
The Google Workspace Admin SDK Reports API retains Drive audit activity for up to 180 days. The first sync ingests events from the previous 180 days, and each later sync ingests events after the last run.
Which authentication method does the connector support?
The connector supports a Google Cloud service account with domain-wide delegation only. The connector impersonates a Google Workspace admin to read Drive audit activity. OAuth U2M, OAuth M2M, and basic authentication aren't supported.