Troubleshoot the Anthropic connector

Important

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

Learn how to troubleshoot common issues with the Anthropic connector.

Pipeline fails to authenticate

If your pipeline fails to read from Anthropic, verify the Compliance Access Key stored in your Unity Catalog connection matches the value in Anthropic. Also verify that the key is a Compliance Access Key (sk-ant-api01-...) created in claude.ai — Admin API keys (sk-ant-admin01-...) are not accepted and return a 403 response. For the prerequisites and key creation steps, see Configure authentication to Anthropic.

If the key is incorrect or has been rotated, create a new key and update the Unity Catalog connection. See Create an Anthropic connection.

A table is missing users, chats, or messages

The users, chats, and messages tables require additional scopes on the Compliance Access Key. If these tables are empty or incomplete, verify that the key was created with the read:compliance_user_data scope in addition to read:compliance_org_data. See Configure Anthropic.