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(243.2, 16%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGT%3C/text%3E%3C/svg%3E)
Hi All,
I am reaching out to see if there is any issue with my AGW setup.
The settings are all configured and i was able to test the health probe manually, however there is nothing shown in the Backend Health tab. I am currently a contributor for this AGW
But if i go to the backend health there is nothing
![](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(83.2, 52%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
Hi Gerald Tan,
Thanks for reaching out in Microsoft Q&A,
Can you check the backend health status using either the Azure CLI or a PowerShell command?
Here is the Azure CLI command:
az network application-gateway show-backend-health -g MyResourceGroup -n MyAppGateway
PowerShell command:
Get-AzApplicationGatewayBackendHealth -Name ApplicationGateway01 -ResourceGroupName ResourceGroup01
If that returns valid “Healthy” statuses, your AGW is fine the UI is just not showing it.
Hi Venkatsean,
For some reason the output shows as "servers": [] as blank
Any idea what causes that? On a different AGW that i set up previously it does show the servers with the address, health and healthprobe log
After many rounds of trying, it seems like adding Rules is breaking the AGW for me
"The resource operation completed with terminal provisioning state 'Failed'."
Hi Gerald Tan,
The resource operation completed with terminal provisioning state 'Failed'" **
When adding or updating Rules in your Application Gateway (AGW) is a strong indicator that there’s a configuration dependency mismatch between your listeners, HTTP settings, backend pools, or probes.
Try running:
Get-AzApplicationGateway -Name <your-agw-name> -ResourceGroupName <your-rg-name> | Set-AzApplicationGateway
This can reset the AGW provisioning state and force a config "recommit".
Hi Gerald Tan,
We haven't heard back from you regarding our last response and wanted to check if you had the opportunity to review our previous post.
We eventually come to a conclusion that i had to use "azure dns" instead of the custom dns which made no sense. It seemed to work once the vnet was switched back to use Azure DNS.
we will try again when we can to use the Custom DNS