Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
Public IP stuck in Failed provisioning state after Basic to Standard SKU upgrade
![](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(256, 21%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Sérgio Raposo
0
Reputation points
Hello,
After upgrading Public IP PIP2 from Basic to Standard SKU,
the resource is stuck in Failed provisioning state.
Current state:
- SKU: Standard
- ProvisioningState: Failed
- IpAddress: Not Assigned
- Allocation: Static
Running Set-AzPublicIpAddress returns InternalServerError.
The IP needs to be reassociated with VPN Gateway VNG2.
Active VPN connection (S2SVPN2) is at risk if tunnel drops.
Failed Operation ID: 4bc45a0c-61b8-43e8-adab-c002fdb097f8
Resource ID: /subscriptions/xxxxxxx-bbbbb-uuuuu-333333-
3333333a/resourceGroups/TST/providers/
Microsoft.Network/publicIPAddresses/PIP2
How can I restore the ProvisioningState to Succeeded?
Azure VPN Gateway
Sign in to answer