Troubleshooting VPN Gateway Migration Error to Standard IP Based Deployment

Question

Troubleshooting VPN Gateway Migration Error to Standard IP Based Deployment

Sergii M 15

We attempted to use the migration tool for a Virtual Network Gateway created with Basic IP to migrate to Standard IP has resulted in the following error: "Failed to execute migration to Standard IP Based Deployment. Error: An error occurred," as referenced in this article - Azure VPN Gateway Migration Guide.

The migration was aborted after encountering this error multiple times. Screenshots of the errors are included below:

User's image

What steps can be taken to troubleshoot this issue and successfully proceed with the migration?

Note that we have others VPNs in the same region were we completed migration successfully.

TP 141.8K Reputation points Volunteer Moderator

2025-09-25T21:59:26.0866667+00:00

Hi @Sergii M

What is the VPN Gateway SKU? If you navigate to your VPN Gateway, Overview blade, and click on the Public IP address, is the Public IP address SKU still Basic, or is it Standard?

Is it Active-Passive or Active-Active?
Sergii M 15 Reputation points

2025-09-26T04:14:39.5766667+00:00
Hi Ravi, TP,

My VPN Gateway SKU is VpnGw1 and it uses Basic SKU IP address, thus based on this document I need to migrate it https://free.blessedness.top/en-us/azure/vpn-gateway/whats-new#upcoming-projected-changes

GatewaySubnet has 5 available addresses (3 is required)

I don't have a FastPath enabled and all related resources are in succeeded state.

I'm trying PowerShell migration path and hope it will work. I will let you know.

UPDATE

The PowerShell migration ended in the same error.
TP 141.8K Reputation points Volunteer Moderator

2025-09-26T04:36:56.99+00:00

@Sergii M Thanks. I asked about your public IP's SKU because recently someone else attempted to migrate VpnGw1, got error, however, the public IP was still upgraded to Standard SKU.

Please note the deadline for Basic SKU Public IP when used with VPN Gateway is end of January 2026. I mention this in case you are worried that you have less than a week to get it migrated.
Sergii M 15 Reputation points

2025-09-26T04:59:59.7933333+00:00

TP,

Well, when the migration fails the IP resource shows as Standard SKU but the VPN Gateway has strange overview page where the public is is not shown. Then when I do Abort the IP SKU goes back to basic.

Thank you for update on the timeline, we do have few month, but I just want to be done with this task as this is the last VPN Gateway with basic IP on our Azure infrastructure.
$@chin 270 Reputation points

2025-09-26T13:15:18.9266667+00:00

Hi TP,

I’m experiencing the same issue. I have met all the prerequisites, but I’m still encountering error messages. Is there any workaround, or could this be a backend issue ?
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-09-26T17:07:22.2733333+00:00

Hello @Sergii M,

Could you please check and provide the requested details in the private message?
TP 141.8K Reputation points Volunteer Moderator

2025-09-26T17:37:08.2233333+00:00

@Sergii M I recommend you create Technical support request so a backend engineer can take a look. Some of the migrations have been failing for some reason.

Hopefully Ravi will offer to open a case on your behalf if you don't already have support plan. Otherwise you will need to upgrade to at least Standard so that you can create case in portal.
Sergii M 15 Reputation points

2025-09-26T22:44:01.0866667+00:00

Hi TP, Ravi,

This morning the VPN stopped working and we had to escalate this request to Azure support.

We have connected with them and are working through the issue.
Harry Tzaferi 0 Reputation points

2025-09-28T16:46:31.5+00:00

I'm having the exact issue.

Any has managed to resolve this?
$@chin 270 Reputation points

2025-09-30T09:51:12.4233333+00:00

Hi ,

It seems like there might be a bug. I’m unable to delete the VPN gateway and I’m encountering the same error message.

Has anyone been able to resolve this issue ?
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-09-30T20:27:47.73+00:00

Hello @Harry Tzaferi

Could you post your question along with the error message in the forum below?

https://free.blessedness.top/en-us/answers/questions/ask/

Thanks
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Gupta1, Sachin 0 Reputation points

2025-10-09T17:26:42.09+00:00

Hi,

Just wanted to provide an update. I was initially unable to delete my VPN gateway because my first migration attempt had failed, which also caused the deletion to fail. After raising a case with Microsoft, they unlocked it from the backend, and I was then able to delete the VPN successfully.

Additionally, the migration feature is currently in public preview and, according to Microsoft’s article, is expected to reach general availability by mid-November.

1 answer

Your answer

TP 141.8K Reputation points Volunteer Moderator

2025-09-25T21:59:26.0866667+00:00

Hi @Sergii M

What is the VPN Gateway SKU? If you navigate to your VPN Gateway, Overview blade, and click on the Public IP address, is the Public IP address SKU still Basic, or is it Standard?

