This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 65%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJO%3C/text%3E%3C/svg%3E)
Hi folks,
I've created 2 azure application gateways that share the same frontend private IP (by mistake however it works!).
Both gateways have listeners on different domain addresses, but since the frontend IP is the same I am just wondering how the requests end up in the right gateway.
Could someone please clarify? :)
Thanks in advance
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 59%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
@José Oliveira ,
Welcome to Microsoft Q&A forum.
Can you please provide more information on your set-up here? Are the two Application Gateways connected to the same subnet in a virtual network?
I have two gateways, one private and another public. Both are living in the same network and subnet.
The gateways were deployed in parallel using terraform. I could not reproduce the issue when deploying the gateways using Microsoft Biceps or ARM templates, I get an error during de preflight validations.
both gateways have listeners on different "interfaces", the public one is listening for requests coming from the public IP, and the private one is listening for requests coming from the internal network.
It looks like it works just because both gateways are listening on different IP address types (public/private)