我使用 TFS 服务器多年。我们将在下个月转向 Azure DevOps。
在阅读了一些文档后，我得到了一些问题:
- 为什么我们调用组织索要网址而不是帐户？
- 为什么 Azure DevOps 只有一个集合(默认集合)，与 TFS 服务器不同？
- 如果一个组织对应一个集合，当我们将TFS迁移到Azure DevOps时，是否需要为多个集合创建多个组织？
最佳答案
这是历史遗留的问题，一些旧的文档/博客可能没有及时更新。
例如，在文档中:
要随时登录您的 Azure DevOps 帐户，请访问https://{youraccount}.visualstudio.com。
…应该变成:
要随时登录您的 AzureDevOps 组织，请访问https://{yourorganization}.visualstudio.com
此更改通过我们的 Sprint 137 Update 推出:
Adopt the word "organization" when referring to a collection of projects in Azure DevOps
We've made a change to our terminology when it comes to referring to a collection of projects in Azure DevOPS.
Previously we used the term "account" but have found that this has caused a lot of confusion for the broader developer and open source community. We've chosen to replace the term "account" with "organization". You'll start seeing this change roll out in documentation and in-product with this Update.
您的帐户可以在多个组织中创建或添加，例如:
至于将TFS迁移到Azure DevOps，是否创建多个组织，这取决于您公司的需求。如果您使用TFS 数据库导入服务
，我们建议您这样做It provides a high fidelity way to migrate collection databases from Team Foundation Server (TFS) to Azure DevOps Services. It's recommended that you download the migration guide if you're looking to use this service to import your collection(s).
The guide serves as a walk through of the different steps involved in an import. Providing best practices, checklists, and helpful tips to make your import as easy as possible. The guide should be used in conjunction with the more technical documentation referenced below to successfully import to Azure DevOps Services.
关于tfs - Azure DevOps 中的帐户和组织、集合之间的主要区别是什么？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/55176560/