Skip to content

Commit dbdcd42

Browse files
committed
updating doc to apply better to both Azure ML and AI Studio
1 parent 7a5f2ee commit dbdcd42

File tree

1 file changed

+4
-36
lines changed

1 file changed

+4
-36
lines changed

articles/machine-learning/how-to-custom-dns.md

Lines changed: 4 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -8,42 +8,26 @@ ms.subservice: enterprise-readiness
88
ms.reviewer: larryfr
99
ms.author: jhirono
1010
author: jhirono
11-
ms.date: 01/08/2024
11+
ms.date: 06/05/2024
1212
ms.topic: how-to
1313
monikerRange: 'azureml-api-2 || azureml-api-1'
1414
---
1515

1616
# How to use your workspace with a custom DNS server
1717

18-
When using an Azure Machine Learning workspace with a private endpoint, there are [several ways to handle DNS name resolution](../private-link/private-endpoint-dns.md). By default, Azure automatically handles name resolution for your workspace and private endpoint. If you instead __use your own custom DNS server__, you must manually create DNS entries or use conditional forwarders for the workspace.
18+
When using an Azure Machine Learning workspace (including Azure AI hubs) with a private endpoint, there are [several ways to handle DNS name resolution](../private-link/private-endpoint-dns.md). By default, Azure automatically handles name resolution for your workspace and private endpoint. If you instead __use your own custom DNS server__, you must manually create DNS entries or use conditional forwarders for the workspace.
1919

2020
> [!IMPORTANT]
2121
> This article covers how to find the fully qualified domain names (FQDN) and IP addresses for these entries if you would like to manually register DNS records in your DNS solution. Additionally this article provides architecture recommendations for how to configure your custom DNS solution to automatically resolve FQDNs to the correct IP addresses. This article does NOT provide information on configuring the DNS records for these items. Consult the documentation for your DNS software for information on how to add records.
2222
23-
> [!TIP]
24-
> This article is part of a series on securing an Azure Machine Learning workflow. See the other articles in this series:
25-
>
26-
> * [Virtual network overview](how-to-network-security-overview.md)
27-
:::moniker range="azureml-api-2"
28-
> * [Secure the workspace resources](how-to-secure-workspace-vnet.md)
29-
> * [Secure the training environment](how-to-secure-training-vnet.md)
30-
> * [Secure the inference environment](how-to-secure-inferencing-vnet.md)
31-
:::moniker-end
32-
:::moniker range="azureml-api-1"
33-
> * [Secure the workspace resources](./v1/how-to-secure-workspace-vnet.md)
34-
> * [Secure the training environment](./v1/how-to-secure-training-vnet.md)
35-
> * [Secure the inference environment](./v1/how-to-secure-inferencing-vnet.md)
36-
:::moniker-end
37-
> * [Enable studio functionality](how-to-enable-studio-virtual-network.md)
38-
> * [Use a firewall](how-to-access-azureml-behind-firewall.md)
3923
## Prerequisites
4024

4125
- An Azure Virtual Network that uses [your own DNS server](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server).
4226

4327
:::moniker range="azureml-api-2"
4428
- An Azure Machine Learning workspace with a private endpoint, including hub workspaces such as those used by Azure AI Studio. For more information, see [Create an Azure Machine Learning workspace](how-to-manage-workspace.md).
4529

46-
- If your workspace resources are secured with an __Azure Virtual network__, familiarity with the [Network isolation during training & inference](./how-to-network-security-overview.md) article.
30+
- If your workspace dependency resources are secured with an __Azure Virtual network__, familiarity with the [Network isolation during training & inference](./how-to-network-security-overview.md) article.
4731
:::moniker-end
4832
:::moniker range="azureml-api-1"
4933
- An Azure Machine Learning workspace with a private endpoint. For more information, see [Create an Azure Machine Learning workspace](./v1/how-to-manage-workspace.md).
@@ -692,22 +676,6 @@ If after running through the above steps you are unable to access the workspace
692676
- Conditional forwarders from DNS Server to Azure DNS Virtual Server IP were not configured correctly
693677
- Conditional forwarders from On-premises DNS Server to DNS Server were not configured correctly
694678

695-
## Next steps
696-
697-
This article is part of a series on securing an Azure Machine Learning workflow. See the other articles in this series:
698-
699-
* [Virtual network overview](how-to-network-security-overview.md)
700-
:::moniker range="azureml-api-2"
701-
* [Secure the workspace resources](how-to-secure-workspace-vnet.md)
702-
* [Secure the training environment](how-to-secure-training-vnet.md)
703-
* [Secure the inference environment](how-to-secure-inferencing-vnet.md)
704-
:::moniker-end
705-
:::moniker range="azureml-api-1"
706-
* [Secure the workspace resources](./v1/how-to-secure-workspace-vnet.md)
707-
* [Secure the training environment](./v1/how-to-secure-training-vnet.md)
708-
* [Secure the inference environment](./v1/how-to-secure-inferencing-vnet.md)
709-
:::moniker-end
710-
* [Enable studio functionality](how-to-enable-studio-virtual-network.md)
711-
* [Use a firewall](how-to-access-azureml-behind-firewall.md)
679+
## Related content
712680

713681
For information on integrating Private Endpoints into your DNS configuration, see [Azure Private Endpoint DNS configuration](../private-link/private-endpoint-dns.md).

0 commit comments

Comments
 (0)