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(249.60000000000002, 20%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOM%3C/text%3E%3C/svg%3E)
Hello,
I was not able to delete the public IP address rapp-stage-gw-public-feip because it keeps showing error message of being associated with the default load balancer created by default by Azure appgwLoadBalancer when it was assigned to the Application Gateway and can not even access that default load balancer created because Azure portal mention that I have no access even though I do.
Can you please force remove this public IP address: 4.205.35.188 named rapp-stage-gw-public-feip from your end though not sure if this issue is caused by internal bug?
This public IP address was previously assigned to Application Gateway and I successfully deleted it from the Gateway Listener configuration but for some reason it is still associated with the default appgwLoadBalancer
Please advise
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
Hi ,
Thanks for reaching out to Microsoft Q&A.
This is not an Azure backend bug; it is a dependency lock issue. Even if you removed the public IP from the Application gateway listener, the underlying auto-created appgwLoadBalancer still holds a reference until the gateway resource is fully updated/deleted. You cannot force delete it directly. Fix is: stop the Application gateway (or delete it temporarily), then check the public IP’s “Configuration -> Associated resources” via Azure CLI (az network public-ip show --name rapp-stage-gw-public-feip --resource-group <rg> --query ipConfiguration.id) to confirm linkage. If it still points to the hidden load balancer, run az network application-gateway stop or fully delete the gateway, wait for backend cleanup (2 to 5 mins), then delete the public IP. If access issues persist, it is likely RBAC on the hidden resource group (MC_*), so ensure you have Network Contributor or Owner at subscription level.
Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.
![](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 **Omar Mohamed,
**Thank you for contacting us about the unable to delete Public IP address: rapp-stage-gw-public-feip issue. We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this.
Hello,
Thank you for your quick reply however the provided instructions didn't help and after stopping the Application Gateway, the issue still persist.
I don't understand, if this is not a bug with Azure, then why do users have to go to the extreme measure of nuking fully configured Application Gateway just to delete external public IP and why in the first place Azure do not show appgwLoadBalancer to users even though they do have access?
I do have both RBAC subscription owner role and contributor roles on that resource so it is not permission issue and it was working before with these roles
The only thing that worked so far, is just trick the Application Gateway by creating another public IP address and assign it to Frontend IP configuration that way it forces Azure to release the default application load balancer and eventually delete the stale IP address.
There should be a better way to handle this!
Hi Omar,
Thank you for sharing the workaround you used.
In Azure, a Public IP can only be deleted once it is fully disassociated from any IP configuration (for example, a load balancer / Application Gateway frontend reference). In some scenarios, even after stopping/removing the Application Gateway, the platform can still show a stale backend association, which blocks deletion.
Your approach of assigning a new Public IP to the Application Gateway frontend effectively forces the backend reference to refresh and releases the stale association that’s why it worked.
Reference:
https://learn.microsoft.com/en-us/answers/questions/472761/unable-to-delete-public-ip-resource