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(32, 26%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAJ%3C/text%3E%3C/svg%3E)
Can I configure multiple backend pools in an application gateway. Each backend pool will be in different availability zone. For e.g. if any vm in a particular backend pool (subnet is in AZ1) is serving an application and it fails then the appln gateway should be redirected towards another vm in the second backend pool which is in another availability zone. Is this achievable. Please refer the attached snapshot for more clarification.
Yes, you can but I'm not sure why you would need multiple backend pools here. Is it the same application that you are hosting across your availability zones? If you just use availability zones for your backend VMs then the traffic will only get sent to healthy hosts anyway.
Yes. We are going to host the same application across different availability zones. The secondary VM in the another availability zone will act like a backup VM. We would be creating 2 subnets - one for Primary and other one for Secondary or Backup. Primary subnet/backend pool will be in AZ1 and Secondary subnet/backend pool will be in AZ2.
If these are not active/active and if this is a DR type solution then you might be better to put a service like traffic manager in front of your application. This can monitor the health of the endpoints and redirect the traffic as a failover.
https://learn.microsoft.com/en-us/azure/networking/disaster-recovery-dns-traffic-manager#manual-failover-using-azure-dns
https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-monitoring