Skip to content

Commit 5eb29fe

Browse files
Merge pull request #3566 from Blackmist/typo
fixing typo
2 parents 2181356 + 3bbfea8 commit 5eb29fe

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
@@ -8,7 +8,7 @@ ms.subservice: enterprise-readiness
88
ms.reviewer: None
99
ms.author: larryfr
1010
author: Blackmist
11-
ms.date: 06/11/2024
11+
ms.date: 03/17/2025
1212
ms.topic: how-to
1313
ms.custom: security
1414
monikerRange: 'azureml-api-2 || azureml-api-1'
@@ -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. 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 data 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

0 commit comments

Comments
 (0)