Skip to main content
Last updated on

Microsoft Graph Logs connector limitations

Beta

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

This page contains information about known limitations of the managed Microsoft Graph Logs connector in Lakeflow Connect.

General software as a service (SaaS) connector limitations​

The limitations in this section apply to all SaaS connectors in Lakeflow Connect.

  • When you run a scheduled pipeline, alerts don't trigger immediately. Instead, they trigger when the next update runs.
  • When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with Spark Declarative Pipelines on Lakeflow behavior.
  • During source maintenance periods, Databricks might not be able to access your data.
  • If a source table name conflicts with an existing destination table name, the pipeline update fails.
  • Multi-destination pipeline support is API-only.
  • You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
  • If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.
  • Databricks can't ingest two or more tables with the same name in the same pipeline, even if they come from different source schemas.
  • The source system assumes that the cursor columns are monotonically increasing.
  • The connector ingests raw data without transformations. Use downstream Spark Declarative Pipelines on Lakeflow pipelines for transformations.

Connector-specific limitations​

The limitations in this section apply to the Microsoft Graph Logs connector.

  • The connector ingests alerts from the Microsoft Graph alerts_v2 endpoint only. It doesn't ingest security incidents or alerts from the legacy alerts endpoint.
  • The connector supports the Microsoft global service, including Government Community Cloud (GCC), and the US Government GCC High and Department of Defense (DoD) clouds. It doesn't support Microsoft Graph operated by 21Vianet in China.
  • The start_datetime option applies only to the first sync. Later syncs resume from the last ingested lastUpdateDateTime value.
On this page