Skip to content

Commit 7388c93

Browse files
author
Larry Franks
committed
writing
1 parent 32f04c8 commit 7388c93

File tree

2 files changed

+14
-2
lines changed

2 files changed

+14
-2
lines changed

articles/machine-learning/how-to-configure-private-link.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -263,7 +263,7 @@ In some situations, you may want to allow someone to connect to your secured wor
263263
264264
> [!WARNING]
265265
> When connecting over the public endpoint while the workspace uses a private endpoint to communicate with other resources:
266-
> * __Some features of studio will fail to access your data__. This problem happens when the _data is stored on a service that is secured behind the VNet_. For example, an Azure Storage Account.
266+
> * __Some features of studio will fail to access your data__. This problem happens when the _data is stored on a service that is secured behind the VNet_. For example, an Azure Storage Account. To resolve this problem, add your client device's IP address to the [Azure Storage Account's firewall](../storage/common/storage-network-security.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#grant-access-from-an-internet-ip-range).
267267
> * Using Jupyter, JupyterLab, RStudio, or Posit Workbench (formerly RStudio Workbench) on a compute instance, including running notebooks, __is not supported__.
268268
269269
To enable public access, use the following steps:

articles/machine-learning/how-to-secure-workspace-vnet.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ When your Azure Machine Learning workspace is configured with a private endpoint
8484

8585
### Azure Container Registry
8686

87-
When ACR is behind a virtual network, Azure Machine Learning cant use it to directly build Docker images. Instead, the compute cluster is used to build the images.
87+
When ACR is behind a virtual network, Azure Machine Learning can't use it to directly build Docker images. Instead, the compute cluster is used to build the images.
8888

8989
> [!IMPORTANT]
9090
> The compute cluster used to build Docker images needs to be able to access the package repositories that are used to train and deploy your models. You may need to add network security rules that allow access to public repos, [use private Python packages](how-to-use-private-python-packages.md), or use [custom Docker images](v1/how-to-train-with-custom-image.md) that already include the packages.
@@ -339,6 +339,18 @@ To enable network isolation for Azure Monitor and the Application Insights insta
339339
340340
[!INCLUDE [machine-learning-workspace-diagnostics](../../includes/machine-learning-workspace-diagnostics.md)]
341341
342+
## Public access to workspace
343+
344+
> [!IMPORTANT]
345+
> While this is a supported configuration for Azure Machine Learning, Microsoft doesn't recommend it. You should verify this configuration with your security team before using it in production.
346+
347+
In some cases, you may need to allow access to the workspace from the public network (without connecting through the VNet using the methods detailed the [Securely connect to your workspace](#securely-connect-to-your-workspace) section). Access over the public internet is secured using TLS.
348+
349+
To enable public network access to the workspace, use the following steps:
350+
351+
1. [Enable public access](how-to-configure-private-link.md#enable-public-access) to the workspace after configuring the workspace's private endpoint.
352+
1. [Configure the Azure Storage firewall](../storage/common/storage-network-security.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#grant-access-from-an-internet-ip-range) to allow communication with the IP address of clients that connect over the public internet. You may need to change the allowed IP address if the clients don't have a static IP. For example, if one of your Data Scientists is traveling and using the WIFI connection from a hotel.
353+
342354
## Next steps
343355
344356
This article is part of a series on securing an Azure Machine Learning workflow. See the other articles in this series:

0 commit comments

Comments
 (0)