You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-managed-network.md
+34-27Lines changed: 34 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Azure Machine Learning provides preview support for managed virtual network (VNe
25
25
26
26
When you enable managed virtual network isolation, a managed VNet is created for the workspace. Managed compute resources (compute clusters and compute instances) for the workspace automatically use this managed VNet. The managed VNet can use private endpoints for Azure resources that are used by your workspace, such as Azure Storage, Azure Key Vault, and Azure Container Registry.
27
27
28
-
The following diagram shows a managed virtual network uses private endpoints to communicate with the storage, key vault, and container registry used by the workspace.
28
+
The following diagram shows how a managed virtual network uses private endpoints to communicate with the storage, key vault, and container registry used by the workspace.
29
29
30
30
:::image type="content" source="./media/how-to-managed-network/managed-virtual-network-architecture.png" alt-text="Diagram of managed virtual network isolation.":::
31
31
@@ -37,7 +37,7 @@ There are two different configuration modes for outbound traffic from the manage
37
37
| Outbound mode | Description | Scenarios |
38
38
| ----- | ----- | ----- |
39
39
| Allow internet outbound | Allow all internet outbound traffic from the managed VNet. | Recommended if you need access to machine learning artifacts on the Internet, such as python packages or pretrained models. |
40
-
| Allow only approved outbound | Outbound traffic is allowed by specifying service tags. | Recommended if you want to minimize the risk of data exfiltration but you need to prepare all required machine learning artifacts in your private locations. |
40
+
| Allow only approved outbound | Outbound traffic is allowed by specifying service tags. | Recommended if you want to minimize the risk of data exfiltration but you will need to prepare all required machine learning artifacts in your private locations. |
41
41
42
42
The managed virtual network is preconfigured with [required default rules](#list-of-required-rules). It's also configured for private endpoint connections to your workspace default storage, container registry and key vault if they're configured as private. After choosing the isolation mode, you only need to consider other outbound requirements you may need to add.
43
43
@@ -87,14 +87,21 @@ Before following the steps in this article, make sure you have the following pre
87
87
88
88
```python
89
89
from azure.ai.ml import MLClient
90
-
from azure.ai.ml.entities import Workspace, ManagedNetwork
91
-
from azure.ai.ml.constants._workspace import IsolationMode
90
+
from azure.ai.ml.entities import (
91
+
Workspace,
92
+
ManagedNetwork,
93
+
IsolationMode,
94
+
ServiceTagDestination,
95
+
PrivateEndpointDestination
96
+
)
92
97
from azure.identity import DefaultAzureCredential
93
-
from azure.ai.ml.entities import ServiceTagDestination, PrivateEndpointDestination
94
98
95
99
# Replace with the values for your Azure subscription and resource group.
@@ -203,9 +210,6 @@ To configure a managed VNet that allows internet outbound communications, use th
203
210
The following example creates a new workspace named `myworkspace`, with an outbound rule named `myrule` that adds a private endpoint for an Azure Blob store:
> These rules are automatically added to the managed VNet.
704
706
705
-
__Outbound__ rules:
707
+
__Private endpoints__:
708
+
* When the isolation mode for the managed network is `Allow internet outbound`, private endpoint outbound rules will be automatically created as required rules from the managed network for the workspace and associated resources __with public network access disabled__ (Key Vault, Storage Account, Container Registry, Azure ML Workspace).
709
+
* When the isolation mode for the managed network is `Allow only approved outbound`, private endpoint outbound rules will be automatically created as required rules from the managed network for the workspace and associated resources __regardless of public network access mode for those resources__ (Key Vault, Storage Account, Container Registry, Azure ML Workspace).
710
+
711
+
__Outbound__ service tag rules:
706
712
707
713
* `AzureActiveDirectory`
708
714
* `AzureMachineLearning`
@@ -712,7 +718,7 @@ __Outbound__ rules:
712
718
* `MicrosoftContainerRegistry`
713
719
* `AzureMonitor`
714
720
715
-
__Inbound__ rules:
721
+
__Inbound__ service tag rules:
716
722
* `AzureMachineLearning`
717
723
718
724
## List of recommended outbound rules
@@ -723,6 +729,7 @@ Currently we don't have any recommended outbound rules.
723
729
724
730
* Once you enable managed virtual network isolation of your workspace, you can't disable it.
725
731
* Managed virtual network uses private endpoint connection to access your private resources. You can't have a private endpoint and a service endpoint at the same time for your Azure resources, such as a storage account. We recommend using private endpoints in all scenarios.
732
+
* The managed network will be deleted and cleaned up when the workspace is deleted.
0 commit comments