Skip to main content
Last updated on

Troubleshoot the Outlook connector

Beta

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

This page describes common issues with the Outlook connector in Databricks Lakeflow Connect and how to resolve them.

General pipeline troubleshooting​

If a pipeline fails while executing, click the step that failed and confirm whether the error message gives sufficient information about the nature of the error.

You can also check and download the cluster logs from the pipeline details page by clicking Update details in the right-hand pane, then Logs. Scan the logs for errors or exceptions.

Authenticated but Outlook data is not visible​

Issue: Authentication succeeded, but no Outlook data appears in the destination table.

Resolution:

  • Confirm that the app registration has the required Microsoft Graph API application permissions (User.Read.All or Directory.Read.All, and Mail.Read) and that admin consent has been granted.
  • Confirm that the mailboxes specified in include_mailboxes (if provided) correspond to active Exchange Online mailboxes.
  • Confirm that the connection was created with the correct Client ID, Client secret, and Tenant ID. Edit the connection in Catalog Explorer to verify.

Insufficient privileges error​

Issue: The pipeline fails with an insufficient privileges error.

Resolution:

  • Confirm that the app registration has the correct Microsoft Graph API application permissions, not delegated permissions.
  • Confirm that an administrator has clicked Grant admin consent for the required permissions in the Azure portal.

MailboxNotEnabledForRESTAPI error​

Issue: The connector reports a MailboxNotEnabledForRESTAPI error for one or more mailboxes.

Resolution:

  • This error indicates that the mailbox is not enabled for the Microsoft Graph REST API. This typically occurs for on-premises mailboxes or mailboxes that have not been migrated to Exchange Online. The connector automatically skips these mailboxes with a warning and continues ingestion for the remaining mailboxes.

Token expired or invalid client secret error​

Issue: The pipeline fails with a token expired or invalid client secret error.

Resolution:

  • Client secrets in Microsoft Entra ID have an expiration date. If the secret has expired:
    1. Create a client secret in the app registration under Certificates & secrets.
    2. Update the connection in Databricks with the new client secret value.

The connector automatically attempts to refresh the OAuth token when it receives an HTTP 401 response from the Microsoft Graph API.

Specified folders are not being ingested​

Issue: Emails from a folder specified in include_folders are not appearing in the destination table.

Resolution:

  • Folder matching is case-insensitive, but the folder name must exactly match the display name as it appears in Outlook. Verify the display name in the target mailbox.
  • If a specified folder does not exist in a mailbox, the connector silently skips it. Check the pipeline logs for skip warnings.

Need more help?​

If you encounter an issue that is not covered in this troubleshooting guide, create a support ticket.

On this page