Skip to content

Commit e32549a

Browse files
committed
Update per feedback
1 parent 4c14009 commit e32549a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/logic-apps/business-continuity-disaster-recovery-guidance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ These examples show the active-active setup where both logic app instances activ
114114

115115
* A "physical" load balancer, such as a piece of hardware that routes traffic
116116

117-
* A "soft" load balancer such as [Azure Load Balancer](../load-balancer/load-balancer-overview.md), [Azure API Management](../api-management/api-management-key-concepts.md), or a service that supports state tracking such as [Azure Service Bus](../service-bus-messaging/service-bus-messaging-overview.md). With API Management, you can specify policies that determine how to load balance incoming traffic.
117+
* A "soft" load balancer such as [Azure Load Balancer](../load-balancer/load-balancer-overview.md) or [Azure API Management](../api-management/api-management-key-concepts.md). With API Management, you can specify policies that determine how to load balance incoming traffic. Or, you can use a service that supports state tracking, for example, [Azure Service Bus](../service-bus-messaging/service-bus-messaging-overview.md).
118118

119119
Although this example primarily shows Azure Load Balancer, you can use the option that best suits your scenario's needs:
120120

0 commit comments

Comments
 (0)