--- title: "Azure Databricks" slug: "azure-databricks-overview-replicate-cloud" updated: 2026-06-11T14:15:26Z published: 2026-06-11T14:15:26Z canonical: "skthelp.syniti.com/azure-databricks-overview-replicate-cloud" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Azure Databricks ## Overview With Replicate Preview, creating a powerful replication pipeline to Azure Databricks is a streamlined process. Users can configure connections, select tables, and deploy a fully managed pipeline in just a few steps—without requiring deep expertise in cluster management or distributed systems. This significantly reduces time-to-value while maintaining enterprise-grade performance and reliability. > [!NOTE] > Note > > Azure Databricks is currently supported only as a **target endpoint** in Replicate Preview, limited to **Snapshot (full load) replication mode**, with Change Data Capture (CDC) not yet supported. ### Microsoft Azure Prerequisites Replicate Preview requires appropriate authentication and permissions to interact with Azure Databricks resources. Ensure the following prerequisites are met: - Access to an active Azure Databricks workspace - A running **SQL Warehouse (formerly SQL Endpoint)** configured in the workspace - Permissions to create and write to target schemas and tables - Network access to the Databricks workspace endpoint Refer to [Create a Connection for Databricks](/v1/docs/connecting-to-databricks) for more information on creating Databricks connections. For secure authentication, we recommend using **OAuth 2.0 via Microsoft Entra ID**. #### Generate a Personal Access Token (PAT) A Personal Access Token (PAT) can be used for authentication when connecting to Azure Databricks. To generate a token: 1. Log in to your Azure Databricks workspace. 2. Access **User Settings** and select **Developer.** 3. Click **Create New Token**. 4. Copy and securely store the generated token > [!NOTE] > **Note:** Personal Access Tokens are optional when using **OAuth 2.0 (Microsoft Entra ID)** authentication, which is the recommended approach for enterprise deployments. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-W93NO0L4.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A10Z&se=2026-11-17T20%3A21%3A10Z&sr=b&sp=r&sig=0swwpYWmyFRlg5sS2ixO8s7ZH0p70%2FKYfZj1xo4fNhQ%3D) ### Connection Considerations - Ensure the correct **Databricks Server Hostname** and **HTTP Path** (SQL Warehouse endpoint) are configured in the connection settings. - Verify that the SQL Warehouse is running before initiating replication jobs. - Confirm that the target schema exists or that the configured user has permissions to create it. - Review object naming conventions when replicating SAP or legacy systems to ensure compatibility with Databricks constraints. In Replicate Preview, configure your workspace using this system datastore and start replicating data. Refer to [Configure Workspace: Datastores](/v1/docs/configure-workspace-datastores) for more information. ### Limitations - Tables with special characters (for example `/SAPAPO/MATKEY`) are not supported. Target table names must contain only alphanumeric characters and underscores. Replace unsupported characters (such as `/`) with underscores when defining the target table. - Azure Databricks targets support **Snapshot (full load) replication only**; incremental or CDC-based replication is not available. - Azure Databricks can be configured **only as a target endpoint** in Replicate Preview. ## Related Articles - [Create a Connection](/v1/docs/create-a-connection) - [Configure Workspace: Datastores](/v1/docs/configure-workspace-datastores) - [Create a Connection for Databricks](/v1/docs/connecting-to-databricks)