Box Audit Logs connector FAQ

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Box Audit Logs from the Previews page. See Manage Azure Databricks previews.

Common questions about the managed Box Audit Logs ingestion connector: supported tables, backfill depth, and authentication methods. For FAQs that apply to all managed connectors, see Managed connector FAQs.

Connector-specific FAQ

Which tables does the connector support?

The connector supports the event_logs table only. For the destination schema, see Destination table schemas.

How far back can the connector ingest data?

The first sync starts at stream position 0 and later syncs resume from the last _stream_position. How far back the first sync can go depends on Box event retention. See Connector-specific limitations.

Which authentication methods does the connector support?

The connector supports Box Server Authentication with Client Credentials Grant (OAuth M2M) only. OAuth U2M and basic authentication with a username and password aren't supported.