TFS 2018
Find answers to frequently asked questions when migrating to Azure DevOps Services from on-premises.
Why is my production import taking longer than the corresponding dry-run import of the same organization?
During a production import, additional provisioning steps are undertaken to cement the organization into the Azure DevOps Services hosted environment. In contrast, the dry-run import of the same organization typically completes faster since dry-run organizations are temporary and thus do not require these additional steps.
Why is my dry-run import taking longer than previous dry-run imports of the same organization?
Any dry-run import after the first is expected to take longer given the extra time required to clean up resources from previous dry-run attempts.
How long after deleting or renaming an existing dry-run organization will the name become available so another import can be queued?
It can take up to one hour for an organization name to become available after deleting or renaming.
Does use of the Hosted XML process model pose a future risk in use of Azure DevOps Services?
No. When it comes to service updates, Hosted XML organizations are treated the same as organizations using the Inheritance process model.
Will my organization be stuck in Hosted XML forever?
No. You are using the Hosted XML process because the Inheritance process model doesn't contain all features yet. However, you can now clone a hosted XML process to an Inheritance process.
Will migrating from Hosted XML into Inheritance process model be a manual process?
No. The migration is automated. Follow the steps to clone a hosted XML process to an Inheritance process.
What happens in Hosted XML when Microsoft makes a change to a system process?
This is the same experience with Azure DevOps Server. If we make a change to a system process, it isn't applied to any of your Hosted XML processes. You won't have to update your processes if you don't want to. But if you do, you'll need to make the changes in the XML definition files manually for each process.
Is there a difference between a project that was created manually versus one that was created from data import?
The features available to each project are the same. The differences occur in how you modify the processes in your organization. When you create an organization, you'll use the Inheritance process model to customize the work tracking experience. Team projects migrated via data import, however, will use the Hosted XML process model to customize the work tracking experience. As described previously, you can clone a Hosted XML process to an Inheritance process model after import.
If my organization is using Hosted XML, can I create new projects to use the Inheritance process model?
Yes. For data import organizations, Azure DevOps Services supports team projects that use Inheritance as well as Hosted XML process models. To learn more about the Inheritance process, see Manage processes.