I just wonder if this has been resolved yet. Do we have any updates regarding the issue?
We plan to migrate during the weekend. However, it has been postponed for three weeks already. FYI, it didn't work on Sunday, 2 June, either.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I'm trying to help a customer plan a platform upgrade, is there any kind of ETA as to when the migration API will be available again?
I just wonder if this has been resolved yet. Do we have any updates regarding the issue?
We plan to migrate during the weekend. However, it has been postponed for three weeks already. FYI, it didn't work on Sunday, 2 June, either.
I was creating a ticket with Microsoft, and it shows up that the Migration Stv1 to Stv2 of Non VNet Injected APIM can be restored by June 8.
Update for everyone following this:
Although not yet attempted to use, noticed that on the 22/05/24 the Azure Banner was removed from with the Portal that was blocking the Migration.
Assume this means issues have now been resolved?
Hello, As of today 27/05/2024, I still getting the same error message.
any update here?
{
"error": {
"code": "NotSupported",
"message": "The Migration API is temporarily disabled due to internal issues. Please visit https://aka.ms/apim-migrate-stv2 to see other migration options.",
"details": null,
"innerError": null
}
}
I tried to migrated the non vnet injected APIM today i.e., 05/28/2024 and got this error - "Self-serve migration for services that are not added to a virtual network is temporary Disabled. This is done to allow time to fix a new detected issue that could cause downtime. We are currently ecpecting the functionality to be restored by May31. We apologize for the inconvinience"
Strange to see how the "expecting" and "inconvenience" are misspelled by the product team, and the dead line keeps extending.