Unable to migrate APIM stv1 to stv2 on Australia East, 3 days before 31st August 2024

Question

I am attempting to migrate our stv1 UAT instance of APIM from Australia East to stv2.

I am getting the following error:

Failed to migrate

Invalid parameter: This Migration API option is not supported or is temporarily disabled due to internal issues. Please visit https://aka.ms/apim-migrate-stv2 to see other migration options.

I have a vnet assigned instance of APIM, I don't understand why this cannot start. This migration process for our SIT environment and DEV environment worked fine 1 day ago.

Given we are 3 days away from 31st August 2024, the day we no longer get support. What will microsoft do about this?

Our organisation has a Production environment too that needs to be upgraded.

Answer 1

@Victor W Thanks for your patience! Customers attempting to migrate their VNET injected stv1 service cannot use the "Keep the same subnet as stv1" option. They will get the following error message:

Invalid parameter: This Migration API option is not supported or is temporarily disabled due to internal issues. Please visit https://aka.ms/apim-migrate-stv2 to see other migration options.

This option has been disabled since issues have been identified with this option that cause migration failures and service outage. Engineering team is investigating the issues, and this option will be enabled once the issues have been addressed. 

ETA for Fix

• Same subnet, new IP migration is expected to be enabled by 29th August
• Same subnet, Preserve IP option is expected to be enabled by September 4th

Workaround: Customers should choose the "Change to a new subnet" option to migrate their service to stv2. This option will change the IP Addresses associated with service.

do let me know incase of further queries, I would be happy to assist you.