Application gateway failed state

Hi @Van Huy Tuyen,

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

I understand that you're facing an issue where the Application Gateway was stopped successfully, but the start operation failed, leaving it in a Failed provisioning state.

This typically happens when the last write operation on the resource did not complete successfully.

A quick recovery step is to trigger a fresh PUT operation on the gateway by retrieving the current configuration and writing it back. Running the following PowerShell command often helps restore the provisioning state:

Get-AzApplicationGateway -Name "<yourresourcename>" -ResourceGroupName "<yourresourcegroup_name>" | Set-AzApplicationGateway

Refer: Troubleshoot Azure Microsoft.Network failed Provisioning State | Microsoft Learn

If the command does not resolve the failed state, it should return an error code—these codes usually contain detailed clues about the underlying issue, so please share the exact error message if possible.

Additionally, if you are seeing an “Internal error” when attempting to make changes, reviewing the Activity Log and Application Gateway diagnostic logs is recommended, as they provide more specific insights into what caused the provisioning failure.

Kindly let us know if the above helps or you need further assistance on this issue.

If the above information is helpful kindly upvote it. If you have extra questions about this answer, please click "Comment".