We reviewed Microsoft Azure DevOps vs TFS according to our users’ review in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison results: Microsoft Azure DevOps is a more advanced solution than TFS. Regardless of the higher cost, it offers stronger capabilities, evolving features, and better support.
"Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements."
"This platform provides a large span of tools and technologies."
"I found the Kanban board to be the most useful for my needs."
"I like the tracking and that we can monitor our velocity."
"The initial setup is very easy."
"In Microsoft Azure DevOps, you have a one shop to get everything."
"The most valuable feature of this solution is that it saves time."
"One of the main features is the user interface is very good."
"The interface is good with TFS."
"The most valuable feature from my point of view is project management, which includes user stories as well as task management."
"It's user friendly. We haven't had any issues so far. It's flexible. If we need something, we can always contact the owner in our headquarters to make a configuration."
"Some of the valuable features are version control and the ability to create different collections in terms of segregating the authorization for teams who connect to small projects."
"The most valuable features of TFS are the test plans. We can reproduce reusable test plans in test automation. We have a lot of queries and this feature is very useful."
"It's is a very stable solution."
"TFS's best features include user-friendly test management, bug reporting, and ID assignment."
"The most valuable feature is integration, particularly if you have a .NET application."
"Testing is very important. Microsoft Azure DevOps tests very well. However, DevOps teams need to be aware of what they are impacting when someone updates anything on the system."
"I can't think of anything I would like to improve, since I don't have complete knowledge of the platform yet. I'm sure that as I gain more experience, I will understand it better. The price could maybe be cheaper, but I'm sure I'll have more ideas as to improvements and additional features once I've used it more."
"They have brought a lot of new collaboration features in the latest version. We haven't used those features, but they should continue to expand it more on the collaboration front so that two developers can look at the code and work at the same time. It will be helpful for working from home."
"The active directory password system needs some improvement because many times the password for the active directory expires before the set time."
"With the query feature, we have to group items, so it becomes difficult for everyone to understand it. It's easier in JIRA, which has filters and other query options."
"The solution should have fewer updates."
"There are some areas that need improvement such as tracking."
"Not all companies use the same methodology which could limit the use of this solution."
"It has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies."
"The user interface could be improved to make it simpler and increase usability."
"Overall, I think it would be useful to have something similar where Microsoft comes up with supporting concepts of scaling Agile in TFS so that clients don't have to look for a separate tool."
"I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code."
"The project management side should be addressed and the project and release planning should be somewhat extended."
"There are many things that I cannot do, and I have a lot of bugs."
"There's not automatic access to test case management and execution."
"The solution should have better dashboards."
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 84 reviews while TFS is ranked 5th in Application Lifecycle Management (ALM) Suites with 22 reviews. Microsoft Azure DevOps is rated 8.0, while TFS is rated 7.8. The top reviewer of Microsoft Azure DevOps writes "Robust functionality, good integration, continually enhanced, and easy to scale". On the other hand, the top reviewer of TFS writes "It is helpful for scheduled releases and enforcing rules, but it should be better at merging changes for multiple developers and retaining the historical information". Microsoft Azure DevOps is most compared with Jira, GitLab, ServiceNow Strategic Portfolio Management, Red Hat Ansible Automation Platform and Rally Software, whereas TFS is most compared with Jira, Rally Software, Visual Studio Test Professional, Micro Focus ALM Quality Center and Zephyr Enterprise. See our Microsoft Azure DevOps vs. TFS report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very friendly user interface. I think TFS does have a few valuable features, though, such as its project management, which happens to not only include user stories, but task management as well. It would be good if TFS offered better integration for third-party tools like Jira. For my needs specifically, for example, I need to do a lot of manual tasks, and integration with SharePoint is not easy. Other than that, I consider the product to be pretty solid, stable, and also scalable, and haven’t experienced too many issues with it.
In contrast to TFS, Azure DevOps provides a seamless user experience that is not only consistent across Azure DevOps service, but is consistent across Azure DevOps server too. It also has great navigation and the user interface is responsive, helping employees focus better on their work. Azure also allows users to connect GitHub Enterprise with Azure Boards, with no disruption to other workflows.
While both Azure DevOps and TFS require SQL Server, Azure DevOps server can be hosted on virtual machines running on Azure. In turn, these support Azure SQL Databases give users superior backup and scaling options - and do so all without increased administrative costs that are usually tacked on to running such complex services. I also like that Azure DevOps has advanced search capabilities. For example, certain features allow information from different components of the product to be accessible from whichever parts users are working on. You can also expand the search box from the product header, which I find useful and a great addition to help improve navigation.
Conclusion:
Azure DevOps is a better match for me than TFS because it has several new features and more additional benefits than TFS can offer for my needs.
Hi @Netanya Carmi,
Both are good and in fact, TFS is now rebranded as Azure DevOps server.
Now the point is about your requirement, if your requirement is to work closely with Cloud Services Cloud Application and you are Ok to manage your code and CI/CD plans over the cloud platform then go for Azure DevOps whereas if you can't move the data to cloud use Azure DevOps Server.
But for such tools my first choice is Gitlab.
Rest you can call me at 9717996125 or drop me at kulbhushan.mayer@thinknyx.com to discuss further.
Both, it depends on what you want to do with it and what is your technical environment.