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.
"Azure DevOps is effective for repository management and code collaboration. We can create branches, differentiate between code versions, save and review code later, get PR approvals, and more. All these features are valuable."
"It's a complete solution that has everything you need."
"It is good for monitoring purposes. We are using the build pipelines of Microsoft Azure. They are also valuable."
"Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development."
"Azure Pipeline and Azure Release are most valuable. I use Azure DevOps through pipeline and release."
"It's a great product for the CI/CD process."
"It's a pretty problem-free solution."
"Most developers and project managers choose the Microsoft tools to begin with because of familiarity, and these new tools are almost an extension of the tools you're already familiar with. There's a lot of knowledge transfer, which helps, rather than bringing in a new product line."
"Stability is okay."
"TFS' most valuable feature is the triage process. It is a robust solution that is easy to use."
"Basically, the capacity to construct various products is something I find handy."
"The interface is good with TFS."
"It is easy to push our changes from quality to pre-prod and prod."
"The most valuable feature is simplicity."
"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."
"The interface is easy to navigate."
"I'd like to have something better for the test plan."
"All of the tests of the applications are done on the mobile or web interface and it could be improved."
"I would like to see better interoperability with the agile scaling frameworks."
"The test management section needs to be improved."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved."
"It is essential that you get buy-in from the top management down to everyone in the pipeline."
"The price could be lowered. It would be nice if it was cheaper."
"TFS should allow more integration with different platforms."
"Merging branches is definitely one of the more challenging aspects for people new to TFS."
"Its pricing could be improved."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
"I'd like to see some kind of visualization tool for TFS that would make life much easier."
"As an end-user, I expect the solution's performance to be faster while staying as stable as possible."
"The solution should have better dashboards."
"TFS and MTM have their own style of working and they are different from other tools like Jira or TestRail, which are simpler and easy to use."
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.