Unable to move an azure sql managed instance to another vnet

Tyson L 0

I have two azure sql managed instances in a failover group and I am trying to move the primary instance to a different vnet. I have fulfilled the documented requirements (Bi-directional peering, NSG, Route Table, Open ports for replication, Non-overlapping ip ranges) and the portal allows me to save the new network setting, however the transfer process appears to hang at the first operation step (Request validation). I have allowed it to process for several hours but it never progresses beyond step 1 and never returns an error message.

My question: Is there some other un-documented requirement for moving instances that are part of a failover group? Do I need to manually failover before moving the primary instance?

Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-09-04T08:05:39.9633333+00:00
Hi Tyson L,
Welcome to the Microsoft Q&A platform, thanks for posting the question.

I'm sorry to hear that you are facing issues while moving the primary instance of your Azure SQL Managed Instance to a different VNet. Based on the information you have provided, it seems that you have fulfilled all the documented requirements for moving the instance, including bi-directional peering, NSG, route table, open ports for replication, and non-overlapping IP ranges. However, the transfer process appears to hang at the first operation step (Request validation) and never progresses beyond that.

To answer your question, while there isn’t any mention of an undocumented requirement or the need to manually failover before moving the primary instance, it might be worth considering a manual failover as a troubleshooting step. This could help determine if the issue is with the primary instance or the failover process itself.

In this case, I would recommend that you try the following steps to troubleshoot the issue:

Check the Azure portal notifications to see if there are any error messages related to the move operation. If there are any error messages, they might provide more information about the issue.

Check the Azure Activity Log to see if there are any error messages related to the move operation. The Activity Log provides detailed information about the operations performed on your Azure resources, including move operations.

Check the Azure Resource Health to see if there are any issues with the Azure SQL Managed Instance or the VNet. Resource Health provides information about the health of your Azure resources and any issues that might be affecting them.

Try to move the primary instance using Azure PowerShell or Azure CLI. This will help you to determine if the issue is with the Azure portal or with the transfer process itself. You can follow the steps: Move the instance.

For additional information please refer this document: Move Azure SQL Managed Instance across the virtual networks.

I hope this helps. Please let me know if you have any other questions.
Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-09-05T11:28:21.6233333+00:00

Hi @Tyson L,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-09-06T11:37:52.8766667+00:00

Hi @Tyson L,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Tyson L 0 Reputation points

2024-09-22T12:12:38.9666667+00:00

Hi Mahesh,

I have tried performing a manual failover before moving the instance, however now it hangs at 'Step 3/6: New SQL Instance Startup'. Once again there is no error message or error code. This is really terrible design from Microsoft as it gives no indication of what is going wrong. As far as I can tell I have fulfilled the requirements set out in the documentation. As per your suggestion I have used PowerShell to monitor the progress of the operation but no error message.
Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-09-23T16:23:51.28+00:00

Hi @Tyson L,
Could you please share the documentation link that you have referred. In order to understand the query and guide you in better way.
Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-09-24T17:05:22.8766667+00:00

Hi @Tyson L,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Ketsha 0 Reputation points Microsoft Employee

2024-09-25T18:09:09.92+00:00

I was following the thread, and I see that you have followed recommended steps including manual failover before moving the primary instance, which is a good best practice.

Another important thing is to ensure that the destination subnet is marked as "Ready for Managed Instance" on the Azure portal, which I think you have done since all NSGs and route tables are in place.

Additionally, just sanity check that the inbound and outbound ports and the port range are open in NSG

Also, verify that the Microsoft.Sql resource provider is registered in your subscription. I have seen issue arise if the resource provider is not properly registered.

If none of these works, it might be beneficial to open up a support case with our support/escalation team.
Please sign in to rate this answer.
Mahesh Kurva 245 Reputation points Microsoft Vendor

2024-09-26T21:42:32.55+00:00

Hi @Tyson L,

Just checking in to see if the above answer provided by @Ketsha helped.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Unable to move an azure sql managed instance to another vnet

1 answer

Your answer