How can I manage the Virtual Network of an Azure PostgresSQL Flexible server after changing the DB's subscription?

Question

I'm trying to move my cloud resources into a new Subscription. I was able to successfully move an Azure Database for PostgresSQL to a new subscription, however the attached virtual network cannot be changed.
Per MSFT documentation, the attached virtual network cannot be changed after provisioning.

Trying to move the virtual network results in a validation error that says "One or more Postgres Flexible Servers are provisioned in the ProductionWeb virtual network, VNET move is not allowed."
It seems odd that I can move the DB instance to a new subscription but the virtual network can't be changed and is stuck in the original subscription.

Is there anything I can do to remedy this?
Thank you!

Answer 1

@Steve Christy Thank you for being patient while working on this issue.

You can use the migration service and use VM as a source and enter the flexible server credentials. It has worked for many customers.

OR

Move PostgreSQL Flexible server from source to target subscription (which did not move VNET to target subscription as expected). Then do PITR of the server to move to the target subscription and use VNET from the target subscription during restore.

Regards,

Oury