Skip to content

Commit 6ca4f2d

Browse files
Tweak
1 parent 31f5d99 commit 6ca4f2d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/load-balancer/load-balancer-custom-probe-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ If all probes for all instances in a backend pool fail, existing UDP flows will
178178

179179
## <a name="probesource"></a>Probe source IP address
180180

181-
All Load Balancer health probes originate from the IP address 168.63.129.16 as their source. When you bring your own IP addresses to Azure's Virtual Network, this health probe source IP address is guaranteed to be unique as it is globally reserved for Microsoft. This address is the same in all regions and does not change. It should not be considered a security risk because only the internal Azure platform can source a packet from this IP address.
181+
Load Balancer uses a distributed probing services on which the health model is based. Each host where VMs reside can be programmed to generate health probes per the customer's configuration. All Load Balancer health probes originate from the IP address 168.63.129.16 as their source. When you bring your own IP addresses to Azure's Virtual Network, this health probe source IP address is guaranteed to be unique as it is globally reserved for Microsoft. This address is the same in all regions and does not change. It should not be considered a security risk because only the internal Azure platform can source a packet from this IP address.
182182

183183
In addition to Load Balancer health probes, the following operations use this IP address:
184184

0 commit comments

Comments
 (0)