Skip to content

Commit 0628482

Browse files
Merge pull request #1337 from meerakurup/patch-2
Update how-to-securely-attach-databricks.md
2 parents f3d8514 + fe9d7f5 commit 0628482

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/machine-learning/how-to-securely-attach-databricks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The information in this article assumes that your Azure Machine Learning workspa
3535

3636
## Limitations
3737

38-
Scenarios where the Azure Machine Learning control plane needs to communicate with the Azure Databricks control plane are not supported. Currently the only scenario we have identified where this is a problem is when using the [DatabrickStep](/python/api/azureml-pipeline-steps/azureml.pipeline.steps.databricks_step.databricksstep) in a machine learning pipeline. To work around this limitation, allows public access to your workspace. This can be either using a workspace that isn't configured with a private link or a workspace with a private link that is [configured to allow public access](how-to-configure-private-link.md#enable-public-access).
38+
Scenarios where the Azure Machine Learning control plane needs to communicate with the Azure Databricks control plane are not supported. To work around this limitation, allows public access to your workspace. This can be either using a workspace that isn't configured with a private link or a workspace with a private link that is [configured to allow public access](how-to-configure-private-link.md#enable-public-access).
3939

4040
## Create a private endpoint for Azure Machine Learning
4141

@@ -90,4 +90,4 @@ To allow Azure Databricks to communicate with the VNet that the Azure Machine Le
9090

9191
## Next steps
9292

93-
* [Manage compute resources for training and deployment](how-to-create-attach-compute-studio.md)
93+
* [Manage compute resources for training and deployment](how-to-create-attach-compute-studio.md)

0 commit comments

Comments
 (0)