Is it Active-Passive or Active-Active?
Sergii M 15 Reputation points

2025-09-26T04:14:39.5766667+00:00

Hi Ravi, TP,

My VPN Gateway SKU is VpnGw1 and it uses Basic SKU IP address, thus based on this document I need to migrate it https://free.blessedness.top/en-us/azure/vpn-gateway/whats-new#upcoming-projected-changes

GatewaySubnet has 5 available addresses (3 is required)

I don't have a FastPath enabled and all related resources are in succeeded state.

I'm trying PowerShell migration path and hope it will work. I will let you know.

UPDATE

The PowerShell migration ended in the same error.
TP 141.8K Reputation points Volunteer Moderator

2025-09-26T04:36:56.99+00:00

@Sergii M Thanks. I asked about your public IP's SKU because recently someone else attempted to migrate VpnGw1, got error, however, the public IP was still upgraded to Standard SKU.

Please note the deadline for Basic SKU Public IP when used with VPN Gateway is end of January 2026. I mention this in case you are worried that you have less than a week to get it migrated.
Sergii M 15 Reputation points

2025-09-26T04:59:59.7933333+00:00

TP,

Well, when the migration fails the IP resource shows as Standard SKU but the VPN Gateway has strange overview page where the public is is not shown. Then when I do Abort the IP SKU goes back to basic.

Thank you for update on the timeline, we do have few month, but I just want to be done with this task as this is the last VPN Gateway with basic IP on our Azure infrastructure.
$@chin 270 Reputation points

2025-09-26T13:15:18.9266667+00:00

Hi TP,

I’m experiencing the same issue. I have met all the prerequisites, but I’m still encountering error messages. Is there any workaround, or could this be a backend issue ?
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-09-26T17:07:22.2733333+00:00

Hello @Sergii M,

Could you please check and provide the requested details in the private message?
TP 141.8K Reputation points Volunteer Moderator

2025-09-26T17:37:08.2233333+00:00

@Sergii M I recommend you create Technical support request so a backend engineer can take a look. Some of the migrations have been failing for some reason.

Hopefully Ravi will offer to open a case on your behalf if you don't already have support plan. Otherwise you will need to upgrade to at least Standard so that you can create case in portal.
Sergii M 15 Reputation points

2025-09-26T22:44:01.0866667+00:00

Hi TP, Ravi,

This morning the VPN stopped working and we had to escalate this request to Azure support.

We have connected with them and are working through the issue.
Harry Tzaferi 0 Reputation points

2025-09-28T16:46:31.5+00:00

I'm having the exact issue.

Any has managed to resolve this?
$@chin 270 Reputation points

2025-09-30T09:51:12.4233333+00:00

Hi ,

It seems like there might be a bug. I’m unable to delete the VPN gateway and I’m encountering the same error message.

Has anyone been able to resolve this issue ?
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-09-30T20:27:47.73+00:00

Hello @Harry Tzaferi

Could you post your question along with the error message in the forum below?

https://free.blessedness.top/en-us/answers/questions/ask/

Thanks
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Gupta1, Sachin 0 Reputation points

2025-10-09T17:26:42.09+00:00

Hi,

Just wanted to provide an update. I was initially unable to delete my VPN gateway because my first migration attempt had failed, which also caused the deletion to fail. After raising a case with Microsoft, they unlocked it from the backend, and I was then able to delete the VPN successfully.

Additionally, the migration feature is currently in public preview and, according to Microsoft’s article, is expected to reach general availability by mid-November.

Answer 1

Ravi Varma Mudduluru 1,790 Microsoft External Staff Moderator

Hello @ Sergii M,

Thanks for reaching out to Microsoft Q&A.

I understand that you’re running into some challenges while migrating your Virtual Network Gateway from a Basic IP to a Standard IP.

The GatewaySubnet was configured with a /28 prefix, which is too small for the migration tool, and high CPU usage during migration caused connection drops and failed resets.

Backend team restored the gateway and connections by updating Key Value Store (KVS) and applying fixes. A fleet upgrade is being rolled out to prevent reboot-related failures in future migrations.

Kindly let us know if the above helps or you need further assistance on this issue.

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

Sergii M 15 Reputation points

2025-10-09T04:32:03.98+00:00

Just wanted to close out this thread for those who might face a similar issue.

As Ravi mentioned, after few attempts to migrate the VPN gateway stopped working at all and we had to contact Azure Support. Once it stopped working we could not do anything with this resource from UI or from CLI.

Azure support team reached out to the Azure engineering team and they were able to restore our VPN Gateway and help us to migrate to Standard IP.

Thus, if you tried to use Migrate to Standard IP process but failed few times then it might be better to recreate VPN Gateway resource(s). In our case the recovery process with Azure support team took us almost 10 hours.

Share via

Troubleshooting VPN Gateway Migration Error to Standard IP Based Deployment

1 answer

Your answer