Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.
This page answers frequently asked questions about the managed Google Workspace 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 33 source tables, one for each Google Workspace activity application: access_evaluation, access_transparency, admin, assignments, calendar, chat, chrome, classroom, cloud_search, contacts, context_aware_access, data_migration, data_studio, directory_sync, gcp, gemini_in_workspace_apps, graduation, groups, groups_enterprise, keep, ldap, login, meet, meet_hardware, mobile, profile, rules, saml, takeout, tasks, token, user_accounts, and vault. All tables contain activity records from the Google Workspace Admin SDK Reports API. For details, see Supported source tables.
Is ingestion incremental?
Yes. The connector ingests each table incrementally, using the time field as the cursor. When no start_datetime is configured, the connector backfills the previous 180 days by default. See Google Workspace connector limitations.
How far back can the connector ingest data?
The Google Workspace Admin SDK Reports API retains activity logs 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 user authorization with 3-legged OAuth only. A Google Workspace Super Admin authorizes access to the Admin SDK Reports API audit-readonly scope. OAuth M2M, service-account domain-wide delegation, and basic authentication aren't supported.
How are activity records ingested given their reporting lag?
Different Google Workspace applications report with different lag windows, ranging from minutes to several days. The connector sets per-application lookback windows to absorb this lag. In particular, the takeout application's "process finished" event can lag by up to several days; very large exports finishing beyond the per-application lookback window may not be captured.