...
Configuration | Service level agreement (SLA) | Information |
Availability set | 99.95% | Protection from hardware failures within datacenters |
Availability zone | 99.99% | Protection from entire datacenter failure
|
At least one backend and a health probe must exist before you can create a load balancing rule.
Outbound rules allow instances to use SNAT (source network address translation) to communicate with the internet.
This is only available in the Standard SKU (not the basic one).
Each public IP assigned as a frontend IP of your load balancer is given 64,000 SNAT ports for its backend pool members.
Ports can't be shared with backend pool members.
A range of SNAT ports can only be used by a single backend instance to ensure return packets are routed correctly.
It's recommended you use an explicit outbound rule to configure SNAT port allocation. This rule will maximize the number of SNAT ports each backend instance has available for outbound connections.
Using Source Network Address Translation (SNAT) for outbound connections
Outbound rules enable you to explicitly define SNAT (source network address translation) for a Standard Public Load Balancer.
This configuration allows you to use the public IP or IPs of your load balancer for outbound connectivity of the backend instances.
SNAT prevents outside sources from having a direct address to the backend instances.
...