Skip to content

Commit e3db85b

Browse files
committed
Fixing broken file link
1 parent bef386d commit e3db85b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/aks/limit-egress-traffic.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ For information on how to override Azure's default system routes or add aditiona
172172
This section covers three network rules and an application rule you can use to configure on your firewall. You may need to adapt these rules based on your deployment.
173173
174174
* The first network rule allows access to port 9000 via TCP.
175-
* The second network rule allows access to port 1194 and 123 via UDP. If you're deploying to Azure China 21Vianet, see the [Azure China 21Vianet required network rules](/outbound-rules-control-egress.md#azure-china-21vianet-required-network-rules). Both these rules will only allow traffic destined to the Azure Region CIDR in this article, which is East US.
175+
* The second network rule allows access to port 1194 and 123 via UDP. If you're deploying to Azure China 21Vianet, see the [Azure China 21Vianet required network rules](./outbound-rules-control-egress.md#azure-china-21vianet-required-network-rules). Both these rules will only allow traffic destined to the Azure Region CIDR in this article, which is East US.
176176
* The third network rule opens port 123 to `ntp.ubuntu.com` FQDN via UDP. Adding an FQDN as a network rule is one of the specific features of Azure Firewall, so you'll need to adapt it when using your own options.
177177
* The application rule covers all needed FQDNs accessible through TCP port 443 and port 80.
178178

0 commit comments

Comments
 (0)