Skip to content

Commit d6c32e2

Browse files
authored
Update how-to-enable-virtual-network.md
1 parent b2ead83 commit d6c32e2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/machine-learning/how-to-enable-virtual-network.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ ms.custom: contperfq4
2121
In this article, you'll learn how to isolate experimentation/training jobs and inference/scoring jobs in Azure Machine Learning within an Azure Virtual Network (vnet). You'll also learn about some *advanced security settings*, information that isn't necessary for basic or experimental use cases.
2222

2323
> [!WARNING]
24-
> If your underlying storage is in a virtual network, users will not be able to use Azure Machine Learning's studio web experience for drag-n-drop designer, the UI for automated machine learning, data labeling, and so on.
24+
> If your underlying storage is in a virtual network, users will not be able to use Azure Machine Learning's studio web experience for drag-n-drop designer, the UI for automated machine learning, and data labeling.
2525
2626
## What is a VNET?
2727

@@ -67,7 +67,7 @@ You can also [enable Azure Private Link](how-to-configure-private-link.md) to co
6767

6868
<a id="amlcompute"></a>
6969

70-
## <a name="compute-instance"></a>Compute targets or compute instances
70+
## <a name="compute-instance"></a>Compute clusters & instances
7171

7272
To use either a [managed Azure Machine Learning **compute target**](concept-compute-target.md#azure-machine-learning-compute-managed) or an [Azure Machine Learning compute **instance**](concept-compute-instance.md) in a virtual network, the following network requirements must be met:
7373

0 commit comments

Comments
 (0)