Share via

How to fix failed basic ip "provisioningState": "Failed"

Joe Holloway 0 Reputation points
2025-12-12T18:52:21.28+00:00

While performing the Virtual Network Gateway migration for basic to standard public ip. The migration failed and the basic IP associated provisioning state went to failed. Now all my connections have gone down for vpn and the ip is un pingable.

Azure VPN Gateway
Azure VPN Gateway

An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.


2 answers

Sort by: Most helpful
  1. Ravi Varma Mudduluru 12,370 Reputation points Microsoft External Staff Moderator
    2025-12-12T19:00:51.2266667+00:00

    Hello @ Joe Holloway,

    Thanks for reaching out to Microsoft Q&A

    The backend team has cleared the struck operation. Please attempt to abort the operation now and proceed with migrating the virtual network gateway.

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

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2025-12-12T18:52:28.3833333+00:00

    To fix the failed provisioning state of the basic public IP associated with your Virtual Network Gateway migration, you should first ensure that all resources involved in the migration are in a succeeded state. If any resources are in a failed state, the migration cannot proceed successfully.

    Here are the steps you can take:

    1. Check Resource States: Verify that all related resources, such as the Virtual Network Gateway, connections, and public IPs, are in a succeeded state. If any are in a failed state, you will need to address those issues first.
    2. Restore the Provisioning State: You can restore the succeeded provisioning state by running a write (PUT) operation on the resource. This can be done using Azure PowerShell. For example, you can use the following command:
         Get-AzPublicIpAddress -Name "your_resource_name" -ResourceGroupName "your_resource_group_name" | Set-AzPublicIpAddress
      
      Make sure to replace your_resource_name and your_resource_group_name with the actual names of your resources.
    3. Retry the Migration: Once all resources are in a succeeded state, you can attempt the migration process again.

    If you continue to face issues, consider checking the Azure documentation for further troubleshooting steps or submitting a support request to Azure support.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.