Application Proxy - multiple datacenters

Brass Contributor

I'm trying to understand how Azure Application Proxy would route the traffic.
I have multiple physical sites with some applications deployed within those datacenters. The locations all can talk to each other through IPSEC VPN tunnels between firewalls.
Let's say Location1 has couple web applications that I want to publish through Azure Enterprise Applications portal.

Currently, users in Location1 access Application1 using link -

Application2 -


Same happens for users in other locations, they are routed over IPSEC tunnel to the corresponding location, where application hosted.

I deploy multiple multiple dedicated VMs with Azure Application Proxy in each location to accommodate the traffic. As recommend by Microsoft - at least 2 proxies per application group.

Assuming other applications (Application4, Application5, etc) deployed in a similar manner across multiple locations -
How best this deployment should be implemented?

What happens for users in Location1, when they trying to lunch application that hosted in the same datacenter they belong to through Azure Enterprise Applications portal?
What is the traffic pattern here? Are they constantly connected to Azure Application Proxy service, that in turn communicates through Service Bus with corresponding Azure Application Proxy agent for that Application1 deployed with-in the same location where Application1 is deployed.

Do we have traffic goes back and forth?

Thank you.

3 Replies


The closest from Microsoft I was able to find:

"Conditional Access requirements:
We do not recommend using Application Proxy for intranet access because this adds latency that will impact users. We recommend using Application Proxy with preauthentication and Conditional Access policies for remote access from the internet. An approach to provide Conditional Access for intranet use is to modernize applications so they can directly authenticate with AAD."

But if that is the case I loose the obvious benefits of having application published through Enterprise Applications portal. I need to move the users away from the applications to get the benefit.


So, the bottom line:

1. Use same FQDN for the application for both type of access either internally or externally. Naming, links, etc.
2. Want benefit from Enterprise portal? Would have to suffer some performance degradation on up and down traffic on the same pipe.