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/ai-studio/how-to/configure-private-link.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -264,6 +264,8 @@ If you need to configure custom DNS server without DNS forwarding, use the follo
264
264
> * Compute instances can be accessed only from within the virtual network.
265
265
> * The IP address for this FQDN is **not** the IP of the compute instance. Instead, use the private IP address of the workspace private endpoint (the IP of the `*.api.azureml.ms` entries.)
266
266
267
+
*`<instance-name>.<region>.instances.azureml.ms` - Only used by the `az ml compute connect-ssh` command to connect to computes in a managed virtual network. Not needed if you are not using a managed network or SSH connections.
268
+
267
269
*`<managed online endpoint name>.<region>.inference.ml.azure.com` - Used by managed online endpoints
268
270
269
271
To find the private IP addresses for your A records, see the [Azure Machine Learning custom DNS](../../machine-learning/how-to-custom-dns.md#find-the-ip-addresses) article.
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-custom-dns.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,20 +75,23 @@ Access to a given Azure Machine Learning workspace via Private Link is done by c
75
75
-```<per-workspace globally-unique identifier>.workspace.<region the workspace was created in>.api.azureml.ms```
76
76
-```<per-workspace globally-unique identifier>.workspace.<region the workspace was created in>.cert.api.azureml.ms```
77
77
-```<compute instance name>.<region the workspace was created in>.instances.azureml.ms```
78
+
-`<compute instance name>-22.<region the workspace was created in>.instances.azureml.ms` - Used by the `az ml compute connect-ssh` command to connect to computes in a managed virtual network.
-```<managed online endpoint name>.<region>.inference.ml.azure.com``` - Used by managed online endpoints
80
81
81
82
**Microsoft Azure operated by 21Vianet regions**:
82
83
-```<per-workspace globally-unique identifier>.workspace.<region the workspace was created in>.api.ml.azure.cn```
83
84
-```<per-workspace globally-unique identifier>.workspace.<region the workspace was created in>.cert.api.ml.azure.cn```
84
85
-```<compute instance name>.<region the workspace was created in>.instances.azureml.cn```
86
+
-`<compute instance name>-22.<region the workspace was created in>.instances.azureml.cn` - Used by the `az ml compute connect-ssh` command to connect to computes in a managed virtual network.
-```<managed online endpoint name>.<region>.inference.ml.azure.cn``` - Used by managed online endpoints
87
89
88
90
**Azure US Government regions**:
89
91
-```<per-workspace globally-unique identifier>.workspace.<region the workspace was created in>.api.ml.azure.us```
90
92
-```<per-workspace globally-unique identifier>.workspace.<region the workspace was created in>.cert.api.ml.azure.us```
91
93
-```<compute instance name>.<region the workspace was created in>.instances.azureml.us```
94
+
-`<compute instance name>.<region the workspace was created in>.instances.azureml.us` - Used by the `az ml compute connect-ssh` command to connect to computes in a managed virtual network.
-```<managed online endpoint name>.<region>.inference.ml.azure.us``` - Used by managed online endpoints
94
97
@@ -134,7 +137,7 @@ The following list contains the fully qualified domain names (FQDNs) used by you
134
137
> [!NOTE]
135
138
> * Compute instances can be accessed only from within the virtual network.
136
139
> * The IP address for this FQDN is **not** the IP of the compute instance. Instead, use the private IP address of the workspace private endpoint (the IP of the `*.api.azureml.ms` entries.)
137
-
140
+
*`<instance-name>-22.<region>.instances.azureml.ms` - Only used by the `az ml compute connect-ssh` command to connect to computes in a managed virtual network. Not needed if you are not using a managed network or SSH connections.
138
141
*`<managed online endpoint name>.<region>.inference.ml.azure.com` - Used by managed online endpoints
139
142
140
143
#### Microsoft Azure operated by 21Vianet region
@@ -152,6 +155,7 @@ The following FQDNs are for Microsoft Azure operated by 21Vianet regions:
152
155
153
156
* The IP address for this FQDN is **not** the IP of the compute instance. Instead, use the private IP address of the workspace private endpoint (the IP of the `*.api.azureml.ms` entries.)
154
157
158
+
*`<instance-name>-22.<region>.instances.azureml.cn` - Only used by the `az ml compute connect-ssh` command to connect to computes in a managed virtual network. Not needed if you are not using a managed network or SSH connections.
155
159
*`<managed online endpoint name>.<region>.inference.ml.azure.cn` - Used by managed online endpoints
156
160
157
161
#### Azure US Government
@@ -167,6 +171,8 @@ The following FQDNs are for Azure US Government regions:
167
171
*`<instance-name>.<region>.instances.azureml.us`
168
172
> * The IP address for this FQDN is **not** the IP of the compute instance. Instead, use the private IP address of the workspace private endpoint (the IP of the `*.api.azureml.ms` entries.)
169
173
174
+
*`<instance-name>-22.<region>.instances.azureml.us` - Only used by the `az ml compute connect-ssh` command to connect to computes in a managed virtual network. Not needed if you are not using a managed network or SSH connections.
175
+
170
176
*`<managed online endpoint name>.<region>.inference.ml.azure.us` - Used by managed online endpoints
0 commit comments