Link a connector to a different Application Proxy service region.
We have AAD Application Proxy Connectors installed in both Australia and Singapore however the Azure AD tenant in Australia so all traffic has to loop via the Australian Application Proxy Service.
This is a problem for our Indonesian users. We setup servers and AADAP connectors in Azure Singapore with the expectation it would provide low latency to Indonesia but that is not the case.
Please allow us to associate a Connector Group with a specific region so that the connectors and applications linked to the connector group are routed via the expected Application Proxy service region.
We are currently developing a solution to allow you to assign a region to applications outside the region of your home tenant. By doing this, connector groups will talk to the App Proxy region specified. Please continue to share your scenarios to make sure we are taking into account these cases.
We will update once we have a better idea for a release date.
Send a note to email@example.com if you have questions or want to send feedback directly to us.
Different applications in different regions. Users in multiple regions.
Had to use a Netscaler reverse proxy in the second region, latency was intolerable when both the user and the application were in the second region.
Jonathan Pitre commented
I have a client in Montreal and I get a latency between 76-80 ms. It would be nice if you could add servers in Eastern Canada! thank you!
Chris Hill commented
Our Azure tenant is in Europe but we have essential infrastructure in Australia. We need to be able to get a proxy in the Australia region to avoid these latency issues
We have a similar issue with our tenant in the US and our app proxy end point is in Sweden.
Sascha Wenninger commented
For historical reasons, our AAD tenant is located in Australia but we are a global company with users in more than 50 countries. Our core SAP systems are running in the US, but the App Proxy endpoint remains in Australia and cannot be moved. This means all users outside Australia (where the HQ is) suffer a latency penalty when accessing the SAP systems via App Proxy.
Ideally we would be able to create a second App Proxy endpoint in the US, and publish the SAP apps from there.
Paul Shadwell commented
We have an application in Switzerland that we want to give access to for users in China, so would be great if we could configure an App Proxy there for those users.
Likewise, we have users in UK, Australia and Dubai performance degredades massively based on the location of the proxies in the connector groups.
This recently scruppered our use of AADAP too. We're in Europe. We have Infra in Australia.