Share via

Application Gateway is not working

Purna Durgarao Sugandhapu 40 Reputation points
2026-03-10T07:56:48.5966667+00:00

We are seeing issues with application gatyeway in west us, it is not forwarding the traffic and also not able monitor the backend health. We have tried restarting, we have stopped correctly but when we try to start it is failing to start.

Azure Application Gateway
Azure Application Gateway

An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.

0 comments No comments

Answer accepted by question author
  1. Thanmayi Godithi 8,150 Reputation points Microsoft External Staff Moderator
    2026-03-10T09:27:39.0633333+00:00

    Hi @Purna Durgarao Sugandhapu,

    Thank you for reaching out on the Microsoft Q&A forum.

    Please try starting the Application Gateway using the Azure CLI command below:

    az network application-gateway start -g <MyResourceGroup> -n <MyAppGateway>
    

    Reference: https://learn.microsoft.com/en-us/cli/azure/network/application-gateway?view=azure-cli-latest#az-network-application-gateway-start

    Next, verify the gateway state using Azure PowerShell or Azure CLI and confirm both OperationalState and ProvisioningState. An Application Gateway may fail to start if there are underlying configuration or dependency issues, such as invalid certificate references, deleted public IPs, or blocked management-plane traffic. These issues must be resolved before the gateway can successfully run. https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-faq

    Additionally, please check for any expired or unused SSL certificates associated with listeners, backend HTTP settings, or Key Vault references, and remove or replace them if found, as expired certificates can prevent the Application Gateway from starting successfully.

    Once the gateway starts successfully, you can validate traffic flow by checking Backend Health. If backend pools show Unhealthy or Unknown, review the health probe configuration, confirm the backend ports and paths are correct, and ensure that NSGs, UDRs, and DNS allow connectivity from the Application Gateway subnet to the backend servers. Application Gateway does not forward traffic when backend health is unhealthy or unknown, which is expected behavior. https://learn.microsoft.com/en-us/troubleshoot/azure/application-gateway/application-gateway-backend-health-troubleshooting

    If the gateway still fails to start, please share the requested details via private message so we can investigate further.

    If this answer is helpful, please click Accept Answer and consider upvoting it. If you have additional questions, feel free to add a comment.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Adm2 Joel Munoz 0 Reputation points
    2026-03-10T16:16:49.3366667+00:00

    We have the same problem, we have multiple AKS clusters that connects to Application Gateway to update microservices backend config. + monitor backend health for each pod. We check this error on the Application Gateway > Activity Log tab, that reflects "Create or Update Application Gateway" state "Failed", event initiated by: "ingressapplicationgateway-aks-xxx-xxx-xxx".

    This was working since we've configured and manage Azure Roles for this identity. Has Microsoft applied any changes today at 8AM CET time, regarding these resources? Our temporary solution after CI/CD deployment is to apply an update to Application Gateway with AZ CLI:

    az network application-gateway update --name agw-xxx-xxx-xxx --resource-group "rg-xxx-xxx-xx"

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.