Skip to content

Commit 74093a2

Browse files
authored
Merge pull request #204302 from thisisanniefang/patch-29
Add note on IP-based pseudovip known issue
2 parents 2d6936e + 958a11f commit 74093a2

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/virtual-network/ip-services/default-outbound-access.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,9 @@ There are multiple ways to turn off default outbound access:
6666

6767
* Flexible scale sets are secure by default. Any instances created via Flexible scale sets won't have the default outbound access IP associated to it. For more information, see [Flexible orchestration mode for virtual machine scale sets](../../virtual-machines/flexible-virtual-machine-scale-sets.md)
6868

69+
>[!Important]
70+
> When a backend pool is configured by IP address, it will use default outbound access due to an ongoing known issue. For secure by default configuration and applications with demanding outbound needs, associate a NAT gateway to the VMs in your load balancer's backend pool to secure traffic. See more on existing [known issues](../../load-balancer/whats-new.md#known-issues).
71+
6972
## If I need outbound access, what is the recommended way?
7073

7174
NAT gateway is the recommended approach to have explicit outbound connectivity. A firewall can also be used to provide this access.

0 commit comments

Comments
 (0)