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/service/how-to-enable-virtual-network.md
+19-8Lines changed: 19 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,14 +33,14 @@ This document assumes that you are familiar with Azure Virtual Networks, and IP
33
33
> [!IMPORTANT]
34
34
> You can put the storage account that is attached to Azure Machine Learning service workspace behind the virtual network only while doing experimentation. Inference requires unrestricted access to the storage account. If you aren't sure if you've modified these settings or not, see __Change the default network access rule__ in [Configure Azure Storage firewalls and virtual networks](https://docs.microsoft.com/azure/storage/common/storage-network-security). Use the steps to allow access from all networks during inference, or model scoring.
35
35
36
-
To use Azure Machine Learning experimentation capabilities with Azure Storage behind a virtual network follow the steps below:
36
+
To use Azure Machine Learning experimentation capabilities with Azure Storage behind a virtual network, follow the steps below:
37
37
38
38
1. Create an experimentation compute ex. Machine Learning Compute behind a virtual network or attach an experimentation compute to the workspace ex. HDInsight cluster or virtual machine. For more information, see [Use Machine Learning Compute](#use-machine-learning-compute) and [Use a virtual machine or HDInsight cluster](#use-a-virtual-machine-or-hdinsight-cluster) sections in this document
39
39
2. Go to the storage attached to the workspace. 
40
40
3. On the Azure Storage page, select __Firewalls and virtual networks__. 
41
-
4. On the __Firewalls and virtual networks__ page select the following:
41
+
4. On the __Firewalls and virtual networks__ page select the following entries:
42
42
- Select __Selected networks__.
43
-
- Under __Virtual networks__ select __Add existing virtual network__ to add the virtual network where your experimentation compute resides. (See step 1.)
43
+
- Under __Virtual networks__, select __Add existing virtual network__ to add the virtual network where your experimentation compute resides. (See step 1.)
44
44
- Select __Allow trusted Microsoft services to access this storage account__.
45
45

46
46
@@ -57,10 +57,10 @@ Key Vault instance associated with the workspace is used by Azure Machine Learni
57
57
58
58
To use Azure Machine Learning experimentation capabilities with Key Vault behind a virtual network follow the steps below:
59
59
1. Go to the Key Vault associated with the workspace. 
60
-
2. On the Key Vault page select __Firewalls and virtual networks__ section. 
61
-
3. On the __Firewalls and virtual networks__ page select the following:
60
+
2. On the Key Vault page, select __Firewalls and virtual networks__ section. 
61
+
3. On the __Firewalls and virtual networks__ page select the following entries:
62
62
- Select __Selected networks__.
63
-
- Under the __Virtual networks__ select __Add existing virtual networks__ to add the virtual network where your experimentation compute resides.
63
+
- Under the __Virtual networks__, select __Add existing virtual networks__ to add the virtual network where your experimentation compute resides.
64
64
- Select __Allow trusted Microsoft services to bypass this firewall__.
65
65

66
66
@@ -97,7 +97,7 @@ Machine Learning Compute currently uses the Azure Batch service to provision VMs
97
97
98
98

99
99
100
-
- (optional) Inbound TCP traffic on port 22 to permit remote access. This is only needed if you want to connect using SSH on the public IP.
100
+
- (optional) Inbound TCP traffic on port 22 to permit remote access. This port is only needed if you want to connect using SSH on the public IP.
101
101
102
102
- Outbound traffic on any port to the virtual network.
103
103
@@ -125,8 +125,19 @@ The following screenshot shows how the NSG rule configuration looks in the Azure
125
125
126
126

127
127
128
+
### User-defined routes for forced tunneling
128
129
130
+
If you are using forced tunneling with Azure Machine Learning Compute, you must add [user-defined routes (UDR)](https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview) to the subnet that contains the compute resource.
129
131
132
+
* A user-defined route for each IP address used by the Azure Batch service in the region where your resources exist. These UDRs enable the batch service to communicate with compute nodes for task scheduling. To get a list of the IP addresses of the Batch service, contact Azure Support.
133
+
134
+
* Outbound traffic to Azure Storage (specifically, URLs of the form `<account>.table.core.windows.net`, `<account>.queue.core.windows.net`, and`<account>.blob.core.windows.net`) must not be blocked by your on-premises network appliance.
135
+
136
+
When you add the user-defined routes, define the route for each related Batch IP address prefix, andset __Next hop type__ to __Internet__. The following image shows an example of this UDRin the Azure portal:
137
+
138
+

139
+
140
+
For more information, see the [Create an Azure Batch pool in a virtual network](/azure/batch/batch-virtual-network.md#user-defined-routes-for-forced-tunneling) article.
130
141
131
142
### Create Machine Learning Compute in a virtual network
132
143
@@ -229,7 +240,7 @@ To use a virtual machine or Azure HDInsight cluster in a virtual network with yo
229
240
> [!IMPORTANT]
230
241
> Check the prerequisites and plan IP addressing for your cluster before proceeding with the steps. For more information, see [Configure advanced networking in Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/configure-advanced-networking).
231
242
>
232
-
243
+
>
233
244
> Keep the default outbound rules for the NSG. For more information, see the default security rules in [Security groups](https://docs.microsoft.com/azure/virtual-network/security-overview#default-security-rules).
234
245
>
235
246
> Azure Kubernetes Service and the Azure virtual network should be in the same region.
0 commit comments