Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit a0a733c

Browse files
committedJan 5, 2022
adding info on removing private endpoint and updating enable private endpoint
1 parent 241b37c commit a0a733c

File tree

3 files changed

+47
-6
lines changed

3 files changed

+47
-6
lines changed
 

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

Lines changed: 47 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.custom: devx-track-azurecli
1010
ms.author: aashishb
1111
author: aashishb
1212
ms.reviewer: larryfr
13-
ms.date: 10/21/2021
13+
ms.date: 01/05/2022
1414
---
1515

1616
# Configure a private endpoint for an Azure Machine Learning workspace
@@ -232,20 +232,57 @@ If you want to create an isolated Azure Kubernetes Service used by the workspace
232232

233233
:::image type="content" source="./media/how-to-configure-private-link/multiple-private-endpoint-workspace-aks.png" alt-text="Diagram of isolated AKS VNet":::
234234

235+
## Remove private endpoints
236+
237+
You can remove one or all private endpoints for a workspace. Removing a private endpoint removes the workspace from the VNet that the endpoint was associated with. This may prevent the workspace from accessing resources in that VNet, or resources in the VNet from accessing the workspace. For example, if the VNet does not allow access to or from the public internet.
238+
239+
> [!WARNING]
240+
> Disabling the private endpoints for a workspace __doesn't make it publicly accessible__. To make the workspace publicly accessible, use the steps in the [Enable public access](#enable-public-access) section.
241+
242+
To remove a private endpoint, use the following steps:
243+
244+
# [Python](#tab/python)
245+
246+
To remove a private endpoint, use [Workspace.delete_private_endpoint_connection](/python/api/azureml-core/azureml.core.workspace(class)#delete-private-endpoint-connection-private-endpoint-connection-name-).
247+
248+
```python
249+
from azureml.core import Workspace
250+
251+
ws = Workspace.from_config()
252+
ws.delete_private_endpoint_connection("your-pe-connection-name")
253+
```
254+
255+
# [Python](#tab/azure-cli)
256+
257+
To remove a private endpoint using the Azure CLI, use the [az network private-endpoint delete](/cli/azure/network/private-endpoint#az_network_private_endpoint_delete) command.
258+
259+
# [Portal](#tab/azure-portal)
260+
261+
1. From the [Azure portal](https://portal.azure.com), select your Azure Machine Learning workspace.
262+
1. From the left side of the page, select __Networking__ and then select the __Private endpoint connections__ tab.
263+
1. Select the endpoint to remove and then select __Remove__.
264+
265+
:::image type="content" source="./media/how-to-configure-private-link/remove-private-endpoint.png" alt-text="Screenshot of the UI to remove a private endpoint.":::
266+
267+
---
268+
235269
## Enable public access
236270

237-
In some situations, you may want to allow someone to connect to your secured workspace over a public endpoint, instead of through the VNet. After configuring a workspace with a private endpoint, you can optionally enable public access to the workspace. Doing so does not remove the private endpoint. All communications between components behind the VNet is still secured. It enables public access only to the workspace, in addition to the private access through the VNet.
271+
In some situations, you may want to allow someone to connect to your secured workspace over a public endpoint, instead of through the VNet. Or you may want to remove the workspace from the VNet and re-enable public access.
272+
273+
> [!IMPORTANT]
274+
> Enabling public access doesn't remove any private endpoints that exist. All communications between components behind the VNet that the private endpoint(s) connect to is still secured. It enables public access only to the workspace, in addition to the private access through any private endpoints.
238275
239276
> [!WARNING]
240-
> When connecting over the public endpoint:
277+
> When connecting over the public endpoint while the workspace uses a private endpoint to communicate with other resources:
241278
> * __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.
242279
> * Using Jupyter, JupyterLab, and RStudio on a compute instance, including running notebooks, __is not supported__.
243280
244-
To enable public access to a private endpoint-enabled workspace, use the following steps:
281+
To enable public access, use the following steps:
245282

246283
# [Python](#tab/python)
247284

248-
Use [Workspace.delete_private_endpoint_connection](/python/api/azureml-core/azureml.core.workspace(class)#delete-private-endpoint-connection-private-endpoint-connection-name-) to remove a private endpoint.
285+
To enable public access, use [Workspace.update](/python/api/azureml-core/azureml.core.workspace(class)#update-friendly-name-none--description-none--tags-none--image-build-compute-none--service-managed-resources-settings-none--primary-user-assigned-identity-none--allow-public-access-when-behind-vnet-none-) and set `allow_public_access_when_behind_vnet=True`.
249286

250287
```python
251288
from azureml.core import Workspace
@@ -260,7 +297,11 @@ The Azure CLI [extension 1.0 for machine learning](reference-azure-machine-learn
260297

261298
# [Portal](#tab/azure-portal)
262299

263-
Currently there is no way to enable this functionality using the portal.
300+
1. From the [Azure portal](https://portal.azure.com), select your Azure Machine Learning workspace.
301+
1. From the left side of the page, select __Networking__ and then select the __Public access__ tab.
302+
1. Select __All networks__, and then select __Save__.
303+
304+
:::image type="content" source="./media/how-to-configure-private-link/workspace-public-access.png" alt-text="Screenshot of the UI to enable public endpoint.":::
264305

265306
---
266307

Loading
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.