Skip to main content

Troubleshoot the Microsoft Entra ID connector

Beta

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

This page describes common errors you might encounter with the managed Microsoft Entra ID connector and how to resolve them.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Pipeline fails to authenticate​

Cause: Microsoft Entra ID rejected the app registration's credentials. The client secret might have expired or been deleted, or the Directory (tenant) ID on the connection might not match the app registration.

Solution:

Create a client secret for the app registration, then update the connection with the new value. Confirm the Application (client) ID and Directory (tenant) ID on the connection. See Create a client secret and Create a Microsoft Entra ID connection.

Insufficient permissions​

Error message:

Output
Access denied due to insufficient permission.

If Microsoft Entra ID returns its own error message, the connector reports that message instead.

Cause: The app registration lacks the Microsoft Graph application permission that the table requires, admin consent isn't granted, or the tenant lacks a required license.

Solution:

Add the required permissions and grant admin consent. For signins and the signInActivity column of users, confirm that the tenant has a Microsoft Entra ID P1 or P2 license. See Grant Microsoft Graph application permissions and Required OAuth permissions.

Resource not found​

Error message:

Output
The requested resource was not found. The object may have been deleted, or it may no longer be available.

Cause: Microsoft Entra ID doesn't serve the requested resource. The Microsoft Cloud Region on the connection might not match the cloud that hosts the tenant.

Solution:

Confirm the Directory (tenant) ID and Microsoft Cloud Region on the connection. See Identify your Microsoft cloud and Create a Microsoft Entra ID connection.

Rate limit exceeded​

Error message:

Output
Rate limit exceeded. Please retry the pipeline after some time.

Cause: Microsoft Graph throttled the connector's requests. See Microsoft Graph throttling guidance.

Solution:

The connector retries automatically after the delay that Microsoft Graph returns. If the error persists, reduce the pipeline schedule frequency or the number of pipelines that share the app registration.