Skip to content

Commit 8a6f3fa

Browse files
Merge pull request #232456 from Blackmist/61720-public-workspace
comment
2 parents 9c5337f + 60349a0 commit 8a6f3fa

File tree

3 files changed

+22
-4
lines changed

3 files changed

+22
-4
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-network-security-overview.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,13 +90,19 @@ The next sections show you how to secure the network scenario described above. T
9090

9191
## Public workspace and secured resources
9292

93+
> [!IMPORTANT]
94+
> While this is a supported configuration for Azure Machine Learning, Microsoft doesn't recommend it. The data in the Azure Storage Account behind the virtual network can be exposed on the public workspace. You should verify this configuration with your security team before using it in production.
95+
9396
If you want to access the workspace over the public internet while keeping all the associated resources secured in a virtual network, use the following steps:
9497

9598
1. Create an [Azure Virtual Network](../virtual-network/virtual-networks-overview.md) that will contain the resources used by the workspace.
9699
1. Use __one__ of the following options to create a publicly accessible workspace:
97100

98101
:::moniker range="azureml-api-2"
99102
* Create an Azure Machine Learning workspace that __does not__ use the virtual network. For more information, see [Manage Azure Machine Learning workspaces](how-to-manage-workspace.md).
103+
104+
OR
105+
100106
* Create a [Private Link-enabled workspace](how-to-secure-workspace-vnet.md#secure-the-workspace-with-private-endpoint) to enable communication between your VNet and workspace. Then [enable public access to the workspace](#optional-enable-public-access).
101107
:::moniker-end
102108
:::moniker range="azureml-api-1"
@@ -291,7 +297,7 @@ Microsoft Sentinel is a security solution that can integrate with Azure Machine
291297

292298
### Public access
293299

294-
Microsoft Sentinel can automatically create a workspace for you if you are OK with a public endpoint. In this configuration, the security operations center (SOC) analysts and system administrators connect to notebooks in your workspace through Sentinel.
300+
Microsoft Sentinel can automatically create a workspace for you if you're OK with a public endpoint. In this configuration, the security operations center (SOC) analysts and system administrators connect to notebooks in your workspace through Sentinel.
295301

296302
For information on this process, see [Create an Azure Machine Learning workspace from Microsoft Sentinel](../sentinel/notebooks-hunt.md?tabs=public-endpoint#create-an-azure-ml-workspace-from-microsoft-sentinel)
297303

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

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ In this article you learn how to enable the following workspaces resources in a
8080

8181
### Azure Container Instances
8282

83-
When your Azure Machine Learning workspace is configured with a private endpoint, deploying to Azure Container Instances in a VNet is not supported. Instead, consider using a [Managed online endpoint with network isolation](how-to-secure-online-endpoint.md).
83+
When your Azure Machine Learning workspace is configured with a private endpoint, deploying to Azure Container Instances in a VNet isn't supported. Instead, consider using a [Managed online endpoint with network isolation](how-to-secure-online-endpoint.md).
8484

8585
### Azure Container Registry
8686

@@ -216,7 +216,7 @@ Azure Container Registry can be configured to use a private endpoint. Use the fo
216216

217217
[!INCLUDE [cli v2](../../includes/machine-learning-cli-v2.md)]
218218

219-
If you've [installed the Machine Learning extension v2 for Azure CLI](how-to-configure-cli.md), you can use the `az ml workspace show` command to show the workspace information. The v1 extension does not return this information.
219+
If you've [installed the Machine Learning extension v2 for Azure CLI](how-to-configure-cli.md), you can use the `az ml workspace show` command to show the workspace information. The v1 extension doesn't return this information.
220220

221221
```azurecli-interactive
222222
az ml workspace show -n yourworkspacename -g resourcegroupname --query 'container_registry'
@@ -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 working from home and can't establish a VPN connection to the VNet.
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)