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.
"It is stable, and we have had no issues with it."
"It's very user-friendly, and the documentation is good. The most valuable feature is backlog item creation, where we pick features and other things. The burndown chart created for projects to be maintained by the development teams is also useful."
"The tool's most efficient feature is the integration of its services in one place. It is an easy-to-use product that improves productivity. Microsoft Azure DevOps is also user-friendly. Its documentation is clear and can be found on Google."
"It's a great product for the CI/CD process."
"I really like the Microsoft DevOps survey."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"Provides us with user histories."
"Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace."
"We use TFS for forecast management."
"It is very user-friendly."
"For what I need TFS for, I have never run into any limitation."
"Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part."
"The most valuable feature of TFS is that it keeps the code secure while working collaboratively in a team of four or five individuals."
"As far as queries are concerned, creating, grading, or customizing the queries as a primary requirement is very easy to do."
"The interface is good with TFS."
"The most valuable feature of TFS is integration."
"In comparison to JIRA, I believe DevOps has very poor reporting and metrics support."
"Azure DevOps is set up more for development and less for testing. If it is set up correctly, everyone can use it better, but it was set up from a development point of view, which means it is lacking in what I need from a testing perspective. Just like any other tool, it depends on how it is configured. I am not happy with the way it is set up. It is configured more from a development side, and it doesn't necessarily cater to all the other areas that probably need to use it, such as testing data, etc."
"Reporting across multiple projects could be improved."
"The communication could work better, especially for the development team."
"It is essential that you get buy-in from the top management down to everyone in the pipeline."
"I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix."
"Its UI can be easier and more customer-friendly. The UI can be improved from the project management and agile perspective."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"The dashboard needs more enhancements."
"The dashboard and the customization of dashboards is an area they have to work on."
"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."
"I would like to see the reporting features expanded so that I can see details on the users connected to all of the projects."
"The tool needs improvement in stability."
"The user interface could improve and test management was not useful in TFS."
"The test management interface is not very handy."
"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."
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 127 reviews while TFS is ranked 3rd in Application Lifecycle Management (ALM) Suites with 93 reviews. Microsoft Azure DevOps is rated 8.2, while TFS is rated 8.0. The top reviewer of Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". 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 GitLab, Jira, Rally Software, ServiceNow Strategic Portfolio Management and OpenText ALM / Quality Center, whereas TFS is most compared with Jira, Rally Software, TestRail, OpenText ALM / Quality Center and Visual Studio Test Professional. 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.