Skip to content

Commit 475acd2

Browse files
authored
Merge pull request #184848 from Blackmist/1906108-multiple-pe-ga
GA for multiple PE workspace
2 parents 5dcee17 + 52509c4 commit 475acd2

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

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

Lines changed: 5 additions & 5 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: 01/10/2022
13+
ms.date: 01/12/2022
1414
---
1515

1616
# Configure a private endpoint for an Azure Machine Learning workspace
@@ -42,7 +42,7 @@ Azure Private Link enables you to connect to your workspace using a private endp
4242
* Using a private endpoint does not effect Azure control plane (management operations) such as deleting the workspace or managing compute resources. For example, creating, updating, or deleting a compute target. These operations are performed over the public Internet as normal. Data plane operations, such as using Azure Machine Learning studio, APIs (including published pipelines), or the SDK use the private endpoint.
4343
* When creating a compute instance or compute cluster in a workspace with a private endpoint, the compute instance and compute cluster must be in the same Azure region as the workspace.
4444
* When creating or attaching an Azure Kubernetes Service cluster to a workspace with a private endpoint, the cluster must be in the same region as the workspace.
45-
* When using a workspace with multiple private endpoints (preview), one of the private endpoints must be in the same VNet as the following dependency services:
45+
* When using a workspace with multiple private endpoints, one of the private endpoints must be in the same VNet as the following dependency services:
4646

4747
* Azure Storage Account that provides the default storage for the workspace
4848
* Azure Key Vault for the workspace
@@ -383,9 +383,9 @@ The Azure CLI [extension 1.0 for machine learning](reference-azure-machine-learn
383383

384384
[!INCLUDE [machine-learning-connect-secure-workspace](../../includes/machine-learning-connect-secure-workspace.md)]
385385

386-
## Multiple private endpoints (preview)
386+
## Multiple private endpoints
387387

388-
As a preview feature, Azure Machine Learning supports multiple private endpoints for a workspace. Multiple private endpoints are often used when you want to keep different environments separate. The following are some scenarios that are enabled by using multiple private endpoints:
388+
Azure Machine Learning supports multiple private endpoints for a workspace. Multiple private endpoints are often used when you want to keep different environments separate. The following are some scenarios that are enabled by using multiple private endpoints:
389389

390390
* Client development environments in a separate VNet.
391391
* An Azure Kubernetes Service (AKS) cluster in a separate VNet.
@@ -400,7 +400,7 @@ As a preview feature, Azure Machine Learning supports multiple private endpoints
400400
> [!IMPORTANT]
401401
> Each VNet that contains a private endpoint for the workspace must also be able to access the Azure Storage Account, Azure Key Vault, and Azure Container Registry used by the workspace. For example, you might create a private endpoint for the services in each VNet.
402402
403-
Adding multiple endpoints uses the same steps as described in the [Add a private endpoint to a workspace](#add-a-private-endpoint-to-a-workspace) section.
403+
Adding multiple private endpoints uses the same steps as described in the [Add a private endpoint to a workspace](#add-a-private-endpoint-to-a-workspace) section.
404404

405405
### Scenario: Isolated clients
406406

articles/machine-learning/how-to-network-security-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ The following table compares how services access different parts of an Azure Mac
5555
* **Associated resource** - Use service endpoints or private endpoints to connect to workspace resources like Azure storage, Azure Key Vault. For Azure Container Services, use a private endpoint.
5656
* **Service endpoints** provide the identity of your virtual network to the Azure service. Once you enable service endpoints in your virtual network, you can add a virtual network rule to secure the Azure service resources to your virtual network. Service endpoints use public IP addresses.
5757
* **Private endpoints** are network interfaces that securely connect you to a service powered by Azure Private Link. Private endpoint uses a private IP address from your VNet, effectively bringing the service into your VNet.
58-
* **Training compute access** - Access training compute targets like Azure Machine Learning Compute Instance and Azure Machine Learning Compute Clusters with public IP addresses (preview).
58+
* **Training compute access** - Access training compute targets like Azure Machine Learning Compute Instance and Azure Machine Learning Compute Clusters with public or private IP addresses.
5959
* **Inference compute access** - Access Azure Kubernetes Services (AKS) compute clusters with private IP addresses.
6060

6161

0 commit comments

Comments
 (0)