I'm planning to deploy two internal-only web servers in Azure across different regions. Given that Azure Load Balancer and Application Gateway seem to support intra-region traffic only for private ips, how can I effectively balance internal traffic between these servers ?

Cross-Region Load balance r, only supports public Load Balancers. I would recommend using Azure Application Gateway, you can use this internally, and as long as the Application Gateway has visibility into the second region (i.e. peered VNET) you can specify it as a backend. Keep in mind that Application Gateway is a regional service though, so if the region goes down, the Application Gateway may fail. Reference: Decision tree for load balancing in Azure If you need something more globally available, then you could utilise Azure Front Door , and only allow traffic from your company's IP address. Refer: Configure an IP restriction rule with a WAF for Azure Front Door

Load balancing internal traffic cross region

Accepted answer

Luke Murray 11,076 Reputation points MVP

2023-09-25T01:20:03.54+00:00
Cross-Region Load balancer, only supports public Load Balancers.

I would recommend using Azure Application Gateway, you can use this internally, and as long as the Application Gateway has visibility into the second region (i.e. peered VNET) you can specify it as a backend.

Keep in mind that Application Gateway is a regional service though, so if the region goes down, the Application Gateway may fail.

Reference: Decision tree for load balancing in Azure

If you need something more globally available, then you could utilise Azure Front Door, and only allow traffic from your company's IP address.

Refer: Configure an IP restriction rule with a WAF for Azure Front Door
Please sign in to rate this answer.

1 person found this answer helpful.
Luke 45 Reputation points

2023-09-25T01:29:25.45+00:00

Thanks @Luke Murray I was playing around with this earlier, when creating an app gateway with a Standard V2 Tier and try set the front-end IP to Private I get

"Application Gateways with a tier of Standard_v2 don’t support only private IP addresses as the frontend. Supported SKU tiers are standard and WAF."

"So I try with Standard, starts deploying then Application Gateway SKU tier Standard has been deprecated, supported SKU tiers are Standard_v2,WAF_v2."

Ok so I try WAF, same thing, depreciated.

Then try WAF_V2 and get

"Application Gateways with a tier of WAF_v2 don’t support only private IP addresses as the frontend. Supported SKU tiers are standard and WAF."

Luke 45 Reputation points

2023-09-25T01:33:42.8166667+00:00

sorted it, you need to select a public and private IP to deploy, you don't actually need to have it public facing though. Thanks Again Luke

Luke Murray 11,076 Reputation points MVP

2023-09-25T01:41:26.49+00:00

Glad you got it sorted!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Load balancing internal traffic cross region

0 additional answers

Your answer