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.
"The most valuable features of this solution are the CI/CD pipeline, and the testing automation."
"It's graphical representation and tools are easy to use."
"The most valuable feature of this solution is that it saves time."
"The product is easy to use and very stable."
"We can eliminate some of the middleman processes."
"If someone is considering developing and deploying the infrastructure in this solution, then using this tool is perfect because it's fully integrated with the pipelines and with a server core repository."
"The most valuable aspect of Azure DevOps for me is its robust version control functionality, which is critical for our workflow."
"It is a cloud-based system. So, it is stable and scalable."
"It's is a very stable solution."
"I like its MTM (Microsoft Test Manager) section which gives us options to create various test plans and add test cases into it."
"I like the build management features and the integration with Jenkins and many other tools."
"The interface is easy to navigate."
"It is easy to push our changes from quality to pre-prod and prod."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"The most valuable features are related to source code management. Using TFS for source code management and being able to branch and have multiple developers work on the same projects is valuable. We can also branch and merge code back together."
"I have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well."
"The portfolio is one area where DevOps has room for improvement. Built-in reporting and visualization also could be better. We're using Power BI and Tableau to compile more complex reports and dashboards. Azure DevOps has some out-of-the-box reporting capabilities, but they're very simple. It's usually okay on the team level, but if you have to run a complex report, it's difficult and insufficient, so we use Power BI as an extension."
"If they could build up requirement traceability metrics, then it would be great."
"Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult."
"We would like some bidirectional synchronization. It's the requirement if you want to analyze it to software requirements, et cetera. That's something that most of the tools aren't that good at."
"I think that the integration is to some extent, immature."
"There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps."
"There is room for improvement on the UI side, especially with merge requests. If we compare Azure DevOps to GitLab when it comes to branches and PRs (pull requests), GitLab has a better interface."
"Its price can also be reduced. It would be great if they are a little bit more competitive in terms of pricing because many open-source products are currently available in the market."
"The usability of TFS is not that great."
"Integration from Visual Studio could be improved."
"The program and portfolio planning facility can be improved."
"TFS should allow more integration with different platforms."
"The solution is stable but could improve."
"The execution of test cases could stand improvement."
"The tool needs improvement in stability."
"More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively."
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 126 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, Visual Studio Test Professional, OpenText ALM / Quality Center and TestRail. 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.