You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/workloads/high-availability-guide-standard-load-balancer-outbound-connections.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ This document outlines different options to configure explicit outbound internet
23
23
24
24
## Overview
25
25
26
-
When VMs without public IP addresses are placed in the backend pool of an internal Standard Azure Load Balancer, they have no outbound internet connectivity by default. But now the behavior applies to all VMs in new virtual networks, including standalone VMs not associated with any load balancer.
26
+
When VMs without public IP addresses are placed in the backend pool of an internal Standard Azure Load Balancer, they have no outbound internet connectivity by default. Now the behavior applies to all VMs in new virtual networks, including standalone VMs not associated with any load balancer.
27
27
28
28
A VM can reach public endpoints if it has a directly assigned public IP address. The same applies when the VM is part of a load balancer backend pool that has a public IP address.
29
29
@@ -35,7 +35,7 @@ SAP systems typically handle sensitive business data, making it rarely acceptabl
35
35
- Using package repositories for patching the operating system.
36
36
- SAP application data flow requires outbound connectivity to external APIs or partner systems.
37
37
38
-
Some SAP deployments don't need to reach public endpoints or accept traffic from the internet. In these cases, an internal Azure Standard Load Balancer for high availability, or a standalone VM without a public IP is sufficient. No extra networking setup is required.
38
+
Some SAP deployments don't require outbound connectivity. In these cases, an internal Azure Standard Load Balancer for high availability, or a standalone VM without a public IP is sufficient. No extra networking setup is required.
39
39
40
40
> [!NOTE]
41
41
> When VMs without public IP addresses are added to the back-end pool of an internal Standard Azure Load Balancer, they lack outbound internet connectivity. Further configuration is needed to enable routing to public endpoints.
@@ -94,9 +94,9 @@ For step-by-step instructions on creating and configuring an Azure NAT Gateway,
94
94
95
95
# [Azure Standard Load Balancer](#tab/azure-standard-lb)
96
96
97
-
Create another external Azure Standard Load Balancer for outbound connections to internet.
97
+
Create external Azure Standard Load Balancer for outbound connections to internet.
98
98
99
-
To achieve outbound connectivity to public end points, without allowing inbound connectivity to the VM from a public end point, is to create a second load balancer with a public IP address. Then you add the VMs to the backend pool of the second load balancer where only [outbound rules](../../load-balancer/load-balancer-outbound-connections.md#outboundrules) are defined. Use [Network Security Groups](../../virtual-network/network-security-groups-overview.md) to control the public end points that are accessible for outbound calls from the VM. For more information, see Scenario 2 in [Outbound connections](../../load-balancer/load-balancer-outbound-connections.md#scenarios).
99
+
To achieve outbound connectivity to public end points, without allowing inbound connectivity to the VM from a public end point, create a load balancer with a public IP address. Then you add the VMs to the backend pool of the load balancer where only [outbound rules](../../load-balancer/load-balancer-outbound-connections.md#outboundrules) are defined. Use [Network Security Groups](../../virtual-network/network-security-groups-overview.md) to control the public end points that are accessible for outbound calls from the VM. For more information, see Scenario 2 in [Outbound connections](../../load-balancer/load-balancer-outbound-connections.md#scenarios).
100
100
101
101
The configuration would look like:
102
102
@@ -139,7 +139,7 @@ Create the Load Balancer.
139
139
140
140
The outbound security rules would look like:
141
141
142
-

142
+

143
143
144
144
For more information on Azure NSG, see [Security Groups](../../virtual-network/network-security-groups-overview.md).
0 commit comments