Skip to content

Commit cc28505

Browse files
committed
vnets1
1 parent dff396f commit cc28505

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/hdinsight/hdinsight-plan-virtual-network-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -232,7 +232,7 @@ For more information on controlling outbound traffic from HDInsight clusters, se
232232
233233
Forced tunneling is a user-defined routing configuration where all traffic from a subnet is forced to a specific network or location, such as your on-premises network or Firewall. Forced tunneling of all data transfer back to on-premise is _not_ recommended due to large volumes of data transfer and potential performance impact.
234234
235-
Customers who are interested to setup forced tunneling, should use [custom metastores](https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-use-external-metadata-stores) and setup the approperiate connectivity from the cluster subnet or on-premise network to these custom metastores.
235+
Customers who are interested to setup forced tunneling, should use [custom metastores](./hdinsight-use-external-metadata-stores.md) and setup the approperiate connectivity from the cluster subnet or on-premise network to these custom metastores.
236236
237237
To see an example of the UDR setup with Azure Firewall, see [Configure outbound network traffic restriction for Azure HDInsight clusters](hdinsight-restrict-outbound-traffic.md).
238238

0 commit comments

Comments
 (0)