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.
"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 solution is easy to implement and easy to use."
"The solution is scalable."
"All features are good. Pipelines feature is great, and Boards and Artifacts features are also really good. It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It is very easy. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated."
"The extensibility of the work item forms and customizations as well as the backend API to query the data, et cetera, and manipulate the data programmatically are all very valuable aspects of the product."
"Azure Port is considered the most valuable feature."
"The work items option is incredibly flexible."
"The installation is straightforward. We can create a whole new organization in less than a day."
"The most valuable feature is simplicity."
"This solution enables us to link all items usefully, in the way we use Agile."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"Stability is okay."
"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 initial setup is fairly easy."
"The most valuable feature from my point of view is project management, which includes user stories as well as task management."
"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."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."
"It should be easier to manage Licenses especially because it's in the cloud."
"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."
"Azure has not yet advanced to the performance level of the other major competitors and is missing integration with important technologies."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix."
"As for improvement, the first one is pricing. For us, luckily because we are partners, it's free. Microsoft gold partners do not have to pay, but if you're not a partner, the product is very expensive."
"I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress."
"TFS on-premise does not support integration with SharePoint Online."
"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 only use 1% of the functionality, so I am not familiar enough to know what needs to be improved."
"The user interface could be improved to make it simpler and increase usability."
"This solution is quite old and it is already being bundled as Azure DevOps Server."
"The overall reports in TFS could improve. Additionally, there should be an easier way to migrate from an older version to a newer one."
"Integration from Visual Studio could be improved."
Microsoft Azure DevOps is ranked 1st in Application Lifecycle Management (ALM) Suites with 123 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 "Good support, helpful management capabilities, and great Kanban boards". 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.