Skip to content

Commit 99c8b0c

Browse files
authored
Update how-to-registry-network-isolation.md
Adding Note for private AML registry DNS resolution
1 parent a103c7b commit 99c8b0c

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/machine-learning/how-to-registry-network-isolation.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -204,6 +204,9 @@ For a system registry, we recommend creating a Service Endpoint Policy for the S
204204
205205
## How to find the registry's fully qualified domain name
206206
207+
> [!NOTE]
208+
> Make sure your DNS is able to resolve the registry private FQDN which is in this format: `<registry-guid>.registry.<region>.privatelink.api.azureml.ms` as there is no public resource specific FQDN which is recursively resolved by Azure DNS.
209+
207210
The following examples show how to use the discovery URL to get the fully qualified domain name (FQDN) of your registry. When calling the discovery URL, you must provide an Azure access token in the request header. The following examples show how to get an access token and call the discovery URL:
208211
209212
> [!TIP]

0 commit comments

Comments
 (0)