Can't deallocate/delete public ip

Mirko Toro 20 Reputation points

For lab porpuses, I created a Firewall resource with its allocated public ip and an associated VM.

As an error, I deleted the VM and now I can't deallocate the IP, therefor delete it and the firewall resource.

Powershell commands did not help.

Is there a way support can do this for me without paying a support account?

Thank you.

Azure Firewall
Azure Firewall
An Azure network security service that is used to protect Azure Virtual Network resources.
604 questions
{count} votes

Accepted answer
  1. ChaitanyaNaykodi-MSFT 24,391 Reputation points Microsoft Employee


    Thank you for sharing additional details above.

    If the firewall resource is still present, then you can try the AZ CLI command az network firewall ip-config delete command using Azure Cloud Shell. This will delete IP configuration and then you can try deleting the Firewall.

    If the Firewall resource has been deleted and the Public IP is till associated to it, then in order to resolve this issue a support ticket will be required as a support engineer can request the backend team to delete the Public IP.

    If you have a support plan you may file a support ticket, else could you please send an email to with the below details and I will enable a one-time free support ticket for you in this case.

    Subject : Attn Chaitanya

    Thread URL: Link to this thread.

    Subscription ID

    Please let me know once you have done the same.

    Thank you!

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Luca Lionetti 3,136 Reputation points


    Welcome to Microsoft Q&A community forum!

    try this command from cloudshell

    Remove-AzPublicIpAddress -Name $publicIpName -ResourceGroupName $rgName -Force

    Hope this helps



    Please "Accept as Answer" and Upvote if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues

    0 comments No comments