Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
Cannot migrate Basic public ip to Standard sku for VPN Gateway
![](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, 40%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERV%3C/text%3E%3C/svg%3E)
R V
0
Reputation points
Hello,
We are currently using a public IP that is associated with our VPN Gateway. This IP is still using the Basic SKU, and as per Microsoft documentation, it needs to be upgraded to the Standard SKU. However, when attempting to perform the manual upgrade, I am encountering an error.
Unfortunately, I cannot identify the cause of the error based on the available logs and messages. I would like to request assistance in resolving this issue. Specifically, I am seeking guidance on how to manually upgrade the public IP without affecting the VPN Gateway or causing any disruptions to our current setup.
Could you please provide instructions on how to successfully upgrade the public IP from Basic to Standard, or if there is an underlying issue preventing the upgrade?
Thank you in advance for your support.
Azure Virtual Network
{count} votes
-
![](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(304, 22%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETG%3C/text%3E%3C/svg%3E)
Thanmayi Godithi 2,460 Reputation points Microsoft External Staff Moderator2025-12-15T09:55:41.1466667+00:00 Hi @R V,
Thank you for reaching out on Microsoft Q&A forum.
Could you please confirm your VPN Gateway SKU?
According to Microsoft’s official “Upcoming projected changes” guidance, the Basic → Standard migration tooling is still rolling out region‑by‑region and SKU‑by‑SKU. During this rollout, some gateways will show the migration UI but the backend will not yet allow the actual Prepare operation — which results in the exact “Gateway operation failed with deployment failure” message you are seeing.
Here is the official migration timeline from Microsoft Learn:
If the backend has not yet enabled migration for your gateway type/region, the Prepare step will fail even if validation passes. This is expected.
The good news is that Microsoft will automatically migrate gateways using Basic Public IPs before the retirement deadline, and no manual action is required if the migration tool is not yet fully supported. You can retry again later as the rollout continues.
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".
Sign in to comment
Sign in to answer