|
1 | 1 | --- |
2 | | -page_title: "Provisioning Databricks on Azure with Private Link - Simple deployment" |
| 2 | +page_title: "Provisioning Azure Databricks with Private Link - Simple deployment" |
3 | 3 | --- |
4 | 4 |
|
5 | | -# Deploying pre-requisite resources and enabling Private Link connections |
| 5 | +# Deploying pre-requisite resources and enabling Private Link connections - Simple deployment |
| 6 | + |
| 7 | +-> **Note** Refer to the [Databricks Terraform Registry modules](https://registry.terraform.io/modules/databricks/examples/databricks/latest) for Terraform modules and examples to deploy Azure Databricks resources. |
6 | 8 |
|
7 | 9 | -> **Note** This guide assumes that connectivity from the on-premises user environment is already configured using ExpressRoute or a VPN gateway connection. |
8 | 10 |
|
9 | | -Databricks Private Link support enables private connectivity between users and their Databricks workspaces and between clusters on the data plane and core services on the control plane within the Databricks workspace infrastructure. |
| 11 | +[Azure Private Link](https://learn.microsoft.com/en-us/azure/private-link/private-link-overview) support enables private connectivity between users and their Databricks workspaces and between clusters on the data plane and core services on the control plane within the Databricks workspace infrastructure. |
10 | 12 |
|
11 | 13 | You can use Terraform to deploy the underlying cloud resources and the private access settings resources automatically, using a programmatic approach. |
12 | 14 |
|
13 | | - |
14 | 15 | This guide covers a [simple deployment](https://learn.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/private-link-simplified) to configure Azure Databricks with Private Link: |
15 | 16 | * No separate VNet separates user access from the VNet that you use for your compute resources in the Classic data plane |
16 | 17 | * A transit subnet in the data plane VNet is used for user access |
17 | 18 | * Only a single private endpoint is used for both front-end and back-end connectivity. |
18 | 19 | * A separate private endpoint is used for web authentication |
19 | 20 | * The same Databricks workspace is used for web authentication traffic but Databricks strongly recommends creating a separate workspace called a private web auth workspace for each region to host the web auth private network settings. |
20 | 21 |
|
21 | | - |
| 22 | + |
22 | 23 |
|
23 | 24 | This guide uses the following variables: |
24 | 25 |
|
|
0 commit comments