Azure DevOps Data migration Importer broken on Azure ServiceTags json file download?

Question

I think Microsoft broke the import functionality when migrating Azure DevOps from on-premises to cloud services. We successfully went through al the steps and prepared everything for the import to start, but when we actually start the import it states the following error: Validating import specification file… [Info @15:32:51.340] Validation completed successfully. [Info @15:32:51.340] Validating import source and target regions… [Info @15:34:05.503] Validation completed with an unknown error, see the logs for more details. [Warning@15:34:05.507] System.Net.WebException: The remote server returned an error: (404) Not Found. at System.Net.HttpWebRequest.GetResponse() at Microsoft.VisualStudio.Services.DataImport.Extensions.AzureRegionIpAddressService.<>c.

Answer 1

Hi @Fabian Biesheuvel,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.

Issue:

I think Microsoft broke the import functionality when migrating Azure DevOps from on-premises to cloud services. We successfully went through al the steps and prepared everything for the import to start, but when we actually start the import it states the following error: Validating import specification file… [Info @15:32:51.340] Validation completed successfully. [Info @15:32:51.340] Validating import source and target regions… [Info @15:34:05.503] Validation completed with an unknown error, see the logs for more details. [Warning@15:34:05.507] System.Net.WebException: The remote server returned an error: (404) Not Found. at System.Net.HttpWebRequest.GetResponse() at Microsoft.VisualStudio.Services.DataImport.Extensions.AzureRegionIpAddressService.<>c.

Solution:

We have been in contact with Microsoft and they admitted they have been shutting down and endpoint that was queried by the importer tool, and they have bringing it back online, and now the importer process is starting again. Thank you!

If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

Hope this helps. Do let us know if you have any further queries.

---

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.

Answer 2

We have been in contact with Microsoft and they admitted they have been shutting down and endpoint that was queried by the importer tool, and they have bringing it back online, and now the importer process is starting again. Thank you!