What causes Fabric Pipeline Error 3200?

The Azure Databricks personal access token (PAT) used in the linked service or connection has reached its 90-day default expiry. The token was manually revoked in the Databricks workspace user settings. The Databricks workspace admin enforced a shorter token lifetime policy that was not reflected in the pipeline connection. The connection was set up with a temporary token intended for testing and was never replaced with a long-lived credential

How do I fix Fabric Pipeline Error 3200?

Step 1: Log in to the Azure Databricks workspace, navigate to User Settings > Access Tokens, and generate a new personal access token with an appropriate lifetime.. Step 2: In Microsoft Fabric, open the Data Factory connection manager and locate the Databricks connection used by the failing pipeline.. Step 3: Update the connection credential with the newly generated token and save the connection.. Step 4: Re-run the pipeline manually to confirm the 3200 error is resolved before re-enabling any scheduled triggers.. Step 5: Document the token expiry date and set a calendar reminder or MetricSign alert 1–2 weeks before expiry to rotate the token proactively.

High severityauthenticationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 3200

What does this error mean?

The Fabric Data Pipeline activity targeting Azure Databricks received a 403 Forbidden response because the configured Databricks personal access token (PAT) has expired. All pipeline activities using this connection will fail until a valid token is provided.

Common causes

1The Azure Databricks personal access token (PAT) used in the linked service or connection has reached its 90-day default expiry
2The token was manually revoked in the Databricks workspace user settings
3The Databricks workspace admin enforced a shorter token lifetime policy that was not reflected in the pipeline connection
4The connection was set up with a temporary token intended for testing and was never replaced with a long-lived credential

How to fix it

1Step 1: Log in to the Azure Databricks workspace, navigate to User Settings > Access Tokens, and generate a new personal access token with an appropriate lifetime.
2Step 2: In Microsoft Fabric, open the Data Factory connection manager and locate the Databricks connection used by the failing pipeline.
3Step 3: Update the connection credential with the newly generated token and save the connection.
4Step 4: Re-run the pipeline manually to confirm the 3200 error is resolved before re-enabling any scheduled triggers.
5Step 5: Document the token expiry date and set a calendar reminder or MetricSign alert 1–2 weeks before expiry to rotate the token proactively.

Frequently asked questions

Can I set a Databricks token to never expire to avoid this issue?

Yes — Databricks allows tokens with no expiry (lifetime set to -1 or left blank), but this is discouraged for security reasons. A better practice is to use a service principal with OAuth or set a long-lived token and rotate it on a documented schedule.

Will updating the connection affect other pipelines using the same Databricks connection?

Yes — if multiple pipelines share the same connection object, updating the token will fix all of them simultaneously, which is usually the desired outcome. Verify no pipeline intentionally uses a different credential before updating.