Skip to main content
Last updated on

Outlook connector limitations

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page lists limitations and considerations for ingesting data from Microsoft Outlook using Databricks Lakeflow Connect.

General 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 Lakeflow Spark Declarative Pipelines 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.
  • Column-level selection and deselection are API-only.
  • 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 Lakeflow Spark Declarative Pipelines pipelines for transformations.

Connector-specific limitations​

The limitations in this section are specific to the Outlook connector.

Supported data​

The connector supports a single table, email_messages, under the default schema. For the destination schema, see Destination schema.

Email delete capture​

The connector does not capture email deletions. If an email is deleted from a mailbox after it has been ingested, it remains in the destination table.

Missing folders​

If a folder name specified in include_folders does not exist in a mailbox or is misspelled, the connector silently skips that folder without raising an error or warning.

History tracking (SCD type 2)​

The email_messages table does not support history tracking (SCD type 2).

Row filtering​

The generic row filter option is not supported for this connector. To filter email messages, use the outlook_options parameters (include_mailboxes, include_folders, include_senders, include_subjects). See Connector options.

On this page