Skip to content

Commit e93c2ac

Browse files
authored
Update how-to-network-isolation-planning.md
1 parent 1d29965 commit e93c2ac

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ In this diagram, you have a hub and spoke network architecture. The spoke VNet h
4040
4141
### DNS resolution of private link resources and application on compute instance
4242

43-
If you have your own DNS server hosted in Azure or on-premises, you need to create a conditional forwarder in your DNS server. The conditional forwarder sends DNS requests to the Azure DNS for all private link enabled PaaS services. For more information, see the [DNS configuration scenarios](../private-link/private-endpoint-dns.md#dns-configuration-scenarios) and [Azure Machine Learning specific DNS configuration](how-to-custom-dns.md) articles.
43+
If you have your own DNS server hosted in Azure or on-premises, you need to create a conditional forwarder in your DNS server. The conditional forwarder sends DNS requests to the Azure DNS for all private link enabled PaaS services. For more information, see the [DNS configuration scenarios](/azure/private-link/private-endpoint-dns#dns-configuration-scenarios) and [Azure Machine Learning specific DNS configuration](how-to-custom-dns.md) articles.
4444

4545
### Data exfiltration protection
4646

@@ -52,7 +52,7 @@ You can mitigate this data exfiltration risk using [our data exfiltration preven
5252

5353
In this diagram, the compute instance and cluster need to access Azure Machine Learning managed storage accounts to get set-up scripts. Instead of opening the outbound to storage, you can use service endpoint policy with Azure Machine Learning alias to allow the storage access only to Azure Machine Learning storage accounts.
5454

55-
The following tables list the required outbound [Azure Service Tags](../virtual-network/service-tags-overview.md) and fully qualified domain names (FQDN) with data exfiltration protection setting:
55+
The following tables list the required outbound [Azure Service Tags](/azure/virtual-network/service-tags-overview) and fully qualified domain names (FQDN) with data exfiltration protection setting:
5656

5757
| Outbound service tag | Protocol | Port |
5858
| ---- | ---- | ---- |
@@ -121,7 +121,7 @@ You can automate this environments creation using [a template](tutorial-create-s
121121

122122
### Removing firewall requirement
123123

124-
If you want to remove the firewall requirement, you can use network security groups and [Azure virtual network NAT](../virtual-network/nat-gateway/nat-overview.md) to allow internet outbound from your private computing resources.
124+
If you want to remove the firewall requirement, you can use network security groups and [Azure virtual network NAT](/azure/virtual-network/nat-gateway/nat-overview) to allow internet outbound from your private computing resources.
125125

126126
:::image type="content" source="media/how-to-network-isolation-planning/recommended-network-diagram-no-firewall.png" alt-text="Diagram of the recommended network architecture without a firewall.":::
127127

@@ -143,7 +143,7 @@ This diagram shows the recommended architecture to make all resources private an
143143

144144
:::image type="content" source="media/how-to-network-isolation-planning/recommended-network-data-exfiltration.png" alt-text="Diagram of recommended network with data exfiltration protection configuration.":::
145145

146-
The following tables list the required outbound [Azure Service Tags](../virtual-network/service-tags-overview.md) and fully qualified domain names (FQDN) with data exfiltration protection setting:
146+
The following tables list the required outbound [Azure Service Tags](/azure/virtual-network/service-tags-overview) and fully qualified domain names (FQDN) with data exfiltration protection setting:
147147

148148
| Outbound service tag | Protocol | Port |
149149
| ---- | ----- | ---- |
@@ -171,4 +171,4 @@ You can use the public workspace if you're OK with Azure AD authentication and a
171171
* [Secure the inference environment](how-to-secure-inferencing-vnet.md)
172172
* [Enable studio functionality](how-to-enable-studio-virtual-network.md)
173173
* [Configure inbound and outbound network traffic](how-to-access-azureml-behind-firewall.md)
174-
* [Use custom DNS](how-to-custom-dns.md)
174+
* [Use custom DNS](how-to-custom-dns.md)

0 commit comments

Comments
 (0